TOP 10 unchanged; Grok API adds watermarks to text outputs starting November 7

New in this edition · 6

• 31 Oct
  APIGemini CLI

  Gemini CLI nightly improves model selection and extension installation

  Version v0.67.0-nightly.20261031 preserves the selected model after a temporary fallback, cancellation, or rewind. It also respects .git/info/exclude and core.excludesFile rules in the shadow repo, locks concurrent extension installations, and recognizes the active/focus keys for custom themes.

  Usage details

  Who can use it: Only in the v0.67.0-nightly.20261031 preview release; there is no indication that it has been extended to the stable Gemini CLI release yet.

  How to use it: Update to the nightly release; select a model via /model and use the active and focus keys in your custom theme configuration.

  Tip: Test these nightly changes in a separate environment before deploying them to production, and pin the version tag in automated installations.

  ✓ Verified by official sourceSource: Gemini CLI v0.67.0-nightly.20261031 sürüm notları
• 30 Oct
  AvailabilityGemini Enterprise Agent Platform

  Computer use reaches GA on Enterprise Agent Platform with HITL safety governance

  Computer use is now generally available on Gemini Enterprise Agent Platform and includes comprehensive Human-in-the-Loop safety governance. Developers can configure and adjust specific approval policies when needed, while administrators can enforce organization-wide guardrails with configurableComputerUseToolSafetyPolicies.

  Usage details

  Who can use it: GA for Gemini Enterprise Agent Platform users; developer and administrator safety policies are available, especially for risky actions such as financial transactions and data modification.

  How to use it: Configure approval policies in your application that uses the Computer use tool; apply the configurableComputerUseToolSafetyPolicies constraint for organization-wide mandatory rules.

  Tip: Require approval for financial or destructive operations; use automatic approval only for low-risk, reversible actions.

  ✓ Verified by official sourceSource: Gemini Enterprise Agent Platform sürüm notları: Computer use tool GASource: Google Cloud sürüm notları: Gemini Enterprise Agent Platform Computer use GA
• 30 Oct
  FeatureGemini Enterprise Agent Platform

  Inference metadata logging reaches GA on Gemini Enterprise Agent Platform

  For each supported Gemini inference request, the platform can write a structured Cloud Logging record containing the model, region, token counts, Provisioned Throughput usage, latency, and error code. Records contain metadata only; prompt and response text are not logged.

  Usage details

  Who can use it: Generally available; can be used at the project or model/region level with Gemini models that use generateContent and streamGenerateContent, with Provisioned Throughput and supported pay-as-you-go options.

  How to use it: In Google Cloud Console, go to Provisioned Throughput > Metrics settings, turn on Enable detailed metrics, and save. Alternatively, in the REST API, set inferenceEventLoggingConfig.state to ENABLED in the setPublisherModelConfig call.

  Tip: Send custom header labels prefixed with x-goog-agent-platform-observability-label- to analyze costs and latency by team, application, or tenant.

  ✓ Verified by official sourceSource: Gemini Enterprise Agent Platform sürüm notları: Inference request metadata logging GASource: Inference request metadata logging’i etkinleştirme ve sorgulama
• 30 Oct
  APIGemini CLI

  `extensions validate` command added to Gemini CLI nightly

  Version v0.67.0-nightly.20261030 adds the `gemini extensions validate` command, which checks local extension configurations before installation or publication. The command checks path safety and file existence for gemini-extension.json, SemVer formatting, and MCP server transport/URL configurations; the 429 rate-limit wait time is also shown in the loading indicator.

  Usage details

  Who can use it: Only in the v0.67.0-nightly.20261030.gb633c0703 preview release; for Gemini CLI extension developers using the nightly channel.

  How to use it: Install the nightly release and run `gemini extensions validate <extension-path>`; fix any errors before installing or publishing the extension.

  Tip: Add validation as a CI step before publishing an extension to catch path traversal and invalid MCP definitions early.

  ✓ Verified by official sourceSource: Gemini CLI v0.67.0-nightly.20261030 sürüm notlarıSource: Gemini CLI `extensions validate` pull request’i
• 30 Oct
  Plugin / IntegrationGemini Enterprise

  S&P Global Adaptive Retrieval connector added to Gemini Enterprise

  The S&P Global - Adaptive Retrieval data store is now available in Gemini Enterprise as a Public Preview. Users can ask natural-language questions of S&P Global data agents they are authorized to access and get answers from company financials, filings, and earnings call transcripts.

  Usage details

  Who can use it: Public Preview; available only in the global, us, and eu locations. Access authorization for the relevant data agents in an S&P Global account is required.

  How to use it: Add an S&P Global - Adaptive Retrieval data store to an application in Gemini Enterprise and complete the official setup flow; then ask natural-language questions about data you are authorized to access.

  Tip: Narrow federated search results by clearly specifying the company name, period, and expected document type in your questions.

  ✓ Verified by official sourceSource: Gemini Enterprise sürüm notları: S&P Global - Adaptive Retrieval data storeSource: S&P Global - Adaptive Retrieval data store genel bakışı
• 30 Oct
  FeatureGemini Notebook Enterprise

  Gemini Notebook Enterprise gets a redesign, audio language selection, and summary customization

  The new interface design for Gemini Notebook Enterprise is now GA. New features include choosing an output language for audio overviews independently of the notebook language, previewing infographic styles, and changing the automatic notebook summary; Web and Fast Research have replaced the Discover sources option.

  Usage details

  Who can use it: Generally available in the Gemini Enterprise Standard, Plus, Pay-as-you-go, and Frontline editions.

  How to use it: In a notebook, select the audio language via Settings > Output language; change the summary via More options > Customize notebook. Review style examples when creating an infographic, and use the Web or Fast Research option for web research.

  Tip: Choose an audio overview language independently of the source language to create more accessible work notes for different teams.

  ✓ Verified by official sourceSource: Gemini Enterprise sürüm notları: Gemini Notebook Enterprise görsel yenilemesi

New in this edition · 32

• 31 Oct
  FeatureClaude Code

  Code Review results are now shown in a findings card

  In cloud and claude remote-control sessions, /code-review launched from Claude Desktop or the web Code tab now shows results in a findings card instead of a plain-text list.

  Usage details

  Who can use it: Claude Desktop and the web Code tab; cloud and Remote Control sessions.

  How to use it: Run /code-review in the Code tab; when the review is complete, select the findings card that appears.

  Tip: Verify findings one by one from the card; also open the relevant diff rather than relying only on the text summary.

  ✓ Verified by official sourceSource: Claude Code v2.1.316 GitHub sürüm notları
• 31 Oct
  FeatureClaude Code

  An exclusions badge was added to the Changes pane in Cloud sessions

  In Cloud sessions, the note indicating which files the Changes pane does not list is now shown as a badge next to the branch name, rather than as a separate line above the diff.

  Usage details

  Who can use it: Claude Code Cloud sessions.

  How to use it: Open the Changes pane in a Cloud session; the note appears in the badge next to the branch name.

  Tip: Check this badge when reviewing missing files or folders.

  ✓ Verified by official sourceSource: Claude Code v2.1.316 GitHub sürüm notları
• 30 Oct
  SettingClaude Code

  The /permissions tab has been renamed Recently blocked, and unreadable calls can’t be approved

  The former review tab in /permissions is now called Recently blocked. Calls that are entirely unreadable—for example, because they’re truncated when the terminal is too short—can no longer be approved from this screen.

  Usage details

  Who can use it: Claude Code’s /permissions interface.

  How to use it: Open /permissions and go to the Recently blocked tab; make the entire call visible before approving it.

  Tip: Enlarging the terminal or opening the call’s details helps prevent accidentally approving incomplete content.

  ✓ Verified by official sourceSource: Claude Code v2.1.314 GitHub sürüm notları
• 30 Oct
  SettingClaude Code

  /ultrareview checks workspace trust before running Git

  /ultrareview now checks whether the workspace is trusted before starting Git operations.

  Usage details

  Who can use it: Claude Code /ultrareview command.

  How to use it: Run /ultrareview in a trusted repository; in an untrusted folder, approve the workspace first.

  Tip: Before approving trust in an unfamiliar repository, inspect its Git hook and contents.

  ✓ Verified by official sourceSource: Claude Code v2.1.314 GitHub sürüm notları
• 30 Oct
  SettingClaude Code

  A subagent’s autoCompactWindow value can now reduce the global window

  A subagent’s autoCompactWindow setting can now reduce the global window set by CLAUDE_CODE_AUTO_COMPACT_WINDOW, but it can’t increase it.

  Usage details

  Who can use it: Claude Code subagents and automatic compaction settings.

  How to use it: Set the global upper limit with CLAUDE_CODE_AUTO_COMPACT_WINDOW; keep the subagent’s autoCompactWindow value below that limit.

  Tip: Use a wider window for demanding tasks and a narrower one for helper tasks to balance cost and context continuity.

  ✓ Verified by official sourceSource: Claude Code v2.1.314 GitHub sürüm notları
• 30 Oct
  CapabilityClaude Code

  Auto mode gives clearer notices for blocked calls

  Auto mode messages now state which command was blocked, that Claude can try again, and that a security check will be performed again; they also direct you to review /permissions.

  Usage details

  Who can use it: Claude Code Auto mode.

  How to use it: Wait for a call to be blocked in Auto mode; read the notice and follow the /permissions path if needed.

  Tip: Before trying again, review whether the command is really necessary and check the permission rule.

  ✓ Verified by official sourceSource: Claude Code v2.1.314 GitHub sürüm notları
