Problem
Lane lifecycle operations can crash active ADE CLI sessions, ADE chats, and sometimes project/runtime state. This consolidates the two observed triggers from ADE-91 and ADE-93.
Observed triggers
- Deleting a lane usually crashes existing CLI sessions and ADE chats associated with that lane.
- Auto-create lane from the Work tab can become extremely slow, then crash active ADE CLI sessions and project state.
Expected
Lane create/delete flows should either complete or fail in a controlled way without crashing active CLI sessions, chats, or open project/runtime state. If a lane is deleted, attached sessions should be gracefully ended, detached, or marked unavailable. If auto-create lane slows or fails, existing sessions should remain isolated and resumable.
Actual
Lane deletion and slow Work-tab auto-create lane flows can cascade into crashes of active CLI sessions, ADE chats, or project state instead of surfacing a contained lane-level failure.
Investigation requirement
Identify the root cause before implementing a surface fix. For each trigger, trace why that specific lane lifecycle failure can propagate into crashes of existing CLI sessions, ADE chats, or project/runtime state. Do not close this with only a timeout, spinner, or UI-level mitigation unless the crash cascade is understood.
Areas to inspect
- Lane deletion cleanup and ownership transfer for attached chats/CLI sessions.
- Work tab auto lane creation trigger and debounce/duplicate-launch behavior.
- Lane creation/deletion service lifecycle and shared runtime/socket state.
- Chat and CLI session ownership when lanes/projects are created, deleted, refreshed, or invalidated.
- Whether lane lifecycle failures invalidate paths, project registry entries, pty ownership, or chat session records still in use.
- Whether failures are taking down a shared process, daemon bridge, project registry, or session manager instead of isolating the affected lane.
Acceptance criteria
- Root cause of the lane deletion crash cascade is identified.
- Root cause of the slow auto-create lane crash cascade is identified.
- Lane lifecycle failures no longer crash active CLI sessions, ADE chats, or project state.
- A regression test or targeted validation covers both the lane deletion path and the slow/failed auto-create lane path.
Consolidation
Consolidates ADE-93 into ADE-91.
Problem
Lane lifecycle operations can crash active ADE CLI sessions, ADE chats, and sometimes project/runtime state. This consolidates the two observed triggers from ADE-91 and ADE-93.
Observed triggers
Expected
Lane create/delete flows should either complete or fail in a controlled way without crashing active CLI sessions, chats, or open project/runtime state. If a lane is deleted, attached sessions should be gracefully ended, detached, or marked unavailable. If auto-create lane slows or fails, existing sessions should remain isolated and resumable.
Actual
Lane deletion and slow Work-tab auto-create lane flows can cascade into crashes of active CLI sessions, ADE chats, or project state instead of surfacing a contained lane-level failure.
Investigation requirement
Identify the root cause before implementing a surface fix. For each trigger, trace why that specific lane lifecycle failure can propagate into crashes of existing CLI sessions, ADE chats, or project/runtime state. Do not close this with only a timeout, spinner, or UI-level mitigation unless the crash cascade is understood.
Areas to inspect
Acceptance criteria
Consolidation
Consolidates ADE-93 into ADE-91.