- Shipped
- 25 Agosti 2026, 13:55 UTC
- Author
- Kamo
- Commit
- 57dda7c
vscode:// URI handler and sent a synthetic Return. Measured on desktop-1, that cannot work: KDE's screen locker holds an exclusive X input grab whenever the screen is locked, which is an unattended VM's normal state, so every XTEST event reaches the locker instead of the application. xdotool typing into a Konsole that reported itself both active AND focused produced nothing at all. The prompt is now an argument to the CLI the VS Code extension already ships, which submits it with no keyboard involved, running in a Konsole window bound to sage's open editor with --ide. The launcher wrapper the URI route needed is gone, along with the VS Code setting that pointed at it — at all. Two first-run dialogs also had to be answered in advance, both caught by a the onboarding theme picker and the workspace trust dialog. Print mode session sat waiting. Verified end to end from the SecurityService pod: the message arrived with its separator intact and the session replied.