• 30 Oct
  AvailabilityClaude Code

  Idle compaction expands to subscribers with telemetry disabled and additional providers

  Idle compaction now also works for subscribers with telemetry disabled. When one-hour prompt caching is enabled, it also covers Bedrock, Vertex, Foundry, and LLM gateway sessions.

  Usage details

  Who can use it: Claude Code subscribers; one-hour prompt caching must be enabled for Bedrock, Vertex, Foundry, and LLM gateway users.

  How to use it: Leave a conversation of over 200K idle; enable one-hour prompt caching with supported providers.

  Tip: In long sessions, monitor the cache duration and the context summary after compaction, and reconfirm critical instructions.

  ✓ Verified by official sourceSource: Claude Code v2.1.314 GitHub sürüm notları
• 30 Oct
  RetiredClaude Code

  The claude_code.safety_event OpenTelemetry event is no longer sent

  Claude Code has stopped sending the claude_code.safety_event OpenTelemetry event. Consumers relying on this event need to switch to new observability signals.

  Usage details

  Who can use it: Claude Code integrations using OpenTelemetry export.

  How to use it: Find claude_code.safety_event dependencies in your telemetry pipeline and stop treating the event that is no longer sent as required data.

  Tip: Do not flag the absence of this event as an error in schema or dashboard checks.

  ✓ Verified by official sourceSource: Claude Code v2.1.314 GitHub sürüm notları
• 30 Oct
  FeatureClaude Code

  A Bash editor with syntax highlighting is now available for the Cloud environment setup script

  The setup script field in Cloud environment settings now offers a Bash editor with syntax highlighting, line numbers, and a Copy button.

  Usage details

  Who can use it: Claude Code Cloud environment settings.

  How to use it: Open the setup script field in Cloud environment settings; edit the script or copy it using the Copy button.

  Tip: Use the line numbers to quickly find the step that caused an error before saving the setup script.

  ✓ Verified by official sourceSource: Claude Code v2.1.312 GitHub sürüm notları
• 30 Oct
  SettingClaude Code

  You can now select an effort level when choosing a model for Cloud routines

  An effort level has been added to the model picker when creating or editing a routine running in Cloud.

  Usage details

  Who can use it: Claude Code Cloud routines.

  How to use it: Create or edit a routine on the Cloud Routines page; select the effort level in the model picker.

  Tip: Choose low effort for regular, simple tasks and higher effort for uncertain or complex tasks.

  ✓ Verified by official sourceSource: Claude Code v2.1.314 GitHub sürüm notları
• 30 Oct
  CapabilityClaude Code

  Long headless and SDK runs using many subagents use less memory

  In long headless and SDK runs, the main session no longer holds subagents’ tool results until the end of the run. This reduces memory consumption in processes that run many subagents.

  Usage details

  Who can use it: Headless Claude Code and SDK sessions; especially jobs that run many subagents.

  How to use it: In headless mode, start a run with subagents using claude -p or the SDK; the change applies automatically.

  Tip: For large parallel jobs, still keep the number of subagents to what each task requires.

  ✓ Verified by official sourceSource: Claude Code v2.1.314 GitHub sürüm notları
• 30 Oct
  CapabilityClaude Code

  A hook that permits MCP calls in Cowork cloud Auto mode no longer counts as a response

  In Cowork cloud sessions, a hook permitting an MCP tool call is no longer treated as the final safety response by Auto mode. The classifier or permission prompt makes the decision.

  Usage details

  Who can use it: Auto mode and MCP tools in Cowork cloud sessions.

  How to use it: Start an MCP call in a Cowork cloud session with Auto mode; when needed, make the decision through the classifier or permission prompt.

  Tip: Use hooks only as a pre-filter; don’t assume the hook alone makes the safety decision.

  ✓ Verified by official sourceSource: Claude Code v2.1.314 GitHub sürüm notları
• 30 Oct
  Plugin / IntegrationClaude Code

  GitHub Enterprise connection test now also verifies the path used by Cloud sessions

  The GitHub Enterprise Test connection action in admin settings now also tests the second connection path used by Cloud sessions and warns if the second test fails.

  Usage details

  Who can use it: Admin settings for organizations using Claude Code Cloud sessions.

  How to use it: Open the GitHub Enterprise section in admin settings and click the Test connection button.

  Tip: Even if the first test succeeds, resolve the second connection warning before starting your Cloud session.

  ✓ Verified by official sourceSource: Claude Code v2.1.314 GitHub sürüm notları
• 30 Oct
  APIClaude Code

  Hook if conditions match Monitor commands like Bash patterns

  Hook if conditions such as Monitor(tail *) now match shell commands from the Monitor tool, similar to how Bash(tail *) patterns match Bash calls.

  Usage details

  Who can use it: Claude Code hook configurations and the Monitor tool.

  How to use it: Define an if condition such as Monitor(tail *) in your hook settings; Monitor shell calls will match this pattern.

  Tip: When adapting existing Bash patterns for Monitor, specify the tool name explicitly.

  ✓ Verified by official sourceSource: Claude Code v2.1.314 GitHub sürüm notları
• 30 Oct
  CapabilityClaude Code

  Flagged requests are retried with another model when eligible

  If ANTHROPIC_DEFAULT_OPUS_MODEL, availableModels, or deniedModels settings leave only an older Opus model or no models at all, a flagged request is now retried with another model instead of ending in an immediate refusal.

  Usage details

  Who can use it: Claude Code setups, especially those using organization model allow/deny lists or a default Opus model.

  How to use it: If you want to preserve the current behavior, set CLAUDE_CODE_DISABLE_REFUSAL_FALLBACK=1; otherwise, retries are enabled by default.

  Tip: When configuring model restrictions, leave at least one compatible fallback model on the allow list.

  ✓ Verified by official sourceSource: Claude Code v2.1.314 GitHub sürüm notları
• 30 Oct
  CapabilityClaude Code

  Model switching after a flagged message now covers custom model names too

  Claude Code now applies automatic model switching after a flagged message, even for unrecognized custom deployment names. To disable this behavior, use CLAUDE_CODE_DISABLE_REFUSAL_FALLBACK=1.

  Usage details

  Who can use it: Bedrock, Vertex, Foundry, or Mantle sessions using a custom deployment name.

  How to use it: Set CLAUDE_CODE_DISABLE_REFUSAL_FALLBACK=1 to disable automatic fallback; switching is enabled by default.

  Tip: Clearly document in your provider settings which model family your custom model names belong to.

  ✓ Verified by official sourceSource: Claude Code v2.1.314 GitHub sürüm notları
• 30 Oct
  SettingClaude Code

  Managed session behavior improved when MDM and remote settings conflict

  Differences in base URL or apiKeyHelper between MDM and remote settings are handled more consistently when signing in to claude.ai, Team, and Enterprise.

  Usage details

  Who can use it: Team and Enterprise organizations using MDM or remote settings.

  How to use it: Sign in with your organization account and start Claude Code; define base URL and apiKeyHelper values in your organization’s managed settings.

  Tip: Explicitly defining the same value in both MDM and remote settings makes troubleshooting easier.

  ✓ Verified by official sourceSource: Claude Code v2.1.314 GitHub sürüm notları
• 30 Oct
  APIClaude Code

  OpenTelemetry now reports the actual name of official plugin MCP servers

  The OpenTelemetry mcp_server.name field now reports fixed-URL remote MCP servers in official Anthropic marketplace plugins by their actual server name instead of custom.

  Usage details

  Who can use it: Installations using Claude Code OpenTelemetry and official marketplace MCP plugins.

  How to use it: Read the mcp_server.name field in OpenTelemetry output; no additional settings are required.

  Tip: Map old custom labels in observability dashboards to the new actual names.

  ✓ Verified by official sourceSource: Claude Code v2.1.314 GitHub sürüm notları
• 30 Oct
  APIClaude Code

  Per-session concurrency limits added for prompt and agent hooks

  Prompt and agent hooks, including subagents, now run at a maximum of 24 concurrently per session. Up to 12 additional jobs are held for events waiting beyond the timeout; timeout values under one second count as one second.

  Usage details

  Who can use it: Claude Code hook API; subagents are also included.

  How to use it: Check timeout values in hook definitions; plan for values under 1 second to be treated as at least 1 second.

  Tip: For jobs that use many hooks, design short, idempotent hooks to reduce queueing.

  ✓ Verified by official sourceSource: Claude Code v2.1.314 GitHub sürüm notları
• 30 Oct
  SettingClaude Code

  Short system prompt behavior clarified for unrecognized custom model names

  Claude Code uses a short system prompt for unrecognized model names on Bedrock, Vertex, Foundry, and Mantle. To retain the full prompt, set CLAUDE_CODE_SIMPLE_SYSTEM_PROMPT=0.

  Usage details

  Who can use it: Custom deployment names and inference profile ARNs from third-party providers such as Bedrock, Vertex, Foundry, and Mantle.

  How to use it: Set the CLAUDE_CODE_SIMPLE_SYSTEM_PROMPT=0 environment variable to use the full system prompt.

  Tip: If your custom deployment’s model family isn’t recognized correctly, test the short and full prompt behavior separately.

  ✓ Verified by official sourceSource: Claude Code v2.1.314 GitHub sürüm notları
