Repository navigation
v0.26.0
Bazilion 0.26.0 simplifies the whole product for a single local operator: about 186,000 lines of code, tests and docs removed, the features you use kept on both the CLI and the web UI.
Removed
- Review packets, specialist verification and publication to a code host (the Team Review diff page and file feedback stay).
- The communication approval queue, Team Policy template lineage and denial history. Team Policy is now plain allow edges with an open/restricted mode per Team, and plain templates.
- The workspace lease and its recovery commands. Teammates run concurrently again and
wait_for_replyworks between them. - The coding evidence layer (
coding_*tools, receipts, retained logs, source snapshots). Live output now shows for every tool, in the web UI and the CLI. - The native Bubblewrap sandbox and the separate protected turn surface.
- Device pairing codes and token scopes.
- macOS-specific process, keychain and Git layers; Windows code paths.
@bazilion/clientand@bazilion/api-typesare no longer published to npm.
Changed
- Docker is the only sandbox:
BAZILION_BASH_SANDBOX=off|dockerapplies to every turn (chat, Telegram, schedules, inbox). Withoff, unattended turns run on the host with the same tools as chat. - The bootstrap token works at the web login; sessions slide for about 30 days; device tokens do not expire by default.
- Scheduled triggers and learning reviews run once per occurrence, without retries; failures show in Attention and in the trigger history with the real error.
- Bazilion's own credentials (ChatGPT OAuth, MCP tokens, Telegram token, bootstrap token) no longer reach agent shells or MCP stdio servers.
- CLI flags renamed:
token create --expires-days,login --skip-verify. Team memory keys must end in.md. - Many fixes found along the way: a path traversal in skill deletion, CSRF/Origin checks for web server functions, attachments over 1.5 MB,
/chat/truncatepersistence, Fireworks endpoints, files lost in queued follow-ups, Telegram members unable to chat, web list filters, default-profile edits overwritten at boot, slow turns with a hung MCP server, and tests that touched the real home.
Upgrading
The database schema was reset to one clean-install schema, and a 0.25 home is refused at startup. Back up the whole home directory (cp -a ~/.bazilion ~/.bazilion-0.25), run bazilion uninstall --yes, then start Bazilion again to bootstrap a fresh home.
Linux is the tested platform; macOS runs commands on the host and is untested; Windows is unsupported.
Validation
pnpm lint, pnpm typecheck, pnpm test (196 files, 1,353 tests plus 12 browser tests), pnpm build, the Docker sandbox suite and the packed-tarball smoke test all pass; the Release workflow's typecheck and tests passed on GitHub before publishing.