Skip to content

G3: hermes-native fileIssue MCP tool (parent: devagentic#203) #57

@PowerCreek

Description

@PowerCreek

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions