TOP 10 unchanged; Message Threads comes to Claude API, phone calls to Grok Bot

New in this edition · 2

• 02 Nov
  FeatureGoogle Vids

  Create a custom avatar in Google Vids by uploading an image

  Google Vids now lets you create a custom AI avatar from an image uploaded from your computer, Drive, or Photos. You can refine the image in Vids and reuse the avatar within the same project.

  Usage details

  Who can use it: Visibility in Rapid Release domains is rolling out starting October 30, 2026; full rollout in Scheduled Release domains begins November 20, 2026. Available to Business Starter/Standard/Plus, Enterprise Starter/Standard/Plus, Education Plus, personal Google accounts, Google AI Pro and Ultra, Enterprise Essentials/Essentials Plus, Nonprofits, Individual, Google AI Pro for Education, Teaching and Learning, and AI Expanded Access.

  How to use it: Open Google Vids > AI avatar > Design a custom avatar > Upload image > Upload. Select an image, edit it with Refine selected if needed, add a voice and name, then click Save > Select; enter your text and select Insert.

  Tip: For best results, use a well-lit, 16:9 landscape image with a clear face and neutral background; you can reuse the avatar stored in the project in the same video.

  ✓ Verified by official sourceSource: Google Workspace Updates: Google Vids'te görsel yükleyerek özel avatar oluşturmaSource: Google Docs Editors Help: Google Vids'te AI avatar kullanma
• 02 Nov
  AvailabilityGemini Enterprise Agent Platform

  Fine-tuned Gemini 3.x models reach GA on global endpoints

  Gemini Enterprise Agent Platform has made serving fine-tuned Gemini 3.x models on global endpoints Generally Available (GA). Developers can now copy fine-tuned models to the global region through Model Registry and deploy them to a global serving endpoint.

  Usage details

  Who can use it: Generally Available (GA) for projects fine-tuning Gemini 3.x models on Gemini Enterprise Agent Platform; the global region and the direct `aiplatform.googleapis.com` endpoint are available.

  How to use it: Copy the fine-tuned Gemini 3.x model to the `global` region using the Model Registry `models:copy` API, deploy it to a global serving endpoint, and send inference requests through `aiplatform.googleapis.com`.

  Tip: The global endpoint expands access; for workloads with data residency or compliance requirements, compare your needs against the `us` and `eu` multi-region options before switching to global deployment.

  ✓ Verified by official sourceModels: Gemini 3.5 Flash-Lite, Gemini 3.5 Flash, Gemini 3.1 Flash-LiteSource: Gemini Enterprise Agent Platform sürüm notları: tuned Gemini 3.x modellerinin global uç noktalarda GA olmasıSource: Google Cloud: Gemini modelleri için supervised fine-tuning dokümantasyonu

New in this edition · 87

