Cline Desktop 0.0.45 and CLI 3.0.70, released on October 8, 2026, address Linux SSH startup failures, MCP and hook-related runtime exits, and rejected model requests. Developers encountering these failures have a reason to prioritize the relevant update; unaffected users can follow their normal update process.
Match the failure to the fix
Cline’s release notes and merged changes identify three distinct problems. The upgrade decision depends on which one matches your workflow.
Affected workflow | Documented correction | What it means for the upgrade |
|---|---|---|
Desktop 0.0.38–0.0.44 cannot start its bundled remote Hub on Linux x64 or arm64. | The merged SSH fix removes executable compression that Cline identifies as the cause and adds a bundled-helper startup check. | Update Desktop to 0.0.45 for this defect. Updating a separate remote CLI is not a substitute. |
A stdio Model Context Protocol (MCP) server or hook exits before consuming its input, followed by Cline terminating. | The runtime patch handles child-input failures; both releases report the corresponding exit fix. | Update the affected Desktop or CLI runtime. A dead MCP server still needs reconnection; automatic reconnection is not added. |
Reasoning-off requests fail with HTTP 400 on GPT-6 Astra, GPT-6.1 Sol, Claude Fable 5 or Claude Opus 5.5. | The adapter update omits unsupported reasoning-off fields for those models. | This corrects request compatibility. It does not make reasoning optional on those models or establish unchanged latency and cost. |
Desktop owns the remote helper
Cline’s SSH documentation says Desktop uploads an isolated helper and leaves a separately running CLI Hub untouched. The practical consequence: upgrading a CLI on the remote machine does not update the helper Desktop uses. For the startup failure, install the corrected Desktop release, reconnect through Desktop, and check that a remote task can actually run.
The branch-label change also reduces SSH authentication churn: one remote command every 30 seconds replaces two every five seconds. The tradeoff is that branch changes made outside the picker can take up to 30 seconds to appear; picker changes still refresh immediately. This is a polling change, not a measured coding-speed improvement.
Before updating CLI automation
Remove obsolete arguments. The CLI validation change rejects
history --pageand theseschedule create/updateflags:--autonomous,--no-autonomous,--idle-timeout,--poll-intervaland--delivery-channel. They previously had no effect; scripts supplying them now fail with an unknown-option error. Existing saved schedules still load.Record the provider and selected model. The release notes also change some provider defaults, including Google Vertex AI from Claude Sonnet 5.5 to Claude Haiku 5.5. Keep an explicit model selection when comparing behavior before and after the update. For that separate model decision, see our Claude Haiku 5.5 pricing and migration guide.
Plan around active work. The CLI reference documents
cline --versionandcline --update, but warns thatcline hub upgradedoes not wait for detached--zenor scheduled tasks. Account for those runs before restarting the Hub.
After updating, repeat the specific workflow that failed using the same provider and model where possible. If an MCP operation failed, establish whether it completed before retrying it; keeping Cline alive is not the same as recovering the operation.
Methodology: AI-assisted reporting from Cline’s published releases, merged pull requests and documentation, rechecked October 8, 2026. No installation, SSH session, MCP server or model request was tested for this article. The full affected-version ranges for the runtime and model-adapter faults remain unconfirmed.