Start in Devin CLI, then hand off to cloud

Use Devin CLI to build context locally, then pass the same session to Devin Cloud so it can keep working without a reset.

Done with Devin· Intermediate· Sep 2026

What they did
The poster began a coding session in Devin CLI on their own machine and let it inspect the repository first. Once it had enough context, they used /handoff to move that same session into Devin Cloud. From there, Devin kept going without asking for the setup again, and they could also change models within that environment when needed.
How it went
They said this local-to-cloud flow is one of the Devin features they rely on most, and it helped keep them using the product. They did not share a specific task result for the handoff itself, but noted that parts of Desktop still feel less polished than the CLI.
Tips
This setup seems useful when you want a local read of the codebase before letting the agent continue on its own. Keep an eye on plan limits and model costs; the poster used the $20 Pro plan and mentioned SWE-2 was free until October 8.

Try it yourself with Devin

I’m working in [repo name] on [task]. First, use the local CLI to inspect the repository, identify the main structure, and note the files and conventions that matter for this work. Briefly tell me what you found. Then continue on your own in the same session, but stop and ask for my approval before you do anything irreversible, such as sending changes, opening a pull request, deleting files, or making payments. After I approve, keep going and finish the task.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on reddit.com ↗

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.