• 03 Nov
  APIAgent SDK

  Agent SDK hooks can block a flow when a callback fails

  The `onFailure: "block"` option was added to Agent SDK hook callbacks. When a callback fails, the relevant operation can now be blocked instead of continuing.

  Usage details

  Who can use it: Developers using Agent SDK hook callbacks.

  How to use it: Add `onFailure: "block"` to the hook definition and update the SDK in flows where you want the action to stop when the callback fails.

  Tip: Use `block` for security or compliance checks; for temporary telemetry hooks, keep the existing behavior to avoid unintended interruptions.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  SettingClaude Code Cloud

  Adding a network secret for the same host no longer overwrites the existing secret

  Adding a new secret to a host that already has a network secret no longer silently replaces the existing value; the Add secret form rejects it and shows the existing secret.

  Usage details

  Who can use it: Organization administrators managing network secrets in cloud environments.

  How to use it: In the Add secret form, select an existing host and try submitting a new secret; follow the form’s rejection and the link to the existing secret.

  Tip: When rotating a secret, use the management workflow that deliberately updates the existing secret instead of adding a new entry.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  AgentClaude Code

  SendMessage reaches a running background agent sooner

  SendMessage sent to a running background agent now moves it to the background without stopping its command, allowing the message to arrive sooner.

  Usage details

  Who can use it: Claude Code agent team workflows that use background agents and SendMessage.

  How to use it: Send SendMessage while a background agent is running; watch to confirm the running command is moved to the background without stopping and the agent receives the message.

  Tip: Use this when you don’t want the command interrupted; choose the separate Stop behavior for an urgent stop.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  Plugin / IntegrationClaude Code Cloud

  MCP connection requests appear as cards in cloud sessions

  Cloud sessions now display a visible card for a link that an MCP server requests to open; users can open or reject the link.

  Usage details

  Who can use it: Claude Code cloud sessions where MCP servers request to open a link.

  How to use it: Run the MCP server in a cloud session; use the visible link card to open the URL or reject the request.

  Tip: Don’t open the link before verifying the domain on the card; make sure it belongs to the expected MCP server integration.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  CapabilityClaude Code

  `claude -p` now exits with code 1 when disk space or quota runs out

  If a transcript or `~/.claude.json` can’t be written because the disk is full or a quota has been reached, `claude -p` no longer returns success code 0; it prints an error and returns exit code 1 in text and JSON modes.

  Usage details

  Who can use it: All users running automation with `claude -p`; some full NFS exports may be excluded.

  How to use it: Check the exit code of the `claude -p` call and log the error message when it returns 1; configure your CI workflow to fail on this code.

  Tip: In automation, rely on the exit code as well as stdout, and monitor disk space and quotas in the transcript directory.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  SettingClaude Code

  Consent added for tool calls that send email addresses over the network

  If a web or shell tool is going to send the account’s email address over the network, Claude Code now asks for consent before making the call.

  Usage details

  Who can use it: Sessions using Claude Code’s web or shell tools.

  How to use it: Run the web or shell tool; if the email address will be included in a network request, review the permission prompt and approve or deny it.

  Tip: To prevent unnecessary identity sharing, deny requests to unexpected domains.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  APIClaude apps gateway

  Date-range cost reporting added to the gateway admin API

  The Claude apps gateway admin API now returns historical spending by total, developer, day, or IdP group through `GET /v1/organizations/analytics/cost`.

  Usage details

  Who can use it: Claude apps gateway administrators; organizations with access to the admin API.

  How to use it: Call `GET /v1/organizations/analytics/cost` from your authorized gateway admin client and request a date range and breakdown by total, developer, day, or IdP group.

  Tip: Export cost reports regularly with IdP group and daily breakdowns to catch budget deviations early.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  APIClaude Code

  Nested `claude -p` calls no longer corrupt the outer transcript

  Fixed an issue where a `claude -p` call running in a Cloud or self-hosted runner session wrote to the transcript using the outer session ID and resumed the wrong conversation on restart.

  Usage details

  Who can use it: Automations running `claude -p` inside a Cloud or self-hosted runner.

  How to use it: Run nested `claude -p` in a runner session, then restart the outer session and check that the transcripts are separate.

  Tip: Track inner and outer workflows using separate IDs; if you need a shared transcript, configure this explicitly.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  AgentClaude Code

  Self-hosted sessions restarted during plan approval retain recent turns

  Fixed an issue where self-hosted runner sessions restarted while awaiting plan approval could lose recent turns or the entire conversation.

  Usage details

  Who can use it: Claude Code sessions with plan approval on self-hosted runner.

  How to use it: Restart the session during plan approval and check that the latest messages and approval status are retained in the transcript.

  Tip: Still, back up the transcript before restarting during critical plan approvals.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  FeatureClaude Code

  `/design-sync` gives an early warning when a design system has moved

  `/design-sync` now tells you upfront that the design system has moved to Claude and stops before starting production instead of failing during upload.

  Usage details

  Who can use it: Claude Code and design system workflows that use `/design-sync`.

  How to use it: Run `/design-sync`; if the design system has moved, read the notification and configure its new location in Claude first.

  Tip: Before a large sync, check the design system source’s active location to avoid unnecessary uploads.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  CapabilityClaude Code

  Won’t delete the wrong guide when no `/team-onboarding` name is specified

  Fixed an issue where Claude deleted the most recently updated guide if no guide was specified when multiple guides existed.

  Usage details

  Who can use it: Claude Code teams using `/team-onboarding` guides.

  How to use it: Explicitly provide the guide name before deleting; with v2.1.317, verify that an unnamed deletion request doesn’t target the wrong guide.

  Tip: For bulk guide management, list guides first and verify their names explicitly before deleting.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  Plugin / IntegrationClaude Code

  `claude auth status` no longer drops the session during a slow token refresh

  `claude auth status` no longer exits before a slow token refresh is recorded, so the user no longer appears to be accidentally signed out on the next run.

  Usage details

  Who can use it: All platforms using Claude Code authentication.

  How to use it: Update Claude Code to v2.1.317 and run the `claude auth status` command.

  Tip: In CI or managed environments, don’t terminate the process immediately after checking authentication status; allow the token refresh to complete.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  FeatureClaude Code

  Shared items remain visible when you have more than 200 personal artifacts

  Fixed an issue where shared artifacts were not visible in the combined list in `/artifacts` and the Artifact tool when a user had 200 or more personal artifacts.

  Usage details

  Who can use it: Users of Claude Code Artifact sharing lists.

  How to use it: Open the `/artifacts` command or view the Artifact tool list; access shared items when you have a large number of personal artifacts.

  Tip: Clean up and name your Artifact archive regularly; search and filters are faster for large lists.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  SettingClaude Code

  Background session permission mode no longer gets lost during promotion

  Fixed an issue where a recent permission mode change was lost when a background session was promoted or retired.

  Usage details

  Who can use it: Users changing permission modes in background Claude Code sessions.

  How to use it: Change the background session’s permission mode, then promote or retire the session; check that the new mode is retained.

  Tip: Keep changes to authorized modes auditable by recording them in the transcript or event log.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  FeatureClaude Code

  Auto mode makes a nonresponsive subagent check visible

  If the Auto mode check cannot respond to a subagent’s tool call, Claude Code now displays a notification in the main view. Previously, the user might not have seen anything in this situation.

  Usage details

  Who can use it: Claude Code sessions using Auto mode and subagents.

  How to use it: In Auto mode, run a subagent that makes a tool call; if the check does not respond, follow the notification in the main view.

  Tip: When you see the notification, check that the subagent isn’t stuck waiting and manually restart the call if needed.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  CapabilityClaude Code

  Auto mode no longer loops on gateway 403 and 422 security responses

  Fixed an issue where Auto mode failed on every turn when an LLM gateway used as the base URL returned 403 or 422 for a server-side security check. The behavior for 403 responses returned by `apiKeyHelper` is unchanged.

  Usage details

  Who can use it: Auto mode sessions using an LLM gateway or custom base URL.

  How to use it: Configure the gateway’s base URL and run Auto mode; check the new error behavior and gateway logs for 403/422 responses.

  Tip: Verify the expected status codes and authentication path for the gateway’s security check in advance.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  APIClaude apps gateway

  The Bedrock ‘Input is too long’ error is no longer hidden

  The gateway no longer converts Amazon Bedrock’s `Input is too long.` error into a generic upstream error, making it possible to understand why the session needs automatic compaction.

  Usage details

  Who can use it: Organizations using Amazon Bedrock through the Claude apps gateway.

  How to use it: When an error occurs in a long-context Bedrock session, inspect the `Input is too long.` message in the gateway response and the compaction behavior.

  Tip: If you see the error, reduce the context or review your compaction settings; don’t retry as if it were a generic upstream error.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  AvailabilityClaude Code

  Region or network blocks are no longer mistaken for sign-in errors

  HTTP 403 errors caused by a region or network block are no longer shown as sign-in failures; the error message now explains the block itself.

  Usage details

  Who can use it: Users accessing Claude Code with region restrictions or network filtering.

  How to use it: Update Claude Code and retry the connection; use the region or network block details in the new error message to resolve the issue with your administrator.

  Tip: Check allowed domains and region policies on your corporate proxy before changing credentials.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  Plugin / IntegrationClaude Code

  An empty Bedrock bearer token setting no longer overrides machine credentials

  When the environment configuration for a Stdio MCP server leaves `AWS_BEARER_TOKEN_BEDROCK` empty, the variable is no longer passed through as empty; the server can use the machine’s AWS credentials.

  Usage details

  Who can use it: Stdio MCP servers using Bedrock.

  How to use it: Leave `AWS_BEARER_TOKEN_BEDROCK` empty in the MCP environment configuration and test with v2.1.317 that the server connects using the machine’s identity.

  Tip: Document the credential source explicitly; monitor logs for unexpected switching between an empty variable and a real bearer token.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  CapabilityClaude Code

  Prompt overflow after compaction is fixed when a large CLAUDE.md changes

  The `Prompt is too long` error after automatic compaction has been fixed for cases where a very large `CLAUDE.md` file changes after the last submission.

  Usage details

  Who can use it: Long Claude Code sessions using a large CLAUDE.md.

  How to use it: Update the CLAUDE.md file, trigger compaction in a long session, and retry the new turn.

  Tip: Avoid bloating the root instruction file with unnecessary repetition; move long rules into a skill or reference file.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  Plugin / IntegrationClaude Code

  Skills synced with claude.ai no longer disappear when writing to disk fails

  When skills synced from claude.ai can’t be written to disk, they no longer disappear and enter a re-download loop every ten minutes.

  Usage details

  Who can use it: Users who sync claude.ai skills with Claude Code.

  How to use it: Leave syncing enabled, update Claude Code to v2.1.317, and verify that the skill remains listed after restarting the session.

  Tip: Fix disk permissions too; the persistence fix doesn’t store the skill locally when the environment lacks write permissions.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  CapabilityClaude Code Cloud

  Cloud Auto mode no longer requests unnecessary confirmation for Artifact output operations

  In cloud sessions, file uploads, database writes, and saves to the outputs folder by the Artifact tool no longer unnecessarily pause Auto mode for confirmation.

  Usage details

  Who can use it: Auto mode and the Artifact tool in Claude Code cloud sessions.

  How to use it: Enable Auto mode in a cloud session, then use Artifact to upload an output, write to a database, or save to the outputs folder.

  Tip: Still review your permission policy before running Artifact operations that write data to external systems with production data.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  SettingClaude Desktop

  Code tab shows when remote managed settings are loaded

  The Claude Desktop Code tab warns if the organization’s remote managed settings have not yet loaded for the session and shows a second notification when they have loaded.

  Usage details

  Who can use it: Claude Desktop Code sessions configured with organization-managed remote settings.

  How to use it: Start a new session in the Code tab in Claude Desktop; wait for the settings-loaded notification and verify that organizational policies have been applied.

  Tip: Don’t start policy-governed tasks before the initial notification clears; wait for the notification confirming that the settings have loaded.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  CapabilityClaude Code

  Memory usage and startup improved in headless sessions with many plugins

  High memory usage and slow startup were fixed in headless sessions using many plugins that register commands.

  Usage details

  Who can use it: Headless Claude Code and automations using many plugins.

  How to use it: Start a headless session with plugins enabled using v2.1.317, and monitor startup time and memory usage.

  Tip: Reduce startup overhead further by enabling only the plugins needed for headless deployments.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  CapabilityClaude Code

  Previous summaries are preserved during compaction in very long conversations

  Fixed an issue that caused very long conversations to lose their previous summary when compaction had to shorten its own request.

  Usage details

  Who can use it: Long-context Claude Code conversations.

  How to use it: Trigger compaction in a long conversation and check that the previous work summary remains in the new context.

  Tip: Also write critical decisions in a short project note; even with improved compaction, don’t rely on a single context store.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  Plugin / IntegrationClaude Desktop

  Local and project MCP servers no longer disconnect in Desktop sessions

  Fixed connection behavior for project and local MCP servers that disconnected after the first turn in some Claude Desktop sessions.

  Usage details

  Who can use it: Users of project or local MCP servers in Claude Desktop.

  How to use it: Update Claude Desktop to v2.1.317 and reconnect your MCP server; check the tool list in subsequent turns.

  Tip: After updating, try calling tools over multiple turns to verify that the MCP connection really persists.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  FeatureClaude Code Cloud

  Disabled scheduled tasks can be listed and deleted

  Fixed an issue where stored tasks could not be listed or deleted after the scheduled task feature was turned off.

  Usage details

  Who can use it: Claude Code cloud scheduled task administrators.

  How to use it: Temporarily turn off scheduled tasks, open the task list, and list or delete a stored task.

  Tip: Export tasks before turning off the feature; verify in the new flow that you can still clean them up while it is disabled.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  CapabilityClaude Code

  Screen reader no longer announces subagent counters on every change

  Fixed an issue where a subagent running in screen reader mode repeatedly announced elapsed time and token counts after every change.

  Usage details

  Who can use it: Accessibility users who use Claude Code screen reader mode.

  How to use it: Turn on screen reader mode and run a subagent; check that elapsed time and token information are not spoken repeatedly without need.

  Tip: For long tasks, keep screen reader notifications low-noise so you hear only status changes.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  APIClaude Code

  Connection floods to a blocked HTTP OTel proxy are prevented

  Fixed repeated connection attempts when a proxy for an HTTP OpenTelemetry endpoint returns HTTP 403.

  Usage details

  Who can use it: Claude Code environments using an HTTP OTLP endpoint and a proxy that returns 403.

  How to use it: Configure an OTel HTTP endpoint and reproduce the proxy block; confirm in the logs with v2.1.317 that the repeated connection flood has stopped.

  Tip: Fix proxy permissions or the OTLP URL instead of retrying a blocked endpoint.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  CapabilityClaude

  Invisible text watermarking is being extended to older Claude models

  According to a report by Mashable citing an email to Anthropic users, starting November 3, outputs from Claude Mythos 5, Claude Opus 4.7, Claude Opus 4.6, and Claude Sonnet 4.6 will also carry an invisible text watermark. Anthropic’s official help page confirms work to add marking to older models, but does not officially state that activation for these four models is dated November 3; this report should therefore be considered unverified.

  Usage details

  Who can use it: According to the report, globally in Claude outputs from the older models in question and across surfaces where Claude is available; the watermark is invisible to readers and does not carry user or organization identity.

  How to use it: There is no user-side setting to enable; generate text with the relevant model. Audit access is currently limited to a private preview for regulators, law enforcement, media, fact-checking organizations, researchers, and similar eligible organizations.

  Tip: Assume Claude output may be watermarked before putting it into an enterprise text workflow; follow the official content marking and detection documentation.

  ! UnverifiedModels: Claude Mythos 5, Claude Opus 4.7, Claude Opus 4.6, Claude Sonnet 4.6Source: Anthropic expands text watermarking to older Claude versions beginning November 3Source: How Claude marks AI-generated contentSource: Claude text watermark açıklaması
