Lesson 1.2 · Meet Devin · 2 of 8
Cloud, Desktop and CLI: where Devin runs
Devin comes as a cloud agent, a desktop editor and a command-line tool. This lesson explains what each one is and how to pick a starting point.
By Trevor Lowing, Devin Ambassador
Checked against Devin's documentation on 2026-11-12
After this lesson you can
- Tell Devin's cloud agent, Devin Desktop and Devin CLI apart
- Explain how Devin Local relates to Devin CLI
- Pick the right starting point for how you work
People talk about Devin as one thing. It is one agent family with three ways in, and they differ mainly in where the work runs.
Read the steps as text
- Devin in the cloud. Runs in a hosted virtual machine. You use the web app, and can walk away while it works.
- Devin Desktop. An editor on your computer with Devin built in. Runs agents locally and can delegate to the cloud.
- Devin CLI. A coding agent in your terminal, working on your local files.
- Devin in the cloud. Runs in a hosted virtual machine. You use the web app, and can walk away while it works.
- Devin Desktop. An editor on your computer with Devin built in. Runs agents locally and can delegate to the cloud.
- Devin CLI. A coding agent in your terminal, working on your local files.
Devin in the cloud
This is the agent from lesson 1.1. It runs in a virtual machine that Cognition hosts, and you work with it in the web app at app.devin.ai. Because the machine is not yours, the session keeps going when you close your laptop.
Devin Desktop
The docs describe Devin Desktop as “an AI IDE with Devin built in.” It is the editor that used to be called Windsurf, and it installs on Mac, Windows or Linux. From one place you can:
- run Devin Local, an agent that works on your machine with your local files and tools
- delegate work to Devin in the cloud
- manage every agent, local and cloud, in the Agent Command Center
Devin CLI
The docs call Devin CLI “a local coding agent that runs directly in your terminal.” It installs with one command on macOS, Linux or WSL:
curl -fsSL https://cli.devin.ai/install.sh | bash
It also connects to the cloud. From the terminal you can create, steer and resume cloud sessions. One limit to know: the docs say the CLI does not yet support Knowledge, Playbooks or Secrets from your Devin account.
Devin Local and the CLI are the same engine
The docs describe Devin Local as a “next-generation agent harness shared with Devin CLI.” That means the same agent modes, permission modes and skills format in both. Learn one and you know the other.
Staying in your own editor
If you use a JetBrains IDE, you can install Devin from the ACP Registry in AI Chat, with no CLI installation needed. ACP is the Agent Client Protocol, a standard way for an editor to run an outside agent. The older Windsurf JetBrains plugin is in maintenance mode, and the docs recommend Devin over ACP.
Which one first?
| If you… | Start with |
|---|---|
| want to hand off a task and walk away | Devin in the cloud |
| want an editor with the agent built in | Devin Desktop |
| live in a terminal | Devin CLI |
| won’t leave your JetBrains IDE | Devin over ACP |
The rest of this course uses the cloud agent, because it is the quickest way to see Devin finish a whole task.
Check what you learned
3 questions. Nothing is recorded.
-
Show the answer
In a virtual machine that Cognition hosts. The docs describe Devin as a cloud-based AI software engineer that runs in a virtual machine.
-
Show the answer
They share the same agent harness. The docs call Devin Local a “next-generation agent harness shared with Devin CLI.” Same engine, two front doors.
-
Show the answer
Install Devin from the ACP Registry in AI Chat. Devin can be installed from the ACP Registry with no CLI setup. The older Windsurf plugin is in maintenance mode.
Sources
- Introducing Devin — docs.devin.ai
- Introducing Devin Desktop — docs.devin.ai
- Devin Local — docs.devin.ai
- Devin CLI — docs.devin.ai
- Devin in JetBrains IDEs — docs.devin.ai
From Devin Central — subscribe for Devin news, features & tutorials. Devin is a trademark of Cognition.