OtoDock 1.6.0 lets you self-host Claude Code and Codex agents in a sandbox

Self-hosting an "AI company OS" is actually viable if you use bubblewrap for kernel sandboxing and pasta for network isolation. I've been using OtoDock to run persistent agents that act as department heads, and the 1.6.0 update just landed. It basically wraps Claude Code and Codex CLI into a multi-tenant app, meaning you can have different agents with their own workspaces and memory, all running on your own hardware via your own API keys or local models.

How the agent isolation works

The biggest risk with giving an agent CLI access is letting it wreck your host machine. OtoDock handles this by running each agent as a persistent process inside a bubblewrap sandbox. This keeps the filesystem isolated and uses pasta to manage network traffic without needing to open a bunch of inbound ports or mess with a complex VPN.

If you need the agent to interact with a remote computer, it uses a single outbound WebSocket. This is a huge win for security because you don't have to poke holes in your firewall for every single agent you deploy.

What these agents can actually do

Most "agent" wrappers are just chat interfaces. These are persistent processes with actual tools. During my setup, I found a few specific integrations that aren't common in basic LLM wrappers:

• Document Handling: It uses Collabora to let agents edit and preview Excel, Word, and PPT files directly in the chat.
• Communications: Integration with Twilio and Asterisk allows agents to actually place and answer phone calls.
• Deployment: It's a single install script and a docker-compose file. No signup process is required to get it running locally.

Getting it running and the cost

The license is Fair Source, and it's free for up to 5 users. Since you provide your own Anthropic or OpenAI keys, your only cost is the token spend and the electricity for your server.

To get it started, you'll need Docker installed. The setup is basically:

# Run the installation script provided in the repo
curl -sSL https://otodock.io/install.sh | bash

Then you launch the stack via docker-compose. If you run into issues with the sandbox, check that your kernel supports bubblewrap, as that's where most "it won't start" errors happen on older Linux distros.

When to avoid this setup

Don't bother with this if you only need a simple chatbot or if you're uncomfortable managing a Docker environment. If you don't have a dedicated server or a high-performance VPS, the overhead of running multiple persistent agent processes might lag your system. Also, if you're looking for a purely SaaS experience where you don't manage keys, this isn't for you.

The code is all public on GitHub, and interestingly, a huge portion of version 1.6.0 was actually written by the agents themselves using Claude Code.

https://github.com/OtoDock/oto-dock