docs(handoff): mirror HERMES_AGENT_ENABLE.md from HermesProof - #44
Conversation
How to activate the Hermes Agent USER bridge on this side. The bridge itself lives in HermesProof (PR #20); Hermes3D consumes it via the HermesProof MCP server. Mirror exists so users find activation instructions from either repo. Lists all 62 supported provider classes (DeepSeek + MiniMax + SiliconFlow + Anthropic + Cohere + 57 others), both routing modes (local_private and hybrid), per-client setup for Claude Code / Codex CLI / KiloCode / Cursor / Windsurf / VSCode+Copilot. Task ID: H3D-V5.3-HERMES-AGENT-ENABLE Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Review rate limit: 0/5 reviews remaining, refill in 5 minutes and 42 seconds. Comment |
There was a problem hiding this comment.
Code Review
This pull request introduces a new documentation file, HERMES_AGENT_ENABLE.md, which provides comprehensive instructions for enabling and configuring the Hermes Agent across various MCP clients like Claude Code, Codex, and Cursor. The documentation covers environment setup, provider routing, and security auditing. The review feedback suggests improving the documentation's portability by replacing environment-specific absolute paths with generic placeholders and correcting a version typo for the DeepSeek provider.
| ## TL;DR — fastest path | ||
|
|
||
| ```bash | ||
| # 1. Put your API keys in G:\private\.env (NEVER inside any repo) |
There was a problem hiding this comment.
The absolute path G:\private\.env is specific to a local environment. Using a placeholder or a generic path would make the documentation more portable for other developers.
| # 1. Put your API keys in G:\private\.env (NEVER inside any repo) | |
| # 1. Put your API keys in a secure .env file (e.g., ~/.hermes/.env) (NEVER inside any repo) |
|
|
||
| | # | Provider | env var | endpoint | | ||
| |---|---|---|---| | ||
| | 1 | DeepSeek (v4) | `DEEPSEEK_API_KEY` | api.deepseek.com | |
| "mcpServers": { | ||
| "hermes3d-locks": { | ||
| "command": "node", | ||
| "args": ["G:/Github/hermes3d-mcp-lock-orchestrator/src/server.mjs"], |
There was a problem hiding this comment.
The absolute path to the MCP server script is environment-specific. It should be replaced with a placeholder (e.g., /path/to/...) to guide users on where to point the command. This also applies to lines 163 and 181.
| "args": ["G:/Github/hermes3d-mcp-lock-orchestrator/src/server.mjs"], | |
| "args": ["/path/to/hermes3d-mcp-lock-orchestrator/src/server.mjs"], |
Task ID: H3D-V5.3-HERMES-AGENT-ENABLE
Summary
Mirrors the Hermes Agent activation guide from HermesProof PR #20 so users find the docs from either repo.
The bridge itself lives in HermesProof (`src/core/hermes-agent-bridge.mjs`); Hermes3D consumes it via the HermesProof MCP server (`hermes3d-locks` server name).
Documents:
Test plan
🤖 Generated with Claude Code