Hand off long-running local Cline sessions to Cloud with /handoff
Use Cline desktop-v0.0.15-beta.1’s /handoff so local chats, images, and a follow-up command continue in a Cloud workspace after you close the app, with preflight push checks and interrupt recovery.
Why this loop
This beta adds session continuity: /handoff moves the conversation, attachments, and an optional follow-up into a cloud workspace that keeps working offline from the desktop app. Preflight verifies repo, branch, and commit are pushed before transfer; the composer shows progress and a receipt link. Interrupted handoffs (restart, network drop, branch move) recover or retry with draft and attachments restored. Cloud sits in the existing Local/Remote environment menu when the Cloud sessions flag is on. Teams running multi-hour agent work or needing to leave a machine can standardize push-then-handoff instead of leaving the desktop app open.
Proposed actions
- In Cline Beta (desktop-v0.0.15-beta.1), enable the Cloud sessions feature flag so Cloud appears as selectable in the Local / Remote environment menu (not "Coming soon").
- Before any handoff, push the active repository so preflight can confirm repository, branch, and commit are on the remote: git status && git push -u origin HEAD
- In a local session that should keep working after you close the app, run /handoff and attach an optional follow-up command describing the next agent step to run in the cloud workspace.
- After handoff completes, open the receipt link in the composer to confirm the cloud session and monitor progress from there instead of keeping the desktop app open.
- If a handoff was interrupted (app restart, network drop, or branch moved mid-transfer), reopen the same session so Cline can recover or cleanly retry and restore your typed draft and attachments.
Agent prompt
Paste into your agent or query via MCP (`get_agent_prompt`) — free, no extra AI costPaste into Claude Code / CLAUDE.md task
# DevAgentRadar → Claude Code You are helping me adopt a real coding-assistant change. Work only from the facts below. Do not invent features. ## Context Assistant: Cline Proposal: Hand off long-running local Cline sessions to Cloud with /handoff Summary: Use Cline desktop-v0.0.15-beta.1’s /handoff so local chats, images, and a follow-up command continue in a Cloud workspace after you close the app, with preflight push checks and interrupt recovery. Primary source: https://github.com/cline/cline/releases/tag/desktop-v0.0.15-beta.1 ## Why it matters This beta adds session continuity: /handoff moves the conversation, attachments, and an optional follow-up into a cloud workspace that keeps working offline from the desktop app. Preflight verifies repo, branch, and commit are pushed before transfer; the composer shows progress and a receipt link. Interrupted handoffs (restart, network drop, branch move) recover or retry with draft and attachments restored. Cloud sits in the existing Local/Remote environment menu when the Cloud sessions flag is on. Teams running multi-hour agent work or needing to leave a machine can standardize push-then-handoff instead of leaving the desktop app open. ## Suggested actions 1. In Cline Beta (desktop-v0.0.15-beta.1), enable the Cloud sessions feature flag so Cloud appears as selectable in the Local / Remote environment menu (not "Coming soon"). 2. Before any handoff, push the active repository so preflight can confirm repository, branch, and commit are on the remote: git status && git push -u origin HEAD 3. In a local session that should keep working after you close the app, run /handoff and attach an optional follow-up command describing the next agent step to run in the cloud workspace. 4. After handoff completes, open the receipt link in the composer to confirm the cloud session and monitor progress from there instead of keeping the desktop app open. 5. If a handoff was interrupted (app restart, network drop, or branch moved mid-transfer), reopen the same session so Cline can recover or cleanly retry and restore your typed draft and attachments. ## Your job 1. Restate the change in one sentence. 2. Propose a minimal plan for my repo (or a throwaway pilot). 3. Implement only what I approve; prefer small diffs and tests. 4. Call out risks (permissions, breaking APIs, cost). Start by confirming you understood the proposal.
Your loop
This browser · no sign-in · not shared as “you”Your decision stays on this device. A public tally appears after a few votes.