Skip to content

[codex] fix Hermes native tool exposure#157

Draft
mostlydev wants to merge 2 commits intomasterfrom
issue-156-hermes-native-tools
Draft

[codex] fix Hermes native tool exposure#157
mostlydev wants to merge 2 commits intomasterfrom
issue-156-hermes-native-tools

Conversation

@mostlydev
Copy link
Copy Markdown
Owner

Summary

  • compile explicit Hermes platform_toolsets for the active supported handles instead of relying on upstream gateway fallback defaults
  • pass FIRECRAWL_API_KEY and FIRECRAWL_API_URL through to the generated Hermes .env
  • add regression coverage for generated config and env output

Why

Hermes upstream already exposes native web, terminal, and file tools for Discord/Slack/Telegram presets, but the Clawdapus Hermes driver was still leaving part of that tool surface implicit.

Two concrete problems showed up in source inspection:

  • the driver did not pass Firecrawl env through to Hermes, so upstream web_search / web_extract availability checks could fail even when the service environment provided them
  • the generated Hermes config.yaml did not set platform_toolsets, so Clawdapus was depending on upstream default fallback behavior instead of compiling the intended tool surface explicitly

Impact

Hermes pods managed by Clawdapus now expose the intended native tool presets more reliably, especially the native web-search path.

Validation

  • go test ./internal/driver/hermes

Refs #156

Document that the project board now has Item closed, Pull request merged,
and Auto-close issue workflows enabled, and that PR bodies must include
Closes/Fixes/Resolves keywords for the linkage to fire — branch names
alone are not enough.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant