Claude Desktop's update can lock out remote Claude Code hosts
Self-installed and mirrored SSH hosts need Claude Code 2.1.330 first, or updated desktops cannot start sessions there.
Anthropic's November 20 Claude Desktop release, version v6.28899.6, pins remote SSH hosts—servers reached over Secure Shell—to Claude Code 2.1.330. For Jon and other builders using Claude and Claude Code to ship AI systems, that turns a routine app update into a strict upgrade order. Until a self-installed or privately mirrored host runs 2.1.330, the Claude Desktop changelog warns, "updated computers can’t start SSH sessions there and may not reach running ones."
The hosts are AI characters.
It is easy to skim a desktop changelog as a footnote to a Claude Code release, but this one can stall live work. Put version 2.1.330 on every self-installed SSH host before updating Claude Desktop. Teams serving Claude Code from a mirror, a private copy of software packages, should add 2.1.330 to the mirror first. Updating a laptop first risks stranding sessions already running on the server.
Once both sides match, the same November 20 build pays off for long-running work. New recurring tasks in a Code session, such as /loop (Claude's command for repeating scheduled jobs), can now run for up to 30 days instead of 7. For teams running Claude through a third-party provider, the changelog adds: "On an SSH host they can keep using your provider with the app closed." Two limits in the Claude Code 2.1.330 changelog shape how to use them: the 30-day window holds only "while their session keeps running," and "tasks made before this release still end at 7 days." Any older recurring job needs to be recreated after the upgrade if it should last a month.
Taking the desktop update also pulls in two sharper changes from build v6.28899.2 on November 19 that can quietly alter a workspace. First, managed MCP allow and deny lists—admin rules that pick which Model Context Protocol tool servers Claude may call—narrowed their reach. In Chat and Cowork, they no longer stop servers under Settings > Developer unless the scope is set to all. As the changelog puts it, "In Chat and Cowork they don’t apply to servers under Settings > Developer, so stopped servers run again." Anyone counting on those lists to keep Developer servers off should check the scope and switch it to all before blocked tools wake back up.
Remote hosts face one more break from that November 19 release. Add-ons tied to one project or local folder have a tighter boundary now: "Project- and local-scope plugins no longer reach the same path on the host." Check any remote workflow that relies on those local paths before rolling out the desktop update.
Sources
- Claude Desktop changelogPrimary · Nov 20, 2026
- Claude Code changelogPrimary · Nov 20, 2026
Comments
No comments yet.
Sign in to comment. You'll come back to this story.