What’s next, and what’s ready.
Follow the current release, explore the next work, and vote for what matters to you. Votes help set priorities; they do not promise a delivery date.
One vote per proposal per browser and network. No account needed. People sharing a public IP share a vote limit. You can remove a vote from the browser that cast it.
Loading the latest votes…
The migration foundation
Local discovery, saved versions, direct migrations, guided setup kits, destination backups, receipts, browser package checks, CLI access, and approval-based MCP are available now.
Native-tool migration walkthroughs
The beta checklist calls for a disposable OpenClaw → Codex move, checking the migrated instructions in the destination tool, and repeating the walkthrough with the platforms you actually use.
Done when: a reproducible report records the platform pair, preview, destination-tool result, and restore result. Automated fixtures already run; they do not replace these real-tool checks.
Installation and recovery coverage
The release process checks installation, migration, byte-for-byte restore, update, and uninstall across the configured Windows, Linux, and macOS CI jobs. The beta process collects operating-system, Node-version, and recovery problems for follow-up.
Done for a release when: its platform checks pass and reported blockers have a verified resolution. Read the beta checklist.
How your vote is counted
Votes are saved on the server and survive page reloads and deployments. Repeated clicks and requests count only once. A first-party cookie remembers your browser; a keyed hash of your network address helps prevent duplicate votes after cookies are cleared. Raw network addresses are not stored in the voting database.
Anonymous voting is a priority signal, not verified one-person-one-vote. Shared networks share a limit; changing both browser identity and network can bypass it. Votes are not a delivery commitment. The team reviews counts alongside beta reports and updates proposal status here.