• 30 Oct
  FeatureClaude Code

  /design-sync upload confirmation shows more detail about files to be sent

  The /design-sync upload prompt now clearly shows the folder, project, and files to be uploaded or deleted.

  Usage details

  Who can use it: The /design-sync workflow in Claude Code.

  How to use it: Run the /design-sync command; review the folder, project, and file list in the confirmation prompt.

  Tip: Check the list of files to be deleted especially carefully before confirming.

  ✓ Verified by official sourceSource: Claude Code v2.1.314 GitHub sürüm notları
• 30 Oct
  CapabilityClaude Code

  The Bash tool no longer passes inherited which functions to commands

  The Bash tool now cleans up inherited which alias or function definitions and doesn’t pass exported which or unsetenv functions to commands, so the system command or zsh builtin is used.

  Usage details

  Who can use it: Claude Code Bash tool; especially shell environments that use aliases or functions.

  How to use it: Run which with the Bash tool without any extra setup; the cleaned-up shell behavior is applied automatically.

  Tip: Test scripts that rely on custom which behavior in your environment against the system command behavior.

  ✓ Verified by official sourceSource: Claude Code v2.1.314 GitHub sürüm notları
• 30 Oct
  SettingClaude Code for VS Code

  The CFC prompt variable also stops Chrome instructions from being added to VS Code messages

  CLAUDE_CODE_DISABLE_CFC_PROMPT now also stops the VS Code extension from adding Claude in Chrome instructions to session messages. Browser tools remain available.

  Usage details

  Who can use it: Claude Code VS Code extension; browser tools remain available.

  How to use it: Set the CLAUDE_CODE_DISABLE_CFC_PROMPT environment variable before starting the VS Code extension.

  Tip: Use only this variable if you want to keep using browser tools while removing the automatic Chrome instructions.

  ✓ Verified by official sourceSource: Claude Code v2.1.314 GitHub sürüm notları
• 30 Oct
  FeatureClaude Code

  Cloud sessions started from the CLI get their session and branch names from the server

  Cloud sessions started from the CLI now get their session and branch names from the server instead of the local client.

  Usage details

  Who can use it: Cloud sessions started from the Claude Code CLI.

  How to use it: Start a Cloud session from the CLI; the session and branch names will appear with the values returned by the server.

  Tip: After renaming the local branch, check that its name in the Cloud session matches the server.

  ✓ Verified by official sourceSource: Claude Code v2.1.314 GitHub sürüm notları
• 30 Oct
  FeatureClaude Code

  Repository and environment lists are displayed as tables in Cloud session transcripts

  Repository and environment lists in Cloud session transcripts are now displayed as readable tables instead of single-line JSON; the rename row also clearly identifies the new title.

  Usage details

  Who can use it: Claude Code Cloud sessions.

  How to use it: Open a Cloud session and view the transcript; repository and environment details appear in table format.

  Tip: Use the table columns to compare long environment names; there’s no need to copy raw JSON.

  ✓ Verified by official sourceSource: Claude Code v2.1.314 GitHub sürüm notları
• 30 Oct
  FeatureClaude Code

  The repository-addition step for Cloud sessions now shows a summary table

  When Claude adds a repository to a Cloud session, opening the relevant step now shows a brief table of actions performed instead of raw JSON.

  Usage details

  Who can use it: Claude Code Cloud sessions.

  How to use it: Add a repository when creating a Cloud session; open the repository-addition step and review the summary table.

  Tip: When adding multiple repositories, check the table to verify the branch and repository pairings.

  ✓ Verified by official sourceSource: Claude Code v2.1.314 GitHub sürüm notları
• 30 Oct
  FeatureClaude Code

  Ctrl+R history search now finds text in collapsed pasted content

  When searching prompt history with Ctrl+R, text inside collapsed [Pasted text] sections is now included in the search.

  Usage details

  Who can use it: Claude Code terminal interface.

  How to use it: In a terminal session, press Ctrl+R and search for a phrase from previously pasted text.

  Tip: When reusing long logs or code blocks, search for a distinctive word.

  ✓ Verified by official sourceSource: Claude Code v2.1.314 GitHub sürüm notları
• 30 Oct
  SettingClaude Code

  FORCE_HYPERLINK environment variable fixed to disable links

  In addition to FORCE_HYPERLINK=false, the values no and off now disable terminal links; the previous inverse behavior has been changed.

  Usage details

  Who can use it: Claude Code terminal output.

  How to use it: Set FORCE_HYPERLINK=false, FORCE_HYPERLINK=no, or FORCE_HYPERLINK=off to disable links.

  Tip: Explicitly set this variable to prevent link escape sequences in CI or plain-text logs.

  ✓ Verified by official sourceSource: Claude Code v2.1.314 GitHub sürüm notları
• 30 Oct
  CapabilityClaude Code

  Claude Code gives better guidance when no GitHub remote is found

  If /ultrareview, cloud session, or cloud agent cannot find a GitHub remote, the message now suggests creating a repository via github.com/new; /ultrareview also no longer suggests an invalid gh command.

  Usage details

  Who can use it: Claude Code /ultrareview, cloud session, and cloud agent workflows.

  How to use it: Start the relevant workflow in a workspace without a remote; follow the notification’s suggested path to create a GitHub repository.

  Tip: Adding a remote before review ensures findings are written back to the correct repository.

  ✓ Verified by official sourceSource: Claude Code v2.1.316 GitHub sürüm notları
• 30 Oct
  FeatureClaude Code

  Session titles can now be generated automatically from skill- or prompt-based commands

  If a session starts with a skill or a prompt-based command such as /security-review, Claude Code now generates a title automatically from that starting point, so the session is no longer left untitled.

  Usage details

  Who can use it: Claude Code terminal and related session lists.

  How to use it: Start a new session with a skill or prompt-based slash command; a title will be created automatically.

  Tip: Choose short, descriptive starting commands to make sessions easier to find later.

  ✓ Verified by official sourceSource: Claude Code v2.1.314 GitHub sürüm notları
• 30 Oct
  OtherClaude Code

  SSL certificate errors now explain the likely cause and how to fix it

  For SSL certificate errors, Claude Code now identifies likely causes, such as a missing intermediate certificate, and recommends a fix for each cause.

  Usage details

  Who can use it: Claude Code network connections.

  How to use it: If you get an SSL error, follow the cause and resolution steps in the new error message.

  Tip: First check that the server is actually sending the intermediate certificate; don’t change the client certificate store at random.

  ✓ Verified by official sourceSource: Claude Code v2.1.316 GitHub sürüm notları
• 30 Oct
  FeatureClaude Code for VS Code

  The VS Code usage limit reset is now shown as a time

  The usage limit card in the VS Code extension now shows a time such as “Resets at 3:10 PM” instead of a generic reset message, and labels the window as 5-hour limit.

  Usage details

  Who can use it: Claude Code VS Code extension.

  How to use it: When you reach the usage limit, open the limit card in VS Code to see the reset time directly.

  Tip: Break long tasks into parts before the reset time.

  ✓ Verified by official sourceSource: Claude Code v2.1.314 GitHub sürüm notları

New in this edition · 15

• 31 Oct
  APIOpenAI Agents API

  Automatic action review and tool switching added to Agent sessions

  The `review` setting and session tools can now be specified when creating or updating an Agents API session. `auto_review` automatically reviews eligible actions; tools changed with `agent.tools` take effect on the next model call or, for built-in tools, the next turn.

  Usage details

  Who can use it: The Agents API beta; available with Python SDK 3.42.0 and Node SDK 7.46.0.

  How to use it: Use `review: "auto_review"` in a session request; when updating an existing session, send the `agent.tools` array to change its tools. Use `review: "none"` to turn off automatic review.

  Tip: Start with `auto_review` for actions with external effects, and add only the tools needed for new turns to the session.

  ✓ Verified by official sourceSource: OpenAI Python SDK v3.42.0 sürüm notlarıSource: OpenAI Node SDK v7.46.0 sürüm notlarıSource: OpenAI API Agents oturum ayarları değişikliği
• 31 Oct
  APIOpenAI Agents API

  Background context compaction is now configurable in the Agents API

  The Python and Node SDK versions dated October 31 added a setting for choosing how agent context is compacted. `compaction.async` uses background compaction by default; setting it to `false` runs compaction synchronously.

  Usage details

  Who can use it: Developers using the Agents API beta and OpenAI Python SDK 3.42.0 or Node SDK 7.46.0 and later.

  How to use it: Update the SDK; send `compaction: { async: true }` or `compaction: { async: false }` in an agent creation or update request. Leaving the field empty or setting it to null enables background compaction by default.

  Tip: For long sessions, `async: true` may reduce latency, but monitor usage metrics because background compaction may incur additional token usage.

  ✓ Verified by official sourceSource: OpenAI Python SDK v3.42.0 sürüm notlarıSource: OpenAI Node SDK v7.46.0 sürüm notlarıSource: OpenAI API: Agents yapılandırması
• 31 Oct
  APIOpenAI Python SDK

  Callable API keys are now scoped per request

  Python SDK 3.42.0 scopes keys to each request when using callable API keys. This prevents one request’s credentials from being carried over to another in calls made through the same client.

  Usage details

  Who can use it: API developers using OpenAI Python SDK 3.42.0.

  How to use it: Update the SDK with `pip install --upgrade openai`; pass the callable API key provider to the relevant request rather than making a persistent client-wide mutation, and test that each request uses the expected key.

  Tip: In multi-tenant applications, select keys in the request context and test for key leakage when sharing a client across users.

  ✓ Verified by official sourceSource: OpenAI Python SDK v3.42.0 sürüm notları