• 03 Nov
  FeatureClaude

  The second call path remains visible in concurrent permission requests

  The second of two permission requests opened at the same time no longer appears in Claude web and mobile apps without showing the file path or command.

  Usage details

  Who can use it: Concurrent tool permissions in Claude web and mobile apps.

  How to use it: Trigger two tool calls at the same time; review the file path or command in the second permission card before deciding.

  Tip: Don’t approve requests in bulk without seeing the permission card’s context; check each call’s path separately.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  SettingClaude Code

  Subagents using a different model now use their own effort level

  Subagents and teammates using a different model from the main conversation now use their own saved level or the model default, instead of forcibly inheriting the session’s effort level.

  Usage details

  Who can use it: Claude Code users running subagents or teammates with multiple models.

  How to use it: Assign the subagent a different model from the main model; check in the session view that it uses that model’s saved effort setting or default.

  Tip: Test each model’s effort level separately to meet model-specific cost and quality goals.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  APIClaude apps gateway

  Daily IdP group records for developers are retained in gateways

  Claude apps gateways with `admin:` enabled record developers’ IdP groups daily. Records are retained for `admin.identity_retention_days`, enabling group breakdowns in cost reports.

  Usage details

  Who can use it: Claude apps gateway organizations with the `admin:` setting enabled.

  How to use it: Set `admin.identity_retention_days` in the gateway admin settings; use the IdP group breakdown in cost reports.

  Tip: Set the identity data retention period to the minimum duration required by your organization’s compliance policy.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  AgentClaude Code

  Ctrl+C clears the prompt line without stopping background agents

  Fixed an issue that stopped all running background agents when Ctrl+C was pressed to clear text in the prompt line.

  Usage details

  Who can use it: Concurrent Claude Code sessions with background agents.

  How to use it: While a background agent is running, type text in the prompt line and clear it with Ctrl+C; check that the agents continue running.

  Tip: Use the explicit stop command to actually stop an agent; don’t mistake the prompt-clearing shortcut for a stop signal.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  Plugin / IntegrationClaude Code

  TLS proxy connections work after root certificate renewal

  Fixed the `unable to get local issuer certificate` API error that occurred after root certificate renewal with some TLS-inspecting proxies.

  Usage details

  Who can use it: Claude Code API clients behind TLS-inspecting proxies.

  How to use it: Update Claude Code and make an API call behind the proxy; if needed, also renew the system root certificate store.

  Tip: Test the proxy’s intermediate certificate chain and the client trust store together; don’t just change the API key.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  APIClaude Code

  Microsoft Foundry credential error is now more informative

  When Azure credentials can’t be loaded, the Microsoft Foundry error now provides refresh or troubleshooting steps and is reported as `cloud_credential_error`.

  Usage details

  Who can use it: Teams using Claude Code through Microsoft Foundry.

  How to use it: Break Foundry authentication or try with an expired credential; refresh the credentials based on the `cloud_credential_error` code.

  Tip: Classify this error code separately from sign-in errors in your monitoring system.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  SettingClaude Code

  Previously opened app sessions now retain the project effortLevel setting

  Sessions that an app starts in advance and opens in a project no longer ignore the project’s `effortLevel` setting.

  Usage details

  Who can use it: App workflows that open sessions in advance, such as the Claude Desktop Code tab.

  How to use it: Set `effortLevel` in the project’s settings file, start a new session in the Claude Desktop Code tab, and check the selected level.

  Tip: For project-specific performance and cost targets, explicitly pin `effortLevel` in a shared settings file.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  APIClaude Code

  Plan and provider attributes added to OpenTelemetry signals

  OpenTelemetry metrics, events, and spans now include the `anthropic.plan`, `anthropic.seat_type`, `anthropic.provider`, and `anthropic.custom_base_url` attributes.

  Usage details

  Who can use it: Teams and administrators exporting Claude Code telemetry to OpenTelemetry.

  How to use it: In your existing OTel collector, define a query or dashboard filter to receive these four `anthropic.*` attributes; send signals from the new Claude Code version.

  Tip: Use these attributes as low-cardinality dimensions to separate error, cost, and usage dashboards by plan and provider.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  SettingClaude Code

  Prompt caching disable variables now apply to all default model name formats

  `DISABLE_PROMPT_CACHING_OPUS` and `DISABLE_PROMPT_CACHING_SONNET` now also take effect with `[1m]`, region-prefixed, and undated default model names.

  Usage details

  Who can use it: Claude Code users managing prompt caching with environment variables.

  How to use it: Set `DISABLE_PROMPT_CACHING_OPUS=1` or `DISABLE_PROMPT_CACHING_SONNET=1` for the relevant model and check cache behavior with different model name formats.

  Tip: Normalize model names in production; verify the variable’s effect with a test request instead of assuming it’s active.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  APIClaude Code

  HTTPS OpenTelemetry exports through a proxy are no longer lost

  Fixed an issue where OpenTelemetry exports to an HTTPS endpoint through a proxy were never sent if they started while another export was in progress.

  Usage details

  Who can use it: Claude Code deployments using an HTTPS OTel endpoint behind a proxy.

  How to use it: Configure an OTLP HTTPS endpoint and proxy, generate telemetry concurrently, and check that all signals reach the collector.

  Tip: After upgrading, verify export delivery by tracking sequence numbers or timestamps on the collector side.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  SettingClaude Code

  Persistent approval option removed for Remote Control and SDK mod tools

  Remote Control and SDK hosts no longer mistakenly offer the `don’t ask again` option for mod tool calls.

  Usage details

  Who can use it: Sessions using mod tools through Remote Control or an SDK host.

  How to use it: Call the mod tool in a session; use only valid options in the permission prompt and note that the persistent approval option has been removed.

  Tip: If automation is needed, explicitly define permissions in the host configuration; don’t assume persistent trust from a one-time prompt.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  Plugin / IntegrationClaude Code Remote Control

  A recent message is answered when Remote Control restarts

  Fixed an issue where, after `claude remote-control` restarted, the next message was left unanswered in an idle session if it was sent within one minute of the previous message.

  Usage details

  Who can use it: Users restarting Claude Code Remote Control.

  How to use it: Restart Remote Control, send a message to an idle session within one minute, and check that the response arrives.

  Tip: Monitor the message queue during a restart; for critical commands, confirm that the session is actually idle and connected.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  CapabilityClaude Code

  Self-hosted runner polls using a new connection after a 5xx

  After a 5xx response other than 501 or 529, the runner’s next poll now opens a new connection instead of reusing the failed connection.

  Usage details

  Who can use it: Organizations using self-hosted runners.

  How to use it: Update the runner to v2.1.317 and check the runner logs to verify that the next poll connection is re-established after a transient 5xx.

  Tip: Monitor the 5xx rate and the number of new connections; don’t rely on reconnection alone for persistent 5xx errors.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  SettingClaude Code

  Nested session ID behavior can be reverted for self-hosted runners

  `CLAUDE_CODE_DISABLE_NESTED_SESSION_ID=1` makes a `claude -p` call inside a self-hosted runner use the outer session’s ID and transcript.

  Usage details

  Who can use it: Teams running nested `claude -p` on a self-hosted runner.

  How to use it: Add the `CLAUDE_CODE_DISABLE_NESTED_SESSION_ID=1` variable to the runner environment and run `claude -p` when you want the inner session to use the outer session’s ID/transcript.

  Tip: Don’t use this variable in automations that need separate conversation histories; consider the audit implications of shared transcript behavior.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  CapabilityClaude Code

  Self-hosted runner sessions refresh their connection after a 5xx

  After a 5xx other than 501 or 529, runner sessions now open a new connection instead of using the failed one.

  Usage details

  Who can use it: Self-hosted runner sessions.

  How to use it: Trigger a transient 5xx and monitor the session; verify in the session logs that a new connection opens automatically.

  Tip: Track server error codes separately as 501, 529, and other 5xx errors; each has different recovery behavior.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  AgentClaude Code

  Self-paced `/loop` wake-ups are now scheduled even when a request field is missing

  Fixed an issue where a self-paced wake-up was sometimes not scheduled when Claude omitted one of the fields in a `/loop` request.

  Usage details

  Who can use it: Users of Claude Code’s self-paced `/loop` workflow.

  How to use it: Start a self-paced task with `/loop` and check that the next wake-up time appears in the session.

  Tip: For critical periodic tasks, check `/loop` status once after initial setup and add independent monitoring.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  AgentClaude Code

  Deleted agent team inboxes are no longer recreated by late messages

  Fixed an issue where a late teammate message recreated an agent team inbox after it had been deleted.

  Usage details

  Who can use it: Teams using Claude Code agent teams.

  How to use it: Run the agent team on v2.1.317, delete the inbox, and check that it is not recreated when a late message arrives.

  Tip: Stop teammates before ending the team lifecycle; this makes late messages more predictable to manage.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  Plugin / IntegrationClaude Tag

  Artifact links pasted into Slack now show a simpler Open card

  Newly pasted artifact links in Slack now show a simpler card with an Open button that opens the artifact in Claude, rather than the Slack side panel.

  Usage details

  Who can use it: Teams using Claude Tag or Claude artifact links in Slack.

  How to use it: Paste a Claude artifact link into Slack; click the Open button on the card to open the artifact in Claude.

  Tip: Check artifact access permissions before sharing; the recipient needs Claude access to use the Open button.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  CapabilityClaude Code

  Claude doesn’t claim success when the server refuses a deletion

  Fixed an issue where Claude said the guide was deleted when the server rejected a `/team-onboarding` deletion request.

  Usage details

  Who can use it: Teams using server-side `/team-onboarding` guide management.

  How to use it: Send a deletion request and check both the returned error and the guide list when the server rejects it.

  Tip: In automations, use the server response and the actual list—not Claude’s text—as proof of deletion.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  CapabilityClaude Code for VS Code

  VS Code now raises ultrathink effort when telemetry is disabled

  Fixed an issue where `ultrathink` did not increase turn effort or show the rainbow indicator in VS Code when telemetry was disabled.

  Usage details

  Who can use it: Claude Code for VS Code users who disable telemetry.

  How to use it: Disable telemetry, start a turn with `ultrathink` in VS Code chat, and check that the effort and visual indicator are enabled.

  Tip: Use high effort only for difficult reasoning steps to limit unnecessary latency and usage.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  AgentClaude Code

  tmux and iTerm2 teammates follow the leader’s manual mode

  Fixed an issue where agent team teammates in tmux or iTerm2 panes started in Auto mode while the leader session was in manual mode.

  Usage details

  Who can use it: Users running Claude Code agent teams with tmux or iTerm2.

  How to use it: Open the leader session in manual mode, start a teammate, and check that the mode remains manual in the panes.

  Tip: Set the leader’s permission mode before the team starts; don’t assume every teammate will behave automatically.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  AvailabilityClaude Code

  Gateway unavailability error explains network and TLS causes

  When a required Claude apps gateway can’t be reached, the startup error no longer presents it as a sign-in issue; it distinguishes network access from an unverifiable TLS certificate.

  Usage details

  Who can use it: Claude Code installations using a required gateway or managed network policy.

  How to use it: Block access to the gateway and start Claude Code; use the new error message to identify whether the cause is the network connection or TLS certificate.

  Tip: Test the gateway’s DNS, firewall, proxy, and certificate chain before resetting credentials.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  AvailabilityClaude Code for VS Code

  VS Code no longer opens the sign-in screen when a network or region blocks a request

  Fixed an issue where the VS Code extension opened the sign-in screen when a request was blocked due to a region or network restriction.

  Usage details

  Who can use it: Claude Code for VS Code users subject to region or network restrictions.

  How to use it: Send a request from a blocked network and check that the extension displays an explanation of the block instead of the authentication screen.

  Tip: Before repeatedly trying to sign in on a restricted network, verify proxy and regional access with your administrator.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  CapabilityClaude Code for VS Code

  The VS Code extension retries a message that was missed during startup

  When a message is lost because Claude could not start in time, the extension now tries to start Claude one more time before showing an error.

  Usage details

  Who can use it: Claude Code for VS Code extension.

  How to use it: Open the extension and reproduce the startup race; check that the second attempt preserves the message when the first startup fails.

  Tip: If the second attempt also fails, record the extension logs and Claude Code version together.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  CapabilityClaude Code for VS Code

  VS Code forked conversations retain parallel calls and compaction messages

  Fixed an issue where forked VS Code conversations retained only one of the parallel tool calls or the final messages kept by compaction.

  Usage details

  Who can use it: Users who use conversation forks in Claude Code for VS Code.

  How to use it: Fork a conversation in VS Code, run parallel tool calls and compaction, and check that the question and final answer are both retained.

  Tip: Before forking large conversations, preserve important decisions in a short summary.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  CapabilityClaude Code

  Tool calls are no longer incorrectly rejected on some Windows volumes

  Fixed an issue where every tool call was rejected on some Windows volumes when native path lookup failed; working-directory checks now compare folder identity.

  Usage details

  Who can use it: Claude Code users who use custom or network volumes on Windows.

  How to use it: Update Claude Code to v2.1.317 and test working-directory validation by making a Read or shell call on the affected volume.

  Tip: On network volumes, track actual folder identity and permissions alongside path text.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  CapabilityClaude Code

  Long project paths no longer push the temporary directory past 260 characters on Windows

  Fixed an issue where scratchpad and temporary paths grew unnecessarily with the project path in sessions outside Claude Desktop, hitting the 260-character limit on Windows in long-path repositories.

  Usage details

  Who can use it: Users who open long-path repositories with Claude Code on Windows.

  How to use it: Open the long-path repository with the latest Claude Code and test scratchpad and temporary file creation.

  Tip: Cloning repositories to a short root path still improves compatibility with Windows tools.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  SettingClaude Code

  Unresponsive OTel proxies time out after 10 seconds

  Fixed an issue where OpenTelemetry exports could hang indefinitely behind an unresponsive proxy; the default timeout is 10 seconds, with a maximum of 30 seconds using `OTEL_EXPORTER_OTLP_TIMEOUT`.

  Usage details

  Who can use it: Claude Code environments using OTel through a proxy.

  How to use it: If needed, set `OTEL_EXPORTER_OTLP_TIMEOUT` to a value between 1 and 30 seconds and send a signal to the OTel endpoint.

  Tip: In production, measure proxy and collector latency and choose a shorter duration rather than using the 30-second maximum.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  CapabilityClaude Code

  Self-hosted session opens a new connection after an unanswered heartbeat

  When a heartbeat goes unanswered, the self-hosted session now recovers by opening new connections instead of trying every idle connection in sequence.

  Usage details

  Who can use it: Self-hosted runner sessions with intermittent connection drops.

  How to use it: Interrupt the heartbeat response and observe the session opening a new connection; review the runner and session logs together.

  Tip: Track heartbeat timeouts and server 5xx events as separate metrics to make root-cause analysis easier.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  Plugin / IntegrationClaude Code

  Warning for unintended connectors in new cloud tasks

  `/schedule` now warns when a connector is added to a new cloud scheduled task without the user requesting it, and explains how to remove it.

  Usage details

  Who can use it: Users of the Claude Code cloud scheduled task flow.

  How to use it: Create or edit a task with the `/schedule` command in Claude Code; check the summary screen for the connector warning and removal instructions.

  Tip: Review the connector list before saving a scheduled task to prevent unnecessary data access.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  CapabilityClaude Code

  An old interrupted tool call remains visible after moving to a new runner

  Fixed an issue where Claude would not see an interrupted tool call when a self-hosted runner session moved to a new runner, even if the call was older than the `CLAUDE_CODE_RESUME_INTERRUPTED_TURN_MAX_AGE_MS` limit.

  Usage details

  Who can use it: Self-hosted environments using runner migration and interrupted turn recovery settings.

  How to use it: Switch runners to resume an old interrupted turn and check that Claude sees the tool call as having an unknown outcome.

  Tip: Set the age limit for automatically resuming old turns according to your operational policy; re-verify unknown outcomes.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  SettingClaude Code Cloud

  New scheduled tasks use the organization’s default environment

  Fixed an issue where new scheduled tasks ignored the organization’s selected default environment and started with the Anthropic-hosted default instead.

  Usage details

  Who can use it: Claude Code cloud scheduled tasks with an organization default cloud environment configured.

  How to use it: Set the organization’s default environment in admin settings, then create a new `/schedule` task and verify the environment in the form.

  Tip: Check the environment name before saving the task to prevent production secrets from being moved into a test environment.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  AgentClaude Code

  Recreated teammates are no longer dropped from the team due to an old shutdown approval

  Fixed an issue where a recreated agent teammate was removed from its team because of an earlier shutdown approval.

  Usage details

  Who can use it: Claude Code agent team and teammate recreation flows.

  How to use it: Recreate a teammate and connect it to the team; check that team membership is retained even when an old shutdown approval exists.

  Tip: When recreating team members, track the new identity separately from the current lifecycle state.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  CapabilityClaude Code

  Timed-out Grep and Glob results are no longer treated as complete

  Fixed an issue where partial results were passed to Claude as complete when a Grep or Glob search hit its time limit.

  Usage details

  Who can use it: Large repositories using Claude Code Grep and Glob tools.

  How to use it: Run Grep or Glob in a large repository; if it times out, narrow the search, keeping in mind that the results are partial.

  Tip: Use path and file-type filters with broad patterns; don’t treat a partial search as definitive evidence.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  FeatureClaude Code

  `/feedback` no longer incorrectly asks for confirmation while submitting

  Fixed the `/feedback` screen showing `Enter to confirm` while a feedback report is being submitted.

  Usage details

  Who can use it: Users of the Claude Code feedback command.

  How to use it: Open `/feedback` and submit a report; watch the status text while it is being submitted and don’t press Enter a second time.

  Tip: Don’t close the terminal before submission completes; the updated status text indicates that the request is being processed.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  FeatureClaude Code Cloud

  `/schedule` results retain the next run time and link

  Fixed an issue where the task’s next run time and link were missing from the results after creating or updating a cloud scheduled task.

  Usage details

  Who can use it: Claude Code cloud scheduled task users.

  How to use it: Create or update a task with `/schedule`; open the next run time and task link in the command result.

  Tip: Save the result link in your task records for operational tracking; the link now takes you directly to the next run.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  CapabilityClaude Code

  `claude --from-pr` can find older sessions in projects with many sessions

  In projects with many sessions, `claude --from-pr` no longer incorrectly reports `No conversations found` when the linked session is older than the first page.

  Usage details

  Who can use it: Users reopening Claude Code conversations linked to GitHub PRs.

  How to use it: Update Claude Code and rerun `claude --from-pr <PR>` for the relevant PR.

  Tip: In very large projects, verify the PR-to-session match using the conversation title and branch name opened after running the command.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  SettingClaude Code

  Settings changes made at startup are applied immediately

  Fixed an issue where edits to settings files made in the first few seconds after Claude Code launched were applied only after a second change.

  Usage details

  Who can use it: Users who automate changes to Claude Code settings files at startup.

  How to use it: Update Claude Code, change the startup settings file, and open a new session; check that the behavior is applied on the first try.

  Tip: In startup scripts, leaving a short delay between writing the file and launching Claude Code can still reduce race conditions.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  FeatureClaude Code

  Exit resume hint preserves startup flags

  The `Resume this session with` hint shown on exit now repeats flags such as `--chrome` or `--debug` used to start the session, before `--resume`.

  Usage details

  Who can use it: Users who start Claude Code sessions with flags.

  How to use it: Start a session with a flag such as `claude --chrome`, then exit; copy the displayed resume command directly.

  Tip: When resuming complex sessions, copying the hint reduces the risk of forgetting required tool flags.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  SettingClaude Code Cloud

  The cloud environment management dialog now uses compact sections

  The organization environment dialog in admin settings now opens each section from a row, like personal dialogs, and prompts you before closing if there are unsaved entries.

  Usage details

  Who can use it: Organization administrators managing cloud session environments.

  How to use it: Open the organization environment dialog in admin settings; edit sections from their rows, then try closing it with unsaved changes.

  Tip: Read the save prompt carefully before closing; keep environment variables for production and testing in separate sections.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  FeatureClaude Code

  Cloud and SDK session titles no longer disappear when messages arrive concurrently

  Fixed a race condition that caused titles to disappear in cloud and SDK sessions if a new message or Stop arrived while the title was being generated.

  Usage details

  Who can use it: Claude Code cloud and SDK sessions.

  How to use it: Update the session; in a new session, send a message while the title is being generated and check that the title remains in the session history.

  Tip: For sessions that matter for search and automation, use `/rename` after the title is generated to give it a meaningful name.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  CapabilityClaude Code

  Reading an unchanged file again returns its content

  The `file unchanged since your last Read` placeholder has been removed from the Read tool; reading an unchanged file again returns its content.

  Usage details

  Who can use it: All sessions using the Claude Code Read tool.

  How to use it: Read the same file twice; check that the second call returns the file content instead of a placeholder.

  Tip: Requesting the same content again consumes tokens; call Read again only when you need the current content.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  CapabilityClaude Code

  Resumed session no longer repeatedly mentions a file change

  Fixed an issue where Claude repeated a previously acknowledged file change in resumed sessions.

  Usage details

  Who can use it: Claude Code sessions resumed with `/resume` or a saved transcript.

  How to use it: Resume the session, start a new turn in a project with a previously processed file change, and check that it doesn’t produce the warning again.

  Tip: When you need to confirm the current file state, get a Git diff; don’t rely solely on contextual memory.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  CapabilityClaude Code

  Resumed session can reuse a built-in tool

  Fixed an issue where a resumed session could not reuse a built-in tool after it had previously failed because it was disabled.

  Usage details

  Who can use it: Claude Code users who temporarily enable or disable built-in tools and resume sessions.

  How to use it: Run a turn while the tool is disabled, then enable it, resume with `/resume`, and check that the tool can be called again.

  Tip: Review tool permissions before resuming a session; verify the permissions of the re-enabled tool.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  CapabilityClaude Code

  Child processes of stopped shell commands no longer receive SIGTERM twice

  Fixed an issue where child processes of a stopped shell command could sometimes receive SIGTERM twice, causing programs to skip cleanup.

  Usage details

  Who can use it: Users who run long-running processes with the Claude Code shell tool.

  How to use it: Start a long-running shell command, stop it, and check in system monitoring that child processes are cleaned up with a single stop signal.

  Tip: Still design your commands to shut down safely at the application level after SIGTERM.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  CapabilityClaude Code

  Old transcripts are also cleaned up with custom setting sources

  Fixed an issue where old transcripts weren’t cleaned up in some runs using `--setting-sources`.

  Usage details

  Who can use it: Claude Code sessions using `--setting-sources` or similar setting sources.

  How to use it: Update Claude Code and start a session with `--setting-sources`; verify that old transcripts are cleaned up by monitoring the Claude directory.

  Tip: If you need a transcript archive, set up a separate archiving policy before relying on automatic cleanup.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  Plugin / IntegrationClaude Code Cloud

  A claude.ai connector in a matching plugin no longer asks for unnecessary authorization

  Fixed a misleading notification claiming that the claude.ai connector running in a cloud session needed reauthorization or had failed when a matching plugin contained the same server.

  Usage details

  Who can use it: Users of claude.ai connector and matching plugins in cloud sessions.

  How to use it: Match the plugin and use the connector in a cloud session; check that the authorization warning disappears when the server is already matched.

  Tip: Prefer a single source instead of adding the same MCP server as both a connector and a plugin.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  FeatureClaude Code

  Nested `claude -p` no longer sends its own title to the outer session

  Fixed an issue where a `claude -p` call inside a Cloud or self-hosted runner generated its own title and sent it to the outer session.

  Usage details

  Who can use it: Users running nested `claude -p` calls inside runner sessions.

  How to use it: Run the nested call and check the outer session history to confirm that only the outer session’s title stream remains.

  Tip: Instead of relying on automatic title generation, explicitly rename important outer sessions afterward.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  SettingClaude Code

  Explanation with the setting name shown when Remote Control is off

  When Remote Control is off, `/remote-control` no longer says `Unknown command`; it explains that the `disableRemoteControl` setting disables the feature.

  Usage details

  Who can use it: Claude Code installations using the `disableRemoteControl` setting.

  How to use it: Turn off Remote Control and run `/remote-control`; enable the feature by turning on the `disableRemoteControl` setting mentioned in the message.

  Tip: If your organization’s policy turns off Remote Control, show users an explanation of the setting and policy instead of a command.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  CapabilityClaude Code

  PDF metadata can no longer throw off page counts in Read and mentions

  Fixed an issue where a PDF’s own metadata caused the page count to be underestimated in Read and `@` mention operations.

  Usage details

  Who can use it: Users working with PDF files via the Claude Code Read tool or mentions.

  How to use it: Open a PDF containing metadata with the Read tool or attach it with `@`; check that all pages are counted.

  Tip: For very long PDFs, specify the page range explicitly to manage both accuracy and token usage.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  SettingClaude Code

  Exiting no longer prompts for background work approval when a plugin monitor is running

  Claude Code now skips the `Background work is running` confirmation when exiting while plugin monitors are running.

  Usage details

  Who can use it: Claude Code sessions using plugin monitors.

  How to use it: Exit Claude Code while a plugin monitor is running; observe the direct exit behavior instead of the usual background work confirmation.

  Tip: Manage the monitor’s lifecycle separately; skipping the exit confirmation may not automatically stop persistent monitoring.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  FeatureClaude Code

  The plugin-authoring skill suggests sharing after a module runs

  The built-in `plugin-authoring` skill offers once to help you share a module you created after it runs successfully.

  Usage details

  Who can use it: Developers using the `plugin-authoring` skill in Claude Code.

  How to use it: Create and run a module with `plugin-authoring`; after it succeeds, accept or dismiss the one-time sharing suggestion.

  Tip: Before sharing, check that the module contains no secret keys, internal company code, or sensitive connector information.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  FeatureClaude Code Remote Control

  Remote Control fork names now distinguish conflicts more clearly

  When the application doesn’t provide a fork name, the `(fork)` suffix is preserved for long names; a new fork from a `Name (fork)` session is named `Name (fork 2)`.

  Usage details

  Who can use it: `claude remote-control` and application-based Remote Control fork sessions.

  How to use it: Fork a Remote Control session; check the new name for long names and names that have already been forked.

  Tip: To distinguish sessions, explicitly rename them after forking to include the job or branch.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  FeatureClaude Code for VS Code

  The VS Code Account panel shows the plan name with correct capitalization

  Fixed an issue where the second word of the plan name appeared in lowercase in the VS Code Account panel.

  Usage details

  Who can use it: Claude Code for VS Code Account panel.

  How to use it: Open the Claude Account panel in VS Code and check that the plan name appears correctly.

  Tip: Don’t treat the displayed plan name as the sole proof of access issues; check model and organization access separately.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  SettingClaude Code for VS Code

  Increasing VS Code `chat.fontSize` also scales panel components

  Fixed an issue where attachment chips, menus, banners, and dialogs remained small when `chat.fontSize` was increased.

  Usage details

  Who can use it: Claude Code users who increase the `chat.fontSize` setting in VS Code.

  How to use it: Increase `chat.fontSize` in the VS Code `settings.json` file and check that all components in the Claude panel scale accordingly.

  Tip: For accessibility, increase the panel width as well as the text size to reduce wrapping in long prompts.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 03 Nov
  FeatureClaude Code for VS Code

  VS Code file links open in a separate editor group

  Fixed an issue where file links in the Claude tab opened over the chat; links now open in another editor group.

  Usage details

  Who can use it: Claude Code for VS Code chat panel.

  How to use it: Click a file link in Claude’s response and check that the file opens in a separate editor group without closing the chat.

  Tip: Use VS Code’s editor group layout to view code and chat side by side.

  ✓ Verified by official sourceSource: Claude Code v2.1.317 release notes
