Skip to content

Better Codex v0.2.0-beta.3 — Maintained Android and local-first core

Pre-release
Pre-release

Choose a tag to compare

@WhyTan00 WhyTan00 released this 07 Oct 17:18
· 9 commits to main since this release

This beta synchronizes the maintained local-first workbench core and adds a configurable Android source build. Android foreground/pinned/recent-20 reads and deep archives have separate priorities; unchanged complete histories retain body witnesses across reopen, observed process state is read locally before the first hydrated frame, and agent details remain accessible by explicit scoped ID without entering the main directory or warm sets.

The generated renderer now consumes the current send preparation, same-attempt configuration, post-ACK queue, draft/navigation ownership, Fast preference and full-image patches. The Native boundary accepts the current single-local-environment reply shape while preserving remote/cross-workspace rejection and request idempotency. Metadata-only diagnostics cover queue/HTTP/body/parse/wire stages with aligned collector whitelists.

The English and Chinese README have been rewritten around native execution, the official renderer, local-first continuity, project plugins and the current showcase. Mac/Tailscale and optional authenticated CVM access remain supported. Android uses a separate application ID and an adopter-supplied HTTPS origin, generated UI and signing key.

Validation: 224 Android Java tests with zero failures/errors (two existing conditional skips), release build; 230 final generated-renderer assertions; 220 core checks; 13 host/auth/plugin contracts; full Go producer-consumer suite; three real Android WebView send/slow-read/reconnect cases; 43 real independent empty-account local-host checks; and nine real local Caddy HTTPS/WebSocket checks.

The Mac ZIP contains the portable installer and source, not a preinstalled account/runtime. The two source archives provide Better Codex and the complete pinned modified OpenCodex corresponding source (AGPL). SHA256SUMS records asset hashes. No official renderer resources, production APK/signing material, credentials, private transcripts or diagnostic logs are redistributed.

Physical phones, Tailscale pairing, Android HTTP Basic handoff, real cloud DNS/tunnel deployment, signed-in model execution, natural send latency and sustained battery behavior remain unverified. See docs/portable-validation.md and docs/android.md for exact boundaries and build instructions. This release does not claim that every private-app regression or occasional long-send cause is resolved.