ALT fix(droid): a slow session load no longer leaves the thread on a session it cannot hear Droid answers a new process's first request only after its startup, which took over two minutes on Oct 26 (catalog_prime 33-38 s, script_run_reap 83 s), so load_session missed its 60 s limit on sessions that were fine. T3 then fell back to a fresh session whose initialize_session also timed out. Droid still ran both stale requests once it caught up, and the late initialize_session left the process on a new session while the adapter stayed bound to the loaded one. Every notification of the next turn was dropped as another session's, so the run never settled.

ALT Screenshot of a dark-mode AI coding agent session. Only tool-call rows are visible, and no chat text appears between them: "Script: Grep," "Script: Execute," a "TaskOutput" row, and "Script: Create" at 6:50 PM. The Script: Create row is expanded to show the file it wrote. The file starts with "Since my chat text is dropped, I'm putting status here," then has a section titled "Why this file exists." It explains that the session was auto-compacted at the start of the turn, so the UI is still bound to the old session, which drops text, thinking, and tool results from the new one. Only tool calls come through, and they stay "running." The visible part ends mid-sentence about a 10 min inactivity watchdog.

ALT Screenshot of the dark-mode Twitter/X Android app on the "Request Community Note" screen, with a back arrow in the top left. The heading reads "Thank you! There's already a proposed Collaborative Note on the post," followed by "You can help rate and improve it." A dark blue info box says "Community Note request submitted" with a "Delete request" link. Below are two buttons: "See Collaborative Note," a white pill-shaped button partly covered by the orange circle, and "Done," an outlined button. An orange hand-drawn circle highlights the Done button. Tapping Done does nothing in this state, which is the bug being reported.