dev-3.0Integrations
Agents dev-3.0 runs, and how far each one is wired in
dev-3.0 does not ship its own model or host agents for you. It launches the coding-agent CLI you already installed, under your own account, inside each task's git worktree and terminal. What differs per agent is how much dev-3.0 can do around it.
Built-in agent support
These agents have a dedicated adapter: dev-3.0 knows their flags, installs the dev3 skill for them, and can bring a task's session back after a restart.
| Agent | Command | Task status updates | Session resume |
|---|---|---|---|
| Claude Code | claude | Automatic, via hooks | The exact session |
| Codex | codex | Automatic, via hooks | The exact session |
| GitHub Copilot CLI | copilot | Automatic, via hooks | The exact session |
| Oh My Pi | omp | Automatic, via a status extension | The exact session |
| Cursor Agent | agent | Reported by the agent, following the dev3 skill | The exact session |
| Gemini CLI | gemini | Reported by the agent, following the dev3 skill | The exact session |
| OpenCode | opencode | Reported by the agent, following the dev3 skill | The most recent session only |
Model selection, permission modes, effort, budgets and system-prompt injection also differ per agent. The full grid, kept next to the code, is the agent support matrix.
Any other CLI tool
Any command can be configured as a task's agent. dev-3.0 starts it in the task's worktree and terminal and passes the task prompt, but there are no status hooks, no dev3 skill and no session resume: you move the card yourself.
Model backends
Claude Code and Codex can each run against their native API or against Amazon Bedrock, switched per agent in Settings → Coding Agents. dev-3.0 sets only the provider switch and the model; your credentials stay in your own agent setup.
Tools around the agent
- Git and GitHub. Every task is a git worktree on its own branch. Pull requests are opened through the GitHub CLI (
gh), and a pull request can be pulled onto the board as a review task. - Your editor. One click opens a task's worktree in VS Code or Cursor. dev-3.0 has no editor of its own.
- Remote access.
dev3 remoteserves the full UI to a browser over your LAN, an SSH forward or a Cloudflare tunnel (cloudflared). See the remote access guide.
Through your agent, not through dev-3.0
Issue trackers, chat, databases and other services are reached by your agent, for example through the MCP servers you configure in it. dev-3.0 has no direct Linear, Jira or Slack integration of its own. For Claude Code, dev-3.0 pre-approves the MCP servers a project lists in its .mcp.json, so they are ready inside every task.