Skip to content

1.4.0: Daytona execution and fast checkpoint sharing

Choose a tag to compare

@rohanarun rohanarun released this 15 Oct 21:12

Run research in private Daytona sandboxes with the same native chat and parallel-agent controls. Save your Daytona API key in macOS Keychain, complete the separate cloud Codex device sign-in, then choose local or cloud execution. Existing chats retain their original execution backend.

Share context now uses fast live checkpoints only: agents maintain compact files while working; the harness drains owned processes, snapshots and combines checkpoint contents verbatim, then supplies them to fresh sessions. There is no synthesis-model call. Checkpoint snapshots, chats and session lineage are preserved.

Cloud workers use private checkouts and fresh provider state. Credentials are transferred only between authorized cloud sandboxes; the app never uploads Mac Codex account files. Management credentials stay on Daytona's API origin. Owned work is exported with credential exclusion and every-entry/hash verification before archival; failed exports preserve the filesystem. Added official device-login streaming, cancellation and owned-compute stop controls.

Includes the compact one-line agent toolbar and benchmark charts/data, including Daytona versus partial historical Mac controls and a clearly provisional old-synthesis comparison. These baseline-eligible finite construction timings do not establish a new research milestone or causal speedup.

Validation: native regression suite; real local two-worker/fresh-successor checkpoint test; real Daytona two-worker/two-successor transport test; owned Linux cancellation and verified recovery archives; actual device-login URL/code streaming and cancellation; Keychain, token-origin confinement, ownership and archive-tampering checks. Cloud execution currently supports Codex; local execution also supports Claude.

Requires macOS 14+ and Apple Silicon. The app and DMG are Developer ID signed, Apple notarized and stapled. Download the DMG and verify its SHA-256 using the accompanying checksum file.