• 31 Oct
  CapabilityOpenAI Images API

  Transparent markup overlays can be used in Images API edits

  A transparent PNG markup overlay can be added to image editing requests to guide edits by placing it over the first image. The overlay must have the same dimensions as the first image and cannot be used with a mask.

  Usage details

  Who can use it: With OpenAI Python SDK 3.42.0 and Node SDK 7.46.0, in editing workflows supported by GPT Image 2.5 and 2.6.

  How to use it: Update the SDK and add a transparent PNG as the `markup` file in the image edit request; prepare the PNG with the same oriented dimensions as the first image and do not send a `mask` in the same request.

  Tip: Clearly mark only the area to be edited in the markup using semi-transparency; first test how the model interprets the overlay with a small sample image.

  ✓ Verified by official sourceModels: GPT Image 2.5, GPT Image 2.6Source: OpenAI Python SDK v3.42.0 sürüm notlarıSource: OpenAI Node SDK image markup değişikliğiSource: OpenAI API: Görüntü oluşturma ve düzenleme
• 31 Oct
  APIOpenAI API Administration

  External key management for AWS, GCP, and Azure added for organizations

  Organization external key records can be created, listed, retrieved, validated, and deleted. The API also supports filtering records by purpose and listing them with pagination.

  Usage details

  Who can use it: Organization administrators; projects with Admin API permissions for AWS, GCP, and Azure external keys.

  How to use it: Upgrade to Python SDK 3.42.0 or Node SDK 7.46.0 and start creating a record with `client.admin.organization.externalKeys.create(...)` in the Admin API client; use retrieve, list, validate, and delete calls for its lifecycle.

  Tip: Validate the provider configuration with a `validate` call before activating the key, and use the `purpose` filter in lists.

  ✓ Verified by official sourceSource: OpenAI Python SDK v3.42.0 sürüm notlarıSource: OpenAI Node SDK v7.46.0 sürüm notlarıSource: OpenAI API dış anahtar yönetimi değişikliği
• 31 Oct
  APIOpenAI Realtime API

  Realtime WebSocket delivery reporting and typing strengthened

  The Python and Node SDKs provide stronger typing for Realtime references and improve WebSocket delivery reporting and recovery. This makes it more reliable to track which session events belong to in voice applications and how state is maintained during connection drops.

  Usage details

  Who can use it: Realtime developers using OpenAI Python SDK 3.42.0 and Node SDK 7.46.0.

  How to use it: Update the SDKs and parse WebSocket events using the SDK’s typed Realtime event types; log delivery and reconnection status, and implement resynchronization for failed events.

  Tip: Persist each event’s session and event IDs in logs; after a network drop, first read the latest state from the server instead of blindly resending.

  ✓ Verified by official sourceSource: OpenAI Python SDK v3.42.0 sürüm notlarıSource: OpenAI Node SDK v7.46.0 sürüm notlarıSource: OpenAI API: Realtime başlangıç kılavuzu
• 31 Oct
  APIOpenAI Node SDK

  Hosted tool usage is reported in Responses output

  An optional `tool_usage` field, separate from model token usage, has been added to stable and beta Responses. It carries input/output token details for image generation, the number of billable requests for web search, and cache details if available.

  Usage details

  Who can use it: Developers using the stable or beta Responses API with Node SDK 7.46.0; responses where tool usage is available.

  How to use it: Update the Node SDK with `npm install openai@7.46.0` and read the `response.tool_usage` field on the Responses object; track `image_gen` and `web_search.num_requests` separately from the model’s `usage` field.

  Tip: For cost reconciliation, compare `tool_usage` values with billing records; do not assume a missing field means zero usage.

  ✓ Verified by official sourceSource: OpenAI Node SDK v7.46.0 sürüm notlarıSource: OpenAI Node SDK barındırılan araç kullanımı değişikliği
• 31 Oct
  CapabilityOpenAI Realtime API

  DTMF key sending and acknowledgment added for SIP connections

  SIP sideband connections can now send telephone key events with the `transport.dtmf.send` command, and successful sends produce a `transport.dtmf.sent` acknowledgment. Legacy notification types remain supported; the feature does not apply to WebRTC connections.

  Usage details

  Who can use it: OpenAI Realtime API SIP sideband connections only; WebRTC is not included.

  How to use it: Send the `transport.dtmf.send` command on the SIP sideband channel, optionally associating it with an event, and handle the corresponding `transport.dtmf.sent` event.

  Tip: In phone menu flows, keep a correlation ID for each key and don’t proceed to the next step until the `transport.dtmf.sent` acknowledgment arrives.

  ✓ Verified by official sourceSource: OpenAI Python SDK v3.42.0 sürüm notlarıSource: OpenAI Node SDK SIP DTMF değişikliğiSource: OpenAI Realtime API referansı
• 31 Oct
  APIOpenAI Agents API

  Agent sessions can be filtered by exact metadata matches

  Session listing calls now support metadata filters based on exact string matches. Filters can be combined with the existing agent filter and pagination; up to 16 key-value pairs are supported.

  Usage details

  Who can use it: The Agents API beta and Node SDK 7.46.0; new sessions or metadata updates may take time to appear in filter results.

  How to use it: List sessions with `client.beta.agents.sessions.list({ metadata: { team: "research" } })`; keep pagination and, if needed, the `agent_id` filter in the same request.

  Tip: Design metadata values as small, stable labels, and account for the fact that new updates may not appear in search results immediately.

  ✓ Verified by official sourceSource: OpenAI Node SDK v7.46.0 sürüm notlarıSource: OpenAI Agents oturum metadata filtresi değişikliği
• 31 Oct
  APIOpenAI Agents API

  Experimental time-awareness setting added to the Agents API

  The experimental `experimental.time_awareness` setting has been added to agent and session configurations. Enabled settings can be read in agent and session responses; partial updates preserve experimental fields that are not sent.

  Usage details

  Who can use it: Developers using the Agents API beta who accept experimental features; Python SDK 3.42.0 and Node SDK 7.46.0.

  How to use it: Send `experimental: { time_awareness: true }` in an agent creation, update, or session configuration; do not include unused experimental fields in the request, because existing settings are preserved.

  Tip: Because this is experimental, keep the setting behind a feature flag and verify outputs against the actual time for tasks involving time zones.

  ✓ Verified by official sourceSource: OpenAI Python SDK v3.42.0 sürüm notlarıSource: OpenAI Node SDK v7.46.0 sürüm notlarıSource: OpenAI Agents zaman farkındalığı değişikliği
• 31 Oct
  APIOpenAI Python SDK ve OpenAI Node SDK

  Responses text format and native output types updated

  The Python SDK has been updated to support native output types alongside Responses format updates; the Node SDK has also adapted Responses parsing to the latest text format. This makes it easier to consume new response formats without losing type information or relying on outdated parsing assumptions.

  Usage details

  Who can use it: Responses API developers using OpenAI Python SDK 3.42.0 and Node SDK 7.46.0.

  How to use it: Run `pip install --upgrade openai` or `npm install openai@7.46.0`; parse Responses outputs with the current SDK types and test any pinned assumptions about legacy text fields.

  Tip: Run contract tests with both standard and tool-using Responses outputs before deploying; don’t rely only on the plain-text field.

  ✓ Verified by official sourceSource: OpenAI Python SDK v3.42.0 sürüm notlarıSource: OpenAI Node SDK v7.46.0 sürüm notlarıSource: OpenAI API Responses referansı
• 31 Oct
  APIOpenAI Responses API

  Typed warmup support added for Responses WebSocket

  Node SDK 7.47.0 and Python SDK 3.42.0 add typed warmup support for preparing a Responses WebSocket connection in advance. The Python release also improves preservation of WebSocket cleanup cancellation.

  Usage details

  Who can use it: Responses WebSocket developers using OpenAI Node SDK 7.47.0 or Python SDK 3.42.0.

  How to use it: Update with `npm install openai@7.47.0` or `pip install --upgrade openai`, and use the SDK’s typed warmup support when opening a Responses WebSocket session; when closing the connection, wait for cleanup cancellation to complete.

  Tip: Warming up the connection before the first user request can reduce initial response latency; still add a fallback to the normal connection path if warmup fails.

  ✓ Verified by official sourceSource: OpenAI Node SDK v7.47.0 sürüm notlarıSource: OpenAI Python SDK v3.42.0 sürüm notları
• 30 Oct
  CapabilityChatGPT

  ChatGPT introduces stricter safety boundaries for violent content

  OpenAI said it will provide fewer potentially misusable details about past mass attacks, such as weapons, equipment, acquisition, and the scale of harm. Responses may be more conservative when warning signs of violence appear in recent conversations; conversations involving an obsession with violence may be ended automatically, and accounts may be temporarily paused in repeated cases.

  Usage details

  Who can use it: All ChatGPT users; protections will roll out gradually over the few weeks following the announcement.

  How to use it: There is no user-controlled setting; ChatGPT will apply these boundaries automatically as the rollout begins. For requests related to violence, ask about safe topics such as historical context, impacts on victims, warning signs, or prevention.

  Tip: Ask for a prevention and safe-response framing instead of weapon acquisition, setup, or attack details; this makes it more likely you’ll receive useful context.

  ✓ Verified by official sourceSource: OpenAI: Topluluk güvenlik raporu ve gençler için yeni korumalar
