AgentFixboard
OpenLast checked Hermes Agent#regression#messaging

hermes peer dm returns bot_chat_not_local after upgrading to 0.22.2

After the upgrade to 0.22.2, every peer call fails immediately when that profile's Bot Chat was created through the API.

From GitHub

NousResearch/hermes-agent

Issue

Difficulty
Moderate
Time
~15 min
Steps
3
Fixed in
—
Last checked

Not fixed upstream yet: the issue is open. Source: issue open. Last checked 2026-10-18.

Symptom

After the upgrade to 0.22.2, every peer call fails immediately when that profile's Bot Chat was created through the API.

Evidence what you'll see

  • The line is Peer 'ix' rejected the request (HTTP 502): Bot Chat admission refused: bot_chat_not_local (this profile's 'Bot Chat' is not a local chat; it is an API conversation; rename or delete it there).
  • POST /v1/runs returns the same refusal. status is failed and output is null.
  • The session id in the report starts with api_, for example api_1790437612_6055b731, title Bot Chat.

Why it happens

0.22.2 refuses a peer turn when the canonical Bot Chat is not a local chat. An API-created session fails validate_legacy_row, so the reason becomes bot_chat_not_local. The same calls worked on v0.21.5 against this host.

Affected versions

Linux, systemd, gateway active (running). The broken build is v0.22.2+1524.ge6f5742 (e6f57427c19). The working build minutes earlier was v0.21.5+4911.g6ec0520.

Fix steps

0 of 3 done

Your check marks stay in this browser only.

How to check it worked

  • hermes peer dm or hermes peer run no longer returns HTTP 502 or bot_chat_not_local.

If it still fails

  • The linked issue does not give a flag or a subcommand that rebinds an api_ Bot Chat into a local chat.

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