0
Fork 0
mirror of https://github.com/zeronsh/comet.git synced 2026-11-16 18:57:19 +00:00
Commit graph

124 commits

Author SHA1 Message Date
Wing
b592c3b067 Merge remote-tracking branch 'origin/zeron/zgx' into zeron/stable-zgx
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-11-11 13:50:49 -07:00
Wing
fbb89b20a4 ci: run restart_hook (an engine freed after shutdown) on pull requests
The engine-graph leaks fixed in 1a7dc2e49 went unseen because CI never
ran local_first. restart_hook fails if either hold comes back (checked:
it fails with the strong hook, and with the plugin host kept), runs in
under a second, and needs no services. It stays its own binary: the hook
it checks is process-wide.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-11-11 13:50:05 -07:00
Wing
f9b6a0578f The macOS bundle version only ever goes up: a release is <x.y.z>.9999
A beta's CFBundleVersion is <x.y.z>.<n>; the release's was plain <x.y.z>,
below its own betas (0.2.139.7 > 0.2.139). LaunchServices takes the highest
of several copies of one bundle id, and a retired bundle can linger. The
release is now <x.y.z>.9999, above every beta of its version and below the
next version's first; a beta's number must stay below 9999, and the build
checks the value.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-11-11 13:22:03 -07:00
Wing
1b8bdfbd49 Merge zeron/zgx d3adab233 into zeron/stable-zgx
The conflicts were the engine's Luau NDEBUG fix arriving twice (stable-zgx
took it on its renamed scripts and the shared zgx-build.yml; zeron/zgx on
the old names and zgx-beta.yml's inline jobs): stable-zgx's text kept.
windows.rs: stable-zgx's version folders with zeron/zgx's DisplayVersion
guard (refresh_installer_version takes the installation). apps/zgx's
windows-sys features are both sides'.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-11-11 13:04:17 -07:00
Wing
83921289e4 Android's core check reads the ABIs just built, and a missing one fails it
It read every libzeron_mobile.so under jniLibs: an ABI left there from
an earlier development build (asserts on, never packaged: abiFilters)
failed a published build. And a library that wasn't there passed. Now
it's each of ZERON_ANDROID_ABIS, as the build had them, and each must
be there.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-11-11 11:43:50 -07:00
Wing
eb7d96ca96 Published mobile cores run Luau without its asserts, and each build checks it
The mobile core links Luau (zeron-visual's, through mlua and luau0-src),
and nothing set LUAU_CXXFLAGS for it: TestFlight's and the App Store's
cores and Android's published ones kept Luau's asserts, about a fifth of
script time. Now a mobile-dist build (scripts/ios/build-core.sh for a
Release configuration; scripts/android/build-core.sh with
ZERON_ANDROID_PROFILE=mobile-dist, android.yml off pull requests) builds
the library with LUAU_CXXFLAGS=-DNDEBUG. A development core (mobile)
keeps them, and so does iOS's host uniffi-bindgen: the flag is on the
library's build alone (through build-core.sh's env -i), so switching
configurations doesn't rebuild Luau for the host.