• 30 Oct
  CapabilityChatGPT for Teens

  Protections around weapons information and age prediction strengthened for teens

  ChatGPT further restricts practical, potentially misusable information about weapons and security systems for users placed in the under-18 experience. OpenAI has also strengthened its age prediction system to continually assess new usage signals; adults mistakenly placed in the teen experience can verify their age through Persona.

  Usage details

  Who can use it: Users under 18 covered by ChatGPT for Teens and consumer accounts predicted to belong to someone under 18; the new protections will roll out gradually over the next few weeks.

  How to use it: The protection is applied automatically. If an adult account is misclassified, start age verification through Persona in ChatGPT under Settings > Account.

  Tip: For teen users, link a parent account and review the existing parental controls and safety notifications together.

  ✓ Verified by official sourceSource: OpenAI: Topluluk güvenlik raporu ve gençler için yeni korumalarSource: OpenAI: ChatGPT for TeensSource: OpenAI: Yaş tahminine yaklaşımımız
• 30 Oct
  SettingOpenAI crawler controls

  A shared AI training preference signal to be supported for websites

  OpenAI announced that it will follow a shared signal that lets websites use robots.txt to tell multiple AI providers at once whether their content may be used to train foundation models. Implementation details will be shared in the coming months; existing OAI-SearchBot and GPTBot controls remain in effect.

  Usage details

  Who can use it: For publishers and website owners; OpenAI’s implementation of the new signal is not live yet and is planned for the coming months.

  How to use it: For now, continue managing OAI-SearchBot and GPTBot rules separately in robots.txt; there is no step to enable the new shared signal until OpenAI publishes the implementation syntax.

  Tip: Don’t confuse visibility in ChatGPT search with preferences for training use; maintain separate rules for OAI-SearchBot and GPTBot.

  ✓ Verified by official sourceSource: OpenAI: Web sitelerinin AI eğitim tercihlerini belirtmesini kolaylaştırmakSource: OpenAI API: Crawler genel görünümü

New in this edition · 5

• 31 Oct
  RetiredFacebook Insights / Meta Business Suite

  Reach metric reportedly being removed from Facebook analytics

  A secondary report says Meta will remove the Reach metric from Facebook analytics starting October 31, 2026, and make Viewers the primary unique audience metric. Meta’s current Help Center page highlights Views, Content interactions, and Follows in Insights, but I could not find an official announcement confirming this dated removal.

  Usage details

  Who can use it: Users tracking Facebook Page and creator analytics through Meta Business Suite; the affected reporting surfaces may vary by account and content type.

  How to use it: Go to Meta Business Suite > relevant Facebook Page > Insights and check for Views, Viewers, or Unique Viewers fields in place of Reach. In external reporting dashboards, map legacy Reach fields to the new metrics.

  Tip: Export historical Reach data and date ranges; don’t compare Viewers or Views directly with Reach as if they were the same series.

  ! UnverifiedSource: Facebook Reach metriğinin 31 Ekim’de sona ereceği haberiSource: Meta Business Suite masaüstünde Insights açıklaması
• 31 Oct
  AvailabilityRay-Ban Meta AI glasses

  Authorized retail launch of Ray-Ban Meta announced in the Philippines

  Manila Bulletin reported that Meta is preparing the first authorized retail launch of Ray-Ban Meta (Gen 3) and camera-free Ray-Ban Meta Audio models in the Philippines; Vision Express has also teased the products. The report did not announce a sale date or price, and Muse will not be available at launch. The Philippines is not on Meta’s official list of supported countries, so there is no official confirmation.

  Usage details

  Who can use it: Philippines; an authorized retail launch is planned, but no exact sale date or price has been announced. According to the secondary report, Muse will not be available at launch.

  How to use it: For now, the Philippines is not on Meta’s list of supported countries, so don’t assume orders are available through the official Meta Store; wait for an announcement from Vision Express and Meta about the local launch.

  Tip: Before buying on the grey market, verify regional warranty, firmware, Meta AI, Muse, and live translation support.

  ! UnverifiedModels: Ray-Ban Meta (Gen 3), Ray-Ban Meta AudioSource: Ray-Ban Meta AI glasses Filipinler’e geliyorSource: Meta AI glasses desteklenen ülkeler
• 30 Oct
  RetiredMeta Advantage+ catalog ads

  Frames being removed from Advantage+ catalog ads and replaced with Image templates

  Meta announced that the Frames option, which adds borders to product images, will no longer be available after October 30, 2026, and will be replaced by Image templates. The new templates can combine product images, catalog fields, logos or images, text, stickers, and background layers.

  Usage details

  Who can use it: Advertisers using Advantage+ catalog ads; Image templates are created for each catalog in Commerce Manager and applied to single image or carousel ads in Ads Manager.

  How to use it: Create a template via Commerce Manager > Catalog > Image templates > + Create. In Ads Manager, select it via Sales campaign > Product data > Ad > Products from your catalog > Ad creative > Image template > Choose template.

  Tip: Prepare templates in 1:1, 4:5, and 9:16 ratios; turn off Background generation and Dynamic overlays if they aren’t needed to prevent conflicts.

  ✓ Verified by official sourceSource: Frames yerine Image templates duyurusu ve kullanım adımlarıSource: Image templates oluşturma ve reklama uygulama rehberi
• 30 Oct
  APIMeta Business Agent

  Meta Business Agent UI skills can send video messages

  Meta Business Agent added the component_type=video value for UI skills. The agent can now send customers a video message with an optional caption, using an HTTPS video URL or an uploaded media ID; existing video UI skills are also listed.

  Usage details

  Who can use it: WhatsApp Business phone numbers using the Meta Business Agent API; integrations that can provide a video URL or uploaded video ID.

  How to use it: Use an Authorization Bearer token and X-API-Version: 2.0.0 in a POST https://api.facebook.com/{entity_id}/agent-ui-skills request. In the JSON body, send component_type=video, status=enabled, title, and an instruction specifying the video’s HTTPS URL or media ID. Captions must be no longer than 1,024 characters.

  Tip: Prefer an accessible HTTPS MP4/3GPP URL; check the expiration period for uploaded media IDs and the 16 MB video limit.

  ✓ Verified by official sourceSource: Meta Business Agent changelog, 30 Ekim 2026Source: Meta Business Agent UI Skills API referansıSource: Meta Business Agent etkileşimli mesajlar rehberi
• 30 Oct
  APIThreads API

  Self-disclosure label for AI content added to the Threads API

  Meta added support for disclosing AI-generated content in text, image, video, and carousel posts created with the Threads API. When is_made_with_ai=true is sent while creating a media container, an AI info label appears on the published post; for carousels, the parameter must be used on the parent container.

  Usage details

  Who can use it: Apps using the Threads API with the threads_content_publish permission and required access; text, image, video, and carousel posts.

  How to use it: Add is_made_with_ai=true when creating a media container in a POST /{threads-user-id}/threads request. For carousels, use the parameter on the parent container with media_type=CAROUSEL; then publish the creation_id through the existing POST /{threads-user-id}/threads_publish flow.

  Tip: Clearly label AI-assisted creations; use the parameter on the parent container rather than setting it to true on carousel child containers.

  ✓ Verified by official sourceSource: Threads API changelog, 30 Ekim 2026Source: Threads gönderileri: Label AI-Generated Content

New in this edition · 2

• 30 Oct
  AvailabilityKimi Work

  3D Make is now available in the Kimi Work desktop app

  Moonshot’s official announcement dated October 30 said that 3D Make is available in Kimi Work as well as Kimi.ai. This makes it possible to use workflows for creating models, scenes, and games by connecting to Blender and CAD tools within Kimi Work; this is an additional desktop availability detail alongside the known web/Kimi app access.

  Usage details

  Who can use it: Kimi Work desktop users; the official product page lists Windows and macOS (Apple silicon) versions. The announcement does not specify any country or membership plan restrictions.

  How to use it: Open Kimi Work and enter Work mode, then describe your 3D goal in natural language. For local Blender, CAD, or game engine workflows, install the relevant 3D plugin from the Plugins section in Work and submit your request.

  Tip: Clearly specify the reference image, dimensions, and expected output type in your first prompt; then add detail through multi-turn editing.

  ✓ Verified by official sourceModels: Kimi K3.1 ProSource: Kimi.ai on X: Introducing 3D Make in KimiSource: How to Create Better 3D Projects with KimiSource: Kimi 3D Make: Feature Guide
• 30 Oct
  OtherKimi Code CLI ve Desktop

  Built-in prompts optimized in Kimi Code CLI and Desktop

  The October 30 release notes for Kimi Code CLI 2.4.1 and Kimi Code Desktop 1.2.1 say that the built-in prompts have been optimized. The official notes do not explain the scope or measurement of the optimization.

  Usage details

  Who can use it: Kimi Code CLI 2.4.1 and Kimi Code Desktop 1.2.1 users; no platform or plan restrictions specified.

  How to use it: Update Kimi Code CLI to 2.4.1 or Kimi Code Desktop to 1.2.1; no additional setting or command is required for this change.

  Tip: Since Moonshot has not published any measurements, record the outputs of a few repeatable tasks before updating and compare the behavior afterward.

  ✓ Verified by official sourceSource: Kimi Code CLI değişiklik günlüğüSource: Kimi Code Desktop değişiklik günlüğü

New in this edition · 1

