Add 1clawAI/1claw-hermes to Integrations & Bridges#141
Open
redbotster wants to merge 1 commit into
Open
Conversation
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
1 participant
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.
As offered in #112 — opening the PR.
Adds 1claw-hermes to Integrations & Bridges.
What it is: TypeScript integration bringing 1Claw to Hermes — MCP-based secret fetching from an HSM-backed vault, a Shroud TEE LLM-proxy sidecar (redacts secrets/PII + blocks prompt injection before prompts reach the model provider), per-subagent identities, and the Intents API for keyless on-chain signing.
Why it fits: Hermes extends via a native MCP client; 1Claw exposes its vault/secrets and signing as MCP tools, so Hermes agents get just-in-time, scoped, revocable credentials without keys ever touching the agent context. Actively maintained under the 1clawAI org.
Closes #112.