StandTerm Desktop 0.4.1 (Windows x64 evaluation)
Pre-releaseStandTerm Desktop 0.4.1 — Windows x64 evaluation
This is an unsigned pre-release, not a production-qualified Desktop or stable Core release. The existing stable Core release remains v2.10.0. This candidate is built from commit 4050a29f467fcfa94e389042a9e18a3154be0459; its source is under review in PR #19.
Download and prerequisites
Download StandTerm-Desktop-0.4.1-win32-x64-Setup.exe and its .sha256 checksum file. The installer contains Electron and the public Core snapshot, but does not include Python or a venv. End users do not need Git, Node.js, or npm.
- Windows only: install 64-bit Windows Python 3.10+ with venv/ensurepip first.
- WSL only: have an existing WSL distribution with Python 3.10+ and venv/ensurepip.
- Windows + WSL: meet both prerequisites; setup prepares separate environments and shortcuts.
Dependency installation requires network access and explicit user approval. Python/WSL are not installed automatically. The unsigned installer may trigger Windows publisher/SmartScreen warnings; this release is intended for evaluation.
Save work and quit Desktop, including tray windows, before installing or upgrading. Existing NSIS evaluations can be upgraded in place; a changed Core bundle prepares a new environment. Full automated installer lifecycle acceptance remains outstanding. Older 0.1.x/0.2.x Squirrel evaluations require manually uninstalling the old interface first. User settings and existing runtimes are retained; optional uninstall venv cleanup is recoverable and disabled by default.
Highlights
- Native Windows or Windows + WSL Desktop launchers share the existing Core UI, with user-approved initial setup and remembered ports. Occupied ports prompt for a replacement without stopping the other service.
- Browser settings and stored keys persist per backend mode and origin, consistent with Core browser behavior. Session authentication is refreshed rather than kept as a long-lived Desktop login token.
- Files/PiP floating windows, PNG screenshots and silent WebM recording are available in the Desktop layer. Native Windows Local Shell does not yet expose the local Files backend; WSL Local Shell supports it.
- Diagnostics show the actual backend URL/port and bounded startup events. Copy backend URL or tokenless agent connection information to avoid connecting to another instance. These exports do not grant agent access; normal mint/approval rules still apply.
- About shows Desktop and actual running Core versions, Python/Electron/Chromium/Node.js/platform, and managed Core bundle SHA-256 when available. Source checkouts and older backends do not receive an invented build identity.
- Long agent approval requests keep action buttons reachable in Core and Desktop. External previews offer a user-confirmed default-browser fallback without forwarding StandTerm credentials.
- Core shortcut startup supports remembered ports, and opt-in platform passkeys can recover a session that remains live in the same Core process. This is not persistence across a Core restart.
Build identity
- Desktop:
0.4.1 - Core:
2.11.0-dev - Electron:
44.2.0 - Platform: Windows x64; Windows and WSL backend modes
- Core bundle SHA-256:
1196654bf9dd391750081953542af727f11768532b3774b6cffba60036b06b15 - Installer SHA-256:
32a30ee047b05bb0db01338b853df60866de6fea7b94eb8ed890e738c827cacd
The checksum detects corruption; it does not replace publisher signing. No private handoffs, profiles, credentials, developer venvs, or unintegrated rescue scripts are included.
Validation and remaining limits
The source passes Core headless regression checks and 51 Desktop unit tests. GitHub push and PR headless checks pass. The packaged executable passes native Windows and WSL authentication, shell I/O, reload reattachment, About/diagnostics/copy-info, PiP/child guards, PNG and decodable silent WebM checks using disposable profiles and existing isolated test venvs. WSL additionally passes Files browse/download/destination navigation. All 48 bundled Core files and the packaged shell match the staging snapshot.
These smoke tests bypass interactive first-run setup. The complete clean-install/upgrade/cancel/uninstall matrix in an isolated Windows account or VM, manual default-browser handoff acceptance, and broader platform acceptance remain outstanding. Python requirements are not fully version-locked. There is no Core updater or automatic Desktop updater; updates are installed manually. This release does not claim that live SSH/shell connections survive restarting Core.