Claude Code 2.1.266
Safe to upgrade? Many reports – consider waiting
13 bug/regression-labelled issues opened in the 20h after release (13 regression-flagged, 1 mention v2.1.266 in title). Normalised score 140.0.
Issues counted
- #93165 [BUG] Dictation mic button disappears from composer once there's text — regression of the v1.46388.1 fix (macOS 1.49585.0)
- #93142 [BUG] Windows desktop 1.49585.0 — computer use app-permission card for File Explorer shows only "Deny", no "Allow"
- #93118 [BUG] Cowork Windows — remote-bash reports "no Plan9 drive shares mounted" after Sept 2026 Windows update; host registers 7 shares successfully
- #93089 SendMessage (cross-session messaging) disabled in Desktop app's Code tab, works fine from terminal — same account, same version
- #93057 CLAUDE_PLUGIN_ROOT unset in agent Bash env, and still source-dir in hooks, for string-source local marketplace plugins (2.1.265)
- #93043 statusLine stops rendering under cmux after updating from 2.1.263 (blank, no error)
- #93038 [BUG] Claude Code 2.1.266 crashes with "Bus error" on WSL2 (npm/NVM install) — 2.1.265 works
- #93022 [BUG] VS Code extension ignores claudeCode.useTerminal and renders a blank activity-bar icon on VS Code 1.136.2 (correct on 1.135.0)
- #93006 Desktop: WSL section missing entirely from environment picker on new session screen (regression after update to 1.49585.0)
- #92977 [BUG] Cowork local sandbox not mounting after update in Claude Desktop 1.49585.0.0 (Windows)
- #92976 Dispatch start_code_task still blocked in 1.49585.0: opening a finished session in the UI re-locks the folder (follow-up to #91745, #92452, #92462)
- #92975 Abrir em no explorador de arquivos do painel nao abre / falta preview e abrir no Word para .docx
- #92972 [BUG] Scheduled-task sessions never register with Remote Control / no session appears in mobile app
Changelog: v2.1.266
What's changed
- Fixed a 2.1.265 regression affecting LLM-gateway and proxy setups: the undocumented
CLAUDE_CODE_USE_GATEWAYenvironment variable, previously ignored unlessANTHROPIC_BASE_URLandANTHROPIC_AUTH_TOKENwere both set, began forcing Cloud-gateway sign-in on its own in 2.1.265, so configurations that set it alongside an API key,apiKeyHelper, or custom auth headers failed every request with "Not signed in to the Cloud gateway". The variable on its own is ignored again; no configuration change is needed