Cloud, Local, and Cascade: the three ways Devin actually works

People do not argue about “Devin” in the abstract. They argue about which Devin showed up for the job — the cloud session that keeps grinding after the laptop sleeps, the helper that lives in the editor, or the one you fire from a terminal.

That mix-up is costing teams hours. Cognition’s docs draw the lines carefully. Hallway talk usually does not. This desk story maps the three surfaces in plain English, with citations — so you pick the right runtime the first time.

Three surfaces — not three marketing slogans

Surface	What Cognition calls it	Where you open it
Cloud Devin	Autonomous engineer on a cloud VM (desktop, browser, computer use)	app.devin.ai, Devin in Desktop, API / Slack / Teams
Cascade	Devin Desktop’s agentic assistant (Code + Chat), Cmd/Ctrl+L	Devin Desktop
Devin Local / CLI	Shared local agent harness on your files — meant to eventually replace Cascade	Agent picker in Desktop; devin in a project folder

That third row is where teams get tripped up. People say “Local” when they mean Cascade. The docs do not. Devin Local “is meant to eventually replace Cascade as the primary local agent,” is still in preview, and is not supported in Desktop’s JetBrains plugin. The CLI is “a local agent like Cascade” that shares Local’s harness — with a hard path into the cloud when the laptop is not enough.

In Devin Desktop 2.0, the Agent Command Center puts local and cloud sessions on one Kanban: Cascade (and Local) beside cloud Devin VMs.

Cloud — the session that does not need your laptop open

Documented sweet spots: parallel backlog (tickets, features, bugs), migrations, repetitive chores, integration prototypes. The playbook is blunt — clear prompts, explicit done-when, and work that is easy to check (CI green, deploy checks). Rule of thumb on both get-started and when-to-use: if you can do it in about three hours, Devin most likely can; longer work gets split.

For shipping culture, the money page is when-to-use: turn on Devin Review with Auto-Fix so Devin answers review comments, fixed flagged bugs, and chases CI failures without you babysitting. Ideal state in their words: CI passes and the PR is ready to approve.

CLI /handoff lists when to bounce to cloud: need a VM or server, browser flows, CI/CD work, long jobs, or parallel runs while you keep coding. Repo, branch, conversation, and uncommitted diffs can ride along — into a fresh VM. Commit or stash what you do not want shipped up.

Pairing: Cloud is async pairing. One person frames the ticket; another (or you tomorrow) reviews the PR. It is a terrible shoulder-surf editor. That job belongs to Cascade or Local.

Cascade — the pair partner in the buffer

Status check: Cascade is still the feature-complete IDE agent. Cognition’s CLI controls page spells out what Local still lacks: Cascade-style memories, workflows, codemaps, code lenses, Fast Context UI, app deploys, in-IDE browser previews, conversation sharing — plus thinner analytics. Local is the future; Cascade is the tool many teams still live in today.

Pairing: Classic desk. Navigator owns direction; driver (Cascade) types. Chat mode lets seniors stay picky before Code mode gets the keys.

Limits: Cascade is not the cloud VM. Overnight autonomy, browser-heavy QA on an isolated machine, or parallel cloud capacity → cloud Devin. Cascade is also the legacy local agent in Cognition’s succession story — fully documented, widely used, not the end of the road.

Devin Local and Devin CLI — one harness, two doors

Status: Preview. Gaps vs Cascade are documented. Intended path: Local becomes the primary local agent. Admins can push teams off legacy Cascade controls; those Cascade toggles do not govern Local/CLI.

When-to-use recommends CLI for quick fixes, exploration, and work that needs your environment — with /handoff when the laptop is not enough. Permissions, hooks, AGENTS.md, skills, MCP, plugins: that is the governance story for teams that want agents inside the same fences as humans.

Pairing: Driver–navigator in the shell or ACP editor. The bridge to CI-minded cloud work is /handoff, not pretending your laptop is the VM.

How this fits pair programming and CI

Cognition’s own guidance collapses to four beats:

1. Prove it. Prefer tasks with CI, tests, or other hard finish lines. Cloud Devin can QA in a full desktop/browser before opening a PR.
2. Close the loop. Review + Auto-Fix is the published way to soak up comments and red builds.
3. Match the runtime. Local context → CLI / Local. VM, browser automation, long or parallel cloud work, CI plumbing → cloud (or handoff). Live buffer pairing → Cascade today, Local as the preview path.
4. Same merge bar. Agent or human — draft PR, CI green, human approve.

What the docs do not say: any surface replaces a teammate, or that Local already is Cascade. Shipping preview Local as “done Cascade replacement” is a desk mistake.

A quick chooser

You need…	Start here	Why (docs)
Overnight draft PR with clear acceptance	Cloud	Own VM; Review / Auto-Fix; parallel sessions
Fixes in your repo and toolchain	CLI / Local	Local context; /handoff when stuck
Live pair in the editor, existing Cascade workflows	Cascade	Full IDE agent; Local still incomplete
Plan here, implement there	Local/Cascade → Cloud	Desktop send; CLI /handoff

References

1. Introducing Devin — cloud framing; tools; three-hour rule; CLI pointer.
2. When to Use Devin — CI verification; Review / Auto-Fix; CLI + handoff.
3. Cascade Overview — Desktop agent; Code/Chat; extensibility.
4. Devin Local Agent — shared harness; succession; preview gaps.
5. Devin CLI Quickstart — local CLI + cloud integration.
6. Controls — Local vs Cascade feature matrix.
7. Hand off to cloud Devins — CI/CD handoff triggers; fresh VM.
8. Devin in Devin Desktop — cloud agent in Desktop.
9. Agent Command Center — local + cloud Kanban.

---

Editorial from Devin Central — a fan news desk, not Cognition. Devin is a trademark of Cognition.