Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

Hermes Agent 0.23.0: paid MCP spend limits

Written November 9, 2026

Hermes Agent 0.23.0 (Nov 5) adds single-gateway sessions and paid MCP spend limits. What the limits cap, and what a single gateway changes.

What 0.23.0 is

Hermes Agent 0.23.0, "The Hearth Release," landed November 5, 2026 from Nous Research, and it is the largest release in the project's history: since v0.22.0, about 10,080 commits, 1,950 merged pull requests, 8,720 files changed, and 850 closed issues from 666 contributors, rolling up the intervening v0.22.1 through v0.22.7 releases. The release notes frame it as the moment Hermes becomes a desktop agent and a workspace in the browser, but two changes are the ones that alter how the tool behaves day to day: one gateway owns every session, and paid MCP tools get a spend limit.

One gateway owns every session

Before 0.23.0, each surface of Hermes could run its own copy of the agent. The CLI, the terminal UI, the desktop app, editor connections, bots, and cron could each hold a session, and messages got written twice or went missing because no single owner of the conversation existed. In 0.23.0, one gateway owns every session: the CLI, TUI, Desktop, editors and ACP clients, bots, and cron all attach to the same gateway as clients, sharing one queue and one history. A message sent from the desktop shows up in the CLI; a cron job's result lands in the same conversation the desktop is showing. The Desktop itself gains a workspace that opens in a browser tab, the Webapp, which is off by default and enabled with webapp.enabled. The practical effect is that Hermes stops being a set of tools that each keep their own copy of the agent and becomes one agent with several doors into it.

The release also changes the default model to GLM-5.3, adds /rewind to step a session back, renders inline images in terminals, and grows the plugin catalog from about 600 entries to more than 1,050. Delegation — letting one agent hand work to another — becomes pluggable, so a custom delegation approach can be dropped in without forking the agent.

Paid MCP tools get a spend limit

Some MCP servers charge per call — 3D generation and media generation are the examples in the release notes — and before 0.23.0 there was no built-in way to bound what an agent could spend on them. Now paid MCP tools declare a per-call price, and every approval prompt shows that price alongside the running total for the chat. The operator sets a spend limit per chat, and Hermes asks for approval before the chat goes over it, even in YOLO mode, where approval prompts are otherwise suppressed. That last point is the one that matters: YOLO mode stops asking about tool calls, but it does not stop asking about money. There is no dollar figure in the release notes — no default cap, no suggested limit — because the limit is set per chat by whoever runs it. The control is the limit you set, not a number the tool chose for you.

Two other changes in the same release touch the same theme of knowing what the agent is doing. /rewind lets you step a session back after a bad turn, which is the recovery path when an approval was wrong. And the single gateway means the spend total for a chat is one number in one place, not a total scattered across surfaces that each kept their own copy.

What to do about it

  1. Set the limit before the unattended run, not after the bill. If a chat can call a paid MCP tool, give it a spend limit first. The approval prompt asks even in YOLO mode, so the limit is the control — but only if you set one. No limit in the release notes means no safety net by default.
  2. Check which of your MCP servers charge per call. The release notes name 3D and media generation. Audit your own server list for anything that bills per call, and set limits on the chats that can reach them, not just the ones you expect to use them.
  3. Use the gateway, not the surfaces. If you run Hermes from more than one surface, stop treating each as its own agent. Attach them all to the gateway so history and spend are one conversation, and use the Webapp only when you need a browser door into it.
  4. Expect breakage on upgrade. The MCP command moved from hermes mcp serve to hermes mcp-serve, the old browser_* tools are gone in favour of browser_exec, and Desktop now needs macOS 13 or newer and 64-bit Windows. Scripts and shortcuts that call the old names will fail.

Verdict

Set the limit before the unattended run, not after the bill — the approval prompt asks even in YOLO mode, so the limit is the control. For anyone running paid MCP tools, that one setting is the whole upgrade; the single gateway is the reason the total is finally one number you can trust.

What can go wrong

Limits

Related playbooks

Sources

Back to: Coding playbooks hub · Also: MCPhantom: agents install dead MCP servers · Baseten Grid routes coding-agent traffic