• 02 Nov
  APIClaude Platform

  Message Threads beta arrives in the Messages API for long sessions

  The Messages API now supports the Message Threads beta, which temporarily stores conversations on the server: the first request sends the full context, while subsequent requests send only new messages. Anthropic says median time to first token for 500,000–1 million-token requests is about 35 percent lower, but token costs and rate limits are unchanged.

  Usage details

  Who can use it: Claude API, Claude Platform on AWS, Anthropic-managed Claude Models on Google Cloud, and Microsoft Foundry; beta on all supported models. A thread ends after five minutes of inactivity and is deleted no later than one hour after its last use; the feature is not eligible for ZDR/HIPAA.

  How to use it: Add the `anthropic-beta: message-threads-2026-08-12` header to a Messages API request. In the first request, send `thread: {type: create}` and the full `messages`, `system`, and `tools`; in subsequent requests, send only new messages with `thread: {type: continue, previous_message_id: ...}`.

  Tip: Use threads in active, long-running agent loops; keep a fallback in your client that can reconstruct the full conversation, since a thread may expire after five minutes of inactivity.

  ✓ Verified by official sourceModels: Claude Opus 5.5Source: Make long-running agents faster with message threadsSource: Message threads documentationSource: Claude Platform release notes

New in this edition · 2

