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: Click View Changes on Cline completion rows to review full task diffs Summary: Cline v4.1.7 restores View Changes on completion rows (SDK checkpoints), a copy button on turn-final rows, and pre-registered OAuth for remote MCP. Use completion-card diffs and OAuth setup to verify every edit and keep MCP sessions alive. Primary source: https://github.com/cline/cline/releases/tag/v4.1.7

Why it matters

Cline v4.1.7 restores review on the completion card: View Changes is back on completion rows, backed by SDK checkpoints, so you can inspect every file a task touched without leaving the card. The button fades until changes since the last message are confirmed and is hidden when there is nothing to show. Checkpoint diffs include files that were untracked at snapshot time, and checkpoints are picked up if git is initialized mid-session. A copy button returns on turn-final response rows.

Remote MCP servers that cannot use dynamic client registration now accept pre-registered OAuth clients. SSE MCP servers surface OAuth authorization on 401 instead of failing. A hung MCP server no longer takes down session creation; unconfigured stdio servers get a 30-second initialize budget instead of blocking indefinitely.

Interrupted work is durable: prompts queued during a turn survive aborts, session context survives hub restarts, a mode-switch abort settles the turn phase, and queued-turn failures report as run.failed. LiteLLM is routed through Chat Completions (not Responses), mid-stream network drops before first tokens are retried, and Vertex ADC refreshes use the configured fetch so they work behind proxies.

Suggested actions

1. Upgrade to Cline v4.1.7. Run a multi-file edit that also creates a previously untracked file, then click View Changes on the completion row. Confirm the SDK checkpoint diff lists every file the task touched (including that untracked file), that the button stays faded until post-message changes are confirmed, and that it is hidden entirely when a task made no file changes. If git was initialized mid-session, confirm checkpoints still appear.
2. Configure a remote MCP server that cannot use dynamic client registration with a pre-registered OAuth client. For an SSE MCP server, force a 401 and confirm Cline surfaces the OAuth authorization flow instead of failing the session. Confirm a hung MCP server does not block new session creation, and that an unconfigured stdio MCP server is given a 30-second initialize budget instead of blocking indefinitely.
3. Point Cline at a LiteLLM proxy and send a chat request; confirm the request uses Chat Completions rather than the Responses API. Behind a proxy, confirm Vertex ADC token refresh uses the configured fetch. Interrupt a stream after the connection is up but before any model tokens arrive and confirm the turn retries instead of failing.
4. Abort a running turn that has prompts queued, then resume after a hub restart. Confirm queued prompts survive (and are drained if the turn aborted itself), session context is restored, a mode-switch abort settles the turn phase, and a queued-turn failure is reported as run.failed instead of completing silently. On a turn-final response row, use the restored copy button to copy the full reply.

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-v4-1-7-click-view-changes-on-cline-completion-rows-to-review-full- and mark Applied, Skipped, or Failed. Proposal id: f7314782-ef84-4921-9adb-d2cae8e924b8

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.