Repository navigation
Zeros v0.1.25
Install
- Download
Zeros-0.1.25-arm64.dmgbelow. - Open it and drag Zeros.app into
/Applications. - Launch from Spotlight / Finder.
Installed apps update in place via the built-in auto-updater.
What's Changed
📦 Other changes
- Log the zeros-dev fixture in through WorkOS's web client and connect its GitHub repo in #464
- Run object and runtime-image maintenance on bounded, hinted sweeps in #465
- Tolerate control-plane clock skew in zeros-dev GitHub connect in #466
- Serve agent actor-confirm, warm-context and relay checks from coherent reads in #467
- Compare zeros-dev GitHub names case-insensitively in #468
- Let the resident-host builtin-loop test shell exit on TERM in #471
- Refresh agent model catalogs on a bounded TTL and trace Codex startup stages in #469
- Tag every advisory lock by purpose and time database work per route in #470
- Create zeros-dev workspaces through the ordinary active-Computer contract in #472
- Add zstack, the in-repo engineering pack every agent host follows in #473
- Accept named-Computer image references in the cloud workspace setup helper in #475
- zstack 0.1.1: pending eval references and two new lessons in #476
- Stop the renderer log flusher from waking every second when idle in #477
- Make the concurrent last-slot warm-context test deterministic in #478
- Share one dedicated LISTEN session across the control plane's notification consumers in #474
- zstack 0.1.5: one file per eval case and per lesson in #481
- Ship the engine's outside-src imports in the runtime bundle and keep the first qualification failure in #482
- Schedule the cloud catalog refresh by its next due time instead of every 2 s in #484
- zstack 0.1.6: fold merged lessons and add the fixture-run lessons in #486
- Let the Alpha barrier wait out an overlapping publication instead of failing in #485
- Keep the shared notification listener for 23 hours instead of ten minutes in #487
- Let zeros-dev cleanup delete a workspace after a failed wake in #488
- Prove each Computer build's runtime pin and name the failing setup stage in zeros-dev in #489
- Retry the zeros-dev credential lock when its holder releases it mid-check in #490
- Let a resumed cloud engine adopt its restored credential ledger, and keep each setup claim's first failure in #491
- Give control-plane API requests and workers their own database pools in #492
- Fix Claude sign-in recovery, notices, and task counts in #480
- Let control-plane repair releases proceed while unrelated cleanup is stalled in #494
- Run the zeros-dev cloud lifecycle hourly on main and gate cloud merges on it in #493
- Share one visible-only runtime-upgrade observer per workspace instead of per-component intervals in #495
- Time the cloud engine's authority renewals without adding timers in #496
- Name why a zeros-dev runtime connection or resume wait failed in #498
- Name the exact checkpoint check that refuses a cloud resume, and stop retrying it in #499
- Make a cloud workspace stop wait for the engine's final seal instead of being superseded in #500
- Let zeros-dev reclaim a run lock only when its owner is provably dead in #501
- Make the concurrent warm-context publication test deterministic in #502
- Drive the cloud agent E2E baseline test from event clocks instead of a sleep in #503
- Rebuild the hourly canary's fixture Computer only when the qualified runtime moves in #497
- zstack Z1: plan and run verification checks, record receipts, and replay escaped bugs in #504
- Return a typed retryable 503 when runtime admission hits a transient provider fault in #505
- Retry runtime admission only on the typed transient 503, within the original budget in #506
- Recover a cloud workspace whose last writer stopped unsealed, with an audited history gap in #507
- Fix Claude/Codex steering and add follow-up behavior settings in #508
- Keep the confirmed writer alive through the final seal when a control reply crosses the stop fence in #509
- Report each cloud checkpoint stage to the control plane as bounded, optional diagnostics in #511
- Add a manual Gate 0 rehearsal profile and a signed 24-hour evidence collector for the zeros-dev fixture in #512
- Connect Design frames to application styles and live builds in #510
- Make the cloud custody and resident-host fixtures deterministic in #513
- Expose an authenticated "compute retired, storage pending" proof for a deleted cloud workspace in #514
- Read skipped scheduled hourly runs whose job name GitHub left unevaluated in #519
- Let zeros-dev hourly and Gate 0 runs accept authenticated storage-pending deletions in #515
- Retry a transient GitHub 5xx when Alpha publication edits the rolling release in #516
- Make dev:gc name a missing control-plane install and keep its apply on the owner's Mac in #517
- Give the two full-ladder migration tests the same 30 s budget as the other ladder cases in #518
Full Changelog: v0.1.24...v0.1.25
📝 Curated highlights & media: https://zeros.build/changelog