Parent: TechDevGroup/devagentic#203.
Gap
No hermes-native tool for surfacing stack gaps as GitHub issues. Per NousResearch#203 §3.2, a worker hitting a stack gap should call fileIssue(repo, title, body) — that tool does not exist today, so workers cannot follow the contract.
What is needed
Add an MCP tool:
fileIssue(repo: \"devagentic\"|\"hermes-agent\", title: str, body: str, labels?: list[str])
- Opens an issue on
TechDevGroup/<repo>.
- Returns issue number + URL so the worker can cite it in its CLAUDE.md / follow-up notes.
Acceptance
- Tool registered under
mcp_serve.py.
- Unit test mocking the gh API.
- Docs: this is the ONLY path for workers to report stack gaps. Workers never edit stack source.
Notes
- Auth: worker container should not hold gh credentials directly — tool routes through a hermes-side helper using the operator's token. Decide whether token lives in hermes-host env or a dedicated sidecar.
Parent: TechDevGroup/devagentic#203.
Gap
No hermes-native tool for surfacing stack gaps as GitHub issues. Per NousResearch#203 §3.2, a worker hitting a stack gap should call
fileIssue(repo, title, body)— that tool does not exist today, so workers cannot follow the contract.What is needed
Add an MCP tool:
fileIssue(repo: \"devagentic\"|\"hermes-agent\", title: str, body: str, labels?: list[str])TechDevGroup/<repo>.Acceptance
mcp_serve.py.Notes