KodaCode
Coming soon
Isolation

Isolated execution. Your environment, protected.

Let agents run freely without putting your machine at risk.

Switch a project to Docker or Podman in one click, and its commands run in a container that sees only your project. KodaCode picks the base image, so there’s nothing to set up manually.

Your system stays out of reach.

Inside the container, the agent sees your project and the folders you choose to share. The rest of your machine stays on the other side.

The same environment, side by side.

Open a terminal inside the agent’s container to run tests and debug exactly where it works, or a shell on your own machine from the same menu.

Full speed for your agents. Peace of mind for you.

Runs onDocker, Podman or your machine, per project
ImageDetected from the project, or your own
SeesThe project, and what you share
TerminalA shell in the same container
01Per project

Choose where each project runs.

Each project can run in Docker, Podman or straight on your machine, or just follow your default. KodaCode picks a base image by looking at the project (Rust, Go, Python or Node), or uses a Dockerfile you keep in the project's .koda folder, or one you choose. Try out an unfamiliar repo in a container and keep the one you know well on your machine.

02What the agent can see
The projectMounted at /workspace, where the agent reads, builds, tests and edits
A build cacheKept per project, so downloads and builds aren't repeated from scratch each time
Folders you allowOnly the ones you've added in Settings, and nothing else from your machine
SkillsShared read-only, so their scripts can run but never be rewritten
Everything elseNot there: your home folder, your other repositories, the folder next door
03The terminal

Open a terminal in the same container.

When a project runs in a container, the terminal opens inside it, so you get the same tools, files and limits as the agent. Click + for another container shell, or for a shell on your own machine in the project folder. Each tab is labelled DOCKER, PODMAN or HOST, and the panel can sit under the session or float over it.

04And approvals
In a containerChanges apply directly and commands aren't stopped by default, because the box holds only the project and what you share
On your machineChanges ask first, and so does anything that reaches outside the project
Either wayEach is a switch you can flip for the project · how approvals work

Let it work in a box of its own.

macOSDesktop appComing soon
WindowsDesktop appComing soon
LinuxDesktop appComing soon