Fix cron bot-chat delivery scoped to correct profile
Cluster 119858. Data as of
Nothing open on GitHub. Fix merged in #120103 on 23 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #120103. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #120103. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug was identified where multiplexed cron jobs using deliver: bot-chat looked up paths against the gateway default rather than the owning job profile. The fix and related work scope cron, kanban, ledger, and adapter background paths to their respective owning profiles under multiplex.
Open issues0
Open PRs0
Fixes on record
-
#120103 Cron, kanban, ledger and adapter background paths follow the owning profile under multiplex (#119858, #119859, #119973, #119242; salvage #119974 #120045 #120019 #120009 #112888)
files:
agent/redact.py,agent/secret_scope.py,contributors/emails/[redacted:email],contributors/emails/[redacted:email],cron/lifecycle_guard.py,gateway/AGENTS.md,gateway/delivery_ledger.py,gateway/platforms/api_server.py,gateway/platforms/api_server_openai_routes.py,gateway/platforms/api_server_runs.py,gateway/run_adapters.py,hermes_cli/env_loader.py,hermes_cli/kanban.py,hermes_cli/kanban_specify.py,hermes_cli/profiles.py,hermes_constants.py,hermes_logging.py,tests/agent/test_i18n.py,tests/agent/test_secret_scope_pinned_launch_home.py,tests/agent/test_serves_routed_profile_pin.py(+14 more)
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#119867 fix(cron): scope bot-chat delivery to job profile · superseded by another PR →
bd970b0,#120103
Closed issues · 1
- Closed#119858[Bug]: multiplexed cron `deliver: bot-chat` (own profile, no -p) runs the delivery turn against the gateway default HERMES_HOME
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.00means 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 LabAt a glance
- Merged PRs
- #120103
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 23 Sep 2026