- Ya
- 28 Agosti 2026, 04:30 UTC
- Mwandishi
- Kamo
- Ahadi ya
- d1839a7
A dispatch now starts a BACKGROUND session and hands VS Code its session id, instead of running the CLI in a terminal window: Passing the prompt to the URI instead is a trap: the extension calls setInputText and never sends, and synthesising a Return is impossible while the KDE locker holds its X grab. A session that is ALREADY RUNNING has nothing left to submit, which is what makes the handoff work with nobody at the machine. Four things measured rather than reasoned about: - cwd must be realpath(workspaceFolders[0]), NOT the common parent this used before. The panel host roots itself at the first folder and lists only the sessions it finds there, so a session started anywhere else is invisible to the window it is meant to open in — the handoff opens an empty tab. The other repositories stay reachable through --add-dir instead. - --add-dir is VARIADIC and was eating the prompt, so sessions came up with an empty composer. The directory list now goes first, closed by the flags after it. - A launch can print no handle, or one marked "(idle — send a prompt to start)". Both mean the message never arrived, so both are stopped and retried rather than opened in front of the operator as an empty tab. - The panel cannot own a background agent, and a finished one stays resident, so a watcher stops it once the work is done. Reopening the tab then resumes the session normally, whole conversation intact. Confirmation is now the transcript addressed by session id, which removes the JSON-escaped-needle search that reported delivered dispatches as failures.