UseAgentBots
A bot is an agent you name and keep. Give it an avatar, a one-line job and the standing rules it works by, then pick its engine: Chat when you want answers from your team's context, or OpenCode, Claude Code, Codex or Pi when it needs a sandbox computer. Each bot has one durable home thread, so what you told it last week is still there this week. Creating one takes about ten seconds.
Routines
A routine is a schedule a bot owns. Pick a preset like weekdays at 9:00 or write a cron expression, and the routine fires into the bot's home thread, where the result lands next to everything else it has done. You can run a routine once to test it, pause it, and read its history. One kill switch, BOTS=off, stops every bot and every routine at once.
Mentions and handoffs
Type @bot/Nova in any thread and that part of the work goes to Nova in a delegated thread of its own. An agent in the middle of a run can do the same through the bot_handoff tool. The thread that asked gets a receipt: a new thread was created, the work was sent to a thread that already existed, or the handoff was refused with the reason and a hint on when to retry.
A handoff is refused when it would loop: a bot handing to itself, a cycle, or too much depth. Handoffs are also capped per parent thread, per family and per bot per hour. Bots never speak as each other. The parent reports that it handed the work to Nova, links the thread, and reads the result when it comes back.
Child sessions
Child sessions are durable and you can message them directly. When a run delegates work to a child, you can open the child, watch it live from inside the parent, and send it a follow-up. A follow-up either goes now or queues behind the run in progress. You choose which.
Computers as plugins
The computer a bot runs on is a plugin. Daytona, Cube and Box each ship as a package behind one contract, and Cube stays the default on the hosted product. You can also connect your own account with one of these providers. Your threads then run on your computers and are billed to you.
Artifacts
Artifacts are delivered through one path no matter which engine produced them. Reclaiming local artifact storage is safer: files go to quarantine first and can be recovered instead of being deleted outright.
Operations
Releases are promoted as immutable images. Each promotion has a short admission window, and rollback is pinned to an image digest, so going back means running exactly the build that ran before.
Where it runs
This release is rolling out to early access now. The public repository is at v0.0.3 and receives it after production verification.
Everything from earlier releases still applies: the multi-engine control plane, approval gates with one-shot capability tokens, editable DOCX, XLSX and PPTX artifacts, knowledge and wiki, skills and playbooks, automations, team memory, Slack, GitHub, MCP, org secrets and self-hosting.