How asimons81/hermes-gpt works
hermes-gpt is a local-first MCP sidecar that exposes selected Hermes Agent capabilities to trusted clients. The principal workflow is a client request reaching the MCP server, passing through an Operator tool surface, and returning a result; mission tools add planning, budget and capability views, recovery decisions, and gated execution. The repository also provides a browser Flight Deck, chat/session access, OAuth, and Fabric/Fleet features. The README documents these capabilities, but most implementation excerpts were not sampled, so uncertain internal call wiring is omitted.
Main entry points: operator_policy.py Operator tools · operator_controller.py Mission controller · server.py MCP server · operator_contract.py Work contracts
Components 25
Client entry
- MCP server
server.py - Operator tools
operator_policy.py
Mission operations
- Mission lifecycle
operator_mission.py - Mission plans
operator_mission_plan.py - Mission ledger
operator_mission_ledger.py - Budget envelope
operator_mission_budget.py - Capability index
operator_capability_manifest.py - Placement scoring
operator_placement.py - Recovery decisions
operator_failure_semantics.py - Mission controller
operator_controller.py - Work contracts
operator_contract.py - Delegation authority
operator_delegations.py
Fabric and fleet
- Fabric routing
operator_fabric_router.py - Fleet operations
operator_fleet.py - Swarm workflows
operator_swarm_workflows.py
Identity and sessions
- OAuth access
operator_oauth.py - Token store
token_store.py - Sessions and chat
operator_session.py
Flight Deck
- Flight Deck app
web/src/App.tsx - Web API client
web/src/api/client.ts - UI API routes
ui_api.py - Mission views
ui_missions.py
Other components
- MCP clients
- Hermes Agent
- Browser user
Connections 26
- MCP clients → MCP server: send requests
- MCP server → Operator tools: serves tools
- Operator tools → Mission lifecycle: exposes operations
- Operator tools → Mission plans: exposes operations
- Operator tools → Mission ledger: exposes queries
- Operator tools → Budget envelope: exposes checks
- Operator tools → Capability index: exposes queries
- Operator tools → Placement scoring: exposes scoring
- Operator tools → Recovery decisions: exposes decisions
- Operator tools → Mission controller: exposes controls
- Operator tools → Fabric routing: exposes routing
- Operator tools → Fleet operations: exposes operations
- Operator tools → Swarm workflows: exposes workflows
- Operator tools → OAuth access: exposes auth
- Operator tools → Sessions and chat: exposes chat
- Mission controller → Work contracts: dispatches through
- Mission controller → Delegation authority: checks authority
- Mission controller → Budget envelope: uses budget gate
- Work contracts → Fabric routing: routes work
- MCP server → Hermes Agent: integrates with
- OAuth access → Token store: stores tokens
- Browser user → Flight Deck app: uses
- Flight Deck app → Web API client: requests data
- Web API client → UI API routes: calls endpoints
- UI API routes → Mission views: serves mission views
- Mission views → Mission lifecycle: reads mission data