Skip to content

Integration

Hermes Agent

Use Hermes Agent with your OpenCode Console workspace's models, policies, MCP servers and Library.

npx @opencode/console setup hermes

What it does

One command adds the OpenCode Console plugin to a Hermes Agent profile on your computer and connects it to a workspace. You keep using hermes, its TUI and desktop app, the messaging gateway and cron as before, with these changes:

  • /model lists the workspace's models, including ones from other providers, and new sessions start on the newest Claude Sonnet the workspace offers. Requests go through Console, so the workspace's model rules and budgets apply.
  • Every tool call, and every skill a /name command loads, is checked against the workspace's policies before it runs.
  • The workspace's MCP servers are added, with OpenCode Web Search when the workspace offers it.
  • The workspace's Library skills are added, so you can run each one as /name. Its Library instructions are added to the profile's SOUL.md.

Hermes checks Console for changes when a session starts, and at most once a minute while you use it. Setup leaves the rest of config.yaml as you wrote it.

Requirements

  • An OpenCode Console workspace you're a member of.
  • Hermes Agent 0.22.6 or later.
  • Node.js 22 or later, for npx.

Setting up

  1. Run this in a terminal:
    npx @opencode/console setup hermes
  2. Your browser opens Console. Check that the code matches the one in your terminal, approve the sign-in and pick the workspace.
  3. Setup prints the models, policies, MCP servers and Library items it set up. If the Hermes gateway is running, restart it with hermes gateway restart so it loads the plugin. Then run hermes.

Setup connects the profile in HERMES_HOME, or the active profile if it isn't set. To connect another, add --profile <name>. Run the command again any time to update the setup.

Keeping your own provider

To keep the providers and models you set up in Hermes, such as Nous Portal or OpenRouter, and still get the workspace's policies, MCP servers and Library, run:

npx @opencode/console setup hermes --keep-provider

If the workspace offers no models, Hermes keeps its own providers the same way. Run setup without --keep-provider to use the workspace's models again.

Checking the connection

To see who you're signed in as, the workspace, and how many policies and models it has, run:

npx @opencode/console status

Removing

To undo setup, run this, with the same --profile if you used one:

npx @opencode/console setup hermes --remove

It puts back the model you used before, unless you changed it since, and removes the plugin, the workspace's provider, MCP servers, skills and instructions. You stay signed in until you run npx @opencode/console logout.

Limits

  • Your Hermes bots on Telegram, Discord, Slack and other platforms, and your cron jobs, run as you. They use your sign-in, the workspace's models and its MCP servers, under the same policies as hermes on your computer.
  • The workspace's Providers rules don't apply. You can still pick another provider in /model, and those requests don't go through Console.
  • Policies are checked by the plugin, so they hold only while it's enabled. Plugins you install aren't checked, and safe mode (HERMES_SAFE_MODE=1) or taking opencode-console out of plugins.enabled turns the plugin off. Tools that run code Console can't read, such as execute_code and browser_exec, are blocked while the workspace's policies limit shell commands, files or web fetches.
  • Until Hermes has the workspace's policies, it blocks every tool call. A check that fails or times out blocks the call or message too. If Console can't be reached, the policies it last fetched stay in place.
  • Console doesn't count Hermes as enforcing skill rules. Hermes checks a skill when you run it as /name, when the model opens it and when skills.auto_load loads it, but not a skill you start Hermes with (hermes -s) or one a kanban task loads.
  • The token that signs Hermes in to the workspace's MCP servers is in Hermes's environment. Hermes hides it in logs and replies, but MCP servers Hermes starts on your computer can read it, and on Hermes 0.23.0 and earlier, so can commands in its terminal.
  • If your profile already has an MCP server or skill with the same name as one of the workspace's, Hermes keeps yours. Skills the Library marks to run only when asked are still offered to the model.

Support

Email help@anoma.ly. We reply within two business days (Monday to Friday, excluding US holidays). The support page covers data requests, security reports and more.