v0.1.0-dev.56.1

Start a fresh installation

Give your installation Agent the version-matched Agent guide. Use this Release’s Server and Desktop attachments together. The Agent should install the Server, connect the first Codex, then connect the chosen Personal Agent and verify each stage.

This build replaces the previous dev browser-login setup with password or passkey on your own Worker. No Cloudflare OAuth client or API-token copying is required for browser login. Passwords are required but have no DotX length or composition policy. Browser sessions renew on authenticated management requests and expire after 30 days of inactivity. Wrangler administration and Personal Agent MCP OAuth remain independent.

Development build from 57d6249. Discovered only by deployments explicitly configured with RELEASE_CHANNEL=dev; stable deployments ignore this Pre-release.

Installation and update requirements

0.1.0 requires a fresh native installation from 0.0.1; no owner keys, device tokens or OAuth grants are migrated. Preserve native Codex accounts, projects and conversations. Install the Server, connect the first Codex and then connect each Personal Agent using its own access code. Updates within the 0.1.0 development series preserve the account, Worker, origin, SERVICE_ID, browser login methods and DO/KV resources; point both main and assets.directory at this release. After Desktop configuration or update, refresh every loaded host MCP configuration and verify the actual owner version. Refresh each Personal Agent catalog when remote_catalog is true. This release uses wire 5; 0.0.1 uses wire 4. Product versions may differ; wire versions must match. Report component completion separately from link recovery.

Browser administration now uses a DotX password or passkey; Wrangler management and Personal Agent MCP OAuth remain independent. After deploying this Server, run admin.mjs setup and give the private link to the user. They choose a password or passkey directly on their Worker; no CF OAuth client or API-token copying is required. Browser setup may be deferred while installation continues through Wrangler. Preserve DeviceHub and OAuth KV. Earlier dev CF browser sessions no longer work: set up the new login once, then remove obsolete CF_OAUTH_CLIENT_ID/CF_OAUTH_CLIENT_SECRET bindings and only the CF OAuth client dedicated to that retired login. Do not recreate the DO, device identities or Personal Agent connections. Subsequent password/passkey releases preserve the saved login methods. A forgotten browser login can be recovered through admin.mjs reset-login; successful reset clears only browser credentials and sessions.

Apply the target Server template's assets.run_worker_first routing array: ["/", "!/assets/", "!/branding/*"]. Keep html_handling and not_found_handling set to "none", and deploy public/_headers with the assets. Public JS/CSS/branding files are served directly by Cloudflare; API and explicit page routes still run through the Worker, with no automatic HTML fallback for unknown API paths.

Server now automatically removes durable request receipts, answer deduplication and response routes after RECORD_RETENTION_DAYS (default 30). Preserve any chosen value in the actual Worker configuration. Existing development receipts keep their creation dates; old interaction records without timestamps start at adoption. Reducing retention applies to remaining records and can make them immediately eligible for deletion. After deletion, old request IDs no longer deduplicate; inspect native state before retrying unknown work. Native Codex tasks and conversations are not deleted. Existing subscription/retry lifecycle cleanup is unchanged. See the version-matched bundled docs for executable steps.