[BUG] With VS Code extension enabled, claude update in external terminal fails with 'Another process is currently updating Claude' error

[grempe]

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

When trying to update claude in a terminal running outside of VS Code, and with the Claude Code VS Code native extension enabled (not active, just enabled) I most often (but not always?) see the following error if I try to run claude update.

➜  claude update
Current version: 2.0.58
Checking for updates...
Another process is currently updating Claude. Please try again in a moment.

Then, when this happens (not always), if I do nothing but disable the Claude Code VS Code extension and return to the external terminal to run claude update again I see success:

➜  claude update
Current version: 2.0.58
Checking for updates...
Claude Code is up to date (2.0.58)

It is not always predictable, and seems possibly related to some kind of stale update lock that the extension is managing poorly if I had to guess.

What Should Happen?

Running claude update in a terminal, even with Claude Code VS Code extension installed/running/enabled, should allow the update of the claude code terminal native command.

Error Messages/Logs

➜  claude update
Current version: 2.0.58
Checking for updates...
Another process is currently updating Claude. Please try again in a moment.

Steps to Reproduce

See steps in description above.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.0.58 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

VS Code Extension version:
2.0.58

[btebbutt96]

facing this issue as well on mac os . no issues with linux though

[github-actions]

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

[github-actions]

Closing for now — inactive for too long. Please open a new issue if this is still relevant.