Draft
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
platform_toolsetsfor the active supported handles instead of relying on upstream gateway fallback defaultsFIRECRAWL_API_KEYandFIRECRAWL_API_URLthrough to the generated Hermes.envWhy
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:
web_search/web_extractavailability checks could fail even when the service environment provided themconfig.yamldid not setplatform_toolsets, so Clawdapus was depending on upstream default fallback behavior instead of compiling the intended tool surface explicitlyImpact
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/hermesRefs #156