Anthropic · Claude
New in this edition · 28
- Pricing / PlanClaude Platform
Linked billing launches in beta on Claude Platform
Third-party platforms can bill customers’ API usage directly to their Claude organizations without sharing API keys. The customer’s organization admin approves the connection, can set a spending limit per platform, and can remove the connection from Console.
Usage details
Who can use it: Claude Platform beta; available on supported third-party platforms and Claude Platform organizations.
How to use it: The customer starts the Claude connection flow on a supported platform, links their Claude Platform organization, and sets a monthly spending limit. The developer creates an OAuth app in Console and implements the flow in the linked-billing documentation and the `user-profiles-billing-2026-10-01` beta header.
Tip: Link the organization instead of giving an API key to a third party, and set a low initial spending limit for each platform.
- SettingClaude Code
`/export` prompts before overwriting an existing file
`/export` now asks for confirmation before overwriting an existing file. An export with a conflicting custom name preserves the file and indicates that you must run `/export` for a confirmed export.
Usage details
Who can use it: Claude Code 2.1.327 terminal.
How to use it: Type `/export` to export the transcript, then confirm or cancel at the existing-file warning. To use a custom name, use `/export <name>`.
Tip: Use descriptive, date-stamped filenames to avoid overwriting important transcripts.
✓ Verified by official sourceSource: Claude Code 2.1.327 GitHub sürümü - FeatureClaude Code
`/status` lists malformed configurations and disabled components
`/status` now shows malformed agent, skill, command, and output style files; keybinding errors; an unavailable sandbox; ignored permission settings; and hook matchers that never match, all in one list.
Usage details
Who can use it: Claude Code 2.1.327 terminal sessions.
How to use it: Type `/status` in the Claude Code terminal and fix the file, permission, or hook warnings in the diagnostics section.
Tip: If a skill or hook isn’t working, checking the `/status` list first is faster than trial and error.
- APIClaude Code
`claude -p` proceeds after 10 seconds if model settings get stuck behind a proxy
If fetching model settings on the first request gets stuck for a reason such as a proxy, `claude -p` no longer waits indefinitely; it continues without those settings after 10 seconds.
Usage details
Who can use it: `claude -p` runs launched headlessly, via the SDK, by cron, or by the desktop app.
How to use it: Run `claude -p` as usual; if the model settings endpoint is unavailable, the request is sent after a 10-second wait.
Tip: Because this behavior can hide a proxy failure, monitor network and model settings logs separately in production automation.
✓ Verified by official sourceSource: Claude Code 2.1.327 GitHub sürümü - CapabilityClaude Code
The stage at which failed hooks stop is now visible
Failures from hooks such as SubagentStop, SessionEnd, CwdChanged, and FileChanged are no longer silent in the relevant flows. Failed hooks, hooks that stop Claude, and normal hook results are shown with different colors and descriptions.
Usage details
Who can use it: Claude Code terminal and fullscreen view; sessions that use hooks.
How to use it: Run a hook and check the colored status lines in the transcript or the Ctrl+O view; fix the cause using the hook output.
Tip: Run hooks in a small test session first, then address the first cause shown in the red error line.
✓ Verified by official sourceSource: Claude Code 2.1.327 GitHub sürümü - APIClaude Code
Billing group naming comes to Claude apps gateway sessions
With the Claude apps gateway’s `admin.billing_group_tag` setting, a session’s billing group can be named using `attributionProject`. This makes it easier to break down usage by project or cost center.
Usage details
Who can use it: Claude apps gateway deployments using `admin.billing_group_tag`.
How to use it: Enable the billing-group configuration expected by the gateway, then set `attributionProject` in the Claude Code session settings to a project or cost center name.
Tip: Keep values consistent with your organization’s existing project or charge-code names to make it easier to consolidate reporting.
✓ Verified by official sourceSource: Claude Code 2.1.327 GitHub sürümü - AvailabilityClaude Desktop
Stable and Latest release channels come to Claude Desktop
Claude Desktop now lets you choose an update channel. Stable gets more thoroughly tested releases less frequently, while Latest delivers fixes and features earlier with roughly daily releases.
Usage details
Who can use it: Available on macOS and Windows on all plans; not available on Linux, Microsoft Store installations, or computers managed by organization policy.
How to use it: In Claude Desktop, open `Settings > Desktop app > Release channel` and select `Latest` or `Stable`. To check immediately, select `Claude > Check for Updates` on macOS or `Help > Check for Updates` on Windows.
Tip: Choose Stable for daily use, and Latest to try new features early and report issues.
✓ Verified by official sourceSource: Claude yardım merkezi sürüm notlarıSource: Claude Desktop kurulumu ve yayın kanalları - SettingClaude Code
GitHub App installation asks for confirmation before changing a repository
`/install-github-app` now displays an explicit confirmation before making changes to a repository. This lets you review the target before the app runs repository, secret, or API key steps.
Usage details
Who can use it: Claude Code 2.1.327; sessions using the GitHub App installation flow.
How to use it: Run `/install-github-app` in Claude Code; review the repository and permission details, then confirm or cancel.
Tip: Before confirming, pay particular attention to the repository name and the scope of the secret to be created.
✓ Verified by official sourceSource: Claude Code 2.1.327 GitHub sürümü - SettingClaude Code
Uncommitted `/config` changes are now clearly reported
If a settings change made with `/config` or a similar command cannot be written to a file, Claude Code no longer continues silently; it displays the save error below the prompt.
Usage details
Who can use it: Claude Code 2.1.327; sessions with a settings file that is corrupted or lacks write permission.
How to use it: After changing a setting, read the warning below the prompt, fix the file permissions or managed settings source, and apply the change again.
Tip: If you see a warning, check whether the settings file actually changed before restarting the session.
✓ Verified by official sourceSource: Claude Code 2.1.327 GitHub sürümü - APIClaude Code
MCP server JSON can now be added securely via stdin
The `claude mcp add-json <name> -` command reads the MCP server’s JSON configuration from stdin. This makes it possible to add a server without exposing access tokens on the command line or in shell history.
Usage details
Who can use it: Claude Code 2.1.327 CLI; cannot be used from within a Claude Code session.
How to use it: Pipe in the JSON by running `cat server.json | claude mcp add-json my-server -`, or connect a secure pipeline to stdin.
Tip: Pipe JSON from a secret store and delete any temporary file to avoid writing secret values to shell history.
- CapabilityClaude Code
`/model` no longer shows the wrong models on custom LLM gateways
Fixed an issue where `/model` showed the wrong models when `ANTHROPIC_BASE_URL` in project settings pointed to an LLM gateway.
Usage details
Who can use it: Claude Code terminal sessions using `ANTHROPIC_BASE_URL`.
How to use it: Set the gateway address in project settings, then open `/model` to check the model list provided by the server.
Tip: After changing the gateway, reopen the `/model` screen and verify your selection to avoid using an outdated model list.
✓ Verified by official sourceSource: Claude Code 2.1.327 GitHub sürümü - AgentClaude Code
Plugin agents are preserved after loading and resuming
Fixed an issue where agents passed with `--agents` disappeared after a plugin was loaded or reloaded, and where a plugin agent was dropped after using the `--resume` picker.
Usage details
Who can use it: Claude Code 2.1.327; terminal sessions using plugins and custom agents.
How to use it: Start custom agents with `--agents` or load them through a plugin; after refreshing the plugin, reopen the session from the `/resume` picker if needed.
Tip: Keep critical agent definitions under version control outside the plugin as well, so you can recover quickly from loading issues.
✓ Verified by official sourceSource: Claude Code 2.1.327 GitHub sürümü - APIClaude Code
Writes are blocked when project MCP configuration is malformed
`claude mcp add --scope project` and `claude mcp remove --scope project` now stop rather than overwrite other top-level fields in `.mcp.json` when servers are at the top level and the `mcpServers` key is missing.
Usage details
Who can use it: Claude Code 2.1.327; repositories using project-scoped MCP configuration.
How to use it: If the command stops, move the servers in `.mcp.json` under `mcpServers` in the correct format, then rerun `claude mcp add --scope project ...`.
Tip: Put the MCP file under version control before modifying it; preserve additional top-level fields such as `$schema`.
✓ Verified by official sourceSource: Claude Code 2.1.327 GitHub sürümü - CapabilityClaude Code
Long replies for unrecognized models now continue up to 128,000 tokens
Long replies that were cut off at 32,000 output tokens for unrecognized model IDs now continue with a 128,000-token limit.
Usage details
Who can use it: Claude Code sessions using a custom gateway or an unrecognized `claude-*` model ID.
How to use it: Send a request as usual with your custom model ID; if the reply exceeds 32,000 tokens, Claude Code will manage the continuation request automatically.
Tip: Also check the gateway’s actual output limit; even if the client raises its limit, the provider may enforce a lower one.
- Plugin / IntegrationClaude Code
Remote MCP servers are retried in the background after long outages
After long outages, such as a VPN disconnection, remote MCP servers accessed over HTTPS by hostname will attempt to reconnect in the background for about a day.
Usage details
Who can use it: Remote HTTPS MCP servers; especially cloud, self-hosted, and sessions affected by network outages.
How to use it: Configure the MCP server as usual; if the connection drops, check `/mcp` status and wait for the background reconnection to complete.
Tip: For short VPN outages, wait for automatic reconnection before deleting and re-adding the server.
✓ Verified by official sourceSource: Claude Code 2.1.327 GitHub sürümü - CapabilityClaude in Chrome
Timeout for long `browser_batch` calls increased to 150 seconds
Long `browser_batch` calls in Claude in Chrome now wait up to 150 seconds for a response instead of 90, reducing the chance of completed results being lost to a timeout.
Usage details
Who can use it: Claude Code sessions using Claude in Chrome tools.
How to use it: Run multiple browser actions in `browser_batch`; for tasks that take longer than 150 seconds, split the work into smaller batches.
Tip: On heavy pages, using two smaller batches instead of one large batch also makes debugging easier.
✓ Verified by official sourceSource: Claude Code 2.1.327 GitHub sürümü - AgentClaude Code
Long `ListAgents` results are paginated
For accounts with many cloud or Remote Control sessions, long `ListAgents` results are now paginated instead of hiding most sessions.
Usage details
Who can use it: Claude Code users managing many sessions or agents.
How to use it: Open the agent view or flows that use `ListAgents`; if results are paginated, move between pages.
Tip: Using a naming convention for many background sessions makes it easier to quickly find the right one.
✓ Verified by official sourceSource: Claude Code 2.1.327 GitHub sürümü - FeatureClaude Code
VS Code Explorer gets a command to add selections directly to chat
Right-clicking files or folders in VS Code Explorer now shows the `Claude Code: Add to Chat` command. Selected paths are added to the chat as `@`-mentions.
Usage details
Who can use it: Claude Code VS Code extension; workspaces using VS Code Explorer.
How to use it: Select files or folders in Explorer, right-click, and run `Claude Code: Add to Chat`.
Tip: Add only the folders needed for the task to Claude to reduce context and file search time.
- SettingClaude Code
`/config` rows identify values overridden by higher-priority settings
`/config` now displays a note when a setting row is overridden by another settings source. This makes it easier to see why a user setting is having no effect.
Usage details
Who can use it: Claude Code 2.1.327; sessions where user, project, or managed settings are applied together.
How to use it: Open `/config`, read the override note on the row that appears ineffective, and change the higher-priority settings source if needed.
Tip: If organization policy or managed settings are in place, confirm which source takes precedence before changing a local setting.
✓ Verified by official sourceSource: Claude Code 2.1.327 GitHub sürümü - FeatureClaude Code
`/doctor` starts showing findings before the full report is ready
Instead of remaining silent until the entire check is complete, `/doctor` now shares findings as it goes.
Usage details
Who can use it: Claude Code terminal users.
How to use it: Run `/doctor` in the terminal and review report lines as they appear; you can fix visible issues without waiting for it to finish.
Tip: Address errors and configuration warnings first, then review performance information at the end of the report.
✓ Verified by official sourceSource: Claude Code 2.1.327 GitHub sürümü - SettingClaude Code
`/statusline` writes to the settings directory selected by `CLAUDE_CONFIG_DIR`
Fixed an issue where `/statusline` mistakenly wrote to `~/.claude/settings.json` when `CLAUDE_CONFIG_DIR` was set to a different directory.
Usage details
Who can use it: Claude Code installations using a custom `CLAUDE_CONFIG_DIR`.
How to use it: Set `CLAUDE_CONFIG_DIR` and run `/statusline`; check that the change is written to the settings file in the selected configuration directory.
Tip: If you use multiple profiles, verify `CLAUDE_CONFIG_DIR` and statusline settings together for each profile.
✓ Verified by official sourceSource: Claude Code 2.1.327 GitHub sürümü - SettingClaude Code
Errors in malformed settings or `.mcp.json` files show the line and column
For settings or `.mcp.json` files containing invalid JSON, the error message now reports the line and column of the error.
Usage details
Who can use it: Claude Code settings and MCP configuration files.
How to use it: If you see a JSON error at startup or while running a command, go to the specified line and column and fix the comma, quotation mark, or bracket error.
Tip: Running a JSON linter before changing the file helps prevent Claude Code restart loops.
✓ Verified by official sourceSource: Claude Code 2.1.327 GitHub sürümü - CapabilityClaude Code
Only the first 100 files are searched in prompts with many `@` mentions
To prevent prompts containing thousands of `@` mentions from hanging before a response, file search is limited to the first 100 mentions.
Usage details
Who can use it: Claude Code terminal and related prompt interfaces.
How to use it: If you need to add more than 100 files, split the prompt across several messages or add files using narrower folder selections.
Tip: For bulk context, selecting a folder path is more efficient than adding hundreds of files one by one with `@`.
✓ Verified by official sourceSource: Claude Code 2.1.327 GitHub sürümü - CapabilityClaude Code
Resumed sessions are faster with many connector permissions
A slowdown in resumed sessions for organizations with tens of thousands of connector tool permissions has been fixed.
Usage details
Who can use it: Cloud or enterprise Claude Code sessions with many connector permissions configured.
How to use it: Resume the current session as usual; no additional settings are required. If needed, reopen the same session from the `/resume` list.
Tip: Regularly removing unused connector permissions helps improve overall session speed, not just the benefits of this fix.
✓ Verified by official sourceSource: Claude Code 2.1.327 GitHub sürümü - APIClaude Code
Managed settings checksum added to gateway hint headers
When `CLAUDE_CODE_GATEWAY_HINT_HEADERS=1` is enabled, Claude Code adds `x-claude-code-managed-settings-checksum` to gateway hint headers. This header helps the gateway identify the applied managed settings version.
Usage details
Who can use it: Claude Code gateway deployments using managed settings; disabled by default.
How to use it: To enable gateway hint headers, set `CLAUDE_CODE_GATEWAY_HINT_HEADERS=1` in the runtime environment; read the checksum header on the gateway side.
Tip: If you use gateway caching, use the checksum as a cache invalidation key when settings change.
✓ Verified by official sourceSource: Claude Code 2.1.327 GitHub sürümü - CapabilityClaude Code
The Read tool reports the actual file size for large files
When a file is 10 MB or larger and too large to read at once, the Read tool now reports its actual size instead of a fixed 512 KB.
Usage details
Who can use it: Claude Code Read tool.
How to use it: Use an appropriate offset and limit in the Read call to split up a large file; refer to the actual size in the warning.
Tip: For large logs, reduce context and token usage by searching first or reading a narrow range of lines.
✓ Verified by official sourceSource: Claude Code 2.1.327 GitHub sürümü - SettingClaude Code
`/tui classic` added as the name for the non-full-screen interface
The non-full-screen renderer can now be selected with `/tui classic`. The old `/tui default` name continues to work.
Usage details
Who can use it: Claude Code 2.1.327 terminal interface.
How to use it: Type `/tui classic` in the terminal; `/tui default` is also valid if you want to use the existing default name.
Tip: Try the `classic` renderer if full-screen behavior causes problems in small or SSH terminals.
✓ Verified by official sourceSource: Claude Code 2.1.327 GitHub sürümü - CapabilityClaude Code
WebFetch now rejects URLs longer than 2,000 characters in advance
Very long WebFetch URLs are now rejected before permission is requested; the limit is 2,000 characters. This prevents long URLs from blocking compaction or session flow.
Usage details
Who can use it: Claude Code WebFetch tool.
How to use it: For links over 2,000 characters, shorten the query parameters, split the URL into a page or API request, and try again.
Tip: Removing unnecessary tracking parameters (such as `utm_*`) brings most long URLs below the limit.
✓ Verified by official sourceSource: Claude Code 2.1.327 GitHub sürümü