Two community posts from July, read together, describe where Devin’s most committed users have landed — and the seam they keep tripping over.
The first is a productivity report. @ishaangtwt, on a Devin Max plan, described his highest-output month of the year: use Devin Desktop to generate a full plan divided into phases with clear instructions, then run Devin CLI sessions under tmux with shell config files to execute autonomously with minimal intervention. His claimed tally — 80k+ generated lines, five shipped projects including a Slack-native agent and a production RAG system over 10M+ documents — is self-reported and unverifiable, but the shape of the workflow is the interesting part: the Desktop is the planning surface, the terminal is the execution surface.
The second is a feature request. @davidfromkansas asked for the missing seam: “My most requested feature for Devin Desktop is to easily allow me to turn local sessions into cloud sessions.” As far as he could find, the only path ran through the CLI.
What the docs actually support
He’s read the product correctly. Per the handoff docs, there are two supported routes into a cloud session today:
From the CLI
The built-in /handoff command packages your conversation context and current git branch into a cloud session that picks up where you left off. Run it bare and the cloud continues automatically.
From any other agent
The open-source Devin Handoff plugin brings the same move to Claude Code, Codex, Cursor and others — it gathers repo, branch, and uncommitted diff (truncated to 100KB) and creates a session via the API.
From Desktop's local agent
No equivalent one-click move documented. The workaround is the CLI path — which is exactly the friction the feature request describes.
The docs are also clear about when the handoff earns its keep: work that needs a VM or browser, CI/CD debugging, long-running migrations, or parallel execution while you keep coding locally. The cloud session gets its own machine, shell, and browser, “so it can keep going after you close your laptop.”
Desk note: we’ll watch the Desktop changelog for this one — the request is specific, loud, and, given the CLI already does it, mostly a UI problem.
Method: Workflow mechanics from docs.devin.ai (fetched 2026-08-12). The productivity figures are the author's own claims on X — a field report, not telemetry. The feature-gap claim was checked against the handoff and CLI docs as of this writing.
References
- Hand off to cloud Devins —
/handoff, the plugin route, and when to use each. - Devin CLI — the local agent with the built-in command.
- Devin Handoff on GitHub — open-source handoff from any coding agent.
- @ishaangtwt’s month report — the Desktop-plans / CLI-executes pattern.
- @davidfromkansas’s request — the local→cloud seam.
Editorial from Devin Central — a fan news desk, not Cognition. Devin is a trademark of Cognition.