Cairn

Bot Mode message_agent headless install requirements docs

NousResearch/hermes-agent · cluster 105359

Data as of

Nothing open on GitHub. Fix merged in #113411. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #113411. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #113411. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and pull requests concern documentation of the undocumented requirements that make message_agent available on headless installs in Bot Mode. The work focuses on clarifying availability conditions, including managed-marker gates and related configuration prerequisites.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #113411 docs(bot-mode): state what makes message_agent available on headless installs (#105359, salvage #105362)

    merged to main

    files: website/docs/user-guide/bot-mode.md

3 PRs closed without merging

From the close comments: done elsewhere 3

  • #105361 docs(bot-mode): note the managed-marker gate behind message_agent and the protocol · done elsewhere → bb8ce96, #113411, #105359
  • #105362 docs(bot-mode): document the real availability requirements of message_agent on headless installs · done elsewhere → bb8ce96, #113411, #105359
  • #105822 docs: four clarifications from open type/docs issues (webhook template token, plugin hook table, delegation transcripts, message_agent requirements) · done elsewhere → bb8ce96, #113411, #105359
Closed issues · 1
  • Closed#105359Bot Mode docs: message_agent unreachable on headless installs — two undocumented requirements (Bot Chat title, profile.yaml ui_meta)
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.40: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Merged PRs
#113411
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
17 Sep 2026

For your agent

The same facts, typed.

cluster/105359.json
cluster/105359.md