[BUG] VS Code extension top bar button missing after v2.0.65 update

[DavidGreigQC]

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?

The Claude Code button in the VS Code editor top bar disappeared after updating to v2.0.65. Downgrading to the previous version restores the button. Can still open Claude Code via Command Palette (Cmd+Shift+P), but the button is gone.

What Should Happen?

The Claude Code button should appear in the VS Code editor top bar as it did in previous versions.

Error Messages/Logs

Steps to Reproduce

1. Install Claude Code VS Code extension v2.0.65
2. Open VS Code
3. Notice the Claude Code button is missing from the editor top bar
4. Downgrade to the version from 3 days ago
5. Button reappears

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.0.62

Claude Code Version

2.0.65

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

VS Code integrated terminal

Additional Information

No response

[github-actions]

Found 3 possible duplicate issues:

1. VSCode Extension: Missing Header Button After Local Install #4398
2. Claude Code in Cursor: UI button missing and cmd + esc shortcut no longer working #1464
3. [BUG] /rename command not available after update 2.0.65 #13658

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[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]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.