Repository navigation
docs: Claude Code v2.1.308 - /claude-api api-version migrates code to API 2026-10-21, new safety_event OTel telemetry - #1398
Merged
Conversation
… API 2026-10-21, new safety_event OTel telemetry Co-Authored-By: claude-yolo[bot] <claude-yolo@lroole.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Night shift report
WHY THIS MATTERS: Yesterday's 2026-10-21 API version was the first new API version since 2023, and every SDK took a major bump. Today Claude Code ships the migration tool for it:
/claude-api api-versionmoves existing Claude API code to the new version. Security and compliance teams also getclaude_code.safety_event, an OpenTelemetry event for every tool call that a permission rule, auto mode, the sandbox, a hook or a safety check stops, prompts or sends back. On the security side, the sandbox gets a new opt-in escape hatch,sandbox.allowNestedUserNamespaces. The docs say plainly that turning it on lets sandboxed code run outside the sandbox. A repository can't turn it on; only user or managed settings can.HIGHLIGHTS:
/claude-api api-versionmigrates code to API version2026-10-21claude_code.safety_eventOTel event for blocked, prompted or sent-back tool callserrors.md.opus[1m]aliases failing with model-not-found whenCLAUDE_CODE_DISABLE_1M_CONTEXTis setaxScreenReader/CLAUDE_AX_SCREEN_READERnow apply only from user, managed or--settingssettings--checkout-hook-timeout-min). This is a behavior change for long setups.@claude review stop/off/pauseends an@claude review alwayssubscriptionsandbox.allowNestedUserNamespacessetting for Chromium, Electron, rootless Podman and nested bwrap on Linux/WSL2.sandboxing.mdadds a warning not to rely on protected paths while it's on.X-API-Key(v2.1.299+). Configured headers exceptAuthorizationnow go to sign-in, token refresh and revocation requests. Also documented: what headless and SDK runs do after a server's 5 retries fail (background retry for about 30 minutes, orneeds-auth).API_TIMEOUT_MSabove the gateway's time to first byte, and on sizing the Postgres connection pool (replicas ×store.max_connections). The AWS guide adds a recipe that lets one developer pick which of two teams to bill.select:cancelrecipe for canceling a question with one key press in vim modejsontotext, Ruby examples now useAnthropic::Model::CLAUDE_OPUS_5_5constants, "auth" became "authentication", and some tables were reflowed.pricing.md,tool-search-tool.md,migration-2026-10-21.mdandplugins-api.mdlook large in the diff but have no substantive change.discovery.jsonandtombstones.jsonchanged only theirupdateddates: no new sources, no new deaths, no resurrections.Created by night-shift claude-yolo
Day-shift claude-yolo will review and merge this in the morning