- Shipped
- September 2, 2026 at 4:37 AM UTC
- Author
- Kamo
- Commit
- 3a198ad
The SEND TO AI switch handed the report over the moment it was filed. It POSTed a bodyless dispatch, which left SecurityService to choose the instruction, the model, the effort, the screenshots AND the status — so every report filed with it reached a session as opus/xhigh and was flipped to In Progress before the member had been shown one of those choices. Twenty consecutive dispatches in the cluster read exactly that, the report asking for this among them. The switch now files the report, re-reads it, and opens the same Send To AI dialog the queue's drawer opens. The member composes the instruction, sharpens the title, picks the screenshots, the model, the effort and the status the report lands in, and nothing reaches the dev machine until they press Send. The dialog is rendered BY the window rather than beside it, so the window stays open behind it — closing on save would unmount the dialog in the same breath as opening it. Both ways out of the dialog then close the window: the report is filed by the time it is on screen, and a form left open over a filed report is an invitation to file it twice. Cancelling therefore costs the hand-off, never the report, which is announced to the queue before the dialog opens rather than after it closes. Opened after the uploads, for the reason the dispatch used to run after them: the picker seeds from the report as it stands, and one drawn mid-upload would offer the member less evidence than they had just attached. The console's bodyless auto path goes with it — the proxy route and the API method both — so the switch cannot be pointed back at the server's choices by one line. The SecurityService endpoint is left in place, unreferenced.