Files
computer-playbook/roles/web-app-hermes/TODO.md
kevinveenbirkenbachandClaude Opus 5 250ced9bcd feat(hermes): configure the discovered MCP servers as agent clients
Hermes registers MCP servers in config.yaml under HERMES_HOME, which the
image pins to the data volume. Render the discovered servers there and
reference each bearer as ${env:<ROLE>_MCP_TOKEN} so the config carries no
secret into the swarm config store. A per-server 'hermes mcp test' then
refuses a deploy whose agent cannot reach a server it was configured
against.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-07-31 00:16:46 +02:00

493 B

TODO

  • Default model: the gateway serves /v1 without a configured model.default; agent turns need hermes config set model.default ollama/<alias> against the LiteLLM-backed provider. Bake it via a config template once a turn-level e2e assertion exists.
  • SSO: the API server authenticates with API_SERVER_KEY only; services.sso is dropped because an oauth2 proxy in front of the bearer API breaks OpenAI-compatible clients. Revisit if a browser dashboard surface appears upstream.