Session lease acquisition and expiry bugs/fixes
Cluster 57052 · apps/desktop. Data as of
2 open items. Fix merged in #122923 on 25 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 9 related items grouped here, 2 issues already closed.
- Fix event
- A fix was merged to main in PR #122923. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
partially resolved, deciding PR #122923. That is separate from the fix event. - Still open
- 1 issue and 1 PR.
Next step: read #122923, then check whether your report is the one still open.
Read #122923Pick up a Lab taskMultiple bug reports and corresponding fixes addressing how active-session leases are claimed, held, and relinquished in desktop and TUI contexts, particularly around idle tabs, session switching, and detach timing.
Open issues1
- Issue#57052[Bug]: Idle desktop/TUI tabs permanently pin max_concurrent_sessions slots (claimed at composer paint, never released while connected)
Open PRs1
- PR#67049fix(desktop): isolate new-session windows
Fixes on record
-
#122923 fix(desktop): track one unscoped stream pin per session
files:
apps/desktop/src/app/session/hooks/use-message-stream/gateway-event/index.ts,apps/desktop/src/lib/gateway-events.test.ts,apps/desktop/src/lib/gateway-events.ts -
#123010 fix(tui-gateway): reap stale deferred active-session leases
files:
tests/tui_gateway/test_deferred_lease_reaper.py,tui_gateway/session_lifecycle.py,tui_gateway/session_reaper.py
3 PRs closed without merging
From the close comments: partial fix 1 · other 2
- #57059 fix(tui-gateway): claim active-session leases lazily and release them when idle (#57052) · other
-
#68947 fix(tui): release active-session lease immediately on session detach, not after orphan-reap delay (#68920) · partial fix →
e35c2f6,0f9ef9b,#68920,#68947,#68949,#1,#15803,#14532,#6,#9,#374151,#4338 -
#68949 fix(tui): reclaim leaked active-session leases with an owner-tagged pid-scoped sweep · other →
#68947,#68920
Closed issues · 2
How this cluster was grouped
-
Link evidence (
partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text. - Members outside that structural core may belong to a different underlying problem.
-
Pairwise link density
0.19: 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 Lab