• 31 Oct
  CapabilityGrok API

  Output Watermarking enabled by default for Grok API text responses

  Starting November 7, 2026, xAI will add an invisible statistical watermark to the text output of seven supported Grok models. The feature will be enabled by default across all API endpoints, including the Responses API and Chat Completions API; the request format is unchanged, and you can check the response’s watermark status in the x-watermark header.

  Usage details

  Who can use it: Starting November 7, 2026, across all xAI API endpoints, including global https://api.x.ai and regional endpoints, for the seven listed text models. Team admins can disable it per model in Console, though some models may be locked for the team.

  How to use it: No code changes are required. Read the x-watermark header in a Responses API or Chat Completions response; a value of true indicates that a watermark was applied. To disable it, open Team settings > Model output watermarking in Console, deselect the relevant models using the settings icon, click Save, and then confirm the Opt Out step; changes apply to new requests within approximately 5 minutes.

  Tip: Store the x-watermark header with the request ID and model in your compliance records; don’t assume the opt-out status is the same across different teams or models.

  ✓ Verified by official sourceModels: grok-4.7, grok-4.6, grok-4.5, grok-4.3, grok-4.20-reasoning, grok-4.20-non-reasoning, grok-4.20-multi-agentSource: Output Watermarking | SpaceXSI Docs

New in this edition · 38

• 01 Nov
  CapabilityQwen Code /autofix-pr

  /autofix-pr allows up to three pushes for failing checks

  If the same check is still failing after three fix pushes, `autofix-pr` marks it as requiring human intervention instead of sending it back to the agent. This entry appears in `/autofix-pr status`, while watch continues monitoring the other checks.

  Usage details

  Who can use it: Qwen Code PR watch/autofix-pr; up to three failed fix pushes per check.

  How to use it: Run `/autofix-pr status`; fix the issue manually for a check awaiting human intervention, or reset the entry with a new successful head.

  Tip: When a check fails for the third time, don’t repeat the same fix approach; review the logs and CI configuration as a human.

  ✓ Verified by official sourceSource: Qwen Code autofix retry-budget PRSource: Qwen Code v0.26.5 release notes
• 01 Nov
  FeatureQwen Code /autofix-pr

  A shared-work mode using --in-place has been added for /autofix-pr

  In a clean checkout on the PR head branch, `/autofix-pr <n> --in-place` now runs the agent in the foreground in the user’s own working tree, with an approval flow. At the end of the run, the agent pushes the branch and responds to the PR using the user’s identity; it stops on a dirty or diverged checkout and asks the user to decide what to do.

  Usage details

  Who can use it: Qwen Code CLI; a clean checkout on or behind the PR head that tracks a named remote; single-run, supervised use.

  How to use it: Start a session in the root checkout of the PR head branch and run `/autofix-pr <PR-number> --in-place`; `--every`, scheduled, and headless use are not supported in this mode.

  Tip: Commit or stash your own changes before the agent starts; this mode explicitly notes that it can also push the user’s commits.

  ✓ Verified by official sourceSource: Qwen Code --in-place co-driving PRSource: Qwen Code v0.26.5 release notes
• 01 Nov
  APIQwen Code CLI

  CLI update can target an exact version without npm discovery

  On standalone installations, `qwen update --target-version <version>` downloads, verifies, and installs a specific version without discovering releases through npm. A `v` prefix, reinstalling the same version, and downgrades are supported; the pinned version preference is not persistent.

  Usage details

  Who can use it: Standalone Qwen Code CLI installations; access to the selected release archive is required, including in environments without npm registry access.

  How to use it: Run `qwen update --target-version 0.26.5`; set `QWEN_UPDATE_BASE_URL` if you need a custom archive root. For a persistent older version, set automatic updates to `general.enableAutoUpdate: false`.

  Tip: For production deployments, pin the target version only after testing checksum verification and the rollback archive.

  ✓ Verified by official sourceSource: Qwen Code exact-version update PRSource: Qwen Code v0.26.5 release notes
• 01 Nov
  FeatureQwen Code Generated UI

  Interactive card values are carried into the next message as context

  After a value change in a card remains stable for about 800 ms, it is retained as a removable tag above the Web Shell composer, and the next question receives the current values. The built-in card’s “Continue analysis with current parameters” action now sends the tagged reference directly without opening a review window.

  Usage details

  Who can use it: Web Shell sessions using Generated UI; only when the card is visible, active, and linked to the same session.

  How to use it: Change a card value, wait for the tag to appear, and then ask your question; remove the tag above the composer if you don’t want it. To continue from the card, click “Continue analysis with current parameters.”

  Tip: Keep the tag to carry the card’s latest parameters into a calculation question instead of re-entering the individual values.

  ✓ Verified by official sourceSource: Generated UI chat continuity and default-on PRSource: Qwen Code v0.26.5 release notes
• 01 Nov
  AvailabilityQwen Code Generated UI

  Generated UI enabled by default in the stable release

  With Qwen Code v0.26.5, Generated UI is now enabled by default in Web Shell without requiring configuration. This expands access from the previous nightly default to the stable release; MCP Apps views aren’t available in terminal, headless, or channel sessions.

  Usage details

  Who can use it: Qwen Code v0.26.5 Web Shell and Desktop; supported trusted workspaces. Can be disabled with `experimental.generatedUi: false`.

  How to use it: Open Web Shell in a new session without adding any settings; to restore the previous behavior, set `experimental.generatedUi` to `false` in settings.json and restart the session.

  Tip: If a view can’t be created in untrusted workspaces, use the text fallback; the default behavior doesn’t generate unnecessary warnings in this case.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notesSource: Generated UI chat continuity and default-on PR
• 01 Nov
  AvailabilityQwen Code Managed Agent

  Experimental one-command Helm installation arrives for Managed Agent

  The Managed Agent control plane gains an experimental Helm installation with a Hosted Harness and persistent MySQL working together. The package also includes optional trusted single-node LOCAL operation and an authenticated gateway that exposes only the Managed interface.

  Usage details

  Who can use it: Experimental Kubernetes deployment; signed Managed Agent, Hosted Harness, MySQL, and authenticated gateway components.

  How to use it: Choose the experimental Helm path in the Qwen Code Managed Agent deployment documentation; provide image, model configuration, and persistent MySQL values, and set the gateway credentials.

  Tip: Before deploying to production, test that the gateway rejects ordinary daemon paths and verify credential and database protection after uninstalling.

  ✓ Verified by official sourceSource: Qwen Code experimental Kubernetes deployment PRSource: Qwen Code v0.26.5 release notes
• 01 Nov
  CapabilityQwen Code Managed WebShell

  Managed WebShell now paginates upward through live messages

  Managed WebShell now reads the latest 100 live items directly and loads older messages by paginating upward. Live updates continue during pagination.

  Usage details

  Who can use it: Managed WebShell sessions; the latest 100 live items in the initial view, with upward scrolling for older history.

  How to use it: Open a Managed WebShell session and scroll up in the message list; older records are added as they load, while new messages appear in the live stream.

  Tip: To quickly reach a section in a long history, scroll up first to load an older page, then return to the live stream.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notesSource: Qwen Code Desktop v0.26.5 release notes
• 01 Nov
  Plugin / IntegrationQwen Code QQ botu

  Opt-in group moderation tools added to QQ bot

  Channel adapters can now expose their own tools to agent sessions; the QQ bot is the first to use this, adding 18 moderation tools, including recall, mute/unmute, kick, blacklist, group info, and join request review. The tools are enabled with the `moderationTools` key, which is off by default.

  Usage details

  Who can use it: Qwen Code QQ group channels; operations that require the bot to be a group admin and `moderationTools` to be explicitly enabled by the operator.

  How to use it: Set `moderationTools: true` in the QQ channel configuration; run the bot as a group admin and call `qq_recall_message`, `qq_set_mute`, `qq_kick_member`, or the relevant tool in the channel session.

  Tip: Test in a separate group before enabling destructive operations; enable the key only when needed to preserve the safe default.

  ✓ Verified by official sourceSource: Qwen Code channel tools and QQ moderation PRSource: Qwen Code v0.26.5 release notes
• 01 Nov
  SettingQwen Code Workflow

  Session Workflow switch added to Web Shell and VS Code

  Web Shell, split pane, and modern VS Code chat can now change a saved session’s Workflow preference using a separate switch. The change takes effect in the next new round without interrupting the response.

  Usage details

  Who can use it: Supported Web Shell sessions, split pane, and modern VS Code chat; new chats show only an informational placeholder.

  How to use it: Turn the Workflow switch in the composer toolbar of a supported session on or off; the preference takes effect in a new message round.

  Tip: To avoid interrupting a long-running response, change the switch while the current response is in progress and expect it to take effect in the next round.

  ✓ Verified by official sourceSource: Qwen Code session Workflow controls PRSource: Qwen Code v0.26.5 release notes
• 01 Nov
  FeatureQwen Code /verify-pr

  /verify-pr reuses a clean PR working tree

  The local `/verify-pr` flow reuses the current working tree only if it is a clean checkout of the PR head. Details of verification rounds are also recorded.

  Usage details

  Who can use it: Local `/verify-pr` flow in the Qwen Code CLI; requires a clean checkout matching the PR head.

  How to use it: Run `/verify-pr` from the root checkout of the PR head branch; if the branch is clean and matches the PR head, the existing tree is used; otherwise, the flow requires new preparation.

  Tip: Clean the working tree with `git status` before verification; do not expect local changes to be reset automatically.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notes
