What is DevAgent?
A 60-second pitch
DevAgent is a desktop IDE for running multiple AI coding agents side by side. Every task gets its own git worktree, its own agent terminal, and its own browser tab — so you can fan out work across Claude Code, Codex, Cursor CLI, and friends without stashing, branch-juggling, or losing flow.
When to use DevAgent
- Race in parallel — spin up three agents on the same bug and pick the winner
- Review before shipping — walk AI-generated diffs line by line before they merge
- One place for many subscriptions — orchestrate Claude Code, Codex, Cursor CLI you already pay for
- Zero-setup start — use DevAgent's built-in Core / Core Pro without installing anything extra
- Remote & self-hosted — run agents over SSH, on a self-hosted DevAgent server, or in an on-demand VM — without leaving your IDE
Who it's for
DevAgent is built for people who already write code for a living and want to use AI as leverage — not as a replacement. It assumes you read diffs, care about commits, and keep a worktree tidy.
If you're looking for a no-code tool, DevAgent is not that.
Built-in Core and Core Pro
Two agents that work out of the box
Alongside external agents like Claude Code and Codex, DevAgent ships two ready-to-use agents of its own: Core and Core Pro.
They come bundled with the install — no separate setup — and appear in the agent list:
- Core — the base agent, covers everyday coding tasks
- Core Pro — builds on Core with a set of preloaded skills for more complex work
First launch just asks you to sign in; once signed in they work right away, with model credits included and nothing else to configure.
What DevAgent is not
Boundaries
DevAgent has clear boundaries. These three are commonly misunderstood:
- Not bring-your-own-only — bring your own Claude / Codex / OpenCode subscription, OR just use built-in Core / Core Pro — sign in once, done
- Not a git replacement — every worktree is a real git worktree; you can
cdin and use plain git anytime - Not a hosted VPS product — DevAgent runs on your desktop by default. Remote compute uses machines and cloud accounts you control: SSH targets, self-hosted DevAgent servers, or Cloud VMs / per-workspace environments