Anthropic · Claude
New in this edition · 41
- AvailabilityClaude
Computer use beta is now available on Team and Enterprise plans
Computer use is now available in beta on Team and Enterprise plans. Claude can view and interact with permitted desktop apps; rollout to organizations is gradual.
Usage details
Who can use it: Team and Enterprise organizations; with the new experience in Claude Desktop, and when Computer access is enabled on web and mobile.
How to use it: A Team or Enterprise administrator should complete the Computer use setup in the help center; users can enable Computer access in Claude Desktop or on web/mobile.
Tip: For the first try, grant access only to the necessary desktop apps and keep the scope narrow.
✓ Verified by official sourceSource: Claude Help Center sürüm notları - FeatureClaude Code
Easel added as a built-in mode that automatically draws charts
The built-in mode called Easel draws charts on request and below MCP metrics results. Automatic chart generation can be turned off in Claude Code settings.
Usage details
Who can use it: Pro and Max on macOS and Linux; Team and Enterprise where available.
How to use it: Request a chart or get an MCP metrics result; to turn off automatic charts, change the Easel setting in `/config`.
Tip: For dense metrics output, ask for the chart first and then the raw data for quick verification.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - AvailabilityClaude Code
Direct sign-in added for organizations on Enterprise Admin Console
Claude Code can now sign in to organizations managed by Anthropic Enterprise Admin Console. After sign-in, it applies the organization’s settings and configured cloud provider or gateway.
Usage details
Who can use it: Organizations managed by Anthropic Enterprise Admin Console.
How to use it: Run `claude auth login` in the terminal and complete organization sign-in; then restart the session and verify that the organization settings have loaded.
Tip: When troubleshooting, check the provider or gateway selected by the organization before local settings.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - SettingClaude Code
Approval requirements expanded for rm commands targeting root and working directories
More `rm` commands targeting the root, home, a top-level directory, or the working directory now require approval; in environments where a response cannot be provided, the command is rejected.
Usage details
Who can use it: Interactive and non-interactive Claude Code sessions.
How to use it: When the command requests approval, review the target path and deletion scope, then explicitly approve it; account for the possibility that the command may be rejected in headless workflows.
Tip: Limit deletions to a narrow target path within the project and an explicit file list.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - AgentClaude Code
Subagent model fallback and Bedrock region now propagate to subflows
Subagents without a specified model now inherit the fallback model in use; forks and subagents they launch also use the relevant Bedrock region.
Usage details
Who can use it: Claude Code sessions that use subagents and forks; region information matters on Bedrock.
How to use it: Set the session model and fallback setting, then launch a subagent; verify that the subflow runs with the expected model and region.
Tip: Account for subagents switching to the fallback model when estimating cost and latency.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - AgentClaude Code
Background agents and Remote Control stopping status are more consistent
Fixed stopped background subagents restarting and Claude continuing to wait for them when they were nearly finished. Also fixed Diff and pull request buttons disappearing in Remote Control mobile apps and stopped sessions appearing to be running.
Usage details
Who can use it: Claude Code background agents and desktop/mobile sessions using Remote Control.
How to use it: Stop a background agent and monitor its status; in a conversation opened mid-session, check the Diff or pull request view in the Remote Control mobile app.
Tip: In automations, check the agent status event as well as the running indicator.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - CapabilityClaude Code
Scheduled tasks and /loop in active sessions can now run for up to 30 days
Recurring scheduled tasks and `/loop` can now run for up to 30 days instead of seven, as long as the session remains active. Tasks created before this release retain the old seven-day duration.
Usage details
Who can use it: Active sessions in Claude Code and newly created tasks.
How to use it: Create a new recurring task in a session or use `/loop`; watch for Claude Code’s notification when the duration ends.
Tip: For long-running tasks, break the work into small, observable steps rather than relying on the 30-day window.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - APIClaude Code
Disk, model, and fast mode diagnostics fixed in claude -p and SDK flows
When redirecting `claude -p` output to a file on a full disk, it now prints an error and exits with code 1. Also fixed `fastMode` ignoring pricing when the model comes from an environment variable or settings file on Google Cloud Agent Platform.
Usage details
Who can use it: Flows using headless `claude -p` and Google Cloud Agent Platform.
How to use it: Check the exit code in scripts that redirect output to a file; verify `--settings '{"fastMode":true}'` on Agent Platform.
Tip: Store stdout and stderr separately in CI, and don’t interpret a disk-full error as success.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - Plugin / IntegrationClaude Code
Claude in Chrome reconnects, and Bedrock sessions retain their pinned model
Fixed Claude in Chrome incorrectly remaining not connected after a brief connection issue. Amazon Bedrock terminal sessions also no longer ignore the pinned Opus model when no model is selected.
Usage details
Who can use it: Claude in Chrome and Claude Code sessions using Amazon Bedrock/Mantle.
How to use it: With Chrome open and signed in, restart the `/chrome` flow from Claude Code; in Bedrock, keep the pinned model setting when the default model is empty.
Tip: Don’t overlook the provider fallback notice; check which model the call actually uses.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - CapabilityClaude Code
Chart, MCP termination, and context visibility fixed in Code Mode
Fixed Code Mode’s long pauses in projects with hundreds of files, failures in the built-in chart tool, and MCP tool requests to end a turn from a script being ignored. `/context` now counts system tools more accurately before the first response.
Usage details
Who can use it: Claude Code Code Mode, especially auto and bypass permissions flows.
How to use it: Enable Code Mode and call a chart or MCP tool; use `/context` to check the session tool count.
Tip: Set path-scoped rules and Read deny restrictions in advance when scanning very large files.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - CapabilityClaude Code
Fixed concurrent settings saves and resume flows with invalid timestamps
Fixed an issue where user settings could be lost when multiple Claude Code processes saved settings, and an issue where `--continue` or `--resume` could open an empty session or fail if the last message had an invalid timestamp.
Usage details
Who can use it: Users running multiple Claude Code processes or resuming older sessions.
How to use it: Upgrade Claude Code to 2.1.330; for affected sessions, select the session from the `--resume` list and verify that the transcript reopens.
Tip: Reduce the number of parallel processes writing to the same settings file during updates.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - Plugin / IntegrationClaude Code
Concurrent plugin tasks and Claude settings backups are preserved
Fixed issues where plugins disappeared from the list when multiple plugin commands ran at once, dependency and metadata loss during concurrent task updates, and a bad `.claude.json` backup on a full disk overwriting a good backup.
Usage details
Who can use it: Claude Code sessions using plugins and tasks.
How to use it: Update to 2.1.330; check `/plugin` and `/tasks` after running parallel plugin commands and task updates.
Tip: Monitor low-disk-space warnings and leave room for backups in the Claude configuration directory.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - AvailabilityClaude Code
Sign-in, connector removal, and account hold errors are clearer
Fixed the unnecessary rejection of `forceLoginOrgUUID` initialization after a temporary connection error, ambiguity around removing a claude.ai connector, and generic errors shown for accounts on hold.
Usage details
Who can use it: Enterprise sign-in enforcement, claude.ai connectors, and account hold flows.
How to use it: Try again when prompted to sign in; disable the connector from `/mcp` or remove it on claude.ai; if the account is on hold, follow the displayed appeal link.
Tip: Include the reason and appeal link now shown, rather than a generic error, in support tickets.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - CapabilityClaude Code
Faster shell workflows on Linux and after Git Bash startup on Windows
Fixed Bash delays and lost diffs on Linux in repositories with large ignored directories, as well as command slowdowns on Windows that persisted after Git Bash’s slow initial startup.
Usage details
Who can use it: Claude Code users on Linux, Windows, and WSL.
How to use it: Update Claude Code to 2.1.330; rerun Bash commands in repositories containing large ignored directories such as `node_modules`.
Tip: Narrowing repository ignore rules reduces both search and diff costs.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - Plugin / IntegrationClaude Code
LSP, /mcp, and plugin servers are classified more accurately
An issue causing concurrent calls and diagnostics to fail while a slow LSP was starting has been fixed. `/mcp` now lists plugin servers under Plugin MCPs and other servers separately, and identifies the plugin name on the server page.
Usage details
Who can use it: Claude Code sessions using LSP and connecting plugin or other MCP servers.
How to use it: Open `/mcp` and check that servers appear under Plugin MCPs and Other MCPs; try multiple file operations while an LSP server is starting.
Tip: If a server has an issue, first read the reason on its server page, then use reconnect.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - APIClaude Code
Automatic retries restored for max_tokens limit errors
Claude Code 2.1.330 restored the automatic retry removed in 2.1.329 for requests that exceed a model or gateway’s `max_tokens` limit.
Usage details
Who can use it: Workflows using Claude Code through a gateway, custom base URL, or provider.
How to use it: Update Claude Code to 2.1.330; if the gateway uses a lower limit, set `CLAUDE_CODE_MAX_OUTPUT_TOKENS` to that limit.
Tip: Explicitly matching the gateway limit with a fixed setting reduces retry-related latency.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - Plugin / IntegrationClaude Code
MCP resources, connector names, and server lifecycle are more reliable
MCP resources from claude.ai connectors and plugin servers are now added when referenced with `@` in the terminal prompt. Issues that caused different connector names sharing the same URL to disappear, or the shared MCP server to shut down when a subagent finished, have been fixed.
Usage details
Who can use it: Sessions using claude.ai connectors, plugin MCP servers, and subagents.
How to use it: Reference the MCP resource with `@`; if multiple connectors use the same URL, check their names in the `/mcp` list.
Tip: Use unique connector names for the same server URL.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - APIClaude Code
commandPrinted and commandFailed added to plugin installation JSON output
`claude plugin install --json` now reports whether the installation command wrote output to stderr and whether it ended with an error, was terminated, or timed out.
Usage details
Who can use it: Scripts that automate plugin installation using JSON output.
How to use it: Read the `commandPrinted` and `commandFailed` fields in the output of `claude plugin install --json` and evaluate the CI result accordingly.
Tip: Do not treat `commandPrinted` alone as a failure; check the actual status alongside `commandFailed`.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - CapabilityClaude Code
File and prompt content loss fixed in rewind and permission approvals
Fixed an issue where `/rewind` could restore an older file version after two queued prompts or consecutive skill runs. Text and images added while approving a permission prompt are no longer lost if the command or tool later fails.
Usage details
Who can use it: Claude Code’s `/rewind` and permission prompt flows.
How to use it: Update to 2.1.330; use `/rewind` after changing a file, or add text/images to a permission prompt and check what happens after a failed command.
Tip: Save a Git diff before rewinding critical files.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - APISelf-hosted runner
Two Prometheus metrics added for runner job order and first session
Two metrics were added to the self-hosted runner `/metrics` endpoint to measure the time from job order to registration acceptance and first session delivery.
Usage details
Who can use it: Self-hosted runners launched by an orchestrator.
How to use it: Collect the `claude_code_self_hosted_runner_order_to_registered_seconds` and `claude_code_self_hosted_runner_order_to_first_session_seconds` metrics from the `/metrics` output.
Tip: Track the two metrics separately to distinguish queue/startup latency from session delivery latency.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - SettingClaude Code
Unnecessary file diffs are skipped by default in self-hosted Bash output
Self-hosted runner Bash commands no longer produce file diffs when there are no changes, so diffs may be absent from transcripts. If needed, managed settings can force every diff to be included.
Usage details
Who can use it: Self-hosted runner sessions.
How to use it: If you need a diff for every command, set `bashEditDiffEnabled: true` in managed settings.
Tip: Keep the default to reduce transcript size; explicitly enable the setting in audit workflows.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - APISelf-hosted runner
Choose a startup directory within the repository for self-hosted runners
The runner can now start in a specific directory within the repository. Settings and hooks continue to load as if no startup directory had been specified.
Usage details
Who can use it: Organizations using self-hosted runners.
How to use it: Pass `--start-dir` when starting the runner, or set the `SELF_HOSTED_RUNNER_START_DIR` environment variable to a directory within the repository.
Tip: In monorepos, narrow the working directory, but test that shared settings and hook files in parent directories are still picked up.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - AvailabilitySelf-hosted runner
Self-hosted runner reports restart and queue errors more clearly
Fixed issues where the runner ignored a session after a failed report, a slow spawn hook locked up free slots, a full disk accepted a session, and an incorrect provider/credential error was shown. The status of pushed work and missing repositories in resumed sessions is also explained more clearly.
Usage details
Who can use it: Organizations using self-hosted runners.
How to use it: Upgrade the runner to 2.1.330; check logs for the new explanations in full-disk, proxy 403, and repository credential scenarios.
Tip: Track runner metrics alongside startup logs to distinguish infrastructure issues from repository issues.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - AgentClaude Code
The skill model setting no longer changes subflows in the main session
Skills with a `model` setting and no `context: fork` now leave subagents, forks, compaction, and the `/recap` flow on the session’s model.
Usage details
Who can use it: Claude Code skills with a model setting.
How to use it: Keep the `model` field in the skill definition; if a subflow needs to run on a separate model, explicitly design for `context: fork` behavior.
Tip: When updating skills, test the main model, compaction model, and subagent model separately.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - APISelf-hosted runner
spawn-runner hooks can now run concurrently with limits
`spawn-runner` hooks can run without waiting for previous hooks to finish; the default maximum is four per orchestrator. The limit can be lowered to one for incompatible hooks.
Usage details
Who can use it: Self-hosted runner orchestrators.
How to use it: If needed, start the orchestrator with `--hook-concurrency 1`; with the default value of four, verify that hooks can safely run concurrently.
Tip: If hooks use shared files or ports, run them one at a time first, then increase concurrency.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - APIClaude Code
Environment variable added to print the full sign-in link
The full link can now be printed when a short sign-in link fails or a script cannot read the link value.
Usage details
Who can use it: All users who use the Claude Code sign-in flow from a terminal or script.
How to use it: Set `CLAUDE_CODE_FULL_SIGN_IN_LINK=1` before signing in; then run `claude auth login` or the relevant sign-in command.
Tip: Restrict access when storing the link in logs; it may contain authentication data.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - CapabilityClaude Code
Teleport no longer runs branch-switching commands itself in some setups
In some setups, `claude --teleport` prints the Git commands required to switch branches instead of running them automatically. When `-p` is used, it returns exit code 1 until the branch is switched.
Usage details
Who can use it: Setups that use Teleport, especially automated or headless workflows.
How to use it: Run the Git commands shown in the Teleport output, switch to the correct branch, and then restart the session; check the exit code in `-p` workflows.
Tip: Make branch switching an explicit step in CI scripts and evaluate Claude Code’s exit code separately.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - CapabilityClaude Desktop
Third-party Desktop sessions recover better after large PDFs
In some third-party provider sessions outside Scheduled tasks, a PDF that exceeded the context limit after a long conversation could permanently end the turn with Prompt is too long. This has been fixed. An order dependency when choosing between user and project agent files with the same name has also been resolved.
Usage details
Who can use it: Claude Desktop sessions using third-party providers and projects with agent files that have the same name.
How to use it: Update Desktop to 2.1.330; add a large PDF after a long conversation and test that the session continues.
Tip: Providing large PDFs at the start of a long context or in sections reduces the risk of hitting provider limits.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - CapabilityClaude Code for VS Code
VS Code prompt, diff, question, and keyboard workflows are more reliable
Fixed issues where VS Code’s attached terminal opened and took focus with every prompt, a line break accidentally ran a command while copying code, an old answer was submitted in question cards, and Accept/Reject buttons appeared on the wrong diff.
Usage details
Who can use it: Claude Code for VS Code.
How to use it: Update the extension to 2.1.330; retest question cards, proposed diffs, code copying, and attached terminal workflows.
Tip: Before production use, also test question and diff workflows with team members who use keybindings and IMEs.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - SettingClaude Code for VS Code
Escape, pinned prompt, and context indicator settings added to VS Code
The `claudeCode.escapeStopsClaude`, `claudeCode.pinPrompt`, and `claudeCode.contextUsageThreshold` settings were added. They control Escape’s stop behavior, whether the prompt stays pinned, and the context indicator’s threshold.
Usage details
Who can use it: Claude Code for VS Code.
How to use it: Search for these three `claudeCode.*` settings in VS Code Settings; turn off `claudeCode.escapeStopsClaude` if you don’t want Escape to stop Claude.
Tip: In long conversations, set `contextUsageThreshold` low to get an early warning.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - FeatureClaude Code for VS Code
Added /fork and /workflows commands in VS Code
The VS Code integration now includes `/fork` to branch a conversation after the latest response and `/workflows` to open running workflows in the agent map.
Usage details
Who can use it: The Claude Code VS Code extension.
How to use it: Type `/fork` or `/workflows` in the Claude panel in VS Code; for a fork, run the command after the conversation’s latest response.
Tip: Use `/fork` to isolate experimental changes and keep the main conversation’s context clean.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - CapabilityClaude Code
WebFetch long waits and empty results fixed
Issues that caused WebFetch to lock up sessions for minutes or return empty results on some pages have been fixed. Page summaries now track the `/effort` level more accurately, even if the gateway rejects the small fast model.
Usage details
Who can use it: Sessions using WebFetch in Claude Code.
How to use it: Update Claude Code to 2.1.330 and retry the same URLs with WebFetch; if the issue persists, check the `/effort` setting.
Tip: On very large pages, specify the target section explicitly to reduce unnecessary waiting.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - AvailabilitySelf-hosted runner
If a checkout hook returns 108, the runner stops without trying another runner
When a checkout hook exits with code 108, the self-hosted runner immediately stops session startup and does not switch to another runner.
Usage details
Who can use it: Self-hosted runner checkout hooks.
How to use it: Document that exit code 108 means an intentional stop in your checkout hooks, and update session startup monitoring rules accordingly.
Tip: Don’t use 108 for transient errors; define a separate exit path for cases where a retry is expected.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - CapabilityClaude Code
CLI sign-in links are shorter
The claude.ai sign-in links shown by `/login`, `claude auth login`, and `claude setup-token` are now shorter.
Usage details
Who can use it: Claude Code CLI users.
How to use it: Update Claude Code to 2.1.330 and run `/login`, `claude auth login`, or `claude setup-token`.
Tip: If the short link fails, use `CLAUDE_CODE_FULL_SIGN_IN_LINK=1` to get the full link.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - CapabilityClaude Code
Config search, local statistics, and Ultrareview feedback improved
`/config` search prioritizes setting-name matches; `/resume` no longer lists sessions that were only opened and exited. `/stats` now shows the local time zone, while `/ultrareview` more accurately shows incorrect repository status and the Team/Enterprise spending share.
Usage details
Who can use it: Claude Code terminal interface; Team and Enterprise plans for Ultrareview.
How to use it: Search for a setting name in `/config`, or run `/resume`, `/stats`, or `/ultrareview`; check the new descriptions and local dates.
Tip: Don’t start Ultrareview before checking the remaining monthly limit for cost approval.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - CapabilityClaude Code
design-sync now builds its reference Storybook only from the project installation
The fallback build for the `/design-sync` reference Storybook now uses only the Storybook installed in the project; it no longer looks for an external installation.
Usage details
Who can use it: Projects using Claude Design and `/design-sync`.
How to use it: Add the Storybook dependency to the project and verify the project installation before running `/design-sync`.
Tip: Pin the Storybook version used in CI with the lockfile.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - Plugin / IntegrationClaude Code
A clear warning added for marketplaces not in the session repository
Cloud and self-hosted runner sessions now explain why they couldn’t be retrieved when the plugin marketplace repository isn’t among the session repositories.
Usage details
Who can use it: Plugin marketplace use in Cloud and self-hosted runner sessions.
How to use it: When the warning appears, add the marketplace repository to the list of repositories accessible to the session, or move the marketplace to a suitable repository.
Tip: For automated installations, verify marketplace repository access before starting the session.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - Plugin / IntegrationSelf-hosted runner
Plugin name and next steps shown when a plugin repository is rejected
When Anthropic-managed git rejects a plugin’s own repository, the self-hosted runner now names the plugin and explains what to do.
Usage details
Who can use it: Self-hosted runner sessions using Anthropic-managed git.
How to use it: Follow the plugin name and recommended repository handling path in the warning; if necessary, exclude the plugin from the session’s repository scope.
Tip: If the plugin repository and working repository are the same, plan the installation through a separate repository.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - APIClaude Code
Prompt hook model field accepts haiku and sonnet aliases
The `model` field in prompt hook configuration now accepts model aliases such as `haiku` and `sonnet`.
Usage details
Who can use it: Claude Code configurations using prompt hooks.
How to use it: Enter the supported `haiku` or `sonnet` alias in the `model` field of the prompt hook definition, then test the hook.
Tip: In production automation, using a fixed model ID instead of an alias can reduce the impact of model changes.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - CapabilityClaude Code
Unrecognized Sonnet and Haiku names use a shorter system prompt
Unrecognized model names containing `sonnet` or `haiku` now use a shorter system prompt, like other unrecognized names.
Usage details
Who can use it: Claude Code sessions using unrecognized model names through a custom gateway or provider.
How to use it: Set your custom model name and start the session; use `CLAUDE_CODE_SIMPLE_SYSTEM_PROMPT=0` if you need the full system prompt for all unrecognized names.
Tip: Standardize model naming in the gateway to reduce surprises in prompt size and model behavior.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları - CapabilityClaude Code for VS Code
Prompt and session group actions expanded in the VS Code sidebar
The Open in Side Bar command now accepts a `prompt` argument for keybindings and extensions; Move up and Move down actions were added to the session group menu.
Usage details
Who can use it: The Claude Code for VS Code extension.
How to use it: Pass the `prompt` argument to the Open in Side Bar command in a keybinding definition; select Move up or Move down from the session group menu.
Tip: Reduce repetitive context entry by opening frequently used prompts with a keybinding.
✓ Verified by official sourceSource: Claude Code 2.1.330 sürüm notları