• 01 Nov
  APIOpenAI Python SDK

  OpenAI Python SDK 3.42.1 fixes WebSocket connections

  Version 3.42.1 includes fixes that preserve Responses WebSocket connection behavior and validate beta Realtime WebSocket authentication profiles. It also adds SDK-managed policy helpers for Responses.

  Usage details

  Who can use it: All developers using the OpenAI Python SDK, especially applications using Responses WebSocket and beta Realtime WebSocket.

  How to use it: Run `pip install --upgrade openai` in your virtual environment to update to 3.42.1, then rerun your WebSocket connection and authentication tests.

  Tip: Before deploying to production, test Responses and Realtime WebSocket scenarios in a staging environment to verify existing connection behavior.

  ✓ Verified by official sourceSource: openai-python v3.42.1 sürüm notları
• 01 Nov
  APIOpenAI Ruby SDK

  OpenAI Ruby SDK 0.115.1 fixes Ruby 3.3.0 compatibility

  Version 0.115.1 includes a dependency fix that prevents the use of `connection_pool` versions incompatible with Ruby 3.3.0.

  Usage details

  Who can use it: OpenAI Ruby SDK users, especially projects using Ruby 3.3.0.

  How to use it: Upgrade the SDK to 0.115.1 with `bundle update openai` or `gem update openai`, update the lockfile, and run your Ruby 3.3.0 tests.

  Tip: Pin your Ruby version and `connection_pool` dependency together in the CI matrix to catch dependency resolution issues early after the update.

  ✓ Verified by official sourceSource: openai-ruby v0.115.1 sürüm notları

