Experimental lab
Switch on what
you want to try.
These capabilities are implemented and experimental. Each one is off by default and needs its switch under [experimental] in your global caudra.toml.
Move execution
into a VM.
Managed sandboxes run workspace tools in a separate VM. Model connections, provider credentials, and the conversation stay on your machine, so a compromised VM cannot read credentials it never received.
How managed sandboxes workHow the separation works
- Network policy allows listed domains and IP ranges, with TLS hostname checks or an inspecting proxy.
- File transfers between your machine and the VM go through a review.
- Requires e2b-libvirt infrastructure that you or your operator run.
Transferred files can still carry secrets. The separation reduces exposure and is no guarantee against compromise.
- Experimental
Durable workflows
Scripts launch subagents in phases, keep a journal, and can pause and resume. Each agent call can name a model job, such as Fast for a wide pass and Best for the answer you read. Built-in workflows cover deep research, change review, and root-cause analysis. They are heavily inspired by Grok Build workflows and mostly compatible with them.
- Experimental
Cross-session messaging
Live sessions on one machine exchange messages, publish to topics, and share work through consumer groups.
- Experimental
Lua extensions
Add your own commands, tools, and interface behavior in Lua when the built-in workflow needs something specific.
- Experimental
Remote Workcell
Run workspace tools on a Workcell server while the conversation stays on your machine.