• 01 Nov
  FeatureQwen Code /verify-pr

  /verify-pr rounds keep reports and comments separate

  Each `/verify` round now updates only its own status comment; the latest round is published, and the verdict line is validated as a plain paragraph. This prevents comments from previous rounds from being overwritten accidentally.

  Usage details

  Who can use it: Qwen Code GitHub `/verify-pr` publishing flow.

  How to use it: Run multiple verification rounds and check each round’s separate status in the PR comments; use the latest report as the source of truth.

  Tip: Compare rounds by their IDs instead of deleting old comments; use the latest published round to make a decision.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notes
• 01 Nov
  FeatureQwen Code

  Export and restore actions are now visible directly on archived conversations

  Archived conversations in Settings now show Export conversation and Restore actions inline, next to the More menu. This reduces the number of menu steps required to manage archives.

  Usage details

  Who can use it: Qwen Code Settings > Archived conversations.

  How to use it: Open Settings, go to Archived conversations, and click Export conversation or Restore on the relevant row.

  Tip: Export conversations you plan to keep for a long time before archiving them to simplify the list.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notes
• 01 Nov
  FeatureQwen Code /autofix-pr

  A blocked autofix run leaves an explanatory comment on the PR

  When an `autofix-pr` run is blocked, it now posts a comment on the PR explaining what was attempted, what blocked it, and what human action is needed. This keeps pending work from being recorded only in a local state file.

  Usage details

  Who can use it: GitHub PRs using Qwen Code PR watch/autofix-pr.

  How to use it: Check the `/autofix-pr` status or PR comments, and complete the human action specified in the comment created for the blocked run.

  Tip: Resolve the stated blocker before closing the comment; start a new run with a new head instead of blindly rerunning the same one.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notes
• 01 Nov
  CapabilityQwen Code CLI

  Context Usage separates instruction files from auto memory

  The CLI’s context usage view now shows instruction files separately from automatic memory. This makes it clearer how much each type of file contributes to the context.

  Usage details

  Who can use it: Qwen Code CLI `/context` and the Context Usage view.

  How to use it: Run `/context` during a session and review the instruction files and auto memory sections separately.

  Tip: When approaching the context limit, reduce large instruction files first, then auto memory content.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notes
• 01 Nov
  FeatureQwen Code

  Memory files can be previewed from the Context Usage panel

  Context memory files in the Context Usage panel can now be clicked to open a read-only preview of files such as AGENTS.md. Users can directly inspect which files contribute to the context.

  Usage details

  Who can use it: Qwen Code CLI/Web Shell Context Usage panel; only memory files included in the context.

  How to use it: Open the Context Usage panel, click a memory file row, and inspect the read-only preview that opens.

  Tip: When context consumption rises, use this preview to identify large files first.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notes
• 01 Nov
  CapabilityQwen Code CUA

  CUA SDK session and window operations aligned with v0.27.0

  The CUA SDK, Browser SDK, and Node REPL in Qwen Code v0.26.5 align their login, window selection, and session cleanup behavior with CUA Driver v0.27.0. The goal is more reliable computer-use sessions.

  Usage details

  Who can use it: Qwen Code CUA integration, Browser SDK, and Node REPL; with CUA Driver v0.27.0.

  How to use it: Upgrade Qwen Code to v0.26.5 and CUA Driver packages to v0.27.0; restart existing CUA sessions.

  Tip: After upgrading CUA, verify the window selection and session-closing flow with a quick test on your operating system.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notesSource: Qwen Code releases list with CUA Driver v0.27.0
• 01 Nov
  FeatureQwen Code Web Shell

  One-click daemon updates support pnpm, yarn, and bun

  Web Shell’s one-click daemon update now also covers pnpm, yarn, bun, and sudo-prefixed npm installations. If automatic updating isn’t possible, the interface shows the steps to apply manually.

  Usage details

  Who can use it: Web Shell daemon update flow; users whose installation method is pnpm, yarn, bun, or sudo npm.

  How to use it: Open the daemon update prompt in Web Shell and select the one-click update; if the automatic route isn’t suitable, run the manual commands shown.

  Tip: If the daemon is installed outside the system PATH, use the manual route suggested by the interface; don’t run a random npm global update.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notes
• 01 Nov
  FeatureQwen Code

  The status bar shows the number of running background agents

  Web Shell and Qwen Code Desktop show the number of active agents in the task capsule in the status bar while background agents are running. This lets you see which sessions are still working without opening them.

  Usage details

  Who can use it: Qwen Code Web Shell and Desktop; sessions with running background agents.

  How to use it: Start multiple background agents and watch the task capsule in the status bar; the count updates as the running agents change.

  Tip: Don’t close the app until the count in the capsule reaches zero; use this indicator to quickly track long-running tasks.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notes
• 01 Nov
  SettingQwen Code OpenTUI

  Native extension commands require approval before installation

  In OpenTUI, native extension commands now require user approval before being installed directly. Replacing or unmounting an extension cancels pending approval requests.

  Usage details

  Who can use it: Qwen Code’s OpenTUI interface and native extension commands.

  How to use it: When a native extension command requests installation, review the approval prompt and explicitly accept it; if you replace or unmount the extension, restart the pending request.

  Tip: Don’t approve native extension commands whose source you don’t recognize; this approval boundary prevents direct execution.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notes
• 01 Nov
  CapabilityQwen Code PR watch

  PR watch merges a stale base before attempting a fix

  When a CI failure may be caused by the branch being behind its base, PR watch now merges the stale base before starting a fix. This reduces the risk of triggering an unnecessary fix cycle.

  Usage details

  Who can use it: Qwen Code PR watch and autofix-pr flows.

  How to use it: Run PR watch as usual; if the branch is behind, the flow applies the stale base merge step before attempting a fix.

  Tip: Ensuring the PR is synchronized with the base before an automatic fix helps reduce unrelated merge conflicts.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notes
• 01 Nov
  CapabilityQwen Code /verify-pr

  Sandboxed /verify-pr checks artifacts before publishing

  The publisher for `/verify-pr` inside the sandbox now runs the artifact check itself. If the check cannot run or fails, the verification round is marked inconclusive.

  Usage details

  Who can use it: Qwen Code sandboxed `/verify-pr` publishing flow.

  How to use it: Run `/verify-pr` and inspect the artifact check result in the published report; if the round is inconclusive, fix the missing artifact and start a new round.

  Tip: Do not treat the verification result as successful until the artifact check passes.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notes
• 01 Nov
  APIQwen Code SDK

  Bulk live session snapshots for 20 workspaces arrive in the SDK

  A new batch request and SDK method retrieve the live session status of up to 20 selected workspaces in a single call. This reduces the need for separate requests in multi-workspace monitoring clients.

  Usage details

  Who can use it: Qwen Code SDK and Managed/serve live sessions; up to 20 selected workspaces in a single batch call.

  How to use it: Call the live-session snapshot batch method in the SDK and send up to 20 workspace IDs; combine the returned snapshots in a single view.

  Tip: Split larger workspace sets into groups of 20 and use live updates instead of polling at short intervals.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notes