New in this edition · 3

• 02 Nov
  APIMessenger Platform

  Messenger read and click notifications now go only to the sending app

  The marketing_message_reads and marketing_message_clicks notifications are now delivered to the app that sent the message; other apps subscribed to the same Page do not receive them. This changes event ownership in integrations that use multiple apps.

  Usage details

  Who can use it: Messenger marketing message integrations that use multiple apps for the same Page.

  How to use it: Update the relevant webhook subscription and event handler in the app that sent the message; reconfigure read and click logic in other apps so it does not rely on these notifications.

  Tip: If you have multiple apps, centralize event ownership in the sending app and write events to a shared data store to prevent duplicate or missing records caused by missed notifications.

  ✓ Verified by official sourceSource: Messenger Platform değişiklik günlüğü — Okundu ve tıklama bildirimleri yalnızca gönderen uygulamaya gider
• 02 Nov
  APIMessenger Platform

  marketing_message_tracking_id added to Messenger click notifications

  The Messenger marketing message click webhook now returns the marketing_message_tracking_id field. Matching this field to the same ID in the POST /act_<AD_ACCOUNT_ID>/messages response when sending the message lets you link the click to the send request.

  Usage details

  Who can use it: Developer apps that send Messenger marketing messages and use the marketing_message_clicks webhook.

  How to use it: Read the marketing_message_tracking_id field in the marketing_message_clicks webhook payload; store the ID from the send response and match it to the click event. No separate setting is specified.

  Tip: Store the ID in the send log alongside campaign and recipient context so you can reliably join click reports.

  ✓ Verified by official sourceSource: Messenger Platform değişiklik günlüğü — Tıklama bildirimlerinde izleme kimliği
• 02 Nov
  Plugin / IntegrationMeta VR Glasses

  The Hunger Games: Sunrise on the Reaping is coming to Meta VR Glasses in 3D

  Meta has partnered with Lionsgate to convert The Hunger Games: Sunrise on the Reaping into 3D. The film will be released in 3D theaters on November 20, 2026, and will also be available to watch in 3D on Meta VR Glasses starting in spring 2027.

  Usage details

  Who can use it: The 3D version for Meta VR Glasses is planned for spring 2027; the theatrical 3D release was announced for November 20, 2026.

  How to use it: No device settings are needed for now; buy a 3D ticket for the theatrical release. When it becomes available on Meta VR Glasses in spring 2027, check the film library for the 3D version of The Hunger Games: Sunrise on the Reaping.

  Tip: If you’re aiming for the 3D experience, plan your theater visit early; for the Meta VR Glasses version, check the library and purchase options separately at launch.

  ✓ Verified by official sourceSource: Meta’nın Lionsgate ile The Hunger Games: Sunrise on the Reaping 3D ortaklığı duyurusu

New in this edition · 5

• 02 Nov
  APIKimi Open Platform

  Kimi Open Platform launches Admin API for organization management

  Kimi Open Platform has launched the Admin API in beta, enabling verified organizations to programmatically manage members, invitations, projects, and inference API keys, and query billing, usage, and audit logs. The API is free and operates as a control plane; Admin API keys cannot be used for model inference calls.

  Usage details

  Who can use it: Kimi Open Platform organizations that have completed organization verification and organization administrators; beta.

  How to use it: Complete verification under Console → Organization → Organization Verification. Then create a key with the required scopes under Console → Organization → Admin API Keys; set the key as the MOONSHOT_ADMIN_KEY environment variable and send a request to the api.moonshot.ai/v1/admin/organizations endpoint with Bearer authorization.

  Tip: Grant only the scopes you need: org:write for write operations, billing:read for billing and usage, and audit:read for audit logs. Don’t confuse the Admin API key with the inference API key.

  ✓ Verified by official sourceSource: Admin API is now available on Kimi Open PlatformSource: Manage Your Organization with the Admin APISource: Admin API overview
• 02 Nov
  CapabilityKimi Code Desktop/Web

  Per-folder Git and PR status comes to multi-directory workspaces

  Kimi Code 2.5.0-canary now shows Git status, change statistics, file diffs, and PR information separately for each folder in multi-directory workspaces. Results and errors are distinguished for each folder in batch queries; draft PRs can now be returned with draft status.

  Usage details

  Who can use it: Multi-directory workspaces in Kimi Code Desktop and Web; normal single-directory behavior is unchanged.

  How to use it: Open a workspace containing multiple source folders in Kimi Code Desktop or Web, then open the Changes view in the session’s right panel; the panel loads Git and PR status separately for each root folder.

  Tip: Organize folders in the same workspace as separate repositories or subdirectories; if one folder has a Git error, the status of the other folders will still be shown.

  ✓ Verified by official sourceSource: @moonshot-ai/kimi-code@2.5.0-canary.20261102033430-40590f6Source: feat: support folder-scoped git statusSource: Interface Tour
• 02 Nov
  FeatureKimi Code

  Kimi Code combines the Skills catalogs of all workspace directories

  Kimi Code 2.5.0-canary now discovers, lists, and invokes Agent Skills from every configured source directory in a multi-directory workspace through a single catalog. Changes in directories are monitored and reloaded; for Skills with the same name, the primary directory and workspace order determine which one takes precedence.

  Usage details

  Who can use it: Multi-directory CLI, Desktop, Web, TUI, and SDK workspaces using the Kimi Code 2.5.0-canary preview.

  How to use it: Add top-level extra_skill_dirs = ["~/team-skills", ".agents/team-skills"] to the ~/.kimi-code/config.toml file, or add multiple source directories to the workspace; leave the merge_all_available_skills setting as true and start a new session. To invoke a Skill manually, use /skill:<skill-adı>.

  Tip: If you use Skills with the same name, arrange the primary working directory and workspace order deliberately; temporary directories added only to a session won’t appear in the shared catalog, so you need to register them as permanent source directories.

  ✓ Verified by official sourceSource: @moonshot-ai/kimi-code@2.5.0-canary.20261102033430-40590f6Source: feat: merge skills across workspace directoriesSource: Agent Skills
• 02 Nov
  OtherKimi Code ACP

  ACP client requests are queued while Kimi Code starts up

  Kimi Code 2.5.0-canary now holds ACP initialize and other requests received before the server is ready until startup completes. This means clients such as Zed receive the normal startup flow or the actual startup error instead of the spurious Internal error seen during early handshakes.

  Usage details

  Who can use it: Zed and other ACP clients connecting to the Kimi Code ACP server; 2.5.0-canary preview.

  How to use it: Upgrade to Kimi Code 2.5.0-canary.20261102033430-40590f6 and start the kimi acp command as usual; there’s no need to add a delay, even if the client sends its initialize request immediately after connecting.

  Tip: Before removing artificial waits or retries from your custom ACP client, log the startup error body; if the service fails to start, the original provider startup reason is now passed through.

  ✓ Verified by official sourceSource: @moonshot-ai/kimi-code@2.5.0-canary.20261102033430-40590f6Source: fix: queue ACP requests until startup completes
• 02 Nov
  OtherKimi Code

  Archived sessions are hidden from the session list immediately

  Kimi Code 2.5.0-canary fixes old session rows reappearing in the list during the brief interval between archiving and the session index being updated on disk. It also prevents stale or duplicate sessions from appearing in paginated lists.

  Usage details

  Who can use it: Kimi Code CLI, kimi web, and Desktop/Web session lists; 2.5.0-canary preview.

  How to use it: Upgrade Kimi Code to 2.5.0-canary.20261102033430-40590f6; after archiving a session, leave it in the normal session list—it should no longer appear, even before the index is written to disk.

  Tip: Use the archive filter to view archived conversations. Since brief inconsistencies between the normal list and archive list are no longer expected, automated listers should need less additional deduplication.

  ✓ Verified by official sourceSource: @moonshot-ai/kimi-code@2.5.0-canary.20261102033430-40590f6Source: fix(agent-core-v2): keep archived sessions out of session lists before the index flush

New in this edition · 2

• 02 Nov
  AvailabilityGrok Bot

  Grok Bot’s phone-calling feature is rolling out gradually to accounts

  An official @grok reply dated November 2 said that Grok Bot’s contact-calling flow was gradually rolling out to accounts using Grok Bot 0.77+ on the iOS app and desktop. The bot can call the requested contact, provide a live transcript during the call, and deliver a summary afterward; no additional add-on is required.

  Usage details

  Who can use it: iOS app and desktop Grok Bot 0.77+; account rollout is gradual, with plan and country availability unspecified.

  How to use it: Update Grok Bot on iOS or desktop to version 0.77+; once the feature is enabled on your account, write in the chat who to call and what you need.

  Tip: In one message, state the purpose of the call, the information to convey to the other person, and the desired outcome; after the live transcript, review the summary and actions taken.

  ✓ Verified by official sourceSource: Grok'un X yanıtı: telefon araması, canlı döküm ve özet
• 01 Nov
  Pricing / PlanGrok Bot

  Cost-related restriction reported on Grok Bot’s weekly usage quota

  On November 1, some Grok Bot users reported that their weekly usage percentage quickly reached 100% despite not using the service; TechCrunch and The Verge reported this as a restriction. Elon Musk confirmed that Grok Bot’s service costs were unsustainably high relative to revenue but did not disclose new quota figures or how much each plan was affected.

  Usage details

  Who can use it: Reported to affect the shared weekly usage pool on paid Grok/X Subscription plans; new limits by plan and country availability were not disclosed.

  How to use it: Open Settings → Usage in Grok Bot and check the remaining percentage, usage breakdown, and reset time; if needed, review top-up or higher-plan options.

  Tip: Spread heavy tasks across the week and track usage on this screen; Grok’s official account says heavy tasks consume the pool faster.

  ! UnverifiedSource: TechCrunch: Grok Bot limitlerinde maliyet kaynaklı kısıtlamaSource: The Verge: Grok Bot limitlerinde olası kısıtlamaSource: Elon Musk'ın X paylaşımı: Grok Bot maliyetleri gelire göre sürdürülemez