Each refuses a published library with the asserts, by what LUAU_ASSERT
keeps when they're on (Luau/Common.h: __FILE__): each Luau source file's
path, VM/src/l*.cpp, as the release engine's packages check.
build-core.sh's library build for a Release archive (mobile-dist,
aarch64-apple-ios, its env -i), here: 45 such paths in
libzeron_mobile.a without the flag, none with it (no luau0-src path at
all); the check fails the first and passes the second. Android's .so
(cargo ndk) has no NDK here to build with.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-11-11 11:39:52 -07:00
Wing
3fc34ad298 Windows CI builds the app as its package does; the beta scripts say what engine they take
windows.yml builds `-p zeron` and then runs package-windows.ps1, which
builds it again with LUAU_CXXFLAGS=-DNDEBUG: Luau and all that links
mlua were built twice. The step takes the same flag. And the beta
scripts' usage says the engine they're given must be built with it, as
the check now holds: a stable release's engine from before isn't.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-11-11 11:23:56 -07:00
Wing
3adca33221 Release engines run Luau without its asserts, and each package checks it
The engine links Luau (mlua's luau0-src: visuals, plugin services) and
was built from the root, where nothing sets LUAU_CXXFLAGS: its Luau kept
its asserts, about a fifth of script time. LUAU_CXXFLAGS=-DNDEBUG now
goes on the builds of a release's engine, not a root .cargo/config.toml,
so test and development builds keep them:

- zgx-beta.yml: each job's "the engine, from this commit" step (macOS,
  Linux, Windows' whole zeron.exe).
- release.yml's engines, which the packaging scripts build themselves:
  package-linux.sh's release build, package-macos.sh, package-windows.ps1
  without -BetaVersion (so a local package is right too).

Each package refuses an engine with them. The engine has no zgx-script,
so not the app's warning; instead what LUAU_ASSERT keeps when asserts
are on (Luau/Common.h: #expr, __FILE__): each Luau source file's path,
VM/src/l*.cpp, either separator. The workflow's engine build, exactly,
here: 36 such paths without the flag, none with it (no luau0-src path at
all); the check fails the first and passes the second. A debug package
(package-linux.sh PROFILE=debug) is left alone: luau0-src turns asserts
on in any debug build.

Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>

On stable-zgx (cherry-picked from d1bf8d327): the engine steps are
zgx-build.yml's, which release.yml's stable and zgx-beta.yml's beta both
call, so the flag goes there, and zgx-beta.yml is stable's as it was;
release.yml's old-app jobs build their engines in the packaging scripts.
package-zgx-beta.sh is package-zgx-macos.sh, and Windows' engine for the
zgx app is -ZgxEngine.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-11-11 11:23:29 -07:00
Wing
bda804a123 Windows CI builds the app as its package does; the beta scripts say what engine they take
windows.yml builds `-p zeron` and then runs package-windows.ps1, which
builds it again with LUAU_CXXFLAGS=-DNDEBUG: Luau and all that links
mlua were built twice. The step takes the same flag. And the beta
scripts' usage says the engine they're given must be built with it, as
the check now holds: a stable release's engine from before isn't.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-11-11 11:23:15 -07:00
Wing
d1bf8d327d Release engines run Luau without its asserts, and each package checks it
The engine links Luau (mlua's luau0-src: visuals, plugin services) and
was built from the root, where nothing sets LUAU_CXXFLAGS: its Luau kept
its asserts, about a fifth of script time. LUAU_CXXFLAGS=-DNDEBUG now
goes on the builds of a release's engine, not a root .cargo/config.toml,
so test and development builds keep them:

- zgx-beta.yml: each job's "the engine, from this commit" step (macOS,
  Linux, Windows' whole zeron.exe).
- release.yml's engines, which the packaging scripts build themselves:
  package-linux.sh's release build, package-macos.sh, package-windows.ps1
  without -BetaVersion (so a local package is right too).

Each package refuses an engine with them. The engine has no zgx-script,
so not the app's warning; instead what LUAU_ASSERT keeps when asserts
are on (Luau/Common.h: #expr, __FILE__): each Luau source file's path,
VM/src/l*.cpp, either separator. The workflow's engine build, exactly,
here: 36 such paths without the flag, none with it (no luau0-src path at
all); the check fails the first and passes the second. A debug package
(package-linux.sh PROFILE=debug) is left alone: luau0-src turns asserts
on in any debug build.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-11-11 11:15:12 -07:00
Wing
007318d882 Merge remote-tracking branch 'origin/zeron/beta-luau-ndebug-on-stable' into zeron/stable-zgx
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-11-11 11:14:21 -07:00
Wing
7f01dad0f6 The beta channel carries every zgx release; beta downloads stay on it
A stable release of the zgx app is also published to the beta feed when it's
newer than the beta there, so the website's beta downloads get each stable
release with no action. The zgx app follows the channel on record on Windows
and Linux too (as on macOS), so those installs stay on beta afterwards
rather than dropping to stable.

Windows: every zgx release keeps its files in beta\<version>, the name the
betas in the field check a package for; with a per-channel folder they
couldn't have installed a stable release from the beta feed. A package also
brings its feed: an install the old app's updater moved here switches from
the GitHub release to the edge's feed (stable at its root, beta beside it),
which release.yml now writes into the package.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-11-11 11:00:08 -07:00
Wing
3f95513e32 Merge zeron/beta-luau-ndebug into zeron/stable-zgx: Luau's NDEBUG for every zgx package
The conflicts are stable-zgx's renames on the same lines (BETA_VERSION
to ZGX_VERSION, $BetaVersion/$BetaEngine to $ZgxVersion/$ZgxEngine,
package-zgx-beta.sh to package-zgx-macos.sh): resolved as stable-zgx's
text with the fix applied to it, the same 28 lines.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-11-11 10:57:18 -07:00
Wing
96a5e4b728 The Linux and Windows zgx builds take Luau's NDEBUG, and each package checks it
Cargo reads .cargo/config.toml by where it runs, not by --manifest-path.
LUAU_CXXFLAGS=-DNDEBUG is in apps/zgx/.cargo/config.toml (the root has
none), and package-linux.sh and package-windows.ps1 built apps/zgx from
the root: the Linux and Windows betas ran Luau with its asserts, about a
fifth of script time, and since zgx 06c6d56ac warned of it on every
script load. package-zgx-beta.sh builds from apps/zgx, so macOS's was
right.

Both now build from apps/zgx, as macOS does. Their target is the one
they used (apps/zgx/target: Linux's paths absolute as before, Windows'
`target` from apps/zgx); the binary each reads afterwards, and the
package, its checks and uploads under target/package, are where they
were. The engine's builds, steps of their own, are untouched.

Each of the three packages refuses an app built with the asserts: zgx-
script compiles its warning about them ("Luau was built with its
asserts", crates/zgx-script/src/lib.rs) into the binary only under
cfg(all(luau_asserts, not(debug_assertions))), the cfg its build script
sets from the same LUAU_CXXFLAGS that Luau's C++ is built with.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-11-11 10:56:26 -07:00
Wing
6bf634308b Stable releases ship the zgx app, installable by every shipped Zeron
release.yml builds the zgx app through zgx-build.yml, the build zgx-beta.yml
now shares, and keeps the old app behind `app: gpui` / STABLE_APP for a way
back. Its manifest says minimumMacOS 13.0, which shipped updaters honour.

Windows: the old app's updater installs only zeron-<v>-windows-<arch>.exe.
That zeron.exe now completes its own install on first start: it fetches the
release's zip from its feed (checksum from the feed's manifest), unpacks its
version's folder (app\<v>\, a beta's beta\<v>\), and offers Retry on failure.
Its later updates come as the zip on every channel.

Linux: zgx's libdbus is linked in (libdbus-sys vendored), so `zeron
headless` on servers and Cloud machines needs no library the old app didn't;
the build checks that.

zgx-beta.yml's manifest gave stable's engine version; it's the beta's own.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-11-11 10:47:23 -07:00
Wing
c2b03c014f zgx: every apps/zgx test passes, the known-failures list empty
Each failure fixed at its cause; none skipped or ignored.

A test fixture's bug:
- shell_fixture set the sidebar's grouping to one list and, later, back to
  project: each reload replayed both, the sidebar still showing crossfaded
  its list out and took the keyboard from its row before the reload could
  keep it (palette_focus_tests' save). Set once, to what it stays. (zgx
  took the focus trail after the load: reported with a repro, zgx #2011.)

Stale tests, the app having moved on:
- Opening a chat gives its composer the keys (c865bf3be): the focus, menu,
  palette and shell tests put the keyboard back on the sidebar row before
  Shift+F10 or ⌘K (focus_tests::keys_on_row).
- Work in's Device row is a submenu row (f5c307863), `@` opens the
  launcher (#mention-popover), and zgx-desktop closes popups and puts the
  window at the back in one event: popups, split tests.
- About's toast and link menu are there; the test runner's tree() stops at
  200 lines, which the page fills: asked for directly.

Tests that took a Mac's keys for every platform's: the history keys
(⌘[ ⌘] or Alt+←/→), the key labels (⌘X or Ctrl+X, ↵ or Enter, …), and
Appshots' ⌘ (`meta`).

Flaky under load, now deterministic:
- A large diff's memory test runs with room per call (30 s): the lexer
  over 8,000 lines came past a debug build's 500 ms with the machine
  loaded past its cores. Its memory limit is as it was.
- A plugin's picture is counted by its path, not by any connection to the
  port: another test's may reach a port reused.

Linux CI: lavapipe (mesa-vulkan-drivers) so visuals' shaders render; with
no GPU at all, the test checks the shader says so and the scene still
draws. scripts/ci/test-zgx.sh runs with an empty list on macOS's bash.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-11-11 02:04:24 -07:00
Wing
51b0e1dc43 Merge zeron/zgx into the Cloud, relay and GitHub work
Conflicts resolved:
- Engine checkpoints: zgx's upload in parts now carries the relay layer's
  atFloor/heal flags and hands the edge's refusal back to the relay state.
  The engine's own size cap follows the room's (256 MB in parts), so a long
  chat's checkpoint isn't held back before it's sent.
- Attachments: zgx's local copies of another device's uploads, rewritten with
  the app-capture attribute escaping.
- zgx app: zgx's composer, mention sections, link chips and remote harness
  retries, with the Cloud machine notices, held messages and turn states on
  top; v2 template base re-recorded.
- Linux packaging: zgx's beta packaging, keeping the fat-LTO engine build.
- apps/zgx Cargo pins: zgx's.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-09 23:21:27 -07:00
Wing
e0365a26ea Plugins launch: one SDK everywhere, zgx tests in CI, install.sh guards ~/.zeron
- A4: re-copy apps/zgx/plugins-sdk/zeron.luau into all 14 copies (git,
  github, parallax-scenes, 11 plugins-dev examples); 12 lacked the agents
  block, all lacked the "project" context fix. examples_tests
  `sdk_copies_match_canonical` checks them byte for byte. The beta packaging
  (macOS, Linux, Windows) stamps the canonical SDK into each shipped builtin,
  so builtins can't ship a stale one. Builtins aren't signed (the engine scans
  them as Zeron's own), so nothing to re-sign.
- A6: a `zgx` CI suite (zgx-tests.yml, planned by scripts/ci/plan.py): apps/zgx
  unit tests and the Luau UI tests (`zgx test ui`, CLI at the pinned rev) on
  macOS and Linux, plus the engine's plugin tests on macOS. Known failures
  (10 Rust, 2 Luau About tests) live in scripts/ci/zgx-known-failures.txt;
  anything else fails. core-tests also runs engine tests/plugin_services.rs.
  No Windows job yet.
- B13: plugins-dev/install.sh refuses ~/.zeron as well as ~/.comet-native
  (and anything under them, symlinks resolved); its default is every example.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-09 16:26:20 -07:00
Wing
aec924c131 Relay: old clients no longer hold a chat or an account back
One old app anywhere on an account kept every chat on stored rows, and a rollout
had to wait out a 14-day window to see them all. A chat now goes to generation 3
whatever else is on the account. Old clients read that as a chat2 room as they
always have, and when one opens a chat the room tells its host, which stores for
as long as it's there. So storage is paid per chat, only while an old client has
that chat open.

With nothing left to gate, the rollout has one control: CHAT_RELAY_LAYER on the
edge, for everyone or a list of user ids. Engines run the layer by default and
follow the room's answer, with ZERON_RELAY_LAYER=0 as a kill switch. Gone: the
registry's list of old clients, the account-wide rule, and CLOUD_RELAY_LAYER.

The smoke test proves it against shipped v0.2.138, v0.2.137 and v0.2.116.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-09 00:46:21 -07:00
Wing
09347e434b Merge zeron/relay-layer 2026-11-07 19:49:40 -07:00
Wing
d2caa1a1ca Dev app: pass ZERON_RELAY_LAYER through to the engine
So a dev or staging app can run the relay layer (rollout step 3).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-07 19:49:38 -07:00
Wing
d0c49fc2c6 Merge zeron/cloud-update-wake-speed 2026-11-07 19:36:35 -07:00
Wing
279a985854 Merge main into zeron/relay-layer
The room's checkpoint upload now takes parts (main) and applies the relay
layer's rules (stale refusal, floor coverage, heal) to both the whole and
the staged commit, before reading the body.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-07 17:38:02 -07:00
Wing
582367628b Build the Linux release with fat LTO in one codegen unit
zeron goes from 205 to 172 MB (16% less; the tarball 103 to 90 MB), with the
same start-up: a median engine boot of 387 ms both ways (n=20 each), --version
5.3 vs 5.7 ms. A Cloud machine copies the binary back in on every wake, so its
size is wake time. The release was already stripped, with no debug info to
split; opt-level stays 3. It costs about 60% more build time, so only the Linux
package does it: macOS and Windows keep theirs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-07 01:55:54 -07:00
Wing
fe911e0fc4 Two-engine smoke: a whale chat, a rejected push; design doc for the review fixes
With the layer on, a chat over the relay limit (64 KiB in this debug run) stays on
stored rows after its first save and after its host restarts. With it off, a
message too big to store reaches the other device by checkpoint, and so do the
turns after it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-07 00:41:27 -07:00
Wing
e1f62fb5be Merge zeron/zgx into the beta branch
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-11-06 19:53:24 -07:00
Wing
f6d5d06334 Provider update rig: isolated and runnable on Linux
Every provider but the target is pinned away: discovery searches /usr/local/bin,
and the engine checks every provider before the rig can disable any. npm comes
from the registry, since a distribution's can't be copied, and without its builtin
config, which says prefix=/usr/local. system_git only checks, as the README says.
pnpm lives where pnpm setup puts it on each system. Adds Linux results, and repairs
the README's double-encoded punctuation.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-06 23:50:37 +00:00
Wing
a9883e5866 Add the relay layer behind flags that default off
Gen-3 chats relay their host's ops instead of storing them. Delivery over the
room or a direct WebRTC link is a hint, and version exchange finds and fetches
whatever was missed. A separate offline queue holds messages for a host that
isn't there until it has saved them. Cloud hosts also post checkpoints.

With CHAT_RELAY_LAYER and ZERON_RELAY_LAYER unset, hello is byte-identical, the
room answers new frames as unknown types, no queue table exists and no engine
state or stream service is created.

Nothing deletes existing rows: the queue is its own table, and relay-era
checkpoints prune nothing. Old clients get a current checkpoint and stored rows
while they're around, and anything queued moves into rows they can read.

Mobile isn't part of this, so a phone seen in the last 14 days keeps its
account's chats on stored rows.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-06 13:32:39 -07:00
Wing
36e15cc671 Provider updates on Windows: Scoop updates its app, WinGet one package
Proven on WING-PC with the rig's Windows rows, before (zeron/zgx) and after:

- Scoop 0.6 names its receipt scoop-install.json (install.json before),
  so no Scoop install's bucket could be read and every check failed.
  Read either, the newer first.
- `scoop update` went through shims\scoop.cmd, which turns each `"` in its
  arguments into `'`; Zeron always quotes a batch file's arguments, so
  Scoop was asked for 'update'. Run the root's scoop.ps1 with -File, as
  the shim does.
- `winget upgrade --id` matches by substring (SST.opencode also matches
  SST.OpenCodeDesktop): pass --exact, as `winget show` and the manual
  command already do.
- A Claude-from-npm test needed npm on the machine's PATH: it brings its
  own prefix and npm. MovingHarness is Unix-only, like its one test.

The rig's Windows rows run through windows-row.ps1 (own port, data dir,
PATH, USERPROFILE, APPDATA, LOCALAPPDATA; every provider pinned), and the
README records what running them by hand trips on and the Windows results.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-06 12:25:15 -08:00
Wing
89a18dcfe6 Provider updates: Scoop is told its root; a rig that proves each owner
`scoop update` finds its root by `SCOOP`, so a Scoop installed anywhere
but `~\scoop` is now told which one it is.

scripts/provider-update-rig runs the real zeron-engine on a throwaway
port, data dir and HOME, with a Finder-like PATH, against sandboxed npm,
pnpm and bun installs of a real package and fakes for the rest, and
prints every phase of a check and an update with its time. Its README has
the macOS results before and after, and the steps for Linux and Windows.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-06 02:51:23 -07:00
Wing
9929004dd7 zgx beta: its engine carries the beta's version
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-11-05 21:53:29 -07:00
Wing
dd55507797 zgx beta: the engine comes from the same commit
A beta tests what's next, the engine too. It compiles the engine from its own
commit on every platform, rather than downloading the latest stable release's.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-11-05 19:02:52 -07:00
Wing
f4f9699fd1 Merge zeron/zgx into zgx/beta-all-platforms for beta.16
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-11-05 14:09:23 -07:00
Wing
cd0ec07d46 The new app icon on macOS, Windows and Linux
macOS gets a Zeron.icon that follows the system's looks on macOS 26 and later,
with an icns for earlier versions and the dmg. Compiling it takes Xcode 26.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-11-05 14:07:47 -07:00
Wing
26f72b06ee Merge commit 'bb587f735c' into HEAD
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-11-05 03:31:05 -07:00
Wing
4c08b1d1b7 zgx: mimalloc's pages at the Mac's page size, and the beta built with its flags
A long session frees most of what it allocated and what survives is scattered,
and a page goes back to the system only when all of it is free. At rest after
the same long session, 64 KiB pages left 259 MB dirty and 16 KiB pages 188 MB,
for the same memory in use (M5 Max).

scripts/package-zgx-beta.sh built from the repository's root, where cargo does
not read apps/zgx/.cargo/config.toml. So betas built that way were missing its
LUAU_CXXFLAGS=-DNDEBUG too, and with it about a fifth of script speed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 5a068e4ae6)
2026-11-05 03:28:28 -07:00
Wing
edcb78ebf1 zgx beta: Linux and Windows
Linux (x86_64, aarch64) and Windows (x86_64) beside macOS: the zgx interface and
the latest stable's own engine, by checksum, with stable's artifact names but
the beta's version. Windows has no standalone .exe, which can't run alone.
Every key stays under beta/, the manifest last, listing every platform's files.
A run by hand can pick platforms.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-11-03 22:32:26 -07:00
Wing
40183b9337 zgx as a beta channel of Zeron.app; shared CLI, launch and notify crates; update channels
- Update channels (stable/beta) with semver prereleases, cross-channel installs, ZeronEngineVersion and a macOS 13 floor for beta; "Get beta updates" in the current app's Check for Updates.
- The command line moves into crates/cli and engine start-up into crates/launch, shared by the current app, zeron-engine and zgx; zgx hands engine commands to the bundle's Zeron Engine helper.
- zgx beta packaging and .github/workflows/zgx-beta.yml (beta-v* tags, gated by ZGX_BETA_ENABLED); the separate Preview packaging is removed.
- Templates install from links with updates, an Unverified badge for unknown authors, the Archived settings page, the Cloud repository picker, palette sub-steps without scope tabs.
- Git plugin refreshes on file changes; GitHub plugin batches, tiers and throttles its polling; failed PR watches retry with backoff.
- zgx f81d5e99.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-03 00:57:33 -07:00
Wing
2d63bdb2ab zgx: Zeron's interface on zgx (app, design system, plugins, onboarding, Zeron Preview)
A new desktop app in apps/zgx: Zeron's interface written in Luau on zgx,
its design system, built-in plugins (Git, GitHub, Parallax scenes) and
theme templates, plus the engine and edge work it needs (plugin services
and agent tools, the agent registry, project icons, profile, organisation
admin, onboarding, plugin signing keys) and a separate Zeron Preview
package and workflow (preview-v* tags, off until enabled).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-02 22:37:18 -07:00
Daniel Katulevskiy
2500e8b34f
CI: one entry workflow with admission, reuse, priority/locks and a fast pull request tier (#1077)
* CI: one entry workflow with run admission and a fast pull request tier

Pull request checks took a median of ~3 hours from push to done, and ~110
minutes of that was jobs waiting for a runner. Each push asked for ~207
runner-minutes on 15-20 jobs, almost all of it compiling, so bursts of
pushes queued hundreds of jobs and every run held a few runners while the
rest of its jobs waited behind other runs.

- ci.yml is the only pull request / main / merge queue entry point. `plan`
  picks the suites a change needs; `admit` waits until every runner the
  run needs is free, then all its jobs start together and each runner is
  released when its job ends (scripts/ci/admit.py, first come first served
  with conservative backfilling, state read from the Actions API so fork
  pull requests work). `CI result` is the one check to require.
- Pull requests get a fast tier: Windows, macOS, voice and Android run only
  when the change looks platform specific (their files, platform
  conditionals or APIs in changed code); `ci:full` or CI_PR_TIER=full runs
  everything. Main and the merge queue run the full tier.
- Voice: 14 `cargo test` builds capped at 2 jobs (~40 min) become core-tests
  additions plus one nextest build for audio and the mobile voice core; the
  workflow no longer runs uncancelled on every push or saves caches from
  pull requests.
- Windows: three test jobs become one nextest build; one shared cache
  instead of four (~4.5 GB of the 10 GB repository cache).
- Linux UI and browser share one job and cache; edge coordinator and vault
  share one job; the macOS app is built with the test dependencies instead
  of a `cargo check` that recompiled everything; iOS no longer waits for
  the frame-source job, which only runs when the GPUI pin can change.
- Only main saves Rust caches.

* CI admission: cap reservations read from other runs, expire unseen ones

A pull request can edit its own ci.yml, so the reservation in its admit job
name is untrusted. Cap it at the largest plan.py makes, and stop counting an
admitted run's never-created jobs 90 minutes after admission, so one run
cannot hold more than a full run's runners or hold unused ones for long.

* CI: reuse passes on unchanged inputs; ci:priority, ci:lock and an emergency workflow

Reuse. plan fingerprints every suite's inputs in the tree under test (the
merge with main for pull requests): workspace manifest, lockfile, toolchain,
CI files, the suite's workflow and non-Rust files, and for Rust suites the
packages it tests plus every workspace package they depend on, plus any file
outside those that their sources name with a ../ path (scanned every run).
Every job records its pass in the Actions cache under that fingerprint as its
last step; a suite whose jobs all passed is skipped and reserves nothing, and
single Windows and voice jobs are skipped on their own. Pull requests trust
their own passes and main's; main and the merge queue trust only main's;
ci:full and manual runs reuse nothing. Callers are split per suite so each
records under its own fingerprint.

