Give your AI tools their own workbench: a real container with your whole stack, services and repos, from one file. Turn them loose, and whatever they do stays off your machine, where your client data lives.
Open source · your own Docker · no cloud, no account, no rental
Each project gets its own container: its own stack, services and agent. What happens in one never leaks into another, or onto your machine.
Describe the workbench, build it, let the agent run, reset to clean. That's the whole loop.
Say what goes in: your stack, your repo, the AI tool. One YAML, editable.
› monoceros init acme \
--with-languages=node,java \
--with-services=postgres \
--with-features=claude,github,atlassian/twg \
--with-repos=https://github.com/acme/booking-manager.git A real container with your stack, up in minutes. That's the box your agent lives in.
› monoceros apply acme ▸ pulling image, installing features... ✓ workbench ready
Hand the agent a task and let it run, unattended. It works the repo inside the workbench - and can't reach past it to your machine.
› monoceros run acme --in projects/booking-manager -- claude "Implement Story ACME-345" ▸ agent working in acme...
Made a mess? Reset to clean in minutes. Or keep the workbench for next time.
› monoceros remove acme ▸ snapshot saved ✓ host clean
The common ways people run AI agents today, and the catch with each.
It can touch your keychain, your other clients, the whole disk. So you babysit every step - or flip on auto-accept and hope.
The agent runs in its own workbench. Turn it loose - it can't reach the rest of your machine.
Your code and client data live on someone else's servers. Off-limits for many contracts, useless offline.
Runs on your machine, not a vendor's. No cloud account, no rental - and it works offline.
A container or VM per project, wired up by hand. No lifecycle, no clean reset - and you maintain it forever.
One YAML, a real workbench, reset in one command. You don't build or maintain the box - that's our job.
The newer agent sandboxes isolate well. But they are proprietary and paid, want an account, and give you just a box: your stack, services and repos are still yours to wire up.
Open source, on your own Docker, no account. One file builds the whole environment - languages, services, repos and your agents - not just a sandbox to drop one into.
Pick what goes in the workbench. Monoceros wires it up - reproducible, isolated, local.
Node, Python, Java, Go, Rust, .NET. Pin the version per workbench.
Postgres, MongoDB, Keycloak and many more. Each workbench gets its own, isolated.
Claude Code, Rovo Dev, GitHub CLI, and many more. Each one a feature you add - swap freely, no lock-in.
Point at an HTTPS repo - GitHub, GitLab or Bitbucket. One token clones it and signs in gh / glab inside the container. No git tooling on your host.
One YAML builds it, the same on any machine. Each workbench pins its runtime version; apply never changes it behind your back, upgrades are a deliberate command.
Your Docker, no account, no rental, no telemetry. Runs on your machine, offline included.
Built on the dev-container spec VS Code and others use. Walk away anytime.
Attach VS Code, VS Codium or JetBrains to the running workbench over SSH - zero setup, Windows included. One monoceros open and you are editing inside the container.
Tool logins, sessions and editor extensions survive a rebuild. Run apply again, and your agents stay signed in, your setup intact.
See all features → More tools, languages and services coming soon.
Open source, runs on your machine. Install on macOS, Linux or Windows, then one command to build a workbench.
› curl -fsSL https://raw.githubusercontent.com/getmonoceros/workbench/main/installer/install.sh | bash › irm https://raw.githubusercontent.com/getmonoceros/workbench/main/installer/install.ps1 | iex