New in this edition · 26

• 02 Nov
  CapabilityQwen Code CLI

  Mods prompt.submit hooks now run in headless executions

  In headless -p and stream-json requests, Mods prompt.submit hooks can now modify the request, add hidden context, or drop the request before the model sees it. Failing hooks do not block the flow by default; terminal paths are out of scope for this release.

  Usage details

  Who can use it: Headless Qwen Code CLI runs; experimental.mods must be enabled and the relevant Mod must be installed.

  How to use it: Install the Mod with `qwen extensions install ./guard-mod --consent`, enable experimental.mods, and use `qwen -p 'prompt' --output-format json` or stream-json.

  Tip: Test a guard Mod that prevents credential leaks under an isolated HOME first.

  ✓ Verified by official sourceSource: Qwen Code v0.26.6 resmî sürüm notlarıSource: Headless prompt.submit kancaları değişikliğinin ayrıntıları
• 02 Nov
  Plugin / IntegrationQwen Code Web Shell

  The Web Shell GitHub Channel setting becomes a full GitHub form

  GitHub Channel configuration now offers a labeled checklist of notification reasons, an explicit choice between a token and local gh, and owner/repo validation. The repository allowlist uses case-insensitive matching, and custom message fields that are not specific to GitHub have been removed from the form.

  Usage details

  Who can use it: Administrators and developers using GitHub Channel in Web Shell; GitHub Enterprise base URLs are also supported.

  How to use it: Go to Settings → Channels → Configure GitHub; complete the Credentials, Connection, Notifications and routing, and Access control sections, then click Save.

  Tip: If you choose local gh authentication, check that the saved token will be removed; enter allowlist items directly in owner/repo format.

  ✓ Verified by official sourceSource: Qwen Code v0.26.6 resmî sürüm notlarıSource: GitHub Channel yapılandırması değişikliğinin ayrıntıları
• 02 Nov
  CapabilityQwen Code

  verify-pr rechecks in the same session retain --publish approval

  verify-pr rechecks in the same session now inherit the previous --publish approval. Users can publish ongoing verification rounds without repeatedly granting the same publishing permission.

  Usage details

  Who can use it: The same sessions using Qwen Code verify-pr workflows.

  How to use it: Run the first round with the ` /verify-pr --publish` command; when you start a recheck in the same session, it continues without asking for approval again.

  Tip: Do not use --publish in the first round if you do not want to generate a publishable report; approval is inherited for the session.

  ✓ Verified by official sourceSource: Qwen Code v0.26.6 resmî sürüm notları
• 02 Nov
  CapabilityQwen Code

  Experimental unifiedAgentLoop brings more ACP turns into the shared loop

  With experimental.unifiedAgentLoop enabled, channel prompts, Goal suggestion approvals, retry, continue, and ask_user_question restore turns run through a shared model turn and batched tool execution. This lets different ACP paths share the same stopping and budget rules.

  Usage details

  Who can use it: Qwen Code sessions using ACP; the feature is off by default and requires an experimental setting.

  How to use it: Set experimental.unifiedAgentLoop to true in your settings, then run a channel prompt, retry, continue, or question restoration flow through ACP.

  Tip: Run your parity tests before using this in production; behavior is unchanged when the setting is off.

  ✓ Verified by official sourceSource: Qwen Code v0.26.6 resmî sürüm notlarıSource: ACP ortak döngü kapsamı değişikliğinin ayrıntıları
• 02 Nov
  AvailabilityQwen Code Desktop

  Fedora 44 and RHEL 10 RPMs added to Desktop Linux packages

  In addition to existing Linux packages, Qwen Code Desktop releases RPM installers for x64 Fedora 44 and RHEL 10. This expands package-manager installation options on these distributions.

  Usage details

  Who can use it: x64 Linux desktop users running Fedora 44 and RHEL 10.

  How to use it: Download the RPM file for your operating system from the Qwen Code v0.26.6 GitHub Releases page and install it with `sudo dnf install ./dosya.rpm`.

  Tip: After installation, verify Desktop's daemon PATH setting and the package update channel.

  ✓ Verified by official sourceSource: Qwen Code v0.26.6 resmî sürüm notları
• 02 Nov
  CapabilityQwen Code Web Shell

  Goal approval text is sanitized for control and bidirectional characters

  Web Shell Goal approval text and edit diff file paths are now displayed with control and bidirectional Unicode characters escaped. This reduces the risk of misleading users through hidden directional or control characters in visible content.

  Usage details

  Who can use it: All sessions displaying Goal approvals and edit diffs in Web Shell.

  How to use it: Open a Goal or edit approval and check that the text and file paths are displayed using visible characters.

  Tip: Before approving, copy the file path and inspect its raw value too; the displayed text may differ from the actual path.

  ✓ Verified by official sourceSource: Qwen Code v0.26.6 resmî sürüm notları
• 02 Nov
  Plugin / IntegrationQwen Code Channels

  Channel users can approve their own one-time tool permissions

  Channel users can now send `/approve` or `/deny` for their own pending one-time tool permissions in the current attended turn. This lets them complete the permission decision through the channel without returning to the terminal.

  Usage details

  Who can use it: Users with attended turns through Qwen Code channel adapters.

  How to use it: When a pending one-time tool permission request arrives, send `/approve` or `/deny` in the same channel.

  Tip: Use these one-time commands when you want to approve only the current request rather than set a permanent permission policy.

  ✓ Verified by official sourceSource: Qwen Code v0.26.6 resmî sürüm notları
• 02 Nov
  AgentQwen Code Managed Agent

  Managed Agent recovery prevents filling gaps without evidence

  The Managed Agent recovery flow no longer fills in missing results without child ledger evidence, and more clearly distinguishes unknown and never-started states. This aims to reduce child tasks that incorrectly appear completed after recovery.

  Usage details

  Who can use it: Qwen Code Managed Agent recovery and failover flows.

  How to use it: Reload a Managed Agent session after an interruption; check the recovery summary to confirm that items without child ledger evidence were not filled in and that states are differentiated.

  Tip: Manually verify unknown states before delivering production output after automatic recovery.

  ✓ Verified by official sourceSource: Qwen Code v0.26.6 resmî sürüm notları
• 02 Nov
  AgentQwen Code Managed Agent

  Managed Agent upgrade uses the correct control plane endpoint

  The qwen-managed-agent-upgrade start and verify steps now reach the control plane and Hosted Harness using the endpoint configuration resolved by the server. This prevents upgrades from targeting the wrong endpoint in deployments with different endpoint configurations.

  Usage details

  Who can use it: Operators managing Managed Agent deployments with qwen-managed-agent-upgrade.

  How to use it: After loading the deployment configuration, run `qwen-managed-agent-upgrade start` and then `qwen-managed-agent-upgrade verify`.

  Tip: If you use multiple endpoints, confirm the server’s resolved endpoint value in the logs before start.

  ✓ Verified by official sourceSource: Qwen Code v0.26.6 resmî sürüm notları
• 02 Nov
  FeatureQwen Code Web Shell

  Managed Session list shows a localized Retry notification on error

  If the Managed Session list fails to load, Web Shell now displays a localized Retry notification and request details instead of an empty state. The error view appears below the Sessions and Archived tabs.

  Usage details

  Who can use it: Users of the Managed Sessions list in Web Shell.

  How to use it: Open the Managed Sessions view in Web Shell; if the list fails to load, click Retry and, if needed, use the reported request ID for support investigation.

  Tip: Check the Retry notification and request ID first to avoid mistaking a loading error for an empty list.

  ✓ Verified by official sourceSource: Qwen Code v0.26.6 resmî sürüm notları
• 02 Nov
  FeatureQwen Code Web Shell

  Token Usage panel shows success rates and colors by model

  The Web Shell Token Usage panel now includes the request success rate, number of failed requests, output speed, and model-level status indicators. When multiple models are used, it also shows a colored share bar and consistent model colors.

  Usage details

  Who can use it: All sessions using the Token Usage panel in Qwen Code Web Shell; it is also backward-compatible with older daemon versions.

  How to use it: Open a session in Web Shell, open the Session token usage panel, and view the Overview or By model section.

  Tip: When interpreting the success rate, keep in mind that retries are counted as separate requests.

  ✓ Verified by official sourceSource: Qwen Code v0.26.6 resmî sürüm notlarıSource: Token Usage başarı oranı ve renkleri değişikliğinin ayrıntıları
• 02 Nov
  CapabilityQwen Code Desktop

  Embedded runtime is automatically stopped before Windows updates

  The Windows installer now stops the embedded runtime before replacing files. This reduces the likelihood of an update failing because node.exe is locked.

  Usage details

  Who can use it: Users updating with the Qwen Code Desktop Windows installer.

  How to use it: Start the update from Desktop; the new installer automatically stops the runtime, replaces the files, and then restarts the app.

  Tip: If a separate Qwen Code runtime is running during the update, close it too; this reduces the chance of remaining file locks.

  ✓ Verified by official sourceSource: Qwen Code v0.26.6 resmî sürüm notları
• 02 Nov
  CapabilityQwen Code CLI

  Background shell notifications are linked to the turn that created them

  Background shell notifications are now associated with the turn that created them. This prevents notifications from being linked to the wrong message when multiple turns run concurrently.

  Usage details

  Who can use it: Qwen Code sessions that use background shell commands and concurrent turns.

  How to use it: Run a shell command in the background and track its completion notification in the corresponding turn.

  Tip: When using multiple background commands, check the turn link in the notification header to avoid acting on the result of the wrong command.

  ✓ Verified by official sourceSource: Qwen Code v0.26.6 resmî sürüm notları
