Isolated Linux workstations for autonomous AI agents A tool called isx, formerly incus-spawn, gives autonomous AI coding agents their own isolated Linux workstations so API keys, GitHub tokens and ~/.ssh files never enter the agent's machine, with a host-side proxy injecting credentials into outgoing requests instead. Each agent gets a full Linux system with its own filesystem, init system, networking and process tree, built on Incus system containers, with a one-flag option for a hardware-isolated KVM virtual machine and instant copy-on-write branching from prepared templates. isx runs on Linux and macOS 15 (Sequoia) or later on the user's own hardware, is written in Java and compiled to native binaries with GraalVM, and installs via Homebrew, dnf, apt, curl or jbang under the package name incus-spawn. Give your AI coding agents their own machines, not your credentials. isx.run https://isx.run is the website, with the full documentation. An AI agent in your terminal can read your API keys, your GitHub token, your ~/.ssh and every repo you have checked out. Your IDE and build tools execute anything the agent writes. isx onboards agents the way you'd onboard a new teammate: - A real machine of their own. Each agent gets a full Linux workstation: its own filesystem, init system, networking and process tree. It can dnf install , run Docker Compose, use strace and nested containers, because it is a real system, not an app container. One flag gives the agent a hardware-isolated KVM virtual machine instead, when you want the strongest isolation. - Zero credential exposure. API keys and tokens never enter the machine in any form. A proxy on your host adds them to the agent's requests as the requests leave the machine, so claude , pi , gh , git and curl work unmodified inside it. See Credential Isolation credential-isolation . - Instant branches. Branch a prepared template like you'd branch a repo: an instant copy-on-write clone. Use it, throw it away, branch again from a clean state. - Full autonomy, no supervision. Each agent runs without permission prompts, and commits under the identity you assign it. It has no credentials to leak, and what it runs, installs or deletes is in its own machine, which you can throw away. Each agent works in its own machine and asks for no approval, so you can run many side by side and build automations that run with nobody watching. isx runs on Linux and macOS, on your hardware, and your repositories and credentials stay there. Agents are the main use, not the only one. The same disposable machines are ideal for triaging untrusted patches, reproducing bug reports and testing on a clean system. Built with Quarkus https://quarkus.io/ and Tamboui https://tamboui.dev/ , powered by Incus https://linuxcontainers.org/incus/ system containers. Written in Java, compiled to native binaries with GraalVM https://www.graalvm.org/ . isx was formerly known as incus-spawn. Requires Linux, or macOS 15 Sequoia or later Installation installation ; isx init sets up the rest, or your coding agent can do it all for you https://github.com/Sanne/incus-spawn/blob/main/docs/AGENT-INSTALL.md . brew install Sanne/tap/incus-spawn sudo dnf install -y 'dnf5-command copr ' on RHEL 9: 'dnf-command copr ' sudo dnf copr enable sanne/incus-spawn sudo dnf install incus-spawn curl -fsSL https://sanne.github.io/isx-apt-releases/public.gpg | sudo gpg --yes --dearmor -o /usr/share/keyrings/incus-spawn.gpg echo "deb signed-by=/usr/share/keyrings/incus-spawn.gpg https://sanne.github.io/isx-apt-releases stable main" | sudo tee /etc/apt/sources.list.d/incus-spawn.list sudo apt update && sudo apt install incus-spawn curl -fsSL https://isx.run | sh jbang app install isx@Sanne/incus-spawn jbang app install isx-proxy@Sanne/incus-spawn The package is called incus-spawn , and it installs the isx command. One-time host setup Incus, firewall, auth isx init On a fresh Linux host, isx init adds you to the incus-admin group and finishes its run in that group. Other terminals get the group at your next login, or in each one with newgrp incus-admin . A template is a machine image you build once: an OS, tools and repos. The template below adds Claude Code to the built-in tpl-minimal template. Save it as ~/.config/incus-spawn/images/tpl-agent.yaml , or run isx templates new tpl-agent and paste it over the skeleton that opens in your editor: name: tpl-agent description: Claude Code on the base OS parent: tpl-minimal tools: - claude default-action: claude Build it builds missing parent images first isx build tpl-agent Branch it: an instant copy-on-write machine of its own, with Claude Code open inside isx branch my-first --from tpl-agent The interactive TUI: your templates and branches isx Claude Code signs in with the Claude credential you set up in isx init ; isx account add claude adds one later. Claude Code never sees the credential: the proxy adds the credential to each request after the request leaves the instance. If you did not install the services isx init offers, start them before building: isx proxy start on Linux, isx vm start && isx proxy start on macOS. For another agent, replace claude with codex , pi , opencode , gemini-cli , antigravity , bob or copilot ; see Agents agents . Pi and opencode use your Claude credential too, unless their provider names another API Pi https://github.com/Sanne/incus-spawn/blob/main/docs/AGENTS.md pi-coding-agent , opencode https://github.com/Sanne/incus-spawn/blob/main/docs/AGENTS.md opencode . To give the agent a project, add repos: Declarative Repos https://github.com/Sanne/incus-spawn/blob/main/docs/TEMPLATES.md declarative-repos . Its commits come back to your host with git fetch Git Remotes git-remotes . The agent must be free to act, so its instance cannot hold anything worth stealing. API keys and tokens never enter an instance in any form. Instead, a proxy on your host isx proxy adds the real credentials to the agent's requests as the requests leave the instance, so curl , git , gh , claude and pi work unmodified inside it. How it works: - The instance's DNS resolves the intercepted domains to the proxy, and the instance trusts the proxy's certificate authority CA , so the traffic reaches the proxy without any setting in the tool. - The proxy replaces the placeholder credential that the tool sent with the real credential and forwards the request upstream over TLS. - Inside the instance, a tool sees only a placeholder such as sk-ant-placeholder . The placeholder satisfies the tool's local checks, and no service accepts it as a credential. - Nothing inside the instance yields a real credential: no API, no endpoint, no variable, no file. What the proxy can sign in as: | Credential | Who uses it in the instance | What you give isx init | |---|---|---| | Anthropic API key | Claude Code claude , Pi pi , opencode opencode | the key | | Claude Pro or Max | Claude Code claude , Pi pi , opencode opencode | the token from claude setup-token ; the proxy adds the OAuth bearer token | | Vertex AI | Claude Code claude , Pi pi , opencode opencode | your project and region; the proxy translates each request and signs it with the host's GCP credentials, which never enter the instance | | OpenAI API key | Codex CLI codex , Pi pi , opencode opencode | the key | | Gemini API key | Gemini CLI gemini-cli , Antigravity CLI antigravity , Pi pi , opencode opencode | the key | | IBM API key | Bob Shell bob | the key | | GitHub token | gh , git , GitHub Copilot CLI copilot | the token | | Atlassian API token | the atlassian-mcp tool, for Jira and Confluence | your account email and the token | | A service of your own | whatever your tool YAML installs | its credential, declared in the YAML's proxy: block Proxy Credentials https://github.com/Sanne/incus-spawn/blob/main/docs/TOOLS.md proxy-credentials | A credential can have several accounts, for example a personal and a client Claude subscription, or two GitHub identities. Each template or instance chooses which account it uses: see Credential accounts https://github.com/Sanne/incus-spawn/blob/main/docs/CONFIGURATION.md credential-accounts . Git must use HTTPS URLs, not SSH; gh defaults to HTTPS. The proxy must be running for every instance that has a network. isx init installs it as a service, systemd on Linux and launchd on macOS, or you run isx proxy start in a terminal of its own. isx checks that the proxy is reachable and compatible before a build, a branch or a shell. The proxy also caches container image layers and build artifacts on the host, so the same dependency is never downloaded twice, and the registries see fewer requests from your address Caching https://github.com/Sanne/incus-spawn/blob/main/docs/CONFIGURATION.md caching . Each start replaces the placeholders with proof tokens unique to the instance and the credential, such as gho isx … in GH TOKEN , exported by the login profile. The proxy adds an instance's credentials only to requests carrying its proof token. The tokens stay the same across stops, starts and reboots, so a nested service you configured with one keeps working. Only what runs in the instance's login environment receives the proof tokens, so a nested container gets none unless you pass one in. Plain Git is the exception: for its HTTPS requests to github.com , a credential helper isx installs presents the GitHub proof token even outside a login shell. Credential proofs https://github.com/Sanne/incus-spawn/blob/main/docs/CREDENTIAL-PROOFS.md says how to share or revoke proof tokens, and what to do after an upgrade. With a GitHub token configured, every instance gets a ready-made .gitconfig : your GitHub name and email, the private @users.noreply.github.com address when there is one, and sensible defaults. - A dedicated agent account recommended : give isx init the token of a separate GitHub account, so the agent's commits and PRs are clearly its own. - Your personal account : use your own token. To use your aliases and settings in the instance, mount ~/.gitconfig as a host resource https://github.com/Sanne/incus-spawn/blob/main/docs/TEMPLATES.md host-resources ; the mounted file takes precedence over the generated config. Commit signing is not supported inside an instance yet 271 https://github.com/Sanne/incus-spawn/issues/271 . To sign, fetch the changes to your host through git remotes git-remotes and rebase there. A branch is an instance made from a template, the way git branch makes a branch from a commit: an instant copy-on-write clone. It has its own filesystem, and nothing it changes reaches the template or another branch. The storage backend btrfs, zfs or lvm shares the unchanged data, so a branch uses disk space only for what it changes. isx init creates a btrfs storage pool if there is none. tpl-agent stopped template, ~2GB ├── fix-nasty-bug running, uses ~50MB extra ├── review-pr-423 running, uses ~30MB extra └── experiment stopped, uses ~10MB extra Install packages, break things, and destroy the branch when done. Sudo works without a password, and the shell sets the terminal title to isx: