Profile-scoped state and routing under multiplexing
Cluster 84253 · gateway. Data as of
1 open item. Fix merged in #120103 on 23 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 0 issues 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
unresolved. That is separate from the fix event. - Still open
- 1 issue and 0 PRs.
Next step: read #120103, then check whether your report is the one still open.
Read #120103Pick up a Lab taskThese items address a shared problem: response history, conversation mappings, and background task paths were being stored or routed globally rather than scoped to the owning profile. The fixes and related work bring API state and background subsystems (cron, kanban, ledger, adapters) into alignment with per-profile ownership under a multiplexed setup.
Open issues1
- Issue#84253Response history and conversation mappings are process/global rather than profile-scoped
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: merged via another change 1
-
#120009 fix(api-server): /v1/responses state belongs to the routed profile · merged via another change →
bd970b0,#120103
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
- Subsystem
- gateway
- Merged PRs
- #120103
- Closed issues
- 0
- Attempts
- 1 PR closed without merging
- Fix link checked
- 23 Sep 2026