• 02 Nov
  FeatureQwen Code Web Shell

  Capture cards use DejaVu fonts in the sandbox

  Capture cards in the sandbox environment now load DejaVu fonts for the intended monospace appearance. This makes lines in code and output cards easier to read.

  Usage details

  Who can use it: Qwen Code Web Shell workflows that generate sandbox capture cards.

  How to use it: Create a capture card in the sandbox environment and check the monospace alignment of code blocks.

  Tip: Use the same version of the sandbox image to rule out font differences when comparing visual output.

  ✓ Verified by official sourceSource: Qwen Code v0.26.6 resmî sürüm notları
• 02 Nov
  CapabilityQwen Code CLI

  Redirections in cd/pushd segments are now reported

  The CLI now reports redirections that occur within `cd` command segments. This makes the effects of shell redirection visible alongside changes to the working directory.

  Usage details

  Who can use it: All sessions using Qwen Code CLI shell commands.

  How to use it: Run a shell command containing `cd` or `pushd` in a session and inspect the redirect report in the command notification.

  Tip: If you are not expecting a file-writing redirection, use this new report to investigate unexpected changes to permissions or security rules.

  ✓ Verified by official sourceSource: Qwen Code v0.26.6 resmî sürüm notları
• 02 Nov
  CapabilityQwen Code Mods

  Unsupported Mod hooks no longer stop startup

  If a Mod manifest contains unsupported hooks such as prompt.paint or ui.place, Qwen Code now skips them without stopping startup. Users are warned about which hooks are unsupported.

  Usage details

  Who can use it: CLI, Web Shell, or related hosts using Qwen Code Mods; hooks the host does not support.

  How to use it: Load the Mod as usual; check the startup logs for warnings about unsupported hooks and rely only on hooks supported by the host.

  Tip: If a Mod’s critical behavior depends on an unsupported hook, monitor startup warnings in CI as failure signals to verify that it is not being silently skipped.

  ✓ Verified by official sourceSource: Qwen Code v0.26.6 resmî sürüm notları
• 02 Nov
  Plugin / IntegrationQwen Code MCP

  Typos in disabled MCP tool names now trigger warnings on every discovery

  MCP discovery flows now warn on every discovery path when disabled tool names contain typos. This makes it clear why a tool is missing not just on the first discovery, but on subsequent attempts as well.

  Usage details

  Who can use it: Qwen Code users with MCP servers and disabled tool configuration.

  How to use it: Add a tool to the disabled list in the MCP configuration, run discovery, and compare the tool name in the warning with your configuration.

  Tip: Copy tool names from the server’s actual discovery output; manually typed names are the most common cause of this warning.

  ✓ Verified by official sourceSource: Qwen Code v0.26.6 resmî sürüm notları
• 02 Nov
  CapabilityQwen Code

  Loop-protection reminder clears only when the request is accepted

  The Loop-protection reminder and related telemetry are now considered complete only when the model request carrying the reminder is actually accepted. Protection state is not cleared prematurely for failed or rejected requests.

  Usage details

  Who can use it: Qwen Code sessions using Loop-protection.

  How to use it: Create a recurring tool loop and, when the reminder appears, use the session logs to check whether the model request was accepted.

  Tip: If the request was rejected, assume protection is still active in the next turn; do not treat it as having been cleared early.

  ✓ Verified by official sourceSource: Qwen Code v0.26.6 resmî sürüm notları
• 02 Nov
  CapabilityQwen Code CLI

  AI attribution notes use the correct diff for git commit --amend

  For loosely written `git commit --amend` commands, AI attribution notes now generate a diff for the commit actually being amended instead of previous commits. This prevents the attribution record from being linked to the wrong set of changes.

  Usage details

  Who can use it: Qwen Code CLI users who enable AI attribution notes.

  How to use it: With attribution enabled, update a commit using `git commit --amend` or an equivalent loosely written command, then check that the generated note uses the diff for the amended commit.

  Tip: After amending, compare the attribution note with the output of `git show --stat HEAD`.

  ✓ Verified by official sourceSource: Qwen Code v0.26.6 resmî sürüm notları
• 02 Nov
  AvailabilityQwen Code Desktop

  Linux AppImage packages check for required dynamic libraries

  Linux AppImage builds now verify that required dynamic libraries are either included in the package or must be provided by the host. This makes missing libraries that prevent the app from launching more visible before installation.

  Usage details

  Who can use it: Users of Qwen Code Desktop Linux AppImage.

  How to use it: Download the new AppImage from GitHub Releases, run it, and if a missing-library notice appears at launch, install the libraries using your distribution’s package manager.

  Tip: Test launch on a clean Fedora/RHEL/Ubuntu image before deploying the AppImage to a production machine.

  ✓ Verified by official sourceSource: Qwen Code v0.26.6 resmî sürüm notları
• 02 Nov
  CapabilityQwen Code Managed Agent

  Managed Agent no longer leaves consumed child results pending

  The delivery status of consumed child results in Managed Agent no longer remains pending. This prevents results that have already been received from appearing as still pending in session state and the recovery screen.

  Usage details

  Who can use it: Sessions using Managed Agent child tasks and result delivery.

  How to use it: In a Managed Agent session, consume child task results and refresh the session state; check that delivered results are no longer pending.

  Tip: After recovery or reconnection, reprocess only records that remain pending.

  ✓ Verified by official sourceSource: Qwen Code v0.26.6 resmî sürüm notları
• 02 Nov
  FeatureQwen Code Web Shell

  Mobile Web Shell composer layout adapts to narrow screens

  On narrow screens, the Web Shell composer now aligns workspace controls, truncates long names, and centers the context-usage ring. This reduces input-field overflow and control clutter in the mobile view.

  Usage details

  Who can use it: People using Web Shell on a mobile device or in a narrow browser window.

  How to use it: Open Web Shell on a mobile device or at a narrow window width; check the workspace name, controls, and context-usage ring around the composer.

  Tip: Switch to a wider screen view when you need to see the full name to distinguish long workspace names.

  ✓ Verified by official sourceSource: Qwen Code v0.26.6 resmî sürüm notları
• 02 Nov
  CapabilityQwen Code

  verify report separates targeted gate results from round assertions

  The verify report now counts the results of the targeted gate test suite separately from the number of scripted assertions in the round. This ensures the assertion total reflects only the checks for that round.

  Usage details

  Who can use it: Qwen Code verify-pr reports and published verification comments.

  How to use it: Run a `/verify-pr` round and review the generated report’s separate fields for round assertions and targeted gate test-suite results.

  Tip: When assessing a round’s success, look not only at the total but also at the separate section for targeted gate results.

  ✓ Verified by official sourceSource: Qwen Code v0.26.6 resmî sürüm notları
• 02 Nov
  CapabilityQwen Code

  verify-pr correctly reports closed PR skips and suite counts

  Verify-pr counts each test suite run as one assertion and correctly handles skip notices on closed PRs. This prevents a verification round from being mistakenly rejected for having zero assertions.

  Usage details

  Who can use it: GitHub PR workflows using Qwen Code verify-pr, especially closed PRs and suite-level checks.

  How to use it: Run `/verify-pr` or the existing monitoring workflow on a PR; check that the report reflects one assertion per suite and the closed-PR skip notice results.

  Tip: When you want to review a closed PR again, treat the skip notice in the report as scope information, not as an error.

  ✓ Verified by official sourceSource: Qwen Code v0.26.6 resmî sürüm notları
• 02 Nov
  SettingQwen Code Web Shell

  Workflow mode is more visible in the composer + menu

  The Workflow mode toggle has moved from the composer toolbar to the composer’s + menu. Web Shell now shows the active mode as a dismissible chip, a warning when tools are unavailable, and a brief description in the + menu.

  Usage details

  Who can use it: Users whose sessions use the Workflow mode setting in Web Shell.

  How to use it: Open the + menu in the composer, then select Workflow mode; if it is active, turn it off using the displayed Workflow chip.

  Tip: In sessions where tools are unavailable, heed the warning on the chip and return to normal mode instead of forcing Workflow.

  ✓ Verified by official sourceSource: Qwen Code v0.26.6 resmî sürüm notları
• 01 Nov
  AgentQwen Code Managed Agent

  Managed Agent upgrade command handles interrupted installations more safely

  The check, backup, install, start, and verify stages of the Managed Agent upgrade command have been hardened to clean up and verify after interrupted installations. This reduces the risk of leftover temporary files and failed startup if an upgrade is interrupted.

  Usage details

  Who can use it: Operators upgrading the Qwen Code Managed Agent reference deployment.

  How to use it: First run the upgrade command’s check stage; then complete the start and verify steps and check the temporary upgrade directory after an interruption.

  Tip: Do not start a new upgrade without manually checking the temporary upgrade directory that may be left behind after SIGKILL.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 resmî sürüm notları

No notable change since the last edition.

New in this edition · 1

• 02 Nov
  AvailabilityGLM

  GLM-5.3 enters production at T-Systems Industrial AI Cloud in Munich

  Z.ai announced that GLM-5.3 is in production on T-Systems’ Industrial AI Cloud in Munich. The model is now available to European enterprise customers in Germany with local hosting and data sovereignty options.

  Usage details

  Who can use it: T-Systems AI Foundation Services users; in Germany on Industrial AI Cloud/T-Cloud Public, especially in Munich. The catalog lists Essential, Professional, and Agentic plans.

  How to use it: Get a trial key from the T-Systems API Key Portal (for production, use T-Cloud Marketplace); set OPENAI_BASE_URL to https://llm-server.llmhub.t-systems.net/v2 and send model: "GLM-5.3" in a /chat/completions request.

  Tip: For projects requiring data residency in Germany or the EU, verify T-Cloud hosting and the 1M context window; also compare GLM-5.3-Flash for lower cost or image input.

  ✓ Verified by official sourceModels: GLM-5.3Source: Carol Lin: GLM-5.3 T-Systems’in Münih ortamında üretimdeSource: Zixuan Li: Almanya’da egemen AI için GLM-5.3Source: T-Systems International: GLM 5.3 Industrial AI Cloud’da genel kullanıma açıldı