2026-09-11 03:31:00 +07:00
|
|
|
|
|
|
|
|
|
Durable desktop updates: Check for Updates, background download, install on quit, Windows installer (#595)
Update detection was late and fragile: the only checker lived in the engine
on a 6h monotonic timer (a laptop's sleep stretched it by the whole night),
the sidebar compared the release against whichever engine the UI attached to
(a daemon of another version hid or faked updates), nothing downloaded until
clicked, and several install paths could not update at all.
- zeron-update: hourly wall-clock schedule with failure backoff (1m→30m),
re-read on window activation; desktop (report-only) checker role; staged
payloads are unpacked beside their final name and must answer
`--version` with the promised release before they can replace anything;
up-front blockers (App Translocation, disk image, unwritable install dir)
instead of a failed download; Linux managed installs update from the app;
a service daemon restarts into a newer installed binary once idle.
- UI: app-level controller with its own checker against this binary; a found
release downloads in the background, the strip offers restart, and a
staged update installs on quit. "Check for Updates…" under About in the
macOS app menu, "Check for updates" in the account menu elsewhere, with a
live result dialog.
- Linux: the tarball's install.sh uses the self-updating ~/.zeron/app layout.
- Windows: per-user Inno Setup installer (LocalAppData, Start menu, zeron://,
uninstall entry kept current after in-app updates), built in release and
CI, with a silent install/uninstall smoke test.
- Fix: closing the window on X11 panicked in the geometry save, skipping the
engine drain and any quit hooks.
Co-authored-by: wing-anara <wing@anara.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-27 17:46:55 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-09-11 03:31:00 +07:00
|
|
|
|
2026-09-11 05:51:11 +07:00
|
|
|
|
2026-09-11 03:31:00 +07:00
|
|
|
|
2026-09-11 05:51:11 +07:00
|
|
|
|
2026-09-25 09:27:40 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-09-11 03:31:00 +07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-09-11 05:51:11 +07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-09-11 03:31:00 +07:00
|
|
|
|
2026-09-11 05:51:11 +07:00
|
|
|
|
2026-09-11 03:31:00 +07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-09-11 05:51:11 +07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Resolve and launch npm .cmd shims through cmd.exe
Both the resolver and the spawner were hard-coded to .exe, so
npm-installed agents were undiscoverable and unlaunchable: npm leaves
only a `name.cmd` shim on PATH with the real binary buried under
node_modules. Discovery is now PATHEXT-aware — per directory,
extensions in PATHEXT order, limited to what we can launch (.com,
.exe, .bat, .cmd) — and overrides accept batch shims that exist on
disk, so availability and launches agree.
Resolved .cmd/.bat scripts spawn through `cmd.exe /d /s /c` with
cross-spawn-style per-argument escaping: the shim is the only
interpreted layer, agent arguments stay literal (spaces, backslashes,
quotes, unicode, cmd metacharacters round-trip verbatim — proven by
re-invoking a real program through a shim fixture), and Job Object
ownership covers the whole tree through cmd.exe's membership. The
codex node_modules vendor special-case is deleted: it searched the
wrong vendor subdirectory (`bin/` instead of `codex/`), and its
fixture encoded that wrong layout, so CI passed while real npm
installs failed. GUI launches additionally backfill %APPDATA%\npm,
%LOCALAPPDATA%\{pnpm,Programs\nodejs}, scoop shims, and
%USERPROFILE%\{.local\bin,.bun\bin} from PATH.
opencode and cursor resolution migrate off raw $HOME to the shared
USERPROFILE-aware home helper; cursor also probes
%LOCALAPPDATA%\cursor-agent. The engine catalog and login tests use
the real npm shim layout, batch-override harness tests assert safe
launch instead of rejection, and the shell-script fixture suites are
gated to Unix where they actually run.
2026-09-11 16:49:14 +07:00
|
|
|
|
2026-09-11 03:31:00 +07:00
|
|
|
|
Resolve and launch npm .cmd shims through cmd.exe
Both the resolver and the spawner were hard-coded to .exe, so
npm-installed agents were undiscoverable and unlaunchable: npm leaves
only a `name.cmd` shim on PATH with the real binary buried under
node_modules. Discovery is now PATHEXT-aware — per directory,
extensions in PATHEXT order, limited to what we can launch (.com,
.exe, .bat, .cmd) — and overrides accept batch shims that exist on
disk, so availability and launches agree.
Resolved .cmd/.bat scripts spawn through `cmd.exe /d /s /c` with
cross-spawn-style per-argument escaping: the shim is the only
interpreted layer, agent arguments stay literal (spaces, backslashes,
quotes, unicode, cmd metacharacters round-trip verbatim — proven by
re-invoking a real program through a shim fixture), and Job Object
ownership covers the whole tree through cmd.exe's membership. The
codex node_modules vendor special-case is deleted: it searched the
wrong vendor subdirectory (`bin/` instead of `codex/`), and its
fixture encoded that wrong layout, so CI passed while real npm
installs failed. GUI launches additionally backfill %APPDATA%\npm,
%LOCALAPPDATA%\{pnpm,Programs\nodejs}, scoop shims, and
%USERPROFILE%\{.local\bin,.bun\bin} from PATH.
opencode and cursor resolution migrate off raw $HOME to the shared
USERPROFILE-aware home helper; cursor also probes
%LOCALAPPDATA%\cursor-agent. The engine catalog and login tests use
the real npm shim layout, batch-override harness tests assert safe
launch instead of rejection, and the shell-script fixture suites are
gated to Unix where they actually run.
2026-09-11 16:49:14 +07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-09-15 20:11:09 +00:00
|
|
|
|
2026-09-29 21:14:54 -03:00
|
|
|
|
2026-09-15 20:11:09 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Resolve and launch npm .cmd shims through cmd.exe
Both the resolver and the spawner were hard-coded to .exe, so
npm-installed agents were undiscoverable and unlaunchable: npm leaves
only a `name.cmd` shim on PATH with the real binary buried under
node_modules. Discovery is now PATHEXT-aware — per directory,
extensions in PATHEXT order, limited to what we can launch (.com,
.exe, .bat, .cmd) — and overrides accept batch shims that exist on
disk, so availability and launches agree.
Resolved .cmd/.bat scripts spawn through `cmd.exe /d /s /c` with
cross-spawn-style per-argument escaping: the shim is the only
interpreted layer, agent arguments stay literal (spaces, backslashes,
quotes, unicode, cmd metacharacters round-trip verbatim — proven by
re-invoking a real program through a shim fixture), and Job Object
ownership covers the whole tree through cmd.exe's membership. The
codex node_modules vendor special-case is deleted: it searched the
wrong vendor subdirectory (`bin/` instead of `codex/`), and its
fixture encoded that wrong layout, so CI passed while real npm
installs failed. GUI launches additionally backfill %APPDATA%\npm,
%LOCALAPPDATA%\{pnpm,Programs\nodejs}, scoop shims, and
%USERPROFILE%\{.local\bin,.bun\bin} from PATH.
opencode and cursor resolution migrate off raw $HOME to the shared
USERPROFILE-aware home helper; cursor also probes
%LOCALAPPDATA%\cursor-agent. The engine catalog and login tests use
the real npm shim layout, batch-override harness tests assert safe
launch instead of rejection, and the shell-script fixture suites are
gated to Unix where they actually run.
2026-09-11 16:49:14 +07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-09-11 03:31:00 +07:00
|
|
|
|
2026-09-11 05:51:11 +07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-09-15 20:11:09 +00:00
|
|
|
|
|
|
|
|
|
2026-09-11 03:31:00 +07:00
|
|
|
|
2026-10-07 23:06:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-09-11 05:51:11 +07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-09-11 03:31:00 +07:00
|
|
|
|
2026-10-02 22:46:24 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-09-11 05:51:11 +07:00
|
|
|
|
2026-09-11 03:31:00 +07:00
|
|
|
|
2026-09-11 05:51:11 +07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-09-11 03:31:00 +07:00
|
|
|
|
|
|
|
|
|
2026-09-11 05:51:11 +07:00
|
|
|
|
|
|
|
|
|
Resolve and launch npm .cmd shims through cmd.exe
Both the resolver and the spawner were hard-coded to .exe, so
npm-installed agents were undiscoverable and unlaunchable: npm leaves
only a `name.cmd` shim on PATH with the real binary buried under
node_modules. Discovery is now PATHEXT-aware — per directory,
extensions in PATHEXT order, limited to what we can launch (.com,
.exe, .bat, .cmd) — and overrides accept batch shims that exist on
disk, so availability and launches agree.
Resolved .cmd/.bat scripts spawn through `cmd.exe /d /s /c` with
cross-spawn-style per-argument escaping: the shim is the only
interpreted layer, agent arguments stay literal (spaces, backslashes,
quotes, unicode, cmd metacharacters round-trip verbatim — proven by
re-invoking a real program through a shim fixture), and Job Object
ownership covers the whole tree through cmd.exe's membership. The
codex node_modules vendor special-case is deleted: it searched the
wrong vendor subdirectory (`bin/` instead of `codex/`), and its
fixture encoded that wrong layout, so CI passed while real npm
installs failed. GUI launches additionally backfill %APPDATA%\npm,
%LOCALAPPDATA%\{pnpm,Programs\nodejs}, scoop shims, and
%USERPROFILE%\{.local\bin,.bun\bin} from PATH.
opencode and cursor resolution migrate off raw $HOME to the shared
USERPROFILE-aware home helper; cursor also probes
%LOCALAPPDATA%\cursor-agent. The engine catalog and login tests use
the real npm shim layout, batch-override harness tests assert safe
launch instead of rejection, and the shell-script fixture suites are
gated to Unix where they actually run.
2026-09-11 16:49:14 +07:00
|
|
|
|
2026-09-11 03:31:00 +07:00
|
|
|
|
|
|
|
|
|
2026-09-11 05:51:11 +07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-09-11 03:31:00 +07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-09-11 05:51:11 +07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-09-11 03:31:00 +07:00
|
|
|
|
2026-09-11 05:51:11 +07:00
|
|
|
|
2026-10-07 23:06:18 -07:00
|
|
|
|
2026-09-11 05:51:11 +07:00
|
|
|
|