DevCapsule.
PyCharmIntelliJ IDEAEclipseRiderVSCodium

Let your coding agent work. Keep your workstation yours.

Run Claude Code, Codex, or Antigravity without approving every routine step. DevCapsule brings your agent, a full IDE, and your project's tools together in one persistent container on your own computer. Start here: open your first workspace on Linux x86-64; on Windows, read the WSL2 notes first.

Your host home directory, SSH keys, and desktop session stay outside by default. You decide what additional access to grant.

The environment your agent tests in is the one you debug in.

Open your first workspace 0.3.0 Watch a session
Watch a real session inside a capsule

See a sample of a full graphical IDE running inside DevCapsule's isolated Docker container. More scenario illustrations coming soon.

Watch a real session inside a capsule

See a sample of a full graphical IDE running inside DevCapsule's isolated Docker container. More scenario illustrations coming soon.
1 / Try it

Your first session

Open a desktop IDE inside a capsule, run a small JavaScript program, stop the session, and come back—in fifteen minutes with no AI account.

Read the guide 2 / Your project

An existing repository

Open an existing repository inside a capsule, whether it already commits .devcapsule/ or needs initialization, and see what crosses the boundary.

Read the guide 3 / Your agent

Choose an agent

Add Claude Code, OpenAI Codex or the Antigravity CLI to your checkout in one command, and let it work at full speed inside the capsule's boundary.

Read the guide
Why switch

Why switch to DevCapsule?

Give agents room to work

Run Claude Code, Codex, or the Antigravity CLI without approving every routine command, behind a container boundary where your host home directory stays outside by default and extra mounts are explicit opt-ins.
What the capsule can touch

Inspect and debug in the same environment

Open PyCharm, IntelliJ IDEA, Eclipse, Rider, or VSCodium on the same workspace and toolchain the agent used—edit, run tests, inspect results, debug, or take over directly.
Your first session

Come back ready to continue

Stop for an hour or a month. Persistent container state, IDE settings, agent sign-ins, and file-based workstream records let you or the next agent resume without rebuilding context from chat history.
Sessions
Engineering continuity

Pick up where the last session stopped

When a developer or coding agent pauses work in DevCapsule, the handoff lives in a versioned status file in the repository rather than inside a chat window. Here is a real handoff excerpt from building DevCapsule (0.3.0 release verification on maintenance):

  • What changed: Repaired the automated GUI smoke harness and verified persistent workspace state across devcapsule stop and devcapsule start for IntelliJ IDEA, PyCharm, Eclipse, Rider, and VSCodium.
  • What was checked: Full test suite (557 passed), documentation contract check (docs-contract), and recorded two-session persistence runs with saved screenshots and WebM videos.
  • What remains uncertain: Cold first-import Maven indexing time on larger multi-module Java projects under constrained container CPU quotas.
  • Next action: Publish the landing-page demonstration update and verify the rendered site across desktop and mobile viewports.

At the start of the next session, the incoming agent or developer reads CURRENT-STATUS.md and the active workstream record before touching code—resuming with the same verified state, open questions, and next step (read the workflow · browse the engineering journal).

Is it for you?

Is it for you?

The long answer ↗

Good fit today

  • You develop on Linux x86-64, or on Windows through WSL2, with Docker and Git already on your command line.
  • You run one or more coding agents on real projects and want them fast without giving them your home directory.
  • You like knowing exactly what a tool can touch, and you would rather read a bug record than guess.

Not yet

  • macOS: the executable is Linux-only and a port has not been started.
  • ARM: not covered by this release.
  • A polished experience: this is pre-V1. Expect edges, and expect every edge to have a file.
Built with itself

The development journal.

DevCapsule is developed inside DevCapsule, by one person and several agents, and the journal is the transcript. We DO eat our own dog food.

All entries ↗
Current release

DevCapsule 0.3.0

DevCapsule 0.3.0 adds a session web console, persistent diagnostics, more IDE choices, and separate project requirements and personal setup.

Release notes ↗All releases ↗All documentation versions ↗
Start here

Open your first workspace.

Start here 0.3.0

Every open bug is a file under engineering-docs/bugs with its evidence, and every workstream a status file that says what is next. Pick a bug, work it with an agent inside DevCapsule, and send it back as a pull request; the developer brief and the workflow tell you what to read first. A one-page front door for first contributions is coming; until then, an issue saying what you tried is the right first message.

Contribute ↗