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
Cline desktop-v0.0.15-beta.1 (app name: Cline Beta) adds /handoff: the local conversation, attached images, and an optional follow-up command move to a Cloud workspace that keeps working after the desktop app closes. Preflight requires the repository, branch, and commit to be pushed; the composer then shows handoff progress and finishes with a receipt linking to the cloud session. If the app restarts, the network drops, or the branch moves mid-transfer, reopening the session recovers or cleanly retries and restores the typed draft and attachments. Cloud now lives in the existing Local / Remote environment menu (selectable only when the Cloud sessions feature flag is on; otherwise Coming soon). The separate Local / Cloud toggle is gone; repository and branch controls are unchanged. This build also includes 0.0.14: unified Plugins hub with Marketplace, recommended and free model tiers, scheduled tasks, and the rename to Cline. Treat long jobs as handoff-first instead of leaving the desktop app open.
Proposed actions
- Install Cline desktop-v0.0.15-beta.1 (window title Cline Beta). Open the existing Local / Remote environment menu and select Cloud. If the Cloud sessions feature flag is off, Cloud will show Coming soon—do not look for the removed Local / Cloud toggle; leave repository and branch controls as they are.
- Immediately before any long-running local session you plan to hand off, satisfy preflight by pushing the current repo/branch/commit: git push -u origin HEAD && git status && git rev-parse --abbrev-ref HEAD && git rev-parse HEAD
- In the local Cline composer that already has the conversation and any attached images, run: /handoff continue from the last incomplete step, keep using the attached images, and do not stop when the desktop app closes
- If handoff is interrupted (app restart, network drop, or the branch moving mid-transfer), reopen the same session so Cline recovers or cleanly retries; confirm the typed draft and attachments are restored, then open the cloud session from the composer receipt link and close the desktop app.
- On this same beta, open the unified Plugins hub Marketplace page, pick a recommended or free model tier in the model picker, and create one scheduled task for the agent so overnight work is not tied to an open desktop window.
Agent prompt
Paste into your agent or query via MCP (get_agent_prompt) — free, no extra AI costCline / .clinerules task
DevAgentRadar → Cline
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
Cline desktop-v0.0.15-beta.1 (app name: Cline Beta) adds /handoff: the local conversation, attached images, and an optional follow-up command move to a Cloud workspace that keeps working after the desktop app closes. Preflight requires the repository, branch, and commit to be pushed; the composer then shows handoff progress and finishes with a receipt linking to the cloud session. If the app restarts, the network drops, or the branch moves mid-transfer, reopening the session recovers or cleanly retries and restores the typed draft and attachments. Cloud now lives in the existing Local / Remote environment menu (selectable only when the Cloud sessions feature flag is on; otherwise Coming soon). The separate Local / Cloud toggle is gone; repository and branch controls are unchanged. This build also includes 0.0.14: unified Plugins hub with Marketplace, recommended and free model tiers, scheduled tasks, and the rename to Cline. Treat long jobs as handoff-first instead of leaving the desktop app open.
Suggested actions
- Install Cline desktop-v0.0.15-beta.1 (window title Cline Beta). Open the existing Local / Remote environment menu and select Cloud. If the Cloud sessions feature flag is off, Cloud will show Coming soon—do not look for the removed Local / Cloud toggle; leave repository and branch controls as they are.
- Immediately before any long-running local session you plan to hand off, satisfy preflight by pushing the current repo/branch/commit: git push -u origin HEAD && git status && git rev-parse --abbrev-ref HEAD && git rev-parse HEAD
- In the local Cline composer that already has the conversation and any attached images, run: /handoff continue from the last incomplete step, keep using the attached images, and do not stop when the desktop app closes
- If handoff is interrupted (app restart, network drop, or the branch moving mid-transfer), reopen the same session so Cline recovers or cleanly retries; confirm the typed draft and attachments are restored, then open the cloud session from the composer receipt link and close the desktop app.
- On this same beta, open the unified Plugins hub Marketplace page, pick a recommended or free model tier in the model picker, and create one scheduled task for the agent so overnight work is not tied to an open desktop window.
After you finish
Do not report this as applied to DevAgentRadar. You cannot write the visitor's loop.
Tell the human: open https://devagentradar.com/proposals/cline-desktop-v0-0-15-beta-1-hand-off-long-running-local-cline-sessions- and mark Applied, Skipped, or Failed. Proposal id: f801548c-c659-499e-b629-de80d8ccd55c
Your job
- Restate the change in one sentence.
- Propose a minimal plan for my repo (or a throwaway pilot).
- Implement only what I approve; prefer small diffs and tests.
- 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”After you run the prompt
Only you can mark this. Agents cannot write your loop.
Your decision stays on this device. A public tally appears after a few votes.