Claude Code

Claude Desktop v2.37337.1: chats in their own window, artifact diagrams that work offline

2 min read AI-generated

Scheduled tasks on your own computer couldn't be edited after their first run. And a new task lost its first message if the app reloaded while it was starting.

Featured image for "Claude Desktop v2.37337.1: chats in their own window, artifact diagrams that work offline"

Claude Desktop v2.37337.1 shipped on October 13, bundling Claude Code 2.1.295. The most visible addition is small and useful: “Open in new window” pulls a chat out of the main window so it can sit beside it.

Cowork tasks no longer lose their first message

Cowork mostly gets bug fixes this time, and they cover the cases that actually hurt. The first message of a new task was lost when the app reloaded while the task was still starting. Messages that couldn’t be sent sometimes appeared as sent, with no error. Scheduled tasks on your own computer couldn’t be edited after their first run, failing with “Failed to update scheduled task”. And Cowork tasks on machines where an administrator had turned off the local VM still tried to start there instead of in the cloud.

Two more you’ll notice right away: visualizations in artifacts went blank when you were offline or when the network blocked the site their libraries came from. Chart.js, Grid.js and Mermaid now come with the app, and disableNonessentialServices no longer turns those three off.

On the Code side, the Files pane editor gets auto save, with an option in the pane menu to switch it off.

Leave the old configuration keys in place and you lose management

The uncomfortable part sits in the “General” and “3P” sections, marked (breaking). Six former key names are gone outright: the three extension keys isDxtEnabled, isDxtSignatureRequired and isDxtDirectoryEnabled, plus enduserAttribution, trustBootstrapLocalExec and inferenceGatewayHeaders.

What matters is what happens if you leave them there. An old name now counts as an unrecognized key, its setting no longer applies, and the deprecation notice disappears with it. In practice: unsigned extensions load, the extension directory shows, end-user attribution is on, a bootstrapUrl set by device management is trusted without asking each user, and no custom inference headers are sent. It’s worse for macOS profiles and Windows user policies that contain nothing but old names — those stop being read as managed configuration at all, so the device counts as unmanaged.

The replacements are isDesktopExtensionEnabled, isDesktopExtensionSignatureRequired, isDesktopExtensionDirectoryEnabled, endUserAttribution, trustBootstrapDelivery and inferenceCustomHeaders. One Windows quirk: registry names ignore case, so enduserAttribution still works there.

If you use MCP connectors over OAuth, expect to sign in again once after this update, and again whenever a connector’s URL changes.

Sources

Claude DesktopCoworkArtifactsConfigurationRelease