Paste 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: Stand up durable todos and recurring schedules in Cline desktop
Summary: Upgrade to Cline desktop-v0.0.15, then drive multi-step work through durable agent todos and one-time/recurring schedules, pick models via Recommended/Free tiers, and manage MCP/Skills from the unified Plugins Marketplace.
Primary source: https://github.com/cline/cline/releases/tag/desktop-v0.0.15

## Why it matters
desktop-v0.0.15 renames the app to Cline (settings/sessions/credentials carry over) and adds agent-managed durable todos plus one-time or recurring schedules—so long-running work no longer depends on a single chat turn. The composer model selector now leads with Recommended and Free tiers (Subscribed/Free on ClinePass) by display name and description instead of raw model ids, which makes cheaper/default picks explicit. Plugins, MCP servers, and Skills sit in one Plugins hub with a Marketplace page, so extensions should be installed and reviewed there. Hook fixes (PreToolUse contextModification reaching the model; PostToolUse output/cancel honored) and provider-executed tool activity now showing mean automated todo/schedule runs are more trustworthy. Usage also shows billed gateway cost, so scheduled work can be cost-aware.

## Suggested actions
1. Upgrade the desktop app to Cline desktop-v0.0.15 (formerly Cline Code); confirm settings, sessions, and credentials carried over and only name/icon changed.
2. In the composer model selector, choose a model from the Recommended or Free tier (Subscribed/Free if on ClinePass) by display name/description—not a raw model id—and mirror that choice in provider settings badges.
3. Open the unified Plugins hub → Marketplace; re-add or install needed MCP servers and Skills from there instead of the old separate entry points.
4. For your next multi-step task, instruct the agent: 'Create durable todos for the remaining work, mark them in progress/done as you go, and do not stop until the todo list is cleared.'
5. For repeat ops (deps refresh, flaky-test triage, changelog draft), instruct the agent: 'Create a recurring schedule that runs this prompt on an interval and a one-time schedule for the next release cutoff; report billed gateway cost from Usage after each run.'

## Config surfaces this release may change
- hooks — check your repo before applying


## 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.