Repository navigation
feat(desktop): support concurrent NeoCode windows and isolated instances #146
Description
Note
GPT-6 Astra on behalf of PsychedelicShayna
Contract
The owner must be able to keep NeoCode open while another window or a private verification instance runs. This is a new product requirement beyond #24's completed raise-existing-window behavior.
Acceptance
- Multiple windows can remain usable at once, with an explicit supported path for opening another window.
- Windows sharing an environment share its authoritative backend/session ownership instead of creating competing native writers.
- Private profiles/verification instances do not steal focus, data, sockets or single-instance ownership from the live profile.
- Closing or crashing one window does not orphan the shared backend or lock the remaining windows out.
- Verify ordinary first launch, concurrent windows, close/reopen and crash recovery in isolated state.
Preserve existing data. The owner has already chosen concurrent windows; this is not blocked on another product-choice interview. Startup/control lockout risk uses the workspace canary procedure.
Owner's words (verbatim)
2026-10-22 owner dictation — contiguous excerpt
I would like to be able to create multiple instances of the fucking window, by the way. I hate the fact that I cannot have it open while you have it open. I'm guessing that's because of the way that the database is designed, but the way the database is designed is based off of something that we don't, we're not subject to. Like the other harnesses, we don't care about them.
Complete unedited message: #125 . The owner's words take precedence over this summary.
Activity