• 01 Nov
  FeatureQwen Code Web Shell

  Keyboard shortcuts added for Session Overview and Split View

  The `Cmd/Ctrl+Shift+O` shortcut to open Session Overview and the `Cmd/Ctrl+\` shortcut to open Split View have been added to Web Shell. The shortcuts also work in Qwen Code Desktop and standalone `qwen serve` web mode.

  Usage details

  Who can use it: Qwen Code Web Shell, Desktop, and standalone `qwen serve`; disabled when a dialog is open or focus is in an embedded terminal.

  How to use it: With a session open, press `Cmd+Shift+O` or `Cmd+\` on macOS, or `Ctrl+Shift+O` or `Ctrl+\` on Windows/Linux.

  Tip: Even if your keyboard layout is not QWERTY, the physical key mapping is preserved, so press the specified physical key rather than the corresponding character.

  ✓ Verified by official sourceSource: Qwen Code view-navigation hotkeys PRSource: Qwen Code v0.26.5 release notes
• 01 Nov
  CapabilityQwen Code code-review skill

  Built-in code-review skill handles head drift and actionlint

  The built-in code-review skill realigns after a PR head changes, runs actionlint checks, reports blockers, and stops rejected retries. This reduces the chance of automated review continuing against the wrong head.

  Usage details

  Who can use it: Qwen Code’s built-in code-review skill and PR review workflows.

  How to use it: Run the code-review skill as usual; if the PR head changes, realignment and actionlint steps run automatically against the new head.

  Tip: For CI configuration changes, check the actionlint result separately before making a review decision.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notes
• 01 Nov
  CapabilityQwen Code

  Built-in reasoning effort recognizes new Qwen prefixes

  Qwen Code’s built-in reasoning effort selection now covers DeepSeek-V4 and new Qwen model prefixes. When the user provides an explicit effort value, that preference continues to override automatic detection.

  Usage details

  Who can use it: Qwen Code model providers; DeepSeek-V4 and new Qwen model names.

  How to use it: Select the model and leave reasoning effort on automatic; if you need specific behavior, provide an explicit effort value in the provider settings.

  Tip: If a new model name isn’t recognized automatically, use an explicit reasoning effort and check the values supported by the provider.

  ✓ Verified by official sourceModels: DeepSeek-V4Source: Qwen Code v0.26.5 release notes
• 01 Nov
  CapabilityQwen Code

  Context files already loaded are no longer imported into memory again

  Qwen Code skips files already loaded as context files during memory import. This reduces unnecessary context consumption from duplicate content.

  Usage details

  Who can use it: Qwen Code context and auto memory loading flows.

  How to use it: Load files through both context and memory in a session; the tool automatically skips duplicate files.

  Tip: Keep the same file in a single source instead of manually adding it through two different mechanisms.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notes
• 01 Nov
  FeatureQwen Code CLI

  /context displays token counts of one million or more more readably

  `/context` now displays token counts of one million or more in millions in terminal, plain-text, and OpenTUI views. Large context usage is quicker to read.

  Usage details

  Who can use it: Qwen Code CLI `/context`, plain-text, and OpenTUI views.

  How to use it: Run `/context` during a session and read token counts above one million in M.

  Tip: Don’t confuse the million-based display with the total limit; check the remaining context and model limit together.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notes
• 01 Nov
  FeatureQwen Code Web Shell

  Long lines in tool diffs wrap vertically

  Diffs in Web Shell tool cards now wrap long lines in long comments or file paths instead of requiring horizontal scrolling on each line. Reviewing large diffs requires less horizontal navigation.

  Usage details

  Who can use it: Qwen Code Web Shell tool-card diff views.

  How to use it: Open a tool diff with long lines and read the wrapped text in the card’s vertical scrolling area.

  Tip: Hover over a line to see the full file path; even in the wrapped view, check all blocks before approving.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notes
• 01 Nov
  CapabilityQwen Code Managed Agent

  Startup probe distinguishes broker write failures from incorrect topic types

  The Managed Agent startup probe now reports broker write failures separately from incorrect topic types. The error message provides clearer fail-fast guidance and a mqadmin remediation path.

  Usage details

  Who can use it: Qwen Code Managed Agent startup and broker connection diagnostics.

  How to use it: Start the Managed Agent; if the probe fails, apply a fix with mqadmin based on whether the error indicates a broker write failure or an incorrect topic type.

  Tip: Don’t treat the two errors as the same network issue; for a topic type error, verify the topic definition first.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notes
• 01 Nov
  CapabilityQwen Code

  Memory writes report skipped directories and scan limits

  Memory writes now report skipped index entries separately from items skipped due to scan capacity, while preserving example filenames and warnings. The diagnostic output makes it clearer why memory is incomplete.

  Usage details

  Who can use it: Qwen Code auto memory write and diagnostic flows.

  How to use it: After a memory write, inspect the CLI output or relevant log; evaluate omitted index and scan-cap warnings separately.

  Tip: If an expected file wasn’t added to memory, check the scan-cap warning first, then narrow the scope and write again.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notes
• 01 Nov
  FeatureQwen Code Web Shell

  Empty No-workspace section is now hidden in the sidebar

  Web Shell doesn’t show the No-workspace sessions section in the sidebar when it loads empty. This behavior is now consistent with the empty state of the Pinned section.

  Usage details

  Who can use it: Qwen Code Web Shell; empty No-workspace sessions catalog.

  How to use it: Open Web Shell; if the section is empty, it’s hidden automatically and reappears when a no-workspace session is created.

  Tip: Use the + Add session action instead of waiting for the section to appear to add a new session.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notes
• 01 Nov
  AvailabilityQwen Code Web Shell

  Goal card and dialog localized in Russian

  Russian localization has been added for Web Shell’s Goal card and Goals dialog. Untranslated strings fall back to English.

  Usage details

  Who can use it: Qwen Code Web Shell’s Russian interface; English fallback for missing translations.

  How to use it: Set the Web Shell language to Russian and start a Goal session; the Goal card and Goals dialog will appear in Russian.

  Tip: If you see a missing string, the feature remains usable; complete the command using the English fallback text.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notes
• 01 Nov
  FeatureQwen Code Web Shell

  The + Add session action remains clickable when the catalog is empty

  Web Shell keeps the `+ Add session` action clickable even when the session catalog is empty. The empty-state screen does not prevent you from starting a new session.

  Usage details

  Who can use it: An empty session catalog in Qwen Code Web Shell.

  How to use it: When the catalog is empty, click `+ Add session` in the sidebar or in the empty state.

  Tip: You don’t need to wait for the section to fill up to start your first session; use the action in the empty state.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notes
• 01 Nov
  FeatureQwen Code Web Shell

  The No-workspace header is now aligned with other session sections

  The No-workspace sessions header now uses the same height, spacing, arrow, muted text, and hover/focus behavior as the Pinned, Workspaces, and Recent sections.

  Usage details

  Who can use it: Qwen Code Web Shell session sidebar.

  How to use it: Open the Web Shell sidebar; the No-workspace sessions section uses the same interaction pattern as the other section headers.

  Tip: If the header isn’t visible, expect it to appear only once a session exists, due to the change that hides empty sections.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notes
• 01 Nov
  FeatureQwen Code

  Session messages explain safe-mode and missing peer states more clearly

  Session messaging now explains separately when messages are suppressed by safe-mode and when a peer address is missing. It no longer gives users the impression that the recipient is unavailable.

  Usage details

  Who can use it: Qwen Code inter-session messaging and peer connections.

  How to use it: Send a session message; check the explanation shown when it doesn’t reach the recipient and the safe-mode status.

  Tip: If a message doesn’t appear, check for safe-mode suppression first, then check the peer address configuration.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notes
• 01 Nov
  FeatureQwen Code Web Shell

  Skill slash commands retain argument hints while typing

  Argument hints for skill slash commands remain visible while typing. As the user enters arguments, the hint narrows to show only the missing arguments.

  Usage details

  Who can use it: Skill slash commands in Qwen Code Web Shell.

  How to use it: Start typing a skill slash command and enter the arguments in order; the remaining required arguments are shown in the composer.

  Tip: Fill in the missing arguments shown in the hint; follow the suggested order rather than entering a long description before completing the command.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notes
• 01 Nov
  FeatureQwen Code Web Shell

  Nested scrollbars removed from long tool approvals

  The floating card opened for tool approval in Web Shell now uses a single scroll area for long diffs. Long lines and changes are easier to scroll through.

  Usage details

  Who can use it: Web Shell tool approval cards, especially for operations that display long diffs.

  How to use it: For a tool call with a long diff, open the approval card and use the single scroll area.

  Tip: Review the entire diff in the single scroll area before approving.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 release notes
• 30 Oct
  AvailabilityDataGuard for Agent

  DataGuard for Agent available free in public preview

  Alibaba Cloud is offering DataGuard for Agent, its AI-powered database security solution, free in public preview. It can inspect supported agent inputs, tool calls, outputs, and sessions; in Guard mode, it can block supported high-risk operations.

  Usage details

  Who can use it: Alibaba Cloud AI workflows; public preview is free, but supported products, regions, and environments vary by feature.

  How to use it: Open Alibaba Cloud’s AI-powered database security solution, select DataGuard for Agent, and configure monitoring in Observe mode first, followed by intervention in Guard mode if needed.

  Tip: First measure normal agent behavior in Observe mode and filter out false positives; enable the blocking policy only afterward.

  ✓ Verified by official sourceSource: Alibaba Cloud’un AI-powered database security yazısıSource: Alibaba Cloud AI-powered database security çözümü

New in this edition · 2

• 31 Oct
  Agentdsh-superagent

  dsh-superagent research prototype released for DeepSeek Harness

  DeepSeek Harness Team released the dsh-superagent research prototype under the MIT license. It proactively handles tasks in a single GitHub repository, running permitted requests in its own session and working directory and relaying results to the source conversation, for example as a pull request. The README specifically notes that it is neither production-ready nor an official DeepSeek product.

  Usage details

  Who can use it: Publicly available on GitHub; can be run from a GitHub repository as a DeepSeek Harness bundle and can listen for GitHub events and optional Feishu chats. This is research/reference code and should not be considered production-ready.

  How to use it: Clone the repository and ask the coding agent in the DeepSeek Harness environment: `Read SETUP.md in this repository and set up dsh-superagent with me.` During setup, select only GitHub or Feishu as the source, specify the `owner/name` repository to work on and a separate agent account, keep the allowlist narrow, and run setup after approving the plan. SETUP.md requires Node.js 22.19+ or 24+, pnpm, git 2.32+, tmux, Python 3.8+, GitHub CLI 2.48+, DSH, and a model provider.

  Tip: For your first test, use SETUP.md's default `observe` acceptance mode, a separate GitHub account, and keep automatic merging disabled. Do not expand to a live repository until you have verified the permissions and agent output.

  ✓ Verified by official sourceSource: GitHub resmî deposu: dsh-superagent-prototypeSource: GitHub resmî ilk commit: dsh-superagent araştırma prototipiSource: GitHub resmî kurulum talimatı: SETUP.md
• 30 Oct
  FeatureDeepSeek Harness

  DeepSeek Harness rc.5 improves how thinking content is displayed in conversations

  DeepSeek Harness v0.2.1-rc.5 released a UI update that improves how thinking content is displayed in conversations. The official release notes do not mention any other features or settings for this release.

  Usage details

  Who can use it: Users who upgrade to the DeepSeek Harness v0.2.1-rc.5 prerelease; conversation view.

  How to use it: Upgrade DeepSeek Harness to v0.2.1-rc.5 or later and open a conversation; the improvement noted in the release notes applies to how thinking content appears in the conversation. The release notes do not mention any additional setting or command that needs to be enabled.

  Tip: When reviewing long thinking responses, start with the new display in this release; when needed for debugging, save the response's thinking sections together with the conversation context.

  ✓ Verified by official sourceSource: GitHub resmî sürüm notu: DeepSeek Harness v0.2.1-rc.5Source: Freedom.Tech: DeepSeek Harness 0.2.1-rc.5

No notable change since the last edition.