TheBlueHouse75/hermes-action-bridge

A configurable bridge that lets external agents delegate real-world actions to Hermes Agent without reimplementing Hermes skills, tools, platform integrations, browser automation, cron jobs, or messaging flows.
Use it from Claude Code, Codex, Cursor, CI jobs, shell scripts, or another
MCP-capable client. MCP execution requires interactive form elicitation and
fails closed in non-interactive clients; plan, draft, dry-run, and direct CLI
workflows remain available to automation.
Why this exists
Coding agents are good at understanding a repository. They should not duplicate your automation stack.
If an agent needs to do something outside its local coding session — research, schedule a job, open a browser workflow, send a message, prepare a social post, use a Hermes skill, or coordinate with a messaging gateway — it can delegate that request to Hermes through this bridge.
Features
- Generic hermes-action run command for one-shot delegation.
- Configurable presets for skills, toolsets, provider/model, source, and max turns.
- Deterministic, language-agnostic safety policy: downgrades execute to request-approval by default, with per-preset trust overrides.
- Explicit --yolo mode for users who intentionally want to bypass bridge-level policy.
- Context file injection with a per-file cap and a configurable aggregate budget (clear error instead of a cryptic E2BIG).
- Automatic large-context delivery: an oversized prompt is handed to Hermes through a secure temp file instead of overflowing the command line.
- Per-run timeouts (configurable, with per-mode defaults) that always reap the Hermes child process.
- Dry-run mode for debugging the exact Hermes command, prompt, and computed prompt size.
- Complete Codex and Claude Code installer: managed skill plus verified global MCP registration.
- MCP capability discovery, cancellable asynchronous jobs, and one-shot two-phase approvals gated on interactive form elicitation, with a privacy-preserving local audit log.
- Local stdio transport plus an opt-in, authenticated Streamable HTTP transport for Tailscale-restricted hosts.
- No project-specific assumptions. All behavior is configured through YAML and CLI flags.
Requirements
- Node.js 20 or newer.
- Hermes Agent installed and available as hermes, or configured with a custom command path.
Check Hermes:
Installation
Install from npm:
Install the skill and MCP registration for Codex and Claude Code, then verify
the complete setup:
Global installation is all-or-nothing for the requested agents. If Codex or
Claude Code is unavailable, conflicting, or cannot verify its user-scoped
stdio MCP entry, the command exits non-zero without installing the requested
skills. Use --project for an explicit skill-only setup.
Other distribution channels
Choose the channel that matches the agent surface. Hermes Agent must always be
installed and configured on the same computer as the local bridge.
| Channel | What it configures | Install |
| --- | --- | --- |
| npm installer | Skill and verified user-scoped MCP for Codex CLI/app and Claude Code | hermes-action install all |
| Claude Code marketplace | Claude plugin with the Skill and a version-pinned MCP server | claude plugin marketplace add TheBlueHouse75/hermes-action-bridge, then claude plugin install hermes-action@hermes-action-bridge |
| Claude Desktop | Self-contained MCPB extension for the bridge runtime | From the latest GitHub Release, download hermes-action-bridge- .mcpb and open it with Claude Desktop |
| Agent Skills | Portable instructions for supported coding agents | npx skills add TheBlueHouse75/hermes-action-bridge --skill hermes-action-bridge |
| Smithery Skill | Public portable instructions in the Smithery Skill catalog | Check the latest release notes for the verified Skill listing or its pending status |
| Smithery MCPB | The same local MCPB bundle through the Smithery catalog | Check the latest release notes for the verified MCPB listing or its pending status |
The standalone Agent Skill only teaches an agent when and how to delegate; it