Cairn
NousResearch/hermes-agent

Bot privacy flags for agent mesh membership

Cluster 111737 · agent. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

These items propose a per-agent private flag and an install-wide bots.force_private setting to control whether a bot agent appears in other agents' rosters and is reachable via direct messages. All three members describe the same feature request or its implementation.

Open issues1

  • Issue#111737[Feature]: bot-mode mesh membership — a per-agent `private` flag and an install-wide `bots.force_private`, so an agent can be kept out of every other agent's roster and DM reach

Open PRs1

  • PR#104876feat(bot-mode): per-agent `private` flag and install-wide `bots.force_private`

1 PR closed without merging

From the close comments: duplicate 1

  • #112090 feat(bots): mesh membership — per-agent private flag and install-wide force_private · duplicate → #104876
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.67: 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

Subsystem
agent
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/111737.json
cluster/111737.md