kshitijk4poor 8077e7d2fb fix(tui): narrow resume lock to avoid blocking session.close ... The salvaged fix held _session_resume_lock across _make_agent (MCP discovery + AIAgent construction, seconds), serializing it against session.close. Since session.close runs on the main RPC dispatch thread (not a _LONG_HANDLER), a close racing a mid-build resume would stall all fast-path RPCs (approval.respond, session.interrupt). Restructure to double-checked locking: build the agent outside the lock, then re-check _find_live_session_by_key under the lock before _init_session. A losing concurrent resume discards its just-built agent (no worker/poller wired yet) and reuses the winner. Updated the concurrent-resume regression test to assert the real invariant (one surviving live session + loser agent closed) rather than the implementation detail of a single _make_agent call.		2026-06-04 08:18:26 -07:00
..
__init__.py	feat: new tui based on ink	2026-04-02 19:07:53 -05:00
entry.py	perf(tui): stop slow/dead MCP servers from freezing TUI startup	2026-05-30 02:53:37 -07:00
event_publisher.py	chore: address copilot comments	2026-04-24 12:51:04 -04:00
render.py	tui: inherit Python-side rendering via gateway bridge	2026-04-05 18:50:41 -05:00
server.py	fix(tui): narrow resume lock to avoid blocking session.close	2026-06-04 08:18:26 -07:00
slash_worker.py	feat: personality	2026-04-08 00:15:15 -04:00
transport.py	fix(tui-gateway): harden stdio transport against half-closed pipes + SIGTERM races (#17118)	2026-04-28 17:54:06 -05:00
ws.py	fix(dashboard): explain WHY a chat WS connection was refused (#38743)	2026-06-04 00:36:03 -07:00