Anthropic · Claude
New in this edition · 46
- AvailabilityClaude Code
Auto mode comes to cloud providers for Opus 4.6 and Sonnet 4.6
Auto mode is now available with Claude Opus 4.6 and Claude Sonnet 4.6 on Amazon Bedrock, Google Cloud Agent Platform, Microsoft Foundry, and Claude apps gateway. Interactive sessions started without a specified permission mode can start in Auto mode with these models; prompts on third-party providers also offer Auto mode for plan and Bash prompts.
Usage details
Who can use it: Amazon Bedrock, Google Cloud Agent Platform, Microsoft Foundry, and Claude apps gateway; Claude Code sessions using the relevant models.
How to use it: Start Claude Code with the relevant model on a supported provider without specifying a permission mode; select Auto mode in prompts. Use `disableAutoMode` to turn it off through an administrator setting.
Tip: Test how provider and organization policies are applied in a small repository before using automatic permission decisions in production workflows.
✓ Verified by official sourceModels: Claude Opus 4.6, Claude Sonnet 4.6Source: Claude Code v2.1.328 sürüm notları - Plugin / IntegrationClaude Code Self-hosted Runner
Self-hosted runner gh api access is disabled by default
In self-hosted runner environments where settings protect Claude GitHub tools by name, the built-in `gh api` is now disabled by default. The `--use-anthropic-gh true` option is required to enable it.
Usage details
Who can use it: Self-hosted runners and organizations that protect GitHub tools with settings.
How to use it: After confirming it is required, add `--use-anthropic-gh true` to the runner startup options.
Tip: Assess whether to enable it in conjunction with the organization’s GitHub permissions policy; treat the disabled-by-default behavior as a secure baseline.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - Pricing / PlanClaude Code
Plugin usage totals no longer stop at 2,000 tokens on 1M context models
The plugin total in `/usage` no longer stops at 2,000 tokens on 1M context models. Low token estimates in `/usage` and `/plugin` when no model is selected have also been corrected.
Usage details
Who can use it: Claude Code `/usage` and `/plugin` screens; includes 1M context models.
How to use it: Run a plugin with a 1M context model and check the totals in the `/usage` and `/plugin` screens.
Tip: When comparing plugin costs, don't rely only on the initial 2,000-token indicator; use the current total.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - AgentClaude Code
Subagent progress summaries are generated with a smaller, faster model
In terminal sessions using the Anthropic API, subagent progress summaries are now generated from brief notes using the default small, fast model. This change also uses fewer tokens when telemetry is disabled.
Usage details
Who can use it: Claude Code terminal sessions and subagents; Anthropic API.
How to use it: Run a subagent and monitor its progress summaries; compare summary token usage in the usage screen.
Tip: Keep this default in workflows that use many subagents and reserve the main budget for the task model.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - AgentClaude Code Agent SDK
Subagents now wait for their own subagents by default
When `CLAUDE_CODE_FORK_SUBAGENT=0` is set, subagents in `claude -p`, Agent SDK, Desktop, and VS Code now wait for their own subagents to complete by default. This reduces the risk of the parent session ending too early.
Usage details
Who can use it: Claude Code `-p`, Agent SDK, Claude Desktop, and VS Code; workflows using `CLAUDE_CODE_FORK_SUBAGENT=0`.
How to use it: Set `CLAUDE_CODE_FORK_SUBAGENT=0` in the environment and run a subagent chain; observe the wait behavior in the session result.
Tip: Plan for the total wait time separately when using long subagent chains.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - CapabilityClaude Code Artifacts
Artifact access status is shown more accurately in shared folders
Claude no longer mistakenly reports an artifact read from a shared folder or published by another organization as private. Its answer about who can open the artifact also takes folder access into account.
Usage details
Who can use it: Claude Code Artifact workflows and shared folders.
How to use it: Read an artifact in a shared folder or publish one to another organization; check the access view and Claude's explanation.
Tip: Before deciding whether to share, verify the artifact folder's actual membership settings rather than relying on Claude's text.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - CapabilityClaude Code
Large session resume speed and memory use improved
Resume time for large sessions has been reduced, and memory use in sessions containing many images has been lowered. Responsiveness has also improved in long SDK and Desktop sessions running slow tools or commands.
Usage details
Who can use it: Claude Code, Claude Desktop, and Agent SDK sessions.
How to use it: Resume a large session or one containing images, then compare startup time and memory use with the previous version.
Tip: Continue to archive very large transcripts regularly; this improvement does not guarantee unlimited memory.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - APIClaude Code CLI
claude -p counts background subagent wait time as a single 10-minute window
`claude -p` running with `CLAUDE_CODE_FORK_SUBAGENT=0` includes waiting for background subagents and the subagents they are waiting on in a single 10-minute wait period. `CLAUDE_CODE_PRINT_BG_WAIT_CEILING_MS` can be increased for longer chains.
Usage details
Who can use it: Headless `claude -p` and non-forking subagent chains.
How to use it: If needed, increase `CLAUDE_CODE_PRINT_BG_WAIT_CEILING_MS` and run `claude -p`.
Tip: Set the value according to the longest expected subagent chain rather than increasing it without limit.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - RetiredClaude in Chrome
Claude in Chrome shortcut tools removed from Claude Code
The built-in Claude in Chrome tools `shortcuts_list` and `shortcuts_execute` have been removed from Claude Code. These tools listed and ran shortcuts saved in the extension.
Usage details
Who can use it: Claude Code's built-in Claude in Chrome tools.
How to use it: Remove automations that call these two tools or migrate them to the current user workflow supported by the extension.
Tip: Before updating, search your commands, skills, and integrations for these tool names.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - Plugin / IntegrationClaude in Chrome
Claude in Chrome makes it clearer that it asks permission before acting
The Claude in Chrome welcome screen and `/chrome` now explain that Claude asks before taking action on a site. This prompt can be skipped if the Permission mode or a `/permissions` rule has already determined the decision.
Usage details
Who can use it: Claude in Chrome workflow in Claude Code.
How to use it: Open the `/chrome` command and review the behavior before actions; manage automatic decisions through `/permissions`.
Tip: Use a mode that explicitly requests permission on untrusted sites.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - AvailabilityClaude Code Cloud
Cloud sessions preserve summaries and recent messages saved late
When a message is saved late, cloud sessions no longer lose the compaction summary or recent messages upon resuming. This reduces the risk of context loss in long cloud sessions.
Usage details
Who can use it: Claude Code cloud sessions.
How to use it: Resume a long cloud session and check that recent messages and the compaction summary are preserved.
Tip: For critical work, separately verify the last response and changed files before resuming the session.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - CapabilityClaude Code
Warnings indicate when messages may be held or dropped in cloud sessions
Users are now notified that a message sent from a session that skips permission prompts may be held or dropped by a cloud session. Claude Code also explains what to do about this in `claude -p` output.
Usage details
Who can use it: Claude Code cloud sessions and cross-session messaging; sessions that skip permission prompts.
How to use it: Send a message to a cloud session from another session and check the terminal warning or `claude -p` stderr output.
Tip: To avoid losing critical messages, use the permission path in the session's settings after a warning says the message was held.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - FeatureClaude Code Code Mode
Code Mode is faster and more observable at runtime
The 0.75-second delay after most scripts has been removed in Code Mode; MCP server connection status and changes to the server list are passed to Claude. The commands run by scripts and their output are now visible, and editing and development server workflows have also been improved.
Usage details
Who can use it: Claude Code Code Mode; including auto and bypass-permissions workflows.
How to use it: Enable Code Mode, run a script in a session with an MCP server, and monitor the command/output flow.
Tip: Start development servers as background tasks that can be monitored under `/tasks` in Code Mode.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - FeatureClaude Code Code Mode
Code Mode script output no longer triggers UserPromptSubmit hooks
Code Mode no longer runs UserPromptSubmit hooks on script output, including managed hooks. A PostToolUse hook that uses `updatedToolOutput` is recommended for masking or modifying output.
Usage details
Who can use it: Claude Code Code Mode; user and managed hooks.
How to use it: If script output needs to be modified, define a PostToolUse hook and use the `updatedToolOutput` field.
Tip: Move sensitive-data cleanup to the PostToolUse stage instead of UserPromptSubmit.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - FeatureClaude Code
Code review findings narrowed and severity labels added
For most models, `/code-review` now primarily reports bugs and CLAUDE.md violations; `/simplify` is recommended for reuse and simplification. Findings are labeled Important, Pre-existing, or Nit, and the recommended fix appears at the end of the summary.
Usage details
Who can use it: Claude Code `/code-review`; most supported models.
How to use it: Run `/code-review` for reviews, and run `/simplify` separately for reuse or simplification cleanup.
Tip: In CI reviews, use only Important findings as a gate and track Pre-existing and Nit results separately.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - SettingClaude Code computer use
Computer use approval dialog shows access levels more clearly
The computer use approval dialog now shows each app's access level and clearer warnings. Users can more easily see the scope of access being granted before approving.
Usage details
Who can use it: Claude Code computer use approval flow.
How to use it: When the computer use approval dialog opens, review each app's access level and choose whether to approve or deny it.
Tip: Approve only the access level required rather than granting broad access to apps that do not need it.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - APIClaude Code
Missing OpenTelemetry endpoints are reported in status and doctor
If the OpenTelemetry exporter has no endpoint and data is likely to be lost, `/status` and `claude doctor` now display a warning. This lets you check from the command line whether telemetry is actually being sent.
Usage details
Who can use it: Claude Code installations using OpenTelemetry.
How to use it: Run `/status` or `claude doctor`; if you see a warning, complete the telemetry exporter's endpoint configuration.
Tip: If you expect observability in production, include this warning in your CI or environment health check.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - APIClaude Code CLI
A variable to disable deferred tool calls from running on resume has been added
`CLAUDE_CODE_DISABLE_DEFERRED_TOOL_RESUME` was added to prevent host applications from executing a tool call deferred by a hook during `claude -p --resume` and `--continue`.
Usage details
Who can use it: Claude Code CLI, especially headless sessions run by a host, SDK, or automation.
How to use it: Set `CLAUDE_CODE_DISABLE_DEFERRED_TOOL_RESUME=1` in the host environment, then run `claude -p --resume` or `--continue`.
Tip: Make this variable the default security option if hook decisions must always be reevaluated when resuming a session.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - Plugin / IntegrationClaude Code
Embedded applications can now restrict managed mods through policy alone
Applications embedding Claude Code can enable the policy plugin's `allowManagedModsOnly` option. Admin-enforced managed settings retain precedence as specified by this option.
Usage details
Who can use it: Applications embedding Claude Code and organization policies.
How to use it: Enable `allowManagedModsOnly` in the embedded application's policy plugin; also review the organization's managed settings.
Tip: When disabling user-installed mods, document the allowlisted managed mods separately.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - APIClaude Code Self-hosted Runner
Custom repository folder name added for capacity 1 runner sessions
`--repository-folder` was added to change the name of the repository path's base folder when using `--capacity 1` on a self-hosted runner. This lets you use the selected folder name instead of the default path layout, which cannot be a symbolic link.
Usage details
Who can use it: Claude Code self-hosted runner; repositories running with `--capacity 1`.
How to use it: Add `--capacity 1 --repository-folder <folder-name>` to the runner startup configuration.
Tip: Use consistent, meaningful folder names across multiple runner environments to make checkout paths easier to track.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - AvailabilityClaude Code Self-hosted Runner
Capacity 1 runner rejects symbolic repository paths earlier
A self-hosted runner using `--capacity 1` now rejects a session earlier if the repository path being pushed is a symbolic link. This moves an error that previously appeared late during checkout and push to startup.
Usage details
Who can use it: Self-hosted runner; `--capacity 1` and repositories being pushed.
How to use it: Before the runner starts, verify that the repository path is a real directory; provide the direct path instead of a symbolic link.
Tip: In runner health checks, inspect the repository path's `realpath` result and whether it's a symbolic link.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - Plugin / IntegrationClaude Code MCP
Complex MCP schemas no longer disappear with third-party providers
MCP tools whose input schemas begin with `anyOf`, `oneOf`, or `allOf` no longer become invisible with third-party providers or when telemetry/feature flags are disabled. If a schema is invalid, the tool is omitted and Claude is given the reason.
Usage details
Who can use it: Third-party providers and MCP sessions with telemetry/feature flags disabled.
How to use it: Publish the MCP tool's input schema with complex unions; check its visibility in `/mcp` or the tool list.
Tip: Monitor omission reasons in MCP server logs so invalid schemas don't prevent the call entirely.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - Pricing / PlanClaude Code
Running out of usage credits is no longer labeled a rate limit
The error shown when usage credits run out during a response has been corrected; the message no longer labels the issue as a rate limit. This distinguishes exhausted credits from a rate limit.
Usage details
Who can use it: Claude Code plans and sessions that use credits.
How to use it: If credits run out mid-response, check the error message and the `/usage` view.
Tip: If you run out of credits, check your plan or spending options before retrying.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - Plugin / IntegrationClaude Code MCP
MCP denial rules now apply to cloud and self-hosted sessions
Entries in `deniedMcpServers` in the format `claude.ai <name>` now block the relevant connector in cloud and self-hosted runner sessions as well. Previously, this scope did not apply to some session types.
Usage details
Who can use it: Cloud and self-hosted runner sessions; `claude.ai` connectors.
How to use it: Add a `claude.ai <name>` entry for the connector you want to block to the `deniedMcpServers` list in your settings file.
Tip: Standardize connector naming across your organization; verify rule matching with `/status` and a test session.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - SettingClaude Code
MCP tool hooks can block an operation when a call fails
The `onFailure: "block"` option has been added for `mcp_tool` hooks. If a hook fails, the relevant operation is blocked, as with command and HTTP hooks.
Usage details
Who can use it: Claude Code hook configurations; MCP tool calls.
How to use it: Add `"onFailure": "block"` to the relevant `mcp_tool` hook in your settings or hook configuration.
Tip: Use this option for hooks that perform security or compliance checks; account for temporary network errors in the hook stopping the operation.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - CapabilityClaude Code
Commands rewritten to run outside the sandbox via PermissionRequest run outside the sandbox
If a PermissionRequest hook rewrites a shell command to run outside the sandbox, Claude Code now executes that command outside the sandbox. This makes the hook’s return value consistent with the actual execution environment.
Usage details
Who can use it: PermissionRequest hooks and Bash commands.
How to use it: Use the outside-sandbox command rewrite behavior in your PermissionRequest hook; verify the command’s execution environment in a test.
Tip: Use this behavior only with trusted hooks, and log outside-sandbox permissions.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - APIClaude Code
Managed PostToolUse does not run for rejected tool calls
Calls rejected before execution no longer trigger managed PostToolUse hooks, so they produce no log, rewrite, block, or stop result. In most cases, call information is left to PostToolBatch.
Usage details
Who can use it: Managed PostToolUse and PostToolBatch hooks.
How to use it: When designing auditing for rejected calls, handle PostToolBatch records as well as PostToolUse records.
Tip: Define a separate path for rejected calls in compliance logs; do not record a tool that never ran as having run successfully.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - APIClaude Code Self-hosted Runner
Claude processes launched by wrappers outside the runner no longer use managed git
On a self-hosted runner, `claude` launched by a wrapper before or after the session's own Claude process now runs without Anthropic-managed git. Managed git is available only during the session's active lifecycle.
Usage details
Who can use it: Self-hosted runner wrapper and hook environments.
How to use it: Manage git access separately for Claude commands run before and after the session in your wrapper script.
Tip: Explicitly manage the provider credentials required for out-of-session git operations under a separate security policy.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - CapabilityClaude Desktop Agent SDK
Desktop and SDK turns that end with an open question no longer continue
For third-party providers or environments with telemetry/feature flags disabled, Claude Desktop and Agent SDK sessions closed while a question is open now end the turn instead of continuing without a user response.
Usage details
Who can use it: Claude Desktop and Agent SDK sessions; third-party providers or environments with telemetry/feature flags disabled.
How to use it: Close the session while a question is open and verify that the question has been terminated before starting a new turn.
Tip: In automations, detect pending questions and add logic to restart the session.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - CapabilityClaude Code
Spinner and subagent token counts corrected during retries
Spinner and subagent token indicators no longer count retried responses twice, miss non-streaming responses, or freeze while Claude is thinking. This makes the usage view better reflect actual consumption.
Usage details
Who can use it: Claude Code usage and subagent indicators.
How to use it: Monitor the spinner and subagent usage indicators during a response; compare the total for a session with retries against `/usage`.
Tip: For cost tracking, rely on completed session usage rather than the live spinner.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - CapabilityClaude Code Self-hosted Runner
Resumed self-hosted sessions check whether previous work is missing
When a self-hosted runner session is resumed, Claude now checks whether the previous work is still available and reports anything that's missing. This avoids silently assuming that checkouts or files are still present when they've been lost.
Usage details
Who can use it: Sessions resumed with a self-hosted runner.
How to use it: Reopen a self-hosted session and review Claude's previous-work check and missing-file notification.
Tip: Also verify important files and commits after runner cleanup or redeployment.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - CapabilityClaude Desktop
Large tool output no longer permanently ends sessions with third-party providers
A fix addresses some Claude Desktop sessions with third-party providers permanently ending with a `Prompt is too long` error after large tool results. The largest results are now omitted so the session can continue.
Usage details
Who can use it: Claude Desktop; third-party provider sessions outside Claude apps.
How to use it: Test a Desktop session that produces large tool output with a third-party provider; check how the session continues when the context limit is exceeded.
Tip: Still, paginate tool output and avoid including unnecessarily large results in prompts.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - CapabilityClaude Code Scheduled Tasks
Saving scheduled tasks no longer deletes other tasks
If the task file cannot be read when using third-party providers or when telemetry/feature flags are disabled, saving no longer deletes the project’s other tasks. A task with a typo in the file is also no longer silently deleted on the next save.
Usage details
Who can use it: Claude Code project scheduled tasks; third-party providers or limited-telemetry environments.
How to use it: Save project scheduled tasks and check that existing tasks are preserved when the file cannot be read.
Tip: Put the task file under version control; verify the save result until you fix the typo warning.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - SettingClaude Code
A Yes/No confirmation appears before submitting a bug report
The `/bug` command now asks Yes or No before submitting a report. This prevents repeated Enter presses from accidentally submitting a report or opening GitHub.
Usage details
Who can use it: Claude Code terminal; `/bug` command.
How to use it: Run `/bug` and explicitly select Yes when asked whether to submit the report.
Tip: Check whether the report contains sensitive data before confirming.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - SettingClaude Code apps gateway
Invalid maxEffortLevel values now trigger a startup warning
The Claude apps gateway now displays a startup warning if `maxEffortLevel` in its policy is not a valid effort level. This makes it easier to catch when a policy value is silently ignored.
Usage details
Who can use it: Organization policies using the Claude apps gateway.
How to use it: Check the gateway startup logs and update the policy's `maxEffortLevel` to a valid effort level.
Tip: Validate effort values against a schema before deploying policies.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - AgentClaude Code
The list-agents list is now shown only to the user
`/list-agents` now shows the subagent list only to the user; Claude lists sessions itself when needed. This prevents the agent list from being unnecessarily added to model context.
Usage details
Who can use it: Claude Code terminal; `/list-agents`.
How to use it: Run `/list-agents` and check that the list remains in the user interface.
Tip: If Claude needs information about agent status, ask it explicitly about the relevant session.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - AvailabilityClaude Code Remote Control
The session list explains when Remote Control is off
If a cloud session or another computer is not visible, Claude now explains more clearly that Remote Control is off and why it is not listed. This distinguishes a lack of connectivity from a lack of sessions.
Usage details
Who can use it: Claude Code cloud sessions and Remote Control.
How to use it: When access to a session on the cloud or another computer is not listed, check the Remote Control explanation shown.
Tip: In environments where connectivity is expected, verify Remote Control status as a health check before starting a session.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - APIClaude Code Self-hosted Runner
Two session UUID variables are now available together in runner hooks
`CLAUDE_RUNNER_SESSION_UUID` and `CLAUDE_CODE_REMOTE_SESSION_UUID` are now both set for the session itself and in checkout, post-session, and spawn-runner hooks.
Usage details
Who can use it: Self-hosted runner hooks.
How to use it: Read both environment variables in your hook code, and verify that their values refer to the same session before removing the old single-variable assumption.
Tip: Use one UUID as the primary key in traceability records and retain the other for backward compatibility.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - APIClaude Code Self-hosted Runner
Two metrics added for runner queue and abandoned sessions
The orchestrator now measures queue wait time by reason with `claude_code_self_hosted_orchestrator_session_queue_wait_by_reason_seconds` and sessions Anthropic chose not to start with `claude_code_self_hosted_orchestrator_sessions_given_up_total`.
Usage details
Who can use it: The self-hosted runner orchestrator `/metrics` endpoint.
How to use it: Collect the orchestrator's `/metrics` output and monitor both metrics by reason, status, and time series.
Tip: Add the new metrics to your existing runner success-rate and queue-duration dashboards.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - APIClaude Code Self-hosted Runner
Metadata can be added to a self-hosted session for spawn-runner
The `--metadata key=value` option has been added to `claude --environment`. This metadata helps the `spawn-runner` hook label the session.
Usage details
Who can use it: Claude Code self-hosted runner environments.
How to use it: Start the session using `claude --environment --metadata key=value`.
Tip: Do not put secrets in metadata; use this field only for routing and observability labels.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - APIClaude Code Self-hosted Runner
Selected session label can be passed to self-hosted runner hooks
The `--hook-label` option was added to the orchestrator. The specified label is passed to the `spawn-runner` hook and can be used in runner startup logic.
Usage details
Who can use it: Self-hosted runner orchestrator and `spawn-runner` hooks.
How to use it: Add `--hook-label <label>` to the `claude self-hosted-runner orchestrator` command.
Tip: Standardize labels using a limited vocabulary, such as team, environment, or priority.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - AvailabilityClaude Code VS Code extension
VS Code shows a settings link for held-session messages
When a message from another session is held, the VS Code extension now shows a notification and a link to the settings file where this can be enabled.
Usage details
Who can use it: Claude Code VS Code extension and cross-session messaging.
How to use it: Send a message from another session; open the settings file link in the notification and review the option in line with your organization's policy.
Tip: Test hold and drop behavior in cloud sessions before changing your organization's settings.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - CapabilityClaude Code
Pasted text is now clearly marked for Claude
When telemetry or feature flags are disabled, or when using a third-party provider, pasted text is marked as pasted for Claude. This improves the distinction between user-written and pasted content.
Usage details
Who can use it: Claude Code; third-party providers and sessions with telemetry/feature flags disabled.
How to use it: Paste text into the terminal and submit the prompt; verify in Claude’s context that it is handled as pasted content.
Tip: Before pasting long text or text from an external source, remove any sensitive data.
✓ Verified by official sourceSource: Claude Code v2.1.328 sürüm notları - SettingClaude Code CLI
claude purge no longer hides deletion prompts when output is redirected
Deletion confirmations remain visible in the terminal when `claude purge` stdout is redirected. This prevents an unseen Enter keypress from deleting project data.
Usage details
Who can use it: Claude Code CLI; `claude purge` runs with redirected stdout.
How to use it: Run `claude purge` with stdout redirected and verify that deletion prompts are clearly visible in the terminal.
Tip: Before automating deletions, test the interactive confirmation behavior in a separate test environment.
✓ Verified by official sourceSource: Claude Code v2.1.327 sürüm notları - CapabilityClaude Code
Unloaded earlier messages are now reported when resuming a session
If some earlier messages can't be loaded when a session is resumed, Claude Code now reports this explicitly. This prevents missing context from appearing as a silent change in behavior.
Usage details
Who can use it: Claude Code 2.1.327 and later; terminal sessions.
How to use it: Resume a session with `--resume`; check the warning shown if earlier messages can't be loaded.
Tip: If you see a warning about missing messages, add important context to the new prompt again.
✓ Verified by official sourceSource: Claude Code v2.1.327 sürüm notları