Re-sign out of Cline and Cline Pass so classic extension credentials stop re-importing
Cline desktop-v0.0.27 makes sign-out stick, surfaces one Sign in to Cline action on expired tokens, and reports a rejected refresh as signed out. Re-clear Cline/Cline Pass and use Settings → API Providers so stale browser-session status and dead Retry loops do not persist.Why this loop
Before desktop-v0.0.27, signing out of Cline removed the provider entry but the runtime re-imported missing providers from the classic extension’s stored credentials on every command, so you appeared signed back in. Cline Pass sign-out did nothing because its credentials live under the Cline provider entry rather than its own. A rejected refresh fell back to a persisted access token that was dead too, so the account request 401’d and Account Retry failed the same way. Settings treated a stale token as Signed in via browser, and a pre-runtime failure stacked a detail-less run.failed bubble on the real error banner. After upgrade, sign-out of Cline and Cline Pass sticks, a rejected refresh reports as signed out (transient refresh failures still fall back), the Account page offers a sign-in prompt, credential failures carry Sign in to Cline / Open model settings / CLI, and the failure renders once in place. Manage credentials under Settings → API Providers, not Models.
Proposed actions
- Upgrade Cline Desktop to v0.0.27, open Settings → API Providers (renamed from Models), sign out of both Cline and Cline Pass, then run any command and confirm neither provider reappears from classic extension credentials.
- If the Account page shows a rejected Cline refresh token, use the sign-in prompt — do not click Retry. Treat the session as signed out; only transient refresh failures should still fall back to the persisted access token.
- When a turn fails before the runtime takes the prompt, keep the single in-place error. Click Sign in to Cline for the Cline provider (ignore Signed in via browser), Open model settings for other hosted providers, or follow the local-CLI pointer.
- Retry OpenCode Go models that failed with missing x-opencode-session or internal server errors: send x-opencode-session, preserve per-model adapters so Muse Spark/GPT/Grok use /responses and MiniMax/Qwen use /messages, and reuse the same session identity on retries.
- On microphone failure, stay in the current chat, read the Speech input failed toast for the actual error, and retry from the microphone button; do not open Settings → Voice unless it is a permission issue.
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: Re-sign out of Cline and Cline Pass so classic extension credentials stop re-importing Summary: Cline desktop-v0.0.27 makes sign-out stick, surfaces one Sign in to Cline action on expired tokens, and reports a rejected refresh as signed out. Re-clear Cline/Cline Pass and use Settings → API Providers so stale browser-session status and dead Retry loops do not persist. Primary source: https://github.com/cline/cline/releases/tag/desktop-v0.0.27
Why it matters
Before desktop-v0.0.27, signing out of Cline removed the provider entry but the runtime re-imported missing providers from the classic extension’s stored credentials on every command, so you appeared signed back in. Cline Pass sign-out did nothing because its credentials live under the Cline provider entry rather than its own. A rejected refresh fell back to a persisted access token that was dead too, so the account request 401’d and Account Retry failed the same way. Settings treated a stale token as Signed in via browser, and a pre-runtime failure stacked a detail-less run.failed bubble on the real error banner. After upgrade, sign-out of Cline and Cline Pass sticks, a rejected refresh reports as signed out (transient refresh failures still fall back), the Account page offers a sign-in prompt, credential failures carry Sign in to Cline / Open model settings / CLI, and the failure renders once in place. Manage credentials under Settings → API Providers, not Models.
Suggested actions
- Upgrade Cline Desktop to v0.0.27, open Settings → API Providers (renamed from Models), sign out of both Cline and Cline Pass, then run any command and confirm neither provider reappears from classic extension credentials.
- If the Account page shows a rejected Cline refresh token, use the sign-in prompt — do not click Retry. Treat the session as signed out; only transient refresh failures should still fall back to the persisted access token.
- When a turn fails before the runtime takes the prompt, keep the single in-place error. Click Sign in to Cline for the Cline provider (ignore Signed in via browser), Open model settings for other hosted providers, or follow the local-CLI pointer.
- Retry OpenCode Go models that failed with missing x-opencode-session or internal server errors: send x-opencode-session, preserve per-model adapters so Muse Spark/GPT/Grok use /responses and MiniMax/Qwen use /messages, and reuse the same session identity on retries.
- On microphone failure, stay in the current chat, read the Speech input failed toast for the actual error, and retry from the microphone button; do not open Settings → Voice unless it is a permission issue.
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-27-re-sign-out-of-cline-and-cline-pass-so-classic-ext and mark Applied, Skipped, or Failed. Proposal id: ae13440f-082c-442c-af11-0441d6b0edea
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.