Choose an agent
DevCapsule supports three coding agents. Each is an ordinary component of the project: selected once, acquired on the next launch, signed in once, and then present in every session with its state kept.
| Agent | Add it to the project | Start it in the IDE terminal |
|---|---|---|
| Claude Code | ~/.local/bin/devcapsule project config need claude-code-agent |
claude |
| OpenAI Codex | ~/.local/bin/devcapsule project config need codex-agent |
codex |
| Antigravity CLI | ~/.local/bin/devcapsule project config need antigravity-agent |
antigravity |
Save your work and stop the capsule first. Run the need command in your
computer's terminal, from the project folder. It adds the agent to the
project's shared tool selection and lock, then asks for the vendor-download
consent that agent needs; read the terms it shows before accepting. Start the
capsule again with project run; it acquires the agent on that launch.
Use your own provider account and plan. DevCapsule does not include an AI subscription and never imports a sign-in from your computer. How each agent signs in, and what its defaults are inside a capsule, is on Sign in and defaults.
Why agents run at full speed here
Every agent starts with tool approvals off: it edits files, runs tests and uses the terminal without asking you for each step. That posture is safe because the capsule is the sandbox. An agent can change your project folder, which Git protects, and its own persistent state. It cannot reach your home directory, your credentials, your Docker daemon or your desktop unless you granted that access explicitly; Containment lists what is shared and what is not. If you prefer approvals, turn them on in the agent's own settings; the setting is yours and survives launches.
A first request
Try something small and reviewable in the IDE terminal:
Explain how this project runs, then suggest one small improvement and a way to check it. Wait for me before changing files.
Read the result, run the project's checks, commit what you keep. Give the agent durable context with an instructions file at the project root; see Instructions for agents.
Which agent?
Whichever your subscription covers. All three read a project instructions file, run inside the same boundary, and keep their sign-in per checkout. A project can select more than one, and you can switch in a later session without losing anything; see Review and change agents.