The release notes for Claude Desktop v2.19675.0 are dated October 1. The bundled Claude Code version is 2.1.286. Three lines change how you work, the rest are repairs — plus one change to scheduled tasks worth reading twice.
Comments on a line of code
In the Files pane you can now comment on individual lines of an open file: click the + beside the line, or select text and choose “Add comment.” The comment is sent with your next message.
That’s the difference between “change the function further down that formats the date” and a plus sign on line 214. For anyone working with Claude in the Code tab on unfamiliar files, it’s the most useful line in the release.
Scheduled tasks stop asking
The line sits under “Cowork” and reads: scheduled tasks that Claude creates for you now use “Automatically approve” by default where your organization allows it. Their runs use tools without asking first and pause only when something looks unsafe.
This is the furthest-reaching change in the changelog, and it’s true in both directions. A task that runs overnight and waits for an approval nobody gives is a task that doesn’t run — which is exactly why 2.1.286 carried the line about a never-started routine run no longer reporting “Succeeded.” On the other hand, if you have Claude set up a task and assume it will ask before the first write, that assumption is wrong from this version on.
Computer use now needs macOS 14
On macOS 13 and earlier, computer use has been removed. The reason: its screenshots could never be taken there. The Computer use section in Settings stays visible and explains why the feature is unavailable instead.
Two more lines from the 3P section:
- Excel, Word and PowerPoint previews in the Code tab, even when Claude’s workspace isn’t running yet. Excel opens in the document viewer; opening a Word or PowerPoint file starts the workspace.
- The default context window behind a gateway or custom base URL is now one million tokens for Opus 4.7 and later, Sonnet 5 and later, and Fable 5 and later. It used to be 200,000 unless you picked the “1M context” option.
What the fixed bugs say about how it gets used
The bug list is sorted into General, Code, Cowork and 3P, and a few entries describe situations you’ll recognize:
- A message that failed to send sometimes looked sent, with Claude still working — or disappeared if you’d already started typing the next one. It now offers Retry.
- Quick Entry on macOS discarded your message when an attached file had been moved, deleted or couldn’t be read before sending. It now sends without that file and says so.
- A finished session showed as working again after a model switch or a built-in slash command. That could hide the usage-limit notice and make Try again send an extra message.
- While working in the background, Claude clicked the wrong item, missed an open menu, or brought apps such as Slack to the front.
- Network requests failed on corporate networks where the proxy is set by a one-word host name. And when the PAC file failed to download, right after a VPN switch for instance, the sandbox was left without a proxy until the app restarted.
- The Windows app failed to start when the Google or Chrome folder under LocalAppData is a junction.
- Claude Code failed to start on some Macs right after a desktop update.
The default worth looking up
If you run scheduled tasks, mark that one line. As of v2.19675.0, a task Claude creates for you gets its approval in advance, and that fact lives in the release notes rather than in the dialog where the task is created. The organization setting is the brake; where there isn’t one, the default decides.
The line comments, meanwhile, are the kind of improvement nobody announces and everybody uses immediately. Two lines in the same changelog, and the unremarkable one is the one you don’t have to check.
Sources: