VSCode extension /model picker shows Opus 4.6 as Default instead of Opus 4.8 1M for Claude Max account

Resolved 💬 2 comments Opened Jun 9, 2026 by hajiwoong Closed Jun 12, 2026

Bug Description

The /model picker in the VSCode extension shows "Opus 4.6" as the Default (recommended) model, while the terminal CLI correctly shows "Opus 4.8 (1M context)" for the same account and same version.

Environment

  • Claude Code version: 2.1.169
  • VSCode extension version: 2.1.169 (anthropic.claude-code-2.1.169-win32-x64)
  • OS: Windows 11 Pro 10.0.26200
  • Account: Claude Max 5x (organizationType: claude_max, organizationRateLimitTier: default_claude_max_5x)

Steps to Reproduce

  1. Install Claude Code VSCode extension v2.1.169
  2. Login with Claude Max account
  3. Open /model picker in VSCode → Default shows "Opus 4.6"
  4. Open terminal, run claude/model picker correctly shows "Opus 4.8 (1M context)" with "Claude Max" label

Expected Behavior

Default (recommended) in VSCode should show "Opus 4.8 with 1M context" — same as terminal CLI.

Actual Behavior

VSCode extension /model picker shows "Opus 4.6" as Default.

Additional Context

  • Another user on the same plan (Claude Max) and same version sees "Opus 4.8 with 1M context" correctly in VSCode.
  • After re-login (claude login from terminal), the ~/.claude.json account cache shows organizationType: None, seatTier: None, subscriptionType: None — but the terminal CLI still correctly identifies the account as Claude Max with Opus 4.8 1M.
  • Removing all local overrides (model, ANTHROPIC_DEFAULT_OPUS_MODEL from settings.json) did not fix the issue.
  • Full VSCode restart, extension reinstall (2.1.163 → 2.1.169), and re-authentication were all attempted — VSCode picker still shows 4.6.

Suspected Cause

The VSCode extension appears to resolve the account tier / default model differently from the terminal CLI, possibly due to how OAuth account entitlements are fetched or cached within the VSCode extension context vs the standalone CLI.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