Add persistent Desktop launchers and Core session recovery - #19
Merged
Conversation
## Why Browser launches need explicit authentication and stable endpoints, while Desktop needs persistent profiles and observable backend identity. ## What changed - Add Windows and WSL Desktop setup, persistent profiles, capture, floating windows, and scoped diagnostics while preserving Core browser behavior. - Add remembered-port startup and platform session recovery; retain explicit launch overrides and approval boundaries. - Report actual Core version and bundle identity in About and diagnostics, with unknown metadata fallback for older backends and tokenless agent connection copying. - Split external-agent guidance into on-demand references while retaining explicit instance selection and user-controlled authorization. ## Testing Core headless regression coverage, 51 Desktop unit tests, isolated backend authentication and lifecycle checks, and Windows Electron with WSL About, diagnostics, Files, and PiP smoke coverage pass. Packaging inputs include Core version identity and exclude private and unintegrated rescue files.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Browser launches need explicit authentication and stable endpoints. Desktop users need persistent settings, reliable Windows/WSL startup, and a visible backend identity so external agents do not connect to another StandTerm instance.
What changed
Testing
Core headless regression checks, 51 Desktop unit tests, isolated backend authentication/lifecycle tests, and Windows Electron + WSL About, diagnostics, Files, and PiP smoke tests pass. Packaging input verification includes the Core version module and excludes credentials, venvs, private handoffs, and unpublished rescue tools.
The accompanying Desktop release is a pre-release, not a stable Core release. It is unsigned, requires separately installed platform Python, and has no updater. Full isolated interactive installer clean-install/upgrade/cancel/uninstall acceptance and manual default-browser handoff acceptance remain outstanding; the complete Python dependency set is not release-locked. Packaged-candidate checks are recorded in the release notes.
Desktop 0.4.1 pre-release is published from this exact commit. The packaged Windows/WSL shell, About/diagnostics/copy-info, PiP, PNG and silent WebM checks pass; WSL Files checks pass. The NSIS-extracted payload matches the smoke-tested package, and both uploaded asset SHA-256 digests match the local artifacts. This PR remains open for review; main and the stable Latest release are unchanged.