Access to Devin Cloud is rolling out gradually. If you don’t see Devin Cloud, try logging out and logging in to Devin Desktop.
What Devin does
Devin handles complex tasks end to end — debugging, deployment, testing, and more. Each Devin session runs on its own VM with a desktop, browser, and computer use, so it can keep working after you close your laptop.Devin pricing
For self-serve users, Devin is included with your existing Devin Desktop plan and will directly consume the shared quota and extra usage balance from Devin Desktop. When you first connect your GitHub to Devin, you will be granted up to $50 in extra usage credits to try out Devin. The exact amount depends on the maturity of your GitHub account.Delegating work to Devin
You can work on a plan with a local agent and, with a single click, send it to Devin for implementation. Devin spins up its own machine and gets to work while you keep coding locally — or close your laptop and come back later.Working in a Devin session
Devin sessions in Devin Desktop stay in sync with the web app:- Send queue — press
Cmd/Ctrl+Enterto queue your next message on the server rather than sending it immediately. Because the queue lives server-side, it survives reloads and shows up in the web app too. - Participant names — in multi-user (Slack) sessions, each message shows the name of the participant who sent it.
- Copy link — grab a link to the session from the session menu to share it or open it in the web app.
Where Devin shows up
Devin sessions appear alongside your local agent sessions in the Agent Command Center, and can be organized into Spaces along with everything else related to a task.Agent Command Center
Manage every agent — local and cloud — in one Kanban view.
Spaces
Group sessions, PRs, files, and context for a task.