Priority and locks (labels, so triage or above). ci:priority puts a pull
request's runs at the front of the admission queue; ci:lock keeps a full
run's runners out of everyone else's budget while the pull request is open
(until unlabelled, merged, closed or CI_LOCK_HOURS), and admits its runs
first. Runs name their pull request in the admit job; the claim counts only
when that pull request's head is the run's commit. ci-emergency.yml (write
access) locks a pull request, cancels the other pull requests' CI runs and
re-runs its own if needed.

* CI reuse: fail closed

The merge queue, the last gate before main, reuses nothing. A pull request
that changes a Rust build file no selected suite's fingerprint covers reuses
nothing. Sources that build a path from CARGO_MANIFEST_DIR's parent in code
make their suite read the whole workspace. concat!(.., "/../x") paths and
.cargo/ count as inputs.

* CI result: fix the result listing (shell quoting)

* CI: run less on pull requests, more on schedule, and merge tiny test binaries

Measured in CI, test execution is a small part of every job; compiling and
starting jobs that run little is the cost. So:

- Voice: only the audio stack (zeron-audio, which nothing else builds yet)
  and the packaged Windows media runtime remain, for their own files. The
  mobile voice/orb tests were a subset of ios-core, the macOS/Windows
  `cargo check` of harness+engine duplicated the platform builds, and the
  voice-media tests join the Windows nextest build.
- Fast tier gating of jobs and steps to their own files: Windows packaging
  (`app`), the iOS simulator tests and their bindings, the Linux and macOS
  browser/preview fixtures. Android builds the APK on pull requests for the
  app, the FFI crate and dependency changes; the iOS mobile-core paths come
  from zeron-mobile's Cargo closure. Gated jobs and optional steps are part
  of the reuse fingerprint.
- GPUI frame-source runs only when the pinned zui revision moves.
- Version bumps (only `version = "..."` lines in Cargo.toml/Cargo.lock)
  select nothing and are left out of fingerprints.
- nextest `ci` profile for pull requests and main leaves out the slow/soak
  tests (48-chat and real-quantum doc_host sync, the codex dying-server
  backoff, preview leak, two sleep-bound discovery tests); the cursor_shim
  stress test runs 14 rounds (ZERON_STRESS_ROUNDS, 100 by default). Preview
  discovery tests run one at a time (fixed port).
- Nightly ci.yml schedule runs everything in full; weekly-tests.yml runs the
  engine integration binaries and crate tests no workflow ran.
- Linux core no longer builds the 8 test binaries that run nothing there
  (Windows-only or all-#[ignore]d). The small harness, engine and preview
  integration suites move into one `tests/misc` binary per crate. The orb
  geometry tests move to zeron-orb (they tested its re-export); the
  assertion-free microbenchmark is dropped. The macOS app builds with the
  tests instead of rebuilding zeron-ui without the fixture feature.

* CI: pass the nextest config to the build-only steps too

NEXTEST_PROFILE=ci names a profile from scripts/ci/nextest.toml; the macOS and
Windows `--no-run` builds did not load that file, so nextest refused the
unknown profile.

* Engine: keep the git identity setup inside the home it is given

configure_git_identity pinned HOME but inherited XDG_CONFIG_HOME, and
`git config --global` writes $XDG_CONFIG_HOME/git/config when that file
exists. With a sandbox or test home, the identity landed in the developer's
real git config: running the engine tests on a machine with XDG_CONFIG_HOME
set replaced the user's name and email with the test's. An XDG_CONFIG_HOME
outside the given home now gives way to the home's own, and the test pins it
for its own git calls too.

* CI: iOS simulator tests in parallel with ios-core; Windows UI tests side by side

- The C header and module map the simulator tests link are committed in
  apps/ios/CoreFFI (outside Xcode's synchronized folders) and refreshed by
  scripts/ios/build-core.sh like the Swift bindings; ios-core checks all
  three are current. ios-tests no longer waits for ios-core's artifact, so
  the iOS path is one job long instead of two.
- The simulator core for the unit tests builds in the dev profile, not the
  optimized `mobile` profile the app ships.
- Windows runs zeron-ui's tests side by side: nextest gives each its own
  process, so the in-process `--test-threads=1` restriction no longer applies.

* CI admission: budget defaults at the organization's runner limits

20 jobs in total and 5 on macOS (the organization's concurrency limits), and
at most 10 on Windows so Linux keeps half the pool. The repository variables
still override them.

* CI: skip the browser steps when the Linux setup failed

They run after a failed UI test on purpose (a separate signal), but without
the system packages (an apt mirror stall) they can only fail too.

* CI: retry the WebRTC terminal path test (a known race)

remote_terminals' network-change test asserts no keystroke goes through the
relay once the path reports Direct; in a loaded run one did. Retried like the
other timing-sensitive tests in nextest.toml until the race is fixed.

* Fix two races that failed CI on loaded runners

- Muse: a crash usually shows first as "Muse stdout closed", racing the
  process exit; `try_wait` lost that race under load and users got the bare
  protocol error instead of "Muse exited unexpectedly" with Muse's last
  stderr lines. Wait up to 250 ms for the exit, as the Pi driver already
  does (a_crash_mid_turn_reports_muses_last_words failed this way).
- Remote terminals: a subscription reported TerminalPath::Direct before
  attaching the direct writer, so a keystroke typed by whoever saw Direct
  could still go through the relay (a_terminal_rides_a_real_webrtc_pair_
  through_a_network_change failed this way). Report Direct once writes
  ride the link. The CI retry for that test goes.

Both tests pass 25 runs in a row under CPU load.

* CI reuse: count only the CI files a suite runs

Every suite's fingerprint included all of scripts/ci and the composite
actions, so a change to the planner or the scheduler (which decide what runs,
not whether it passes) re-ran every suite. Each suite now counts the CI files
it executes: nextest.toml and the Linux or Windows setup for the Rust suites,
test-core.sh for core, the macOS fixture runner for macOS, apt-install.sh for
the installer. ci.yml still counts for all.

* docs: changing the fingerprint inputs reruns everything once

* CI admission: no circular waits

Two ways admission could deadlock (until the fail-open timeout):

- Each waiting run counted every other waiting run's admit job as a busy
  runner, including runs queued behind it. With a full run (16 of 20) at the
  head and five or more waiting behind it, the head waited for their runners
  and they waited for it. A run now counts only the admit runners ahead of it.
- Two ci:lock labels each reserved 16 of 20 runners and counted the other's
  reservation, so neither locked pull request (nor anyone else) could start.
  Locks are now ordered by when their label was added: an older lock ignores
  a newer one's standing reservation.

Every wait now points forward in one order, so no cycle can form. A test
simulates 3000 random queues (sizes, priority, overlapping locks, polling
order) and checks they all drain; the previous scheduler deadlocked in 309.
The fail-open timeout drops from 5 h to 2 h as the backstop for the one case
outside the model (waiting admit jobs taking every runner in the pool).

* CI admission: waiting admit jobs yield when they starve the pool; ignore runs that never take their turn

Waiting costs a hosted runner from the same pool as the suites. With about
20 runs waiting, their admit jobs held the whole pool, admitted runs' jobs
got no runner, and nothing moved until the 2-hour fail-open. When an
admitted run's Linux or Windows job has queued 10 minutes, every running
admit job but the first quarter of the budget now starts its run without a
reservation, giving its runner back. A new test models GitHub's runner pool
as well as admission: without yielding most 30-run queues never drain, with
it all 200 do.

A reservation read from another run is not trusted, but a run whose edited
admit step never finished still held everyone behind it for 2 hours (and a
fake admitted run held a full run for 90 minutes). A waiting run that could
have been admitted for 3 minutes but still waits is now ignored, and an
admitted run's jobs that have not appeared 10 minutes after admission stop
counting, except the late result and publish jobs.

Polling backs off further from the head of the queue (5 min, 10 min under
400 requests left): the GITHUB_TOKEN quota is shared with releases, the
Cursor SDK update and CI emergency.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>

* CI: voice and the Linux browser fixture nightly only; forks reuse only main's passes

Over two weeks the voice jobs left after the move into core-tests (AEC3
and the packaged Windows runtime) never failed, and the Linux browser
fixture's failures were window-timing flakes and package downloads. Both now
run nightly, on manual runs and with ci:full. The zeron-ui tests stay on
every change: 2,046 tests in 29 s, and the only check that caught one real
regression in that window.

A fork's earlier runs could save a pass entry for the fingerprint of a
later, clean-looking commit, so its suites would be skipped and the pull
request would still show a green CI result. Until the merge queue (which
reuses nothing) is the required gate, forks reuse only main's passes;
CI_FORK_REUSE=own turns their own back on (ci.yml passes it to plan in the
workflow commit that follows).

Docs: admission's new yield and unresponsive-run rules and polling.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>

* Engine: keep the user's own XDG_CONFIG_HOME when the git identity home is theirs

The XDG_CONFIG_HOME guard replaced any XDG_CONFIG_HOME outside `home` with
`home`'s. When `home` is this process's own, that hid an identity the user
keeps in an XDG_CONFIG_HOME elsewhere, and the machine identity went into
~/.gitconfig, which wins over it. It now only applies to a sandbox or test
home.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>

* CI workflows: Android gets only its own secrets, on pushes to main; CI_FORK_REUSE

secrets: inherit gave android.yml every repository secret, and the merge
queue (code not on main yet) would have signed with the release keystore.
ci.yml now passes the four signing secrets and the R2 token by name, on
pushes to main only; pull requests and the merge queue use the debug key,
as forks always did.

Also: ci.yml passes the CI_FORK_REUSE variable to plan, and the comments in
ci.yml, voice-tests.yml and ui-tests.yml say voice and the Linux browser
fixture run nightly.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* CI: test-core also runs main's crates/doc/tests (attachments_roundtrip is among them)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Wing <44917547+wingleeio@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-11-01 15:51:25 -07:00
Chance
6973500bc0
Sync: update loro to 1.17 so streaming chats stop leaking memory (#1116)
* Sync: update loro to 1.17 so streaming chats stop leaking memory

loro before 1.17 left another copy of a doc's text in its string arena on
every snapshot export (fixed in loro-dev/loro 089a4e6). chat_persistence
exports a dirty chat each second, so a chat with a streaming agent grew
quadratically until the arena passed 4 GiB and export panicked (#905).

* Sync: upgrade edge Loro and guard snapshot memory growth

Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>

---------

Co-authored-by: gratenes <claude@storage.gay>
Co-authored-by: Wing <44917547+wingleeio@users.noreply.github.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-10-31 11:55:18 -07:00
Alexandre V.L
95b294658f
Claude subagents: give a typed /skill's fork a chip and a tab (#1043)
* Claude subagents: give a typed /skill's fork a chip and a tab

A `/skill` typed as the prompt, when the skill runs in a fork
(`context: fork`), showed nothing while it ran: no chip, no tab, and
the badge and card didn't count it. No tool call starts it. Its
`task_started` carries no tool id, and its messages carry
`forked-command-<name>` and arrive "together and in order after the
forked skill finishes"
(https://code.claude.com/docs/en/headless.md#follow-subagent-messages).
The spawn gate kept them in the journal.

That task start now makes the fork a spawn chip, `Agent: /<name>`, and
the skill's prompt opens its tab. The chip's id adds the task to the
CLI's, which repeats on every run. Until the turn ends, any
`forked-command-*` traffic feeds the chip, and the prompt's echo is
dropped once. The fork's notification comes before that replay, so it
only records the status. The chip settles just before the turn's Done,
or when the driver ends a stopped turn itself. After that the CLI's id
stays in the journal again, and a late frame can't reopen the chip.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Typed-fork-chip demo media for the PR (live stills)

* Claude subagents: a second typed fork settles the first

A turn runs one typed fork, but nothing enforced it: a second task start
before the first settled replaced it, and the first's chip ran on with
nothing left to settle it, counted in the badge for good.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Wing <44917547+wingleeio@users.noreply.github.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-10-26 22:02:38 +00:00
Alexandre V.L
ae1ec6ad8d
Fork: settle the running subagent chips a fork copies (#1045)
* Fork: settle the running subagent chips a fork copies

A fork copies the source's entries as they are, so a subagent still
running there kept a `running` chip in the fork. No run in the fork ever
settles it: the chip and its lanes-card row spun forever (#1001).

The copy now settles it `failed`, like run end and the restart sweep
do. The chip keeps its ref, so it still opens the subagent's transcript.
The source keeps its own.

CI now runs the engine's `side_chats` tests, where the fork tests live.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Fork-settles-subagents demo media for the PR (live before/after stills)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: a fork settles copied questions and running spawn chips

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>

* docs: reflow the ForkSideChat paragraph

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>

---------

Co-authored-by: Wing <44917547+wingleeio@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-10-26 21:53:34 +00:00
Wing
684becf0f8
Android app on the shared Rust mobile core (Material 3 Expressive) (#609)
* Android app on the shared Rust mobile core

A Jetpack Compose app (apps/android) that links crates/mobile through
UniFFI — the same transcript layout engine, text measurement and
virtualization as iOS. The painter draws Rust display lists on a Skia
canvas at Rust coordinates with the same Geist bytes; Minikin backs the
fallback measurer. UI is Material 3 Expressive with Zeron's palette.

Kotlin-only renames in crates/mobile/uniffi.toml avoid clashes with
Throwable.message and AutoCloseable.close.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Android: online hosts first, fade the transcript behind the composer; more screenshots

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Android: composer-first new session, capsule composer, iOS-parity session rows

- New session is the iOS/desktop canvas: harness mark + "What are we
  building?" over a composer card whose chips (project, branch or host,
  model, effort) open Material 3 Expressive grouped menus.
- One shared composer: a resting one-line capsule that becomes a card
  with context chips when focused; no drop shadow; shape-morphing
  send/stop; a Queue/Steer delivery chip while the agent works.
- Session rows show the harness brand mark, project + branch subline,
  Done/Input/Failed status and state-tinted PR badges; small extended FAB.
- Harness brand marks ported from the shared SVG path data.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Android: Zeron's icon set and a Material 3 Expressive shell

- Every glyph is Zeron's own: the desktop icon set (crates/ui/assets/icons)
  plus the iOS tab/tool icons, compiled to VectorDrawables at build time
  (scripts/android/svg2vd.py) — no Material icons left in the UI.
- Expressive shell: display-weight Geist headers (emphasized type scale),
  filter pills with live counts, SegmentedListItem rows with project-toned
  harness tiles, a floating nav capsule + round search button, and the
  New session bar with the live summary (iOS accessory parity).
- Round tonal chrome on the session screen, expressive action menus for
  row / transcript / overflow actions, rebuilt settings and search.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Android: runway, fold/reveal motion, attachments, @ mentions, queue editing

- Own-turn runway (desktop OwnTurnAnchor): an immediate send glides the
  prompt to the top and holds a viewport of room for the reply; a message
  queued behind the live turn takes the runway once its bubble lands.
- Row motion: fold toggles tween 140 ms ease-out, a growing tool group
  reveals over 360 ms expo; rows interpolate from the previous frame.
- Attachments: Photos / Files / Paste image via the system pickers,
  staged as JPEG (long side <= 2560, <= 24 MB, up to 8) with removable
  thumbnails; pending thumbnails in the transcript show a wavy upload
  ring driven by the escort progress.
- @ mentions: file suggestions above the composer; tokens become
  zeron-file links on send (session + new session).
- Queue editing: host lease with renewal, the user's draft stashed and
  restored, only the visible text committed.
- Project picker is a bottom sheet grouped by machine; choice menus are
  one group with a trailing check.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Android: replace all screenshots with the current UI

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Android: chat wallpaper (iOS parity)

The wallpaper hero behind the sessions list and the new-session page:
aspect-filled artwork fading out downward at the opacity the Rust
contrast guard allows (wallpaper_safe_opacity), the new-session composer
softening it, and the list fading it as it scrolls. Effects (dither,
ASCII, halftone, scanlines) run in the shared core (wallpaper_render).
Settings has choose / effect / remove; --es wallpaper <path> and
--es wallpaper-effect set it at launch, like iOS -wallpaper.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Android: flat session chrome, per-chunk streaming veil

- The transcript ends where the composer begins: no gradient scrim, no
  text streaming behind the composer (the runway's viewport was the full
  height, so reply tails ran under it, faded and cramped).
- Header is a flat Material top app bar that takes the container tone
  once content scrolls under it, instead of a gradient cut-off.
- Jump to latest is a small FAB floating over the transcript.
- Streaming veil: each inserted chunk fades on its own clock, found by a
  prefix+suffix diff (list rows carry their bullet after the item text,
  so the old prefix check skipped the veil and words popped in); chunks
  are recorded during composition so new text is never drawn opaque
  first.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Android: Material navigation — search app bar, extended FAB, no custom nav

Two destinations don't take a navigation bar in Material 3 (it's for
three to five), and a floating capsule isn't a Material component. Home
now follows the search-led Material pattern: AppBarWithSearch with the
account avatar (→ Settings, now its own screen with a large top app
bar), ExpandedFullScreenSearchBar for search, FilterChips, and an
ExtendedFloatingActionButton for New session that collapses on scroll.
Session and new-session headers are standard TopAppBars with icon
buttons. Removes the custom floating nav, pills, and tonal circle
buttons. All screenshots recaptured.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Android: restore the filter pills; white send arrow on the accent

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Android: restore the pre-review home, settings and chat header

Brings back the Sessions header, floating nav with the New session bar,
Settings as a tab, the search screen, and the round header buttons.
Keeps the flat transcript/composer layout, jump FAB, streaming veil,
filter pills and white send arrow, and adds a status-bar scrim on
scrolled home and settings. Screenshots recaptured.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Android: iOS feature parity — questions, drafts, sections, projects, archive

- Question panel: one page per question, auto-advance, "Other…" text,
  Pi input/editor prompts (prefill + multiline) answerable; replaces the
  composer while open.
- Sessions: Group by Project (git identity, Home per device), options
  menu (New section, Collapse all, Group by project, Archived), swipe
  right to pin, Move to section, section rename/delete, pinned reorder,
  Archived screen, Undo snackbar from every archive, iOS row precedence.
- New session: project picker grouped by repository with a host chip
  for checkouts, New project folder browser, text/options/images kept
  when closed unsent.
- Session: per-chat drafts, open failures return to Sessions with a
  note, image viewer (thumbnails and image chips), chip icons, "Sending
  to host…" and reconnect countdown, PR chip Open/Copy link, take photo,
  Ctrl+Enter sends, markSeen on leave.
- App: sends get 25s to deliver after backgrounding (short FGS), an
  expired session keeps its local store, OAuth state checked, tokens
  sealed with Android Keystore, sign-out confirmation, list/detail
  layout on large screens, Ctrl+N / Ctrl+Shift+F.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Android: README launch routes; pull to refresh waits for a real change

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Android: remote voice mode (port of the iOS voice call)

Adds sh.zeron.android.voice, the Android side of the Codex voice
orchestrator call: audio on the phone, Codex and its tools on a
registered execution host advertising voiceHostCapability().

- VoiceController (iOS RemoteVoiceController): host eligibility and the
  remote-voice dev override, start/stop/mute, end reasons with messages
  and Retry/Settings, per-user/org remembered host and style, call
  sounds, proximity (earpiece + screen off at the ear), one call at a
  time, no auto reconnect, the scripted preview and a WebRTC self-test.
- VoicePeer + VoiceMedia (CodexVoicePeer/NativeVoiceMedia): Google WebRTC
  M150 (io.github.webrtc-sdk:android, the iOS pin's milestone), audio
  only; Prepare/Offer/ApplyAnswer/SetMuted/Levels/Close completed through
  VoiceCall.completeMedia exactly as iOS; manual audio until the host
  confirms, focus loss ends the call, speaker/earpiece/headset routing.
- VoiceCallService: microphone foreground service with a CallStyle call
  notification (host, call clock, Mute, Hang Up; tap opens the stage).
- Compose UI: the core orb on a Canvas, the core caption fader, the call
  stage, voice settings, the New session bar button / live call strip,
  the session header button and VoiceHost (mic prompt, keep-awake,
  off-stage failure snackbar).
- Call sounds from the iOS app in res/raw.

Wiring into AppModel, navigation and the existing screens is left to
the integrating change.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Android: wire voice into the app

The call lives on AppModel (stopped on any sign-out). The New session
bar carries the voice button and the live call strip; sessions get a
header voice button; Settings gets a Voice row; the call stage and
voice settings are routes (also from the call notification and
zeron://voice). Launch extras: voice-preview, voice-stage, remote-voice,
voice-selftest.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Android: zeron://voice opens the call

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Android: stop re-composing every session row on scroll

The sessions screen read `list.firstVisibleItemScrollOffset` while
composing (for the status-bar scrim), so it re-ran on every scroll frame
while the header was on screen. `RowActions` was rebuilt on each run, so
no row could skip: every visible row re-composed every frame.

`StatusBarScrim` now takes the list and derives `scrolled` itself (the
same read in Settings, Archived and Voice settings goes with it), and
`RowActions` is remembered.

Nothing Phone (2), release build, 1.5 s drag at the list top: UI thread
p90 7.7 -> 5.6 ms; 8 flings: 7 -> 0-3 janky frames.

* Android: fade the status-bar scrim without a grey flash

Animating from Color.Transparent (black at zero alpha) passes through
semi-transparent grey: in the light theme the status-bar band dropped
from luma 249 to 173 for ~67 ms on each toggle (screen recording). Fade
from the page tone at zero alpha instead; same for the nav bar pill.

* Android: ask for the panel's peak refresh rate while touching

Nothing OS holds third-party windows at 90 Hz on its 120 Hz panel
(`PRIORITY_APP_REQUEST_RENDER_FRAME_RATE_RANGE ... mMaxRefreshRate=90.0`)
unless the window asks for a display mode. Ask for the fastest mode while
the user touches the app and for 10 s after, then hand the choice back so
an idle screen isn't pinned at 120 Hz.

Drag at the list top: a frame every 11.2 -> 8.4 ms (90 -> 119 fps), no
dropped frames; coming back from idle costs one ~19 ms frame while the
mode switches.

* Android: side chats, subagents, terminals and visuals (iOS parity); M3 floating toolbar

Companions, as on iOS:
- Chips above the composer ("2 working", side chats, live terminals) and a
  companions sheet listing a session's subagents (live first, ticking),
  side chats (new, fork, swipe to archive) and terminals (swipe to close).
- Session header gains the companions button (badged while agents run); the
  menu groups New side chat / Fork / Terminal, Pin / Copy / Archive, Delete.
- Side chats head themselves under their parent; fresh ones left unused go.
- Subagent cards in the transcript open the subagent's live, read-only
  transcript with a working/finished/failed bar.
- Terminals: a View painting the Rust emulator's frames (box drawing and
  blocks drawn per cell), IME + hardware keys, fling scrollback, pinch to
  resize, word selection with a floating Copy / Add to message / Paste menu,
  a key bar (esc, sticky ctrl/alt, tab, repeating arrows, punctuation,
  paste), a tab switcher, status pill, and refs that reattach after launch.
- Agent visuals (show_visual) paint in the transcript with live surfaces
  and controls.

Home drops the tab bar for a Material 3 Expressive floating toolbar
(Settings, Search, voice) with New session as its FAB; it tucks away to the
FAB while scrolling down. Settings is a pushed page.

Merged main; the Kotlin bindings rename TerminalSession.close → end, and
build-core.sh ships libc++_shared.so (the core now links C++).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Android: Material 3 bottom app bar on the Sessions page

Settings, Search and voice as the bar's actions, New session as its FAB;
the bar slides away while the list scrolls down. Replaces the floating
toolbar, which sat small and centred over the list.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>

* Android: Cloud and large-screen parity with iOS

Cloud (iOS Cloud/):
- CloudStore: status and credits, GitHub, the vault's logins and their
  usage, billing, session machines; cached reads that revalidate, with
  backoff when a read fails. Browser hand-offs come back through
  zeron://signed-in.
- Settings → Agents: Providers (each device's agents with their switches
  and logins, plus Cloud's), Cloud (GitHub, repositories, Cloud projects),
  Billing (credits, plans, packs, Stripe checkout and portal).
- An agent's accounts on Cloud or a device: usage bars, switch, remove,
  sign in through the browser (paste-code fallback), API keys.
- GitHub device-flow sheet; the Cloud project picker.
- New session on Cloud: the Cloud host, Cloud's models, branches from
  GitHub, "New Cloud project…", "Starting on Cloud…", out-of-credits.
- Sessions: the out-of-credits notice (a refused send shakes it), a failed
  Cloud machine named in the banner, an error card's "Log in".
- Welcome pages after sign-in: appearance, sync, GitHub, agents,
  notifications.

Large screens (iOS SplitRootController), from 700dp wide: the sessions
sidebar beside the open session or the new-session page; companions in an
inspector column with terminals, subagents and side chats pushed inside it
(the sidebar steps aside below 1100dp); Settings as a dialog; Ctrl+N,
Ctrl+Shift+F, Ctrl+B, Ctrl+J, Ctrl+Alt+0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>

* Android: the Cloud list's scrim derives its scroll state too

* Android: drop the title header from the session menu

It repeated the header's title and host, and clipped the first item.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>

* Android: the model picker as a sheet (iOS parity)

"Model" over where the chat runs, a provider switcher whose thumb follows
swipeable pages (the chat's provider first), models straight on the sheet
with the current one tinted and checked and scrolled into view, a notice
("Your next message continues this chat with Codex", or why the provider
can't change now), search past 12 models, loading skeletons, and a beat to
see the pick land before it closes. Sessions offer the host's other
providers between turns when the host can switch (Cloud chats: Cloud's
agents); picking one moves the chat there and drops the old effort and
options. The new-session page opens the same sheet with a tab per provider
the target runs.

A host that doesn't answer its model list gets the built-in catalog after
5 s (the FFI call can't be cancelled, so the wait is raced, not timed out);
providers that join after the sheet opens load then.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>

* Android: build the APK in CI and offer it on zeron.sh

- .github/workflows/android.yml: a release APK (arm64, the core at the
  mobile-dist profile) whenever the app or the Rust core changes. Pull
  requests get it as an artifact; main publishes it to R2 as
  zeron.sh/releases/zeron-android-arm64.apk (no-cache) plus a versioned copy
  and sha256s. Publishing needs the upload key in secrets; forks and
  unconfigured repos build debug-signed and don't publish.
- Gradle: the version is the workspace's (Cargo.toml), the build number comes
  from CI, and assembleRelease signs with ZERON_ANDROID_KEYSTORE when set.
- build-core.sh: ZERON_ANDROID_PROFILE picks the core's Cargo profile.
- Website: Android in the mobile downloads row; on an Android phone the
  download buttons offer the APK.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>

* Android: a third the APK size; CI artifact holds only the APK

- Compress native libraries and dex in the APK: it's downloaded from
  zeron.sh, not delivered by Play (161 MB → 44 MB locally).
- Drop material-icons-extended: the app draws Zeron's own icons, and only
  leftover imports referenced it.
- Package only the ABIs the core was built for (ZERON_ANDROID_ABIS): CI's
  arm64 APK no longer carries WebRTC's x86_64 library.
- The workflow stages in out/android: the repo's dist/ (desktop packaging)
  was swept into the artifact.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>

* Android CI: build with the release key

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>

* Android CI: stop compiling the core for the host

The Kotlin bindings came from a host build of zeron-mobile, compiled twice
(the plain lib, then again with the generator's feature): about 7 of the
build's 15 minutes. UniFFI's generator now has a crate of its own
(crates/mobile-bindgen, uniffi + its CLI) and reads the bindings out of the
Android library just built, as the iOS script does with its device library;
the output is byte-identical. Without the NDK the script still builds a host
library for the bindings.

Pull requests build the core at the quicker `mobile` profile; main keeps
`mobile-dist` (thin LTO) for the published APK.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: wing-anara <wing_13@live.com>
Co-authored-by: Alexandre VARGAS <alexandre.vargas.lopez@gmail.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
2026-10-24 17:12:34 -07:00
Wing
a2c68b097a
iOS core build: find cargo where the caller's PATH does (#982)
The TestFlight archive on the macos-26-arm64 20261021 runner image failed
with "env: cargo: No such file or directory": build-core.sh runs cargo
with a fixed PATH starting at ~/.cargo/bin, and that image no longer
puts cargo there. Keep the directory the caller's PATH resolves cargo
from, and pass CARGO_HOME/RUSTUP_HOME through the clean env.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 14:46:41 -07:00
Wing
cc7da5c2aa
Zeron Cloud, provider switching, and the phone model picker (#966)
Cloud chats on machines of their own (delegation, sleep/wake, durable delete), a credential vault, Stripe billing with Cloud's own portal, per-account Cloud availability, the edge's Cloud model list, provider switching between turns, the phone's tabbed model picker, and desktop/phone/engine polish.
2026-10-22 03:18:13 -07:00
José Gurruchaga
5918248811
Session card: side chats and subagents (#895)
* Session card: side chats and subagents ride a lanes card under it

The explorer's Subagents / Chats footer moves into a card of its own,
stacked under the session card and shown with it. It lists the open
chat's side chats and subagents in session-card rows, each lane's status
marks joined by one thin track. New side chat and Fork chat close the
side-chat lane; settled subagents fold into one "finished" row.

- The two cards share the height below the titlebar, each scrolling
  inside what it gets.
- Renaming a side chat in place now shows the card and pages its lane
  to the row, instead of needing the explorer open.
- Running subagents badge the session card's toggle while the card is
  closed, with no breathing glow, in place of the explorer button's mark.
- The explorer footer, its `FilesEvent` variants and the rename handoff
  to the files surface are gone.

* Session card: drop the running pill from the Subagents heading

The lane's own spinners show what runs, and the session card's toggle
keeps the count while the card is closed.

* Session card: badge the toggle while side chats or subagents run

The count now adds working side chats to running subagents, and stays on
the toggle with the card open or closed until nothing runs.

* Fix side chat rename opening the file explorer

* Session card: cap the lanes card at half the window's height

However much runs, the lanes card stops at half the window and scrolls
past it. The session card above keeps its height; only the lanes give.

* Scroll side chat rename fields into view

* Session card: a click on a side chat only opens it

Renaming a side chat goes through its context menu; a second click no
longer turns its row into a title field.

* Demo: a session fanning out 40 subagents for the lanes card

The mock harness answers a `/fanout [N]` prompt (40 when bare, at most
200) by spawning N subagents at once and settling them one by one,
oldest first, every seventh failing — the only data-side way to fill the
session card's subagent lane, scroll it, and watch it drain into its
finished fold. They settle `ZERON_MOCK_DELAY_MS` apart, 2.5s by default.

scripts/dev-demo.sh seeds "Fan Out Forty Scouts" with three side chats
and fans it out again on each launch. It also lists each demo folder
once (a second space on the same folder was never created, so seeding
failed with "no such space") and falls back to /tmp/zeron-demo-projects
when ~/github is missing.

* Session card: side chats wear their harness mark

Each side chat leads its title with its harness's brand mark, as the
sidebar's session rows do.

* Session card: the lanes card scrolls with the floating rail

Once the lanes outgrow the card and scroll, the card shows the file
tree's floating scrollbar: it appears on scroll, lingers, fades, holds
under the pointer, and drags. `popover::rail_for` gives a view that
already hosts a rail through `ScrollRailHost` (the shell, for the
projects menu) the same treatment for another scroller.

Subagents now list plainly, with no track between their marks; side
chats keep theirs.

* Demo: let a second demo pick its own state and port

ZERON_DEMO_DIR and ZERON_DEMO_PORT run the demo beside one already open
from another worktree; unset, it keeps /tmp/zeron-demo-* and :27921.

* Session card: drop the side chats' track

Side chats list plainly too; no line runs between any lane's marks.

* Session card: side chat starters move to the heading once branches exist

* Session card: subagent rows carry the session's harness mark

* Session card: drop the failed count from the finished fold

* Session card: the branch row shows the checkout's uncommitted +/- totals

* Session card: leave takeover to rename a side chat; stop the diff watch while hidden

Renaming a side chat from a tab menu in takeover focused an editor in the
zero-width transcript column, so keystrokes went to an unseen field. Leave
takeover before revealing the lane. The branch row's checkout-diff stream
also ran for as long as the app lived; drop it while the card is hidden.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Wing <contact@winglee.io>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-17 11:54:12 -07:00
Laurent
3b2f78027a
fix: send cursor model defaults for plus subscriptions (#920)
* fix(cursor): send account catalog defaults with model selections

* fix(dev): prevent release updates from replacing local builds

* fix(cursor): fill defaults on model switches, skip Max Mode, avoid refresh waits

- Mid-session model switches (in-place reconfigure via steer) now get the
  same catalog defaults as a fresh run; they previously still sent bare ids.
- Runs reuse the already-loaded catalog instead of waiting on a refresh
  every 60s; only a cold catalog is fetched.
- Never send a default from a Max Mode variant: the backend rejects the
  variant the catalog marks default for Grok 4.7 (500k, "Invalid
  parameters" — verified live) while the bare id runs, so those models keep
  sending the bare id as before. Every non-Max default in a live catalog was
  verified to run.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Wing <contact@winglee.io>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-15 13:40:31 -07:00
José Gurruchaga
053ce2eac0
Persist embedded browser sessions across tabs and app restarts (#573)
* refactor(browser): define stable device-local profile identity

* fix(browser-linux): persist website data and cookies by profile

* fix(browser-macos): persist isolated website stores on macOS 14

* fix(browser): preserve profile lifecycle across tabs and windows

* test(browser): verify persistent storage across app launches and profiles

* docs(browser): document persistent profiles and session lifecycle

* fix(browser-linux): initialize WebKit without blocking the UI

* fix(browser): correct macOS fixture import and Windows profile test

* fix(browser): invoke macOS storage fixture wrapper through bash

* fix(browser): propagate macOS fixture failures and initialize profile cleanup

Require explicit storage results, validate deletion in every store, and preserve primary failures while attempting all profile cleanups. Add opt-in native cookie and same-process reopen diagnostics.

Validated on macOS 27 arm64: release check/build and native tests pass. Two complete storage runs correctly fail on cookies returning after process restart; all profile cleanups pass. Cookie deletion persistence remains unresolved.

* fix(browser-macos): retain profile stores for the application lifetime

* fix(browser-macos): preserve profile stores through process exit

* test(opencode): remove fixture startup and clock races

* Revert "test(opencode): remove fixture startup and clock races"

This reverts commit dffcec2cdee4d6903649fe156c5b813d91e12376.

* test(browser): verify PR state follows profile identity
2026-10-12 17:53:46 -07:00
neo773
e54c3a8610
Let dropped files from any folder attach on macOS (#812)
* Let dropped files from any folder attach on macOS

Files dropped into a chat from outside a project folder (Downloads,
Desktop, …) failed to attach. The app was signed with only the microphone
entitlement.

Sign the app with the user-selected and Downloads file entitlements, as Zed
does (zed-industries/zed#43609), and rename Dictation.entitlements to
Zeron.entitlements now that it covers more than dictation.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Sign ad-hoc macOS packages with Zeron.entitlements too

Ad-hoc builds signed with voice.entitlements (microphone only), so they
missed the file-access entitlements. One entitlements file now covers
every signing path.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: wing-anara <wing_13@live.com>
2026-10-11 13:28:33 -07:00