Claude Code 2.1.305-306: /artifacts drops its y/n shortcut, Vertex and Bedrock work again

Claude Code 2.1.305 and 2.1.306 shipped on October 20 and 21, 2026. 2.1.305 carries four additions, six changes, six improvements and twenty-two fixes; 2.1.306 is just two fixes. Nothing dramatic, but one change breaks a habit if you manage artifacts from the keyboard, and two fixes repair sessions where every request failed, or that compacted for no reason, in certain setups.

/artifacts: y and n no longer answer the delete confirmation

The /artifacts command lists the pages you've published or that others shared with you, each a single static page capped at 16 MB and served under a security policy that blocks external scripts, styles and network calls, apart from Google Fonts and five allowed CDNs. Since 2.1.304, confirming a delete from that panel used a numbered choice: 1 or Enter to keep the artifact, 2 to delete it, Esc to cancel, with the older y and n keys still answering alongside the numbers. 2.1.305 removes that fallback: y and n do nothing now, only the digits, Enter and Esc work. If your fingers still reach for y/n out of years of shell confirmations, the first delete you try after upgrading will do nothing. Not a disaster for a delete action, but worth knowing before you type fast.

Two fixes that get broken sessions working again

2.1.304 had turned on tool search by default behind a custom ANTHROPIC_BASE_URL: instead of loading every MCP tool's full definition at startup, Claude Code loads only their names and fetches each tool's details on demand, which keeps MCP tools from eating up the context window. That release already retried without tool search when the gateway answered with a 400 or 422, but the safety net had gaps: on Vertex, Bedrock and other providers, when the endpoint or an LLM gateway rejected tool search, or behind a gateway where the ToolSearch tool was disallowed or left out of --tools, every request in the session failed outright. 2.1.305 fixes that regression: Claude Code now retries the request without tool search. If every request failed on Vertex, Bedrock or behind a gateway since 2.1.304, this was the bug.

2.1.306 fixes a related symptom: in a session loaded with many MCP tools, a genuine API error was getting replaced by a "prompt is too long" message, along with a compaction that had no reason to happen. You lost context over a problem that was never about prompt length in the first place.

One change matters mostly to admins: allowedMcpServers no longer filters managed-mcp.json stdio servers that use ${VAR} only in their env block. A server like that which your allowlist left out now loads as soon as you upgrade; to keep it off, use deniedMcpServers. Everything else in these two versions leaves your day-to-day workflow untouched: a sandbox.allowNestedUserNamespaces option for Linux commands that need to create user namespaces (Chromium, rootless podman), at the cost of letting them get around the sandbox's file protections, a fix for claude -p reporting "Not logged in" inside cloud sessions, and a dozen fixes touching VS Code, cloud sessions, Claude Tag and self-hosted runners. If you don't manage artifacts from the keyboard, don't use Vertex, Bedrock or an LLM gateway, and don't administer managed MCP servers, these two releases change nothing for you.