← Guides · 日本語 · Português · 中文
On this page
Guide 12 — Devin CLI & extensibility
Goal: the local-terminal Devin — run the agent on your machine, hand work to Devin Cloud, and extend it with skills, rules, plugins, hooks, and subagents. Level: intermediate Sources: Devin CLI docs — introducing, essential commands, extensibility
What it is#
Devin CLI is a coding agent that lives in your terminal and connects to Devin Cloud. Two working modes, and the power is in moving between them:
- Local — it edits your checked-out repo on your machine
- Cloud —
devin --cloudcreates/steers/resumes cloud sessions;/handoffsends a local task to a cloud Devin,/pickuppulls a cloud session back to your machine (/openopens it in the web app or Devin Desktop)
local repo ──/handoff──► Devin Cloud session ──/pickup──► local repo
▲ │
└──── devin ssh / forward (inspect its VM) ────┘
The pieces that matter#
| Surface | What it does |
|---|---|
devin ssh / devin forward |
SSH into a cloud session's VM, forward its ports, scp files |
| Subagents | Delegate to independent agents (foreground/background) with own profiles and permissions |
| Models | Adaptive routing picks the model per task; Fusion pairs a frontier lead + cheap sidekick |
| ACP | Runs inside JetBrains, Zed, Xcode via the Agent Client Protocol |
| Daemon | Since v3000.13.4 local sessions run in a background process — close the app, reattach from any client (devin daemon, devin ls session monitor) |
The daemon also rewrote multi-client semantics: a session open in another terminal or editor is no longer locked — a second client joins it, and every client sees its output and questions. devin daemon start|stop|status manages the process (it exits ~10 min after the last session and client leave); --process-model daemon|in-process picks per launch, process_model in config.json or /config sets the default. One recorded exception: in our Desktop v3.14.30825 run a second Desktop window still got a lock banner with Force open — join held CLI-side (Guide 17, frame 9).
The extensibility stack#
This is where teams make the CLI theirs — same layering as Guide 9, applied locally:
| Layer | File/mechanism | Use for |
|---|---|---|
| Rules | AGENTS.md / rules files |
Always-on instructions every session reads |
| Skills | SKILL.md |
Reusable procedures — slash-invoked or agent-chosen, with own permissions/allowed-tools |
| Plugins | plugin manifest | Bundle skills + rules + hooks + MCP servers; share through a team marketplace |
| Hooks | lifecycle hooks | Shell/LLM logic on PreToolUse, PostToolUse, SessionStart, SessionEnd… — block or rewrite tool calls, inject context |
| MCP | MCP config | External tool servers (stdio / HTTP / SSE) |
Import path: read_config_from imports settings from Cursor, Windsurf, Claude Code, Copilot, Codex, Kiro, OpenCode, Zed — migration is one flag, not a rewrite.
Three workflows worth copying#
1. Local → cloud fan-out. Start a task locally, hit its limits, /handoff to a cloud session that keeps going on its own machine — pull the work back to your machine with /pickup.
2. Skills as memory. Turn any repeated procedure (Guide 11's migration skill, a hotfix runbook, a release cut) into a SKILL.md — the CLI docs note feeding successful session transcripts back into skills to close gaps. Plugins package and share them to the whole team.
3. Guardrails via hooks. PreToolUse hook that blocks rm -rf patterns or forces review on migrations — enforcement lives in the hook, not in hoped-for model behavior.
Walkthrough — recorded on Devin CLI v3000.14#
A real run, not a mock-up: Devin CLI 3000.14.30821 on Linux, Pro plan, a throwaway demo-repo with an app.py. Models: swe-2-flash-high for the edit task, swe-2-high for the skill run (both SWE-2 tiers are listed as Free in devin models).
Video (67 s, no audio): the whole session below, from login to the handoff error.
1. devin --model swe-2-flash-high — login confirmed, then the workspace trust prompt
2. Prompt: add a subtract function and a test. Devin shows the diff and asks — Allow, Accept edits mode, Bypass mode or Deny
3. Result: app.py edited, test_app.py written; pytest was missing, so Devin ran the tests with python -c and said so
4. /model — Adaptive, Fusion (lead + sidekick) and model families; SWE-2 Flash shows FREE, no quota consumed
5. /exit prints a devin -r
6. devin --cloud, then /list-sessions — the account's cloud sessions, newest first
7. .devin/skills/review/SKILL.md runs as /review on swe-2-high and reviews the uncommitted changes
8. Pitfall: /handoff fails in a repo with no git remote — "Handoff only works from git repos with a remote configured"
The skill used in step 7, verbatim:
---
name: review
description: Review recent changes in this repo and report issues
---
Review the working tree's uncommitted changes. List each changed file,
summarize what it does, and flag anything that looks wrong or risky.
Keep it under 10 lines.
Verify it#
- [ ]
devinruns a local session;devin --cloudlists/creates cloud sessions - [ ] A
/handoff'd task completed in the cloud and the session came back to your machine via/pickup - [ ] A
SKILL.mdinvoked by slash command ran your procedure - [ ] (Enterprise) team marketplace serves your plugin to another member
Pitfalls#
- Local for parallel work. The CLI is one agent in your terminal — for parallel slices use cloud sessions or a Bot; the CLI is the hands-on surface.
- Rules sprawl.
AGENTS.md+ project rules + global rules interact by precedence — keep each rule in exactly one layer or they fight. /handoffneeds a remote. In a repo with no git remote it fails immediately — push the repo somewhere Devin Cloud can clone first.
Knowledge check#
- When do you use
/handoffto Devin Cloud instead of finishing locally? (When the work needs cloud-scale parallelism, org tools, or runs longer than your laptop stays open.) - What's the difference between a skill, a rule, and a plugin? (A skill is a task procedure, a rule is standing context, a plugin is the package that ships both plus hooks.)
- Why does hooks + subagents matter for team adoption? (Hooks enforce org policy at every CLI session; subagents let one operator run a fleet — the two scale in opposite directions.)
Sources#
- Devin CLI docs — quickstart, commands, cloud integration, extensibility, ACP, models
- Related: Guide 9 — Playbooks & knowledge (same conventions layer, org-wide)
