Claude Desktop v5.11492.0 shipped yesterday, with v5.11492.2 following today carrying no user-facing changes at all. The bundled Claude Code is 2.1.321, so Code Mode from 2.1.323 is not in this desktop build yet. This line runs in parallel to v5.1231, which I covered two days ago.
Auto mode starts sessions of its own
The most important line sits under “Code”. In local Code sessions, a session Claude started may now start further sessions for its task without approval, as long as Auto’s own check allows it. The limits are set: ten per message you type, and five at once.
If you run agents in groups, that is exactly what was missing in practice. If you prefer knowing how many processes are running on your machine, keep those two numbers in mind.
Connectors now ask in every mode
Local, SSH, and WSL sessions in the Code tab ask before using a connector tool that your organization set to “Needs approval” in claude.ai, and they do it in every permission mode. Scheduled runs are exempt, and it does not apply in third-party deployments. Outside Auto and plan mode the prompt can offer “Allow for this session”.
The change to builtinToolPolicy points the same way. Ask rules with arguments, such as Bash(curl *) or Read(~/.ssh/**), now show the prompt on devices that have their own managed settings for Claude Code too, unless those settings specify allowManagedPermissionRulesOnly.
The change that breaks something
The built-in browser and the preview panes now send a client certificate only to sites listed under builtinBrowserClientCertificateHosts in device management. A site that requires one and is not on the list stops loading there. Behind a proxy that asks for a certificate on every site, * is the answer. Anthropic marks the line as breaking itself, and it hits exactly the environments where nobody enjoys improvising.
For administrators: templates at the push of a button
New under Developer is “Export Configuration Template”. It exports ADMX and Profile Manifest policy templates for the settings of standard Claude Desktop, third-party inference, or both. A macOS change comes with practical value too: automatic restarts for updates now wait while the keychain is locked, for up to 72 hours. Deadlines from autoUpdaterEnforcementHours and installedUpdateEnforcementHours are unaffected.
For SSH sessions on the built-in library, MCP servers from claude_desktop_config.json now run under Claude Code on Mac and Linux hosts, the way they do over OpenSSH. They follow the host’s MCP rules and stop with the session.
Among the fixes, one will look familiar to anyone who uses artifacts: edits to an artifact were lost when you left your chats or Cowork tasks within a few seconds of typing. On Windows there were brief freezes when opening a session, a blank window after closing Claude while minimized, and a setup that offered users without admin rights an install that would have removed their working MSIX install.
The limits are moving from the prompt into the number
Two changes in this build belong together, even though they sit in different sections. Auto mode gets to decide more on its own, and at the same time connectors ask in every mode. Anthropic loosens things where the machine only keeps itself busy, and tightens them where data leaves the building. As a rule of thumb for your own configuration, that is more useful than any single line.