← Guides · 日本語 · Português · 中文

Updated 2026-11-20

On this page
  1. What it is
  2. Agent Command Center
  3. Devin Local — the daemon change
  4. IDE mode
  5. Two workflows worth copying
  6. Walkthrough — recorded on Devin Desktop v3.14.30825
  7. Verify it
  8. Pitfalls
  9. Knowledge check
  10. Sources

Guide 17 — Devin Desktop

Goal: the agent-native editor — every surface of Devin in one window: cloud sessions, local sessions (Devin Local), Bots, and a real IDE around them. Level: start here Sources: Desktop changelog · CLI changelog

What it is

Devin Desktop is the Windsurf-based editor where all of Devin's surfaces live side by side. Three things to tell apart:

Surface Where it runs Use it for
Cloud session Devin's machine, in your org Unattended tasks, parallel work, PRs for review
Devin Local A background process on your machine Hands-on edits in your checked-out repo
Bot Persistent agent (see guides 1–5) An outcome to own — available in Desktop since v3.14

Agent Command Center

The Command Center is the session hub — not an editor:

Devin Local — the daemon change

Since v3.13.4 (Desktop) / v3000.13.4 (CLI), a local session runs in a background process, not inside the window that started it:

The practical consequence: local work is now durable. Start a long task, close the laptop, reattach from another client — the session kept going.

IDE mode

Two workflows worth copying

1. Local → cloud → local. Work in Devin Local, hit the wall (needs org tools, more parallelism, longer than your laptop stays open), /handoff to cloud, review the PR back home. The daemon makes both halves resumable.

2. One window, many surfaces. Command Center for the fleet view, Local for the repo you're in, a Bot for the outcome you don't want to babysit — Desktop is the only place all three share a window.

Walkthrough — recorded on Devin Desktop v3.14.30825

A real run, not a mock-up: macOS, Pro plan. A Devin Local session edits a throwaway demo-repo on SWE-2 High, then survives the app quitting and gets handed between the CLI and Desktop.

Video (91 s, no audio): Command Center → tabs → Bots → Devin Local → daemon proof → IDE view.

Devin Local session finishing on SWE-2 High — 2 files changed in demo-repo

1. Command Center Home — recent sessions, Your Bots, Cloud/Local toggle on the composer 1. Command Center Home — recent sessions, Your Bots, and the Cloud/Local toggle on the composer

2. The composer model picker — capability tiers plus model previews 2. The composer model picker: capability tiers (Fusion → Free) and previews incl. SWE-2 Lightning/Flash

3. A cloud session opens as a tab; the right rail holds Computer, Files, Changes, Terminal 3. A cloud session opens as a tab — the right rail holds Computer, Files, Changes, Terminal

4. The session header "..." menu — usage stats, archive, network config, create-automation/skill-from-session 4. The session header "..." menu; MCP servers appear here when a session has them (this one has none)

5. Bots in Desktop — the Bots page opens, but messaging needs Max or Teams 5. Bots in Desktop: the Bots page opens, but this plan can't message a Bot — "Bots require Max or Teams" (honest gap)

6. Devin Local asks before running commands — Allow or Reject, per command 6. Devin Local asks before running commands — Allow or Reject, per command

7. The Local session finished on SWE-2 High — 2 files changed, quick-review diff 7. The Local session finished on SWE-2 High — 2 files changed, with a quick-review diff

8. Daemon proof: quit Desktop, devin ls still lists the session; resuming attaches with the full transcript 8. Daemon proof: quit Desktop, devin ls still lists the session — resuming attaches with the full transcript

9. A second client gets a lock banner; Force open transfers the session, the first client disconnects 9. Two clients can't co-pilot: the second gets a lock banner, Force open transfers the session, the first client disconnects

10. IDE view: source control lists the session's edits; unsaved tabs show a dot until Cmd+S 10. IDE view: a real editor around the same session — source control lists its edits; unsaved tabs show a dot until Cmd+S

Verify it

Pitfalls

Knowledge check

  1. What changed about local sessions in v3.13.4? (They run in a background process — closing the app no longer stops them, and any client can see and take over the session.)
  2. When do you pick Devin Local over a cloud session? (When you want hands-on edits in your checked-out repo with your local context; hand off to cloud for scale or org integrations.)
  3. What lives in the session header's "..." menu? (The session's MCP servers — toggle or re-authenticate them per session.)

Sources