# NousResearch/hermes-agent · Bot mode peer DM fails without profile pin

## Open now

- Nothing open on GitHub.

A bug where peer DM delivery in bot mode omits the profile flag, causing registry resolution to fail when the sending profile is not the default. The items cover the bug report and two related fixes targeting profile pinning in peer DM calls.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #93935: Bot Mode: message_agent peer delivery fails from non-default profiles — runner calls 'hermes peer dm' without -p, peer registry is profile-scoped

## Prior & competing PRs

- **#93952: fix(bot-mode): pin the registry-owning profile on peer DM deliveries**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `d4cec15b47e`, `#93935`
- **#99463: fix(bot-mode): pin default profile for peer dm so the peer registry resolves from non-default profiles**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#93952`

## Fix status

- No merged fix on record.