Install Cline Desktop v0.0.20 on Windows and move global rules to ~/Cline/Rules
Cline Desktop now ships a code-signed Windows x64 installer on the same auto-update feed as macOS. Put global rules in ~/Cline/Rules (WSL/headless), consolidate schedules in ~/.cline/schedules, and use Cmd/Ctrl+P for full-history session search.Why this loop
desktop-v0.0.20 is the Windows ship: a code-signed x64 installer, the same auto-update feed as macOS, sidecar/git no longer flash console windows, and updates download in the background then apply on restart. MCP settings fall back to USERPROFILE when HOME is unset. Global rules at ~/Cline/Rules were previously ignored (only ~/Documents/Cline/Rules was scanned), so they never reached the model on WSL and headless installs. Agent-created schedules were scattered across chat folders and hub-managed schedules were wiped by cron reconciliation after updates; they now live in ~/.cline/schedules, appear on the Schedules page, and the completing step auto-expands a markdown final answer. Session search is Cmd/Ctrl+P over full indexed history instead of a sidebar dialog that loaded every session. Disable enabled-but-offline remote MCP servers so startup does not stall. Checkpoint restore now refuses to reset the workspace if later commits exist. Image-returning browser/MCP tools render inline with a carousel instead of base64.
Proposed actions
- On Windows, install the code-signed Cline Desktop x64 build from https://github.com/cline/cline/releases/tag/desktop-v0.0.20, then restart the app so background-downloaded updates apply and sidecar/git no longer pop console windows.
- mkdir -p ~/Cline/Rules && if [ -d ~/Documents/Cline/Rules ]; then cp -R ~/Documents/Cline/Rules/. ~/Cline/Rules/; fi # desktop-v0.0.20 discovers ~/Cline/Rules so WSL/headless installs actually send global rules to the model
- mkdir -p ~/.cline/schedules and move agent-created schedule files out of individual chat folders into ~/.cline/schedules so they show on the Schedules page and survive cron reconciliation after an app update.
- On Windows, if HOME is unset, keep USERPROFILE set so MCP settings resolve (v0.0.20 falls back to USERPROFILE). Disconnect any enabled-but-offline remote MCP servers before starting a session so startup does not stall until teardown.
- Open session search with the sidebar search icon or Cmd/Ctrl+P (server-ranked full indexed history). When creating scheduled-task templates, require a specific final report so the completing step auto-expands as markdown labeled "Scheduled task completed".
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: Install Cline Desktop v0.0.20 on Windows and move global rules to ~/Cline/Rules Summary: Cline Desktop now ships a code-signed Windows x64 installer on the same auto-update feed as macOS. Put global rules in ~/Cline/Rules (WSL/headless), consolidate schedules in ~/.cline/schedules, and use Cmd/Ctrl+P for full-history session search. Primary source: https://github.com/cline/cline/releases/tag/desktop-v0.0.20
Why it matters
desktop-v0.0.20 is the Windows ship: a code-signed x64 installer, the same auto-update feed as macOS, sidecar/git no longer flash console windows, and updates download in the background then apply on restart. MCP settings fall back to USERPROFILE when HOME is unset. Global rules at ~/Cline/Rules were previously ignored (only ~/Documents/Cline/Rules was scanned), so they never reached the model on WSL and headless installs. Agent-created schedules were scattered across chat folders and hub-managed schedules were wiped by cron reconciliation after updates; they now live in ~/.cline/schedules, appear on the Schedules page, and the completing step auto-expands a markdown final answer. Session search is Cmd/Ctrl+P over full indexed history instead of a sidebar dialog that loaded every session. Disable enabled-but-offline remote MCP servers so startup does not stall. Checkpoint restore now refuses to reset the workspace if later commits exist. Image-returning browser/MCP tools render inline with a carousel instead of base64.
Suggested actions
-
On Windows, install the code-signed Cline Desktop x64 build from https://github.com/cline/cline/releases/tag/desktop-v0.0.20, then restart the app so background-downloaded updates apply and sidecar/git no longer pop console windows.
-
mkdir -p ~/Cline/Rules && if [ -d ~/Documents/Cline/Rules ]; then cp -R ~/Documents/Cline/Rules/. ~/Cline/Rules/; fi # desktop-v0.0.20 discovers ~/Cline/Rules so WSL/headless installs actually send global rules to the model
-
mkdir -p ~/.cline/schedules and move agent-created schedule files out of individual chat folders into ~/.cline/schedules so they show on the Schedules page and survive cron reconciliation after an app update.
-
On Windows, if HOME is unset, keep USERPROFILE set so MCP settings resolve (v0.0.20 falls back to USERPROFILE). Disconnect any enabled-but-offline remote MCP servers before starting a session so startup does not stall until teardown.
-
Open session search with the sidebar search icon or Cmd/Ctrl+P (server-ranked full indexed history). When creating scheduled-task templates, require a specific final report so the completing step auto-expands as markdown labeled "Scheduled task completed".
Config surfaces this release may change
- MCP servers (high confidence) — check your repo before applying
- background and headless runs — check your repo before applying
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-20-install-cline-desktop-v0-0-20-on-windows-and-move- and mark Applied, Skipped, or Failed. Proposal id: f60dedfd-71de-4697-85d5-4d15a9f7d231
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.