# NousResearch/hermes-agent · Cron bot-chat delivery uses wrong profile environment

## Open now

- Nothing open on GitHub.

A bug where cron bot-chat deliveries to another profile incorrectly run using the destination profile's environment (credentials and authorization) instead of the sender's. The cluster covers the bug report and associated fixes.

## 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 #117619. Verify it addresses your case.
- **Recommended:** read PR #117619 (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: `resolved` · deciding PR(s): `pr-117619`. 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

- #117220: \[Bug\]: cron \`deliver: bot-chat:<other profile>\` runs the destination's turn with the sending gateway's environment (credentials and authorization gates included)

## Prior & competing PRs

- **#117619: fix(cron): bot-chat delivery to another profile runs with the destination's environment, not the sender's (#117220, salvage #117221)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `cron/scheduler_delivery.py`, `tests/cron/test_bot_chat_delivery_child_env.py`, `website/docs/user-guide/features/cron.md`
- **#117221: fix(cron): a bot-chat delivery builds its child env for the DESTINATION profile, not the sender**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `786c0e3f9d`, `#117619`

## Fix status

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