Warp's Oz Keeps AI Coding Agents Running After You Close Your Laptop
Warp's new Cloud Handoff lets you close your laptop mid-task and have your AI agent seamlessly continue running in the cloud, with full context preserved.
Takeaways
- Cloud Handoff is live in the latest Warp version: closing your laptop automatically migrates active agent sessions to the cloud.
- Full context is preserved on handoff -- no re-prompting, no lost history, artifacts carry forward automatically.
- Enable it via Settings > Agents > Warp Agent > Cloud Handoff; conversations sync after each agent interaction.
- Multi-harness support: Oz can now orchestrate Claude Code, Codex, and Warp Agent in parallel across cloud environments.
- Free preview period: platform credits for cloud agent runs are not billed until July 1, 2026 on self-serve plans.
- Current limits: cloud agents don't support image attachments; same-conversation multi-device sync is snapshot-based, not real-time.
Warp just shipped a feature that solves one of the most frustrating problems with long-running AI coding agents: what happens when you need to close your laptop. The answer is Cloud Handoff -- a new capability that automatically migrates an active local agent conversation to the cloud the moment your machine goes to sleep, so the work keeps going without you.
The problem it actually solves
Anyone who has used an AI agent to tackle a large refactor or a multi-step deployment knows the anxiety: the task takes 20 minutes, you need to leave your desk, and closing the lid kills everything. You come back to a dead session and have to start over, re-explaining the entire context from scratch.
Cloud Handoff eliminates that worry. The conversation, context, and artifacts carry forward automatically -- no copy-pasting prompts, no re-explaining the task. When the cloud agent finishes, you can verify locally, iterate, or ship.
How it works
Warp's agent platform is called Oz -- it's the orchestration layer that coordinates agents whether they run locally on your machine or in the cloud. Oz is the orchestration platform for cloud agents that powers all of Warp's intelligent features, designed to coordinate agents at scale -- understanding your codebase, executing tasks autonomously, and adapting to your workflows.
The cloud sync feature syncs agent conversations to the cloud, making them accessible across devices, shareable with teammates, and persistent even after logging out. The handoff mechanism is what's new: instead of just saving a snapshot, it actively promotes a running local session into a full cloud agent run that continues executing.
Warp has made it easier to hand off agent sessions in any direction -- local-to-remote, remote-to-local, or remote-to-remote. You can start an agent on your phone, continue on your laptop, and then move it back to the cloud to continue working overnight.
Enabling it
The feature is live now in the latest version of Warp. To turn it on:
- Open Settings
- Navigate to Agents > Warp Agent > Cloud Handoff
- Toggle it on
When enabled, your agent conversations automatically sync to the cloud as you interact with the agent. When disabled, conversations are stored locally on your machine only.
Once a conversation lands in the cloud, cloud-synced conversations appear in all the usual conversation management entry points alongside your local conversations. You can browse, search, restore, and delete them just like any other conversation.
What you can do with cloud agents
Cloud agents aren't just a passive backup. They're useful for running parallel agents across multiple tasks, running agents remotely on hosted computers to offload compute from your local machine, running agents autonomously in the cloud, and checking in on your agents from anywhere.
You also retain full control mid-run. For cloud agent runs, you can inspect run state, tool calls, and logs; steer the agent while it's running; and unblock it with additional instructions or context. If you're not happy with where it landed, you can take over to finish the task. That human handoff is a core part of making agents reliable beyond demos.
You can interact with cloud agents through Warp Terminal, Web, or Mobile, and trigger them from Slack, Linear, GitHub, or directly via CLI, API, or SDK.
The bigger picture: multi-harness orchestration
Cloud Handoff is part of a broader push Warp is making with Oz. Warp now supports the most popular CLI coding agents -- including Claude Code, Codex, Gemini CLI, and OpenCode. Being multi-harness means that companies can ask Oz to spin up cloud agents that directly use Claude Code, Codex, and Warp Agent to solve their tasks. Oz provides the ability to launch, track, govern, and steer any of these agents in one unified control plane.
Oz can now orchestrate subagents automatically, deploying and tracking multiple agents in parallel for difficult, long-horizon tasks like large feature builds, code migrations, and production deployments. This works across harnesses, and comes with auto-tracking, steering, and a management interface that shows progress across subagents.
The security story holds up too. All cloud agent data stored in the cloud is encrypted at rest and in transit, and protected by Warp account-level access controls. Cloud agent environments are sandboxed by default, with scoped access to repos, secrets, and compute.
What it costs
The Build plan starts at $20/month and includes 1,500 credits per month for cloud and local agents, with full Warp Agent access including frontier OpenAI, Anthropic, and Google models. The Free tier gives you limited cloud agent access to try the feature. For self-serve plans, platform-credits billing doesn't start until July 1, 2026 -- between now and June 30, all self-serve plans are in a preview period where platform credits are not consumed. That means right now is actually the best time to experiment with cloud agents at no extra cost.
The limitations worth knowing: cloud agent conversations do not currently support image attachments. And if you open the same conversation on two different machines, each continues independently from the last snapshot -- changes on one machine do not sync to the other in real time. For live collaboration on a single session, Warp has a separate Session Sharing feature for that.
For anyone running long-horizon agent tasks -- migrations, feature builds, production deployments -- Cloud Handoff removes the last major reason to babysit your terminal. Close the laptop. The agent keeps going.