AgentFixboard
UnverifiedLast checked Hermes Agent#state#error-messages

Deleting a non-root profile session always returns 409 runtime_coordination_required

DELETE /api/sessions/<id>?profile=<name> on a non-root profile returns HTTP 409 RuntimeStoreError('runtime_coordination_required'). The root profile deletes fine in the same window.

From GitHub

NousResearch/hermes-agent

IssuePull request

Difficulty
Easy
Time
~5 min
Steps
2
Fixed in
—
Last checked

Unverified: we could not confirm from the sources that a fix shipped. Source: PR #140191 merged. Last checked 2026-10-19.

Symptom

DELETE /api/sessions/<id>?profile=<name> on a non-root profile returns HTTP 409 RuntimeStoreError('runtime_coordination_required'). The root profile deletes fine in the same window.

Evidence what you'll see

  • The refusal is {"detail":"runtime_coordination_required"} and fires before any turn-liveness check. An idle session with zero messages is refused the same way.
  • The guard in gateway/session_mutations.py compares store._routing_db.db_path to authority.db.db_path on delete.
  • store._routing_db is one shared routing index at <launch HERMES_HOME>/state.db. authority.db for ?profile=<p> is profiles/<p>/state.db, so the paths differ for every non-root profile.

Why it happens

The delete guard treated a shared routing index as a foreign store. Pull request 140191 drops the multiplexed secondary profile's rows in that shared index at once, so the delete no longer 409s runtime_coordination_required.

Affected versions

Hermes Agent v0.22.1+52.g348f145 (git install) and v0.22.1 (297552a9d646), Windows, Desktop client sending DELETE /api/sessions/<id>?profile=<name>.

Fix steps

0 of 2 done

Your check marks stay in this browser only.

How to check it worked

  • DELETE /api/sessions/<id>?profile=<name> on a non-root idle session returns success, not HTTP 409 runtime_coordination_required.

If it still fails

  • No published release tag contains pull request 140191. Tags v0.22.0, v0.22.1, and v0.22.2 were compared against merge c31b4f62e70b and do not contain it.
  • A session PATCH/DELETE with no mutation identity still gets 409 client_upgrade_required (a separate change in the same pull request).

Sources and credit

Summarized in our own words from these public reports. Credit goes to their authors.

Provided as is, without warranty. Try changes in a non-production environment and back up first. Security-related steps: verify against the official docs. Terms · Request removal or attribution change

Hit an error we don't cover? Submit it