# NousResearch/hermes-agent · QQBot DM vs C2C approval button auth mismatch

## Open now

- Nothing open on GitHub.

These issues and PRs address a bug where approval buttons in QQ private (DM) chats are incorrectly rejected as unauthorized due to a mismatch between 'dm' and 'c2c' channel type handling in session authorization logic. The work involves identifying the problem and proposing fixes to treat the two types equivalently.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #105349. Verify it addresses your case.
- **Recommended:** read PR #105349 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## 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

- #98100: qqbot: DM (c2c) approval buttons rejected as unauthorized (dm vs c2c mismatch in _is_authorized_interaction_for_session)

## Prior & competing PRs

- **#105349: fix(qqbot): approval buttons in QQ private chats resolve instead of timing out (salvage #31593)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `contributors/emails/penginman@users.noreply.github.com`, `gateway/platforms/qqbot/adapter.py`, `tests/gateway/test_qqbot.py`
- **#101814: fix(qqbot): treat dm like c2c in approval-button session authorization**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `e5382cd823`, `#105349`, `#31593`

## Fix status

- Merged to main in PR #105349 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-07`.