Gateway idle-exit behavior with secondary local adapters, plus bundled fixes
Cluster 140509 · gateway. Data as of
Nothing open on GitHub. Fix merged in #140967 on 18 Oct 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 #140967. 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
- Nothing open on GitHub.
Two of the three members concern gateway idle exit, specifically secondary local adapters or profiles that appear to keep an auto-started gateway from idle-exiting. The first member is a broad gateway fix bundle that also lists unrelated items (parked-profile ingress, downgrade relaunch, side-agent drain, worker birth, Kanban ACK wait, log lock order), so the cluster is only partly coherent.
Open issues0
Open PRs0
Fixes on record
-
#140967 fix(gateway): parked-profile ingress, downgrade relaunch, side-agent drain, idle exit, worker birth, Kanban ACK wait, log lock order (package 10 lane 1)
files:
agent/managed_worker.py,agent/side_question.py,gateway/AGENTS.md,gateway/parked_route_refusal.py,gateway/platforms/api_server_response_admissions.py,gateway/platforms/shared_ingress.py,gateway/platforms/webhook.py,gateway/platforms/webhook_ingress.py,gateway/relay/inbound_admission.py,gateway/run_idle_exit.py,gateway/run_profile_reconcile.py,gateway/run_runtime.py,gateway/run_shutdown.py,gateway/runtime_downgrade_exit.py,gateway/session_api_turn.py,gateway/session_authorities.py,gateway/session_ingress_context.py,gateway/session_kanban.py,gateway/session_managed_worker.py,gateway/session_runtime_workers.py(+21 more)
1 PR closed without merging
From the close comments: done elsewhere 1
-
#140510 fix(gateway): ignore secondary local adapters for idle exit · done elsewhere →
25eb0bb,#140967
Closed issues · 1
- Closed#140509Auto-started gateway never idle-exits after a secondary profile uses a local session
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
- #140967
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 18 Oct 2026