TOP 10 unchanged; 84 changes to Claude Code, Qoder Lite at $10 a month

New in this edition · 7

• 03 Nov
  SettingGemini for Education

  Gemini products will be off by default for K-12 student accounts until an administrator enables them

  Google announced that access to Gemini, Gemini Notebook, Gemini in Classroom, and Google Search will be off by default for K-12 student accounts. These products will not be available to student accounts unless a school administrator explicitly enables them; rollout details will be shared in the coming months.

  Usage details

  Who can use it: K-12 student accounts and school administrators; the effective date has not yet been finalized.

  How to use it: When the rollout begins, school administrators must explicitly enable each AI product in the admin controls; Google has not yet published the exact menu path or implementation date.

  Tip: Schools should prepare product-specific permission policies and inform teachers now so classroom workflows are not disrupted during the transition to the default-off model.

  ✓ Verified by official sourceSource: Google: Öğrenme için sorumlu AI tasarımı
• 03 Nov
  Plugin / IntegrationGemini Enterprise

  Salesforce federated data store reaches GA in Gemini Enterprise

  Connecting a Salesforce data source to Gemini Enterprise through federation, without importing it, is now generally available. Assistant can search accounts, contacts, opportunities, cases, leads, and custom objects; generate grounded responses; and create, update, or delete records.

  Usage details

  Who can use it: Gemini Enterprise organizations using Salesforce; the release notes cover Standard, Plus, Pay-as-you-go, and Frontline edition documentation.

  How to use it: In the Gemini Enterprise documentation, open the Connectors > Salesforce > Set up a data store flow; authorize Salesforce and complete the federated data store configuration.

  Tip: Before enabling write operations, use read-only queries to verify Salesforce permissions and which object fields will be exposed through federation.

  ✓ Verified by official sourceSource: Gemini Enterprise sürüm notlarıSource: Salesforce veri deposu kurma rehberi
• 03 Nov
  SettingGoogle Meet

  Custom pre-meeting policy notice for Gemini in Google Meet

  Administrators can set a short policy message and optional URL to display on the Green Room screen before participants join a meeting. They can choose to show the notice in every meeting or only when recording, transcription, or Gemini notes are enabled.

  Usage details

  Who can use it: Business Standard and Plus; Enterprise Standard and Plus; Education Fundamentals, Standard, and Plus; Frontline Plus; Google AI Pro for Education. The expanded rollout began on 2026-11-02.

  How to use it: In the Admin console, enable the feature under Meet Safety Settings for the relevant OU; configure the Green Room message, URL, and display conditions.

  Tip: Keep the policy message short and link to a detailed organization page; showing the notice only when Gemini notes or recording is enabled can reduce clutter on the join screen.

  ✓ Verified by official sourceSource: Google Workspace Updates: Meet öncesi özel politika bildirimi
• 03 Nov
  FeatureGemini in Google Classroom

  Guided Learning becomes globally available in Google Classroom

  Guided Learning is now globally available in Google Classroom. A teacher-assigned activity works like a one-on-one study tool linked to class materials and gives teachers real-time insights into the topics where the class needs support.

  Usage details

  Who can use it: Global availability in Google Classroom; rollout and school administrator controls may vary by organization.

  How to use it: A teacher assigns a Guided Learning activity in Google Classroom; the student opens the assigned activity to start the step-by-step study flow.

  Tip: Link the activity to class materials; this helps Guided Learning guide students through the steps of thinking in the context of the lesson rather than simply giving them the answer.

  ✓ Verified by official sourceSource: Google: Öğrenme için sorumlu AI tasarımı
• 03 Nov
  AvailabilityGoogle Search

  Guided Learning begins piloting in Google Search for student accounts

  Google is adding Guided Learning capabilities to Search for student accounts. When the system detects homework-like queries, it will guide students with questions and step-by-step prompts instead of jumping straight to the result; the pilot is planned to begin at select U.S. schools during the month.

  Usage details

  Who can use it: Select U.S. schools and student accounts during November 2026; not generally available.

  How to use it: Submit a homework- or problem-type query using a participating school account; Search will show Guided Learning steps for eligible queries. There is no setting to enable it for general users yet.

  Tip: Describe the question and what you are trying to understand in detail; complete each step of the guided flow rather than asking only for the final answer.

  ✓ Verified by official sourceSource: Google: Öğrenme için sorumlu AI tasarımı
• 03 Nov
  OtherGemini CLI

  Gemini CLI no longer treats interrupted Whisper downloads as installed

  The 2026-11-03 nightly release fixes an issue that incorrectly treated interrupted Whisper model downloads as installed. This prevents a corrupted or incomplete download from being skipped as if it had completed successfully.

  Usage details

  Who can use it: Gemini CLI nightly channel; version v0.67.0-nightly.20261103.g0ac57c029.

  How to use it: Update Gemini CLI nightly to v0.67.0-nightly.20261103.g0ac57c029 or later, then restart the interrupted Whisper download.

  Tip: After network interruptions, keep the nightly release up to date and check that the model is actually available before the first call.

  ✓ Verified by official sourceModels: WhisperSource: Gemini CLI v0.67.0-nightly.20261103 GitHub sürümü
• 03 Nov
  OtherGemini for Google Cloud

  Bug fixes released for Gemini in VS Code

  The Gemini section of Google Cloud’s November 3 release notes lists various bug fixes and minor product improvements for VS Code. The notes do not detail the fixes individually or specify a version number.

  Usage details

  Who can use it: Developers using Gemini for Google Cloud in VS Code; deployment and extension version are unspecified.

  How to use it: Update the Gemini for Google Cloud extension from the VS Code Extensions panel and reload the window if prompted.

  Tip: When reporting an issue, first update the extension to the latest version and restart VS Code; this makes it easier to rule out problems caused by an outdated client.

  ✓ Verified by official sourceSource: Google Cloud sürüm notları

New in this edition · 84

• 04 Nov
  SettingClaude Code

  deniedMcpServers URL blocking also covers connectors

  URL entries also block matching Anthropic servers, cloud connectors, and runner connectors.

  Usage details

  Who can use it: Organizations managing MCP and connector policies.

  How to use it: Add a URL or connector name to deniedMcpServers in managed settings.

  Tip: Verify broad URL matches in a test group first.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  SettingClaude Code

  Invalid claude.json is no longer overwritten with defaults

  An invalid ~/.claude.json is no longer replaced with defaults; startup fails and the file is preserved.

  Usage details

  Who can use it: CLI installations using ~/.claude.json.

  How to use it: Restore from the recommended backup and restart.

  Tip: Make a copy of claude.json before startup.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  AgentClaude Code Managed Agents

  managed-agents-onboard applies risk judgment by default

  managed-agents-onboard now grants the auto permission policy to new agents and quickstart MCP tools by default; you can opt out with run without asking.

  Usage details

  Who can use it: Managed Agents onboarding and Claude Console workflows.

  How to use it: Run /claude-api managed-agents-onboard; keep the secure default or choose run without asking.

  Tip: Use run without asking only for low-risk tasks.

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

  AWS assume_role support for Mantle upstreams

  Mantle upstreams support assuming a role in another AWS account and developer-based AWS cost attribution.

  Usage details

  Who can use it: Claude apps gateway administrators and AWS setups using a Mantle upstream.

  How to use it: Add the assume_role field and target role to the Mantle upstream configuration.

  Tip: First test the role’s trust relationship and cost permissions with a limited scope.

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

  Approved shell commands run in the correct folder after restart

  After a restart, the approved command now runs in the requested folder rather than the starting folder; it won't run if the folder doesn't exist.

  Usage details

  Who can use it: Cloud and self-hosted runner sessions.

  How to use it: Approve the command again after restart and check the working folder.

  Tip: Verify the folder before running destructive commands.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  AvailabilityClaude Code Remote Control

  Remote Control and runner can start new sessions

  Fixed an issue that left Remote Control, the daemon, and the runner with spawn ENOENT when an update or version cleanup removed the binary.

  Usage details

  Who can use it: Remote Control, daemon, and self-hosted runner installations.

  How to use it: Upgrade the host, daemon, and runner components to 2.1.318.

  Tip: Plan version cleanup around the lifecycle of running binaries.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  APIClaude Code self-hosted runner

  Runner orchestrator log fields have changed

  ok lines now include a reason field at every stdout level, and nack lines use a new reason position.

  Usage details

  Who can use it: Operations teams that parse runner logs.

  How to use it: Update log parsers to match the reason field and stdout format.

  Tip: Replace old retryable patterns with ones matching the new format.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  SettingClaude apps gateway

  The trusted_proxies guidance is now safer

  Log hints say that only proxies that add X-Forwarded-For should be listed in trusted_proxies.

  Usage details

  Who can use it: Administrators running a gateway behind a proxy.

  How to use it: Limit listen.trusted_proxies to trusted proxies.

  Tip: Don’t trust the client header directly.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  CapabilityClaude Code

  --continue preserves conversations after a broken tool call

  Fixed an issue where the --continue command lost the previous conversation after retries for a broken tool call were exhausted.

  Usage details

  Who can use it: Sessions using --continue in the Claude Code CLI.

  How to use it: Update to 2.1.318 and run claude --continue.

  Tip: Keep transcript backups for long-running tasks, too.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  CapabilityClaude Code

  Failed settings changes in network home directories are no longer reported as successful

  Logout, MCP, and permission changes that can’t be written to a shared network home directory no longer appear to succeed silently.

  Usage details

  Who can use it: CLI installations using a shared network home directory.

  How to use it: Upgrade to 2.1.318 and rerun the command; fix the write issue.

  Tip: Check that configuration files are writable.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  CapabilityClaude Code

  Configuration saves in network home directories are more reliable

  Reduced the likelihood of claude.json, settings, and saved logins being deleted, emptied, or replaced with an older copy.

  Usage details

  Who can use it: Installations using a shared network file system.

  How to use it: Upgrade the client to 2.1.318, then save your settings and login.

  Tip: Back up critical configuration separately.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  CapabilityClaude Code

  Settings that appear missing on network file systems are checked again

  If a network file system mistakenly reports that the configuration is missing, the session checks again; this reduces the loss of MCP and trusted folders.

  Usage details

  Who can use it: Sessions using a network file system.

  How to use it: Update to 2.1.318 and restart the session.

  Tip: Monitor file visibility delays.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  AvailabilityClaude Code

  Incorrect startup block caused by allowedProviders fixed

  Fixed an issue where an allowedProviders list saved by another login incorrectly rejected session startup.

  Usage details

  Who can use it: Sessions using multiple providers on one machine.

  How to use it: Upgrade to 2.1.318 and restart the session.

  Tip: Keep provider permissions aligned with your organization’s policy.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  AvailabilityClaude Code Cloud

  A session without a repository in an Anthropic-hosted cloud environment

  Cloud sessions can now be started without selecting a repository by choosing No repository.

  Usage details

  Who can use it: Anthropic-hosted cloud environments.

  How to use it: Select No repository when choosing a repository during session creation.

  Tip: Use this option for tasks that don’t require a repository.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  AgentClaude Code

  Background subagents move shell jobs to the background after three minutes

  Background subagents move shell commands that run for three minutes to the background across all providers.

  Usage details

  Who can use it: Background subagents and all supported providers.

  How to use it: Assign a long-running shell job to a subagent and monitor its background status.

  Tip: Redirect long command output to a file.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  CapabilityClaude Code

  Auto-update immediately retries version checks after network errors

  A brief network interruption during version validation is now retried without waiting for the next check.

  Usage details

  Who can use it: Claude Code installations with Auto-update enabled.

  How to use it: Leave Auto-update enabled and monitor checks after brief network interruptions.

  Tip: Allow update domains through your corporate proxy.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  CapabilityClaude Code

  Signing in again from the same home directory no longer interrupts jobs

  Fixed an issue where running jobs ended with Not logged in when another terminal signed in again with the same account.

  Usage details

  Who can use it: Multiple terminals or hosts sharing the same home directory.

  How to use it: Use 2.1.318 on all hosts and resume the job.

  Tip: Keep versions consistent on shared machines.

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

  Failed Remote Control sessions no longer appear available

  Fixed an issue that made a /remote-control session appear available after the connection failed.

  Usage details

  Who can use it: CLI sessions using Remote Control.

  How to use it: Reopen the /remote-control menu and check the status.

  Tip: Start a new connection instead of using the failed card.

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

  Bedrock CountTokens error identifies the right component

  The warning says Claude Code handles counting after a 501, and IAM should be checked only for access-denied errors.

  Usage details

  Who can use it: Gateways using a Bedrock upstream.

  How to use it: For a CountTokens error, read the warning and check IAM only for access-denied errors.

  Tip: Distinguish 501 errors from permission denials.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  CapabilityClaude Code

  Empty claude.json is treated like a missing file

  An empty ~/.claude.json without a backup is no longer reported as corrupt, and startup proceeds as if the file were missing.

  Usage details

  Who can use it: Installations with an empty configuration file.

  How to use it: Leave the file empty and start with 2.1.318.

  Tip: Verify that organization settings are reloaded.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  CapabilityClaude Code

  Idle compaction now replaces the conversation with a summary

  A bug where idle compaction replaced the conversation with a non-summary response has been fixed.

  Usage details

  Who can use it: VS Code, Desktop, and CLI sessions with idle compaction enabled.

  How to use it: Leave a long session idle and check the generated summary.

  Tip: Save important decisions separately in a short file.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  SettingClaude Code

  A malformed NODE_EXTRA_CA_CERTS file no longer breaks all connections

  Readable certificates continue to be used when the certificate file is invalid, and a warning is printed to stderr.

  Usage details

  Who can use it: Connections using custom CA certificates.

  How to use it: Set NODE_EXTRA_CA_CERTS and test the connection with 2.1.318.

  Tip: Keep only valid PEM certificates in the variable.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  CapabilityClaude Code

  Responses are preserved when restarting after a large image or tool retry

  Fixed an issue that dropped an interrupted response when restarting immediately after a large image or tool retry.

  Usage details

  Who can use it: Restartable sessions that use images and tools.

  How to use it: Update to 2.1.318 and use the resume flow after an interruption.

  Tip: Check that the session state has been saved before restarting.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  FeatureClaude Tag

  Claude Tag admin setup fixes accessibility issues

  Keyboard focus and screen reader announcements have been fixed; Escape no longer closes the Add dialog in the connect form.

  Usage details

  Who can use it: Teams setting up Claude Tag as an administrator.

  How to use it: Open Admin setup and test the keyboard and screen reader flow.

  Tip: Test Escape and screen reader announcements together.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  CapabilityClaude Code

  claude.json restore command uses the correct backup

  Fixed an incorrect backup reference and a read-only error in the restore command printed for a damaged or missing claude.json.

  Usage details

  Who can use it: Installations using configuration backups.

  How to use it: Run the restore command provided at startup and verify the file.

  Tip: Test backups before restoring them.

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

  The Cloud MCP row shows the number of available tools

  Cloud /mcp no longer counts tools the model can’t use and now shows the number available.

  Usage details

  Who can use it: Cloud sessions and MCP servers.

  How to use it: Open the /mcp command in a cloud session and check the server row.

  Tip: Distinguish the total number of tools from the number of active tools.

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

  Cloud sessions can read GitHub Actions logs

  gh run view --log and gh api log requests now return logs in most cloud environments instead of being redirected.

  Usage details

  Who can use it: Cloud sessions using GitHub Actions.

  How to use it: Run gh run view --log or gh api in a cloud session.

  Tip: Limit the output using specific run and job IDs.

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

  Standard Chrome names can be used in cloud sessions

  In cloud sessions, the names google-chrome and CHROME_PATH let tools find the bundled Chromium.

  Usage details

  Who can use it: Tools that use Chromium in Cloud sessions.

  How to use it: Call the browser through google-chrome or CHROME_PATH.

  Tip: Try resolving CHROME_PATH first in the tool.

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

  Cloud PR errors show the cause or a GitHub link

  Create PR failures now provide the cause or a GitHub link instead of only showing Try again.

  Usage details

  Who can use it: Users creating PRs from Cloud and Remote Control.

  How to use it: Try creating a PR and follow the error cause or link.

  Tip: Don’t blindly retry the request without fixing the cause.

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

  The Cloud Setup hook’s environment variables reach Bash

  Fixed an issue where variables written by the Setup hook to CLAUDE_ENV_FILE did not reach Bash.

  Usage details

  Who can use it: Projects using the Setup hook in Cloud sessions.

  How to use it: Write variables using the Setup hook and check them in the next Bash call.

  Tip: Verify that secrets are present rather than logging them.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  FeatureCode Review

  Code Review analytics retries a failed request once

  The Analytics page retries once after a network or server error, then displays a Try again banner.

  Usage details

  Who can use it: Teams using Code Review analytics.

  How to use it: Open the Analytics page; if an error occurs, wait for the automatic retry.

  Tip: Don’t conclude that data is missing before using the retry in the banner.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  APIClaude API

  Actual image size limit shown for requests with many images

  For more than 20 images, the error now shows the API’s actual limit instead of a fixed 2000px.

  Usage details

  Who can use it: Clients sending many images to the Claude API.

  How to use it: Resend the request and resize the images based on the returned limit.

  Tip: Check image dimensions on the client side in advance.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  FeatureClaude Code

  design revoke no longer reports a 404 error as success

  Fixed an issue where the command reported success when a /design revoke request returned 404.

  Usage details

  Who can use it: Users revoking Claude Design connections from the CLI.

  How to use it: Run /design revoke with 2.1.318 and check the output.

  Tip: Verify the server status after revoking.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  CapabilityClaude Code

  A saved login is no longer replaced with an empty file when storage is full

  Fixed an issue where a saved login was replaced with an empty file when the network home directory ran out of space for data.

  Usage details

  Who can use it: Network home directories approaching their capacity limit.

  How to use it: Free up quota and save the login again with 2.1.318.

  Tip: Monitor home directory quotas regularly.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  APIAgent SDK

  A stopped response is no longer counted as a success because of a Mod

  The turn.step hook can no longer finish a stopped response as successful in headless runs.

  Usage details

  Who can use it: Headless Agent SDK and claude -p Mod workflows.

  How to use it: Upgrade to 2.1.318 and check the status of a stop scenario.

  Tip: Handle stopping and success as separate states.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  AvailabilityClaude Code Remote Control

  Missing working folder errors are now explained

  Remote Control now reports the missing folder instead of showing a misleading spawn ENOENT error.

  Usage details

  Who can use it: Remote Control sessions whose working folder has been deleted.

  How to use it: Re-create the specified folder or start with the correct folder.

  Tip: Verify the remote folder before starting a session.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  RetiredClaude Code

  Previous thinking may not be preserved when resuming an old conversation

  The behavior that preserved old thinking in 2.1.288 has been removed; thinking may be discarded in old conversations.

  Usage details

  Who can use it: Conversations started in 2.1.286 or earlier.

  How to use it: Resume the old conversation and provide the necessary intermediate result again.

  Tip: Don’t leave critical results only in the thinking field.

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

  Gateway warning for federated Google token expiration

  The gateway logs a warning when the Google token in the external_account credential file is nearing expiration.

  Usage details

  Who can use it: Gateway administrators using Google federation.

  How to use it: Monitor gateway logs and renew the federation credential before the token expires.

  Tip: Connect the warning to a centralized log alert.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  APIClaude Code

  Login expiration added to auth status and JSON output

  The expiration date for a stored claude.ai login is provided as loginExpiresAt in auth status and as credential_expires_at in claude -p JSON.

  Usage details

  Who can use it: Claude Code CLI and claude -p JSON automations.

  How to use it: Run claude auth status or read the field in the JSON output.

  Tip: Set up monitoring to start the re-login flow before expiration.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  AvailabilityClaude Code

  The IDE terminal no longer automatically installs and updates the extension

  Claude Code launched from the IDE terminal no longer installs or updates the IDE extension; use /ide or the extension view instead.

  Usage details

  Who can use it: Users launching Claude Code from the IDE terminal.

  How to use it: Run /ide in an external terminal or open the editor’s extension view.

  Tip: Manage the extension version through centralized distribution.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  AvailabilityClaude for iOS

  iPhone correctly shows when a cloud session turn ends

  Fixed an issue where the iPhone app showed an ongoing cloud turn as finished.

  Usage details

  Who can use it: Those tracking cloud sessions with Claude for iOS.

  How to use it: Update the iPhone app and monitor the cloud session.

  Tip: Compare the notification status with the session in the app.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  AgentClaude Code

  The Ask each time subagent doesn’t switch models for flagged messages

  When model switching is set to Ask each time, the subagent stops instead of switching models.

  Usage details

  Who can use it: Sessions using a model policy for flagged requests.

  How to use it: Set the option to Ask each time and run the flagged-message scenario.

  Tip: Intentionally restart the stopped agent.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  CapabilityClaude Code

  Keys pressed early in permission prompts no longer cause incorrect responses

  Fixed an issue where keys pressed before a slow-to-open permission prompt appeared could inadvertently answer it.

  Usage details

  Who can use it: Interactive terminal sessions.

  How to use it: Update to 2.1.318 and use the normal keyboard flow when the prompt appears.

  Tip: Don’t press the confirmation key before the prompt appears.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  APIClaude Code

  Setup tokens from an allowed organization are no longer rejected

  Fixed an issue where setup tokens belonging to an allowed organization were rejected on machines with forceLoginOrgUUID.

  Usage details

  Who can use it: Managed machines that enforce an organization ID.

  How to use it: Configure the allowed organization’s token with setup-token and start it.

  Tip: Store the token in an approved secure secrets store.

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

  Closed stdio MCP servers are no longer probed repeatedly

  During version checks, closed stdio MCP servers are no longer retried repeatedly; a server that closes quickly uses the legacy handshake for seven days.

  Usage details

  Who can use it: Installations running stdio MCP servers.

  How to use it: Start the MCP server with 2.1.318 and check /mcp status.

  Tip: Don’t restart it without fixing the cause of the early shutdown.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  FeatureClaude Code

  Requesting more usage from the usage limit menu takes one step

  The Ask your admin for more usage option now submits the request in one step.

  Usage details

  Who can use it: Plans with administrator-approved usage limits.

  How to use it: Select Ask your admin for more usage in the usage limit menu.

  Tip: Add brief task context to the request.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  AgentClaude Code

  A finished agent no longer runs again after a usage limit

  Fixed an issue where workflows resumed after hitting a limit reran finished agents.

  Usage details

  Who can use it: Sessions using workflows and agent chains.

  How to use it: Resume the workflow that hit the limit with 2.1.318.

  Tip: Design agent tasks to be idempotent.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  CapabilityClaude Code

  Git operations are more reliable with the built-in Bash on macOS

  Reliability of creating Git commits and pull requests in macOS’s /bin/bash shell has been improved.

  Usage details

  Who can use it: Git workflows using the built-in Bash on macOS.

  How to use it: Upgrade to 2.1.318 and run the commit and PR workflow.

  Tip: Verify the diff and remote branch before opening a PR.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  CapabilityClaude Code

  Multiple Bash sessions no longer stall on macOS

  Memory growth and stalls have been fixed in sessions running many Bash commands on macOS.

  Usage details

  Who can use it: Sessions running multiple Bash commands on macOS.

  How to use it: Upgrade Claude Code to 2.1.318 and rerun the workflow.

  Tip: Monitor memory during long-running parallel commands.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  APIClaude Code

  MCP add and remove operations write configuration under a lock

  claude mcp add and remove now wait for the configuration lock; if the lock cannot be acquired, they return exit code 1.

  Usage details

  Who can use it: Processes accessing MCP configuration concurrently.

  How to use it: Run the MCP command; if the lock is busy, wait or handle the error code.

  Tip: Serialize jobs that write to the same configuration in parallel.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  FeatureClaude Code

  Mod activation responses are now recorded

  When Claude Code asks to activate Mods it has written, it adds your response to the session record.

  Usage details

  Who can use it: All sessions using Claude Code 2.1.318.

  How to use it: Update Claude Code to 2.1.318 and respond when the Mod prompt appears.

  Tip: Check the session record to audit Mod behavior later.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  SettingClaude Code

  Mod fork tasks can have a separate effort level

  The $.model.fork call in Mod can now accept effort; the subtask runs at a level independent of the main session and reports that level.

  Usage details

  Who can use it: Claude Code users developing Mods.

  How to use it: Add, for example, effort: low to the $.model.fork call.

  Tip: Run short, low-risk subtasks with low.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  CapabilityClaude Code

  Stop works on the message immediately after a model change

  In headless sessions, the message immediately after a model change can now be stopped or canceled with Stop.

  Usage details

  Who can use it: Headless Claude Code sessions.

  How to use it: Change the model and use Stop on the running message.

  Tip: Wait for the model switch before sending a new request.

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

  Validation of specially named marketplaces is now consistent

  plugin validate no longer reports success for a specially named file that marketplace add would reject.

  Usage details

  Who can use it: Developers managing plugin marketplaces.

  How to use it: Run claude plugin validate first, then marketplace add.

  Tip: Use an accepted format for the marketplace filename.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  APIClaude Code

  Custom slash commands produce output in p and SDK sessions

  Fixed an issue where custom slash commands that failed or were called only by Claude were silent in p and SDK sessions.

  Usage details

  Who can use it: Users of custom slash commands with claude -p or Agent SDK.

  How to use it: Run the command with 2.1.318 and read the text or SDK output.

  Tip: In automation, distinguish empty output from error output.

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

  Slow token refresh in plugin commands is fixed

  Fixed an issue where a plugin command exited before token refresh finished, causing the session to be dropped on the next run.

  Usage details

  Who can use it: Claude Code CLI installations using plugins.

  How to use it: Update to 2.1.318 and run the plugin command again.

  Tip: Wait for token refresh to finish before shutting down.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  APIClaude Code

  prompt.submit Mod content stays in the user turn

  Content added at the prompt.submit stage stays in the user turn instead of becoming a system message.

  Usage details

  Who can use it: Users developing Mods and hooks.

  How to use it: Run the Mod with 2.1.318 and inspect the prompt.submit content.

  Tip: Configure persistent system rules separately.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  SettingClaude Code self-hosted runner

  Missing value for release-idle-session-min triggers a warning

  A release-idle-session-min argument with no value or only whitespace now triggers a startup warning.

  Usage details

  Who can use it: Self-hosted runner administrators.

  How to use it: Provide a numeric value for the argument and check the startup log.

  Tip: Pass arguments as a shell array.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  CapabilityClaude Code

  Retention cleanup preserves the latest good backup

  When cleanup runs only in the home directory used by claude -p, it takes a fresh backup before deleting the latest good backup.

  Usage details

  Who can use it: Non-interactive installations using retention cleanup.

  How to use it: Update to 2.1.318 and check the backups after cleanup.

  Tip: Keep an external backup in addition to automatic retention.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  APIClaude Code self-hosted runner

  Request reason added to the runner spawn hook

  CLAUDE_RUNNER_SPAWN_REASON adds the reason, such as runner_lost or resumed, to the runner hook environment.

  Usage details

  Who can use it: Organizations using the self-hosted runner spawn-runner hook.

  How to use it: Read the CLAUDE_RUNNER_SPAWN_REASON variable in the hook.

  Tip: Route empty or unknown values to a safe default path.

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

  A new cloud session can be opened from a deleted environment card

  Deleted cloud environment cards now show a New session button.

  Usage details

  Who can use it: Users who see a deleted cloud environment card.

  How to use it: Click the New session button on the card and select a new environment.

  Tip: Select the repository and environment settings again.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  CapabilityClaude Code

  Deleted transcript is no longer recreated from the last prompt

  Fixed an issue where a transcript deleted when an idle, non-interactive session closed was recreated from the last prompt.

  Usage details

  Who can use it: Non-interactive or claude -p-based sessions.

  How to use it: Update to 2.1.318 and reapply transcript cleanup.

  Tip: Clearly define your transcript retention policy.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  AgentClaude Code

  Subagent responses can wait longer with a cold cache

  In Bedrock, Vertex, Foundry, or sessions with telemetry disabled, pending responses can wait for up to five minutes.

  Usage details

  Who can use it: The specified providers and sessions with telemetry disabled.

  How to use it: Start the subagent and wait up to five minutes for a progress summary.

  Tip: Don’t cancel early when the cache is cold.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  AvailabilityClaude Code

  The right renewal option is recommended for expired logins

  An expired login is clearly reported; claude -p auth login and setup-token are recommended.

  Usage details

  Who can use it: Users whose saved claude.ai login has expired.

  How to use it: Run the recommended claude auth login or claude setup-token command.

  Tip: Monitor token expiration for CI.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  CapabilityClaude Code

  claude -p warning for an expiring login

  A stderr warning is added to claude -p text output 10 days before a stored claude.ai login expires.

  Usage details

  Who can use it: CLI and CI workflows that use claude -p text output.

  How to use it: Upgrade to 2.1.318 and monitor the stderr stream as well.

  Tip: Collect stdout and stderr in separate channels.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  CapabilityClaude Code

  Version cleanup no longer deletes another user’s process

  Fixed an issue where a running Claude Code process belonging to another user was mistaken for a dead process and its binary was deleted.

  Usage details

  Who can use it: Shared machines and processes belonging to different users.

  How to use it: Upgrade to 2.1.318 and run version cleanup again.

  Tip: If possible, use the same user for updates and running the process.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  APIAgent SDK

  Success status corrected for turn.step interruptions

  Responses interrupted by a turn.step API error are no longer reported as successful in claude -p and the Agent SDK.

  Usage details

  Who can use it: Agent SDK and claude -p Mods that use turn.step.

  How to use it: Upgrade to 2.1.318 and check the exit code for an API error scenario.

  Tip: In CI, rely on the exit code rather than the text.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  AvailabilityClaude Code Remote Control

  Remote Control reconnects faster after sleep or suspension

  The reconnection speed of remote sessions after sleep or suspension has been improved.

  Usage details

  Who can use it: Remote Control and remote session users.

  How to use it: Open the session after sleep and observe the reconnection.

  Tip: Verify the connection status before the first critical command.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  AvailabilityClaude Code Cloud

  A prolonged upload rejection no longer stops a cloud turn

  Fixed an issue that caused a cloud session to stop mid-turn when the service rejected uploads for several minutes.

  Usage details

  Who can use it: Claude Code users using Cloud sessions.

  How to use it: Upgrade to 2.1.318 and rerun the task that requires an upload.

  Tip: For large files, monitor the task and service status together.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  AvailabilityClaude Code VS Code extension

  VS Code sign-in screen shows CLI error output

  When the sign-in status check fails, the VS Code screen shows Claude Code’s explanation.

  Usage details

  Who can use it: Users whose sign-in check fails in VS Code.

  How to use it: Update the extension to 2.1.318 and follow the explanation on the sign-in screen.

  Tip: Forward the exact error text to your administrator.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  CapabilityClaude Code VS Code extension

  VS Code no longer enters a process loop when sign-in is rejected by a setting

  Fixed an issue where VS Code started a new Claude Code process every minute when an organization setting rejected sign-in.

  Usage details

  Who can use it: Organization-managed sign-in settings in VS Code.

  How to use it: Update the extension to 2.1.318 and reopen the window.

  Tip: Share the enterprise sign-in policy with users.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  CapabilityClaude Code

  On restart, an older message with an API error is no longer moved ahead

  Fixed an issue where an older message that received an API error was resent before a new message after a restart.

  Usage details

  Who can use it: CLI, cloud, and runner sessions that can be restarted.

  How to use it: Upgrade to 2.1.318 and restart the interrupted session.

  Tip: Record message IDs in workflows where ordering matters.

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

  Unavailable connector tool is reported after restart

  A fix ensures Claude is notified when an approved connector tool is unavailable after a restart.

  Usage details

  Who can use it: Plans using connectors in Cloud sessions.

  How to use it: Restart the session and try calling the connector.

  Tip: Check the tool list on the first call.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  APIMCP

  MCP tool returns its schema when called before loading

  The error response for an MCP call made before loading now includes the tool’s input schema.

  Usage details

  Who can use it: Clients that call MCP tools programmatically.

  How to use it: Test the scenario where a tool is called before loading, then read the error schema.

  Tip: Manage loading state and don’t retry blindly.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  FeatureClaude Code

  Runtime duration updates live in background shell details

  Fixed an issue where the runtime duration of a background shell in an open dialog did not update.

  Usage details

  Who can use it: Sessions running background shell commands.

  How to use it: Send a shell command to the background and keep its details dialog open.

  Tip: Use the live duration as a helpful indicator, not as a completion signal.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  CapabilityClaude Code

  claude -p and the SDK no longer write unchanged config

  Non-interactive claude -p and SDK runs no longer rewrite claude.json if it hasn’t changed.

  Usage details

  Who can use it: claude -p and SDK automations.

  How to use it: Upgrade to 2.1.318 and compare the file’s timestamp.

  Tip: Trigger file monitoring only when there’s an actual change.

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

  Connector search indicates a partial directory

  Connector results tell Claude that the search covers only part of the directory.

  Usage details

  Who can use it: Users of Cloud sessions and connector search.

  How to use it: Search, then narrow or repeat the search based on the partial-results information.

  Tip: Don’t treat a single result as evidence that the entire directory is empty.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  FeatureClaude Code

  Usage credit notifications no longer keep repeating

  Fixed a bug that showed the credit notification every 30 seconds while a background subagent was running.

  Usage details

  Who can use it: Plans using background subagents and usage credits.

  How to use it: Update to 2.1.318 and run a background subagent.

  Tip: Check actual usage with /usage.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  SettingClaude Code

  permissions views moved to the standard dialog

  permissions details and delete confirmation now use the standard dialog; pressing Ctrl+C twice returns or cancels.

  Usage details

  Who can use it: Interactive Claude Code sessions.

  How to use it: Open /permissions and use the rule details or delete view.

  Tip: Check the dialog context when canceling.

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

  Duplicate PushNotification notifications are fixed

  Fixed a duplicate notification that occurred when the status field was omitted from a PushNotification call.

  Usage details

  Who can use it: Sessions and integrations using PushNotification.

  How to use it: Update to 2.1.318 and run the scenario without the status field.

  Tip: Deduplicate notifications by ID in the consumer.

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

  Terminal fork names better distinguish conflicts

  The second terminal fork is named Name (fork 2) when the app doesn't assign it a name.

  Usage details

  Who can use it: Users who fork with Remote Control.

  How to use it: Create a terminal fork, fork it again, and check the name.

  Tip: Distinguish sessions with meaningful names.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  FeatureClaude Code VS Code extension

  A long error word no longer pushes the close button out of view

  Fixed an issue where a long error word in the VS Code Claude panel hid the close button.

  Usage details

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

  How to use it: Update the extension to 2.1.318 and open the error banner.

  Tip: If needed, copy the error text before closing it.

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

  Side-by-side checkouts are distinguished in the environment menu

  Checkouts of the same repository appear in the Remote Control menu under their own folder names.

  Usage details

  Who can use it: Users with multiple Remote Control checkouts for one repository.

  How to use it: Open the environment menu and compare the folder names.

  Tip: Keep folder names short and distinctive.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes
• 04 Nov
  FeatureClaude Code

  Help notifications say to try again instead of using a terminal-only key

  You should know notifications say try again instead of press 2, which does not work in the GUI.

  Usage details

  Who can use it: Claude Code interfaces outside the terminal.

  How to use it: Open the notification and use the try again action.

  Tip: Select the button shown in the non-terminal interface.

  ✓ Verified by official sourceSource: Claude Code v2.1.318 release notes

New in this edition · 9

• 03 Nov
  APIOpenAI Go SDK

  Go SDK expands GPT-Live Responses delegation tools

  OpenAI Go SDK 3.92.0 adds a new API surface for GPT-Live’s Responses-based delegation tools. This release makes it easier to use Go for the delegation flow that lets GPT-Live sessions work with Responses-side hosted tools, MCP, and the application’s own tools.

  Usage details

  Who can use it: OpenAI Go SDK users; v3.92.0 is available for Go applications using GPT-Live/Responses delegation.

  How to use it: Run `go get github.com/openai/openai-go/v3@v3.92.0`; use the `delegation.responses.tools` configuration in a GPT-Live session and send the required tool results back with the matching `call_id`.

  Tip: Keep delegation separate from client-side tool calls; for long-running tasks, explicitly monitor the backend model, tool approvals, and error events.

  ✓ Verified by official sourceSource: OpenAI Go SDK v3.92.0 sürüm notlarıSource: GPT-Live delegation ve araçları kılavuzu
• 03 Nov
  APIOpenAI Python SDK

  Python SDK expands GPT-Live Responses delegation tools

  OpenAI Python SDK 3.43.0 expands tool support in GPT-Live’s Responses-based delegation flow. The official GPT-Live guide explains that options such as hosted tools, MCP, tool search, programmatic tool calling, custom functions, computer use, local shell, and apply patch can be configured under delegation.responses.tools.

  Usage details

  Who can use it: OpenAI Python SDK users; v3.43.0 is available for applications using GPT-Live/Responses delegation.

  How to use it: Upgrade the SDK with `pip install -U openai==3.43.0`; add the required tools to `delegation.responses.tools` in a GPT-Live session, then set `tool_choice` and `parallel_tool_calls` as needed.

  Tip: Handle tool calls together with your application’s approval and result-return flow; in particular, provide MCP credentials again for update requests.

  ✓ Verified by official sourceSource: OpenAI Python SDK v3.43.0 sürüm notlarıSource: GPT-Live delegation ve araçları kılavuzu
• 03 Nov
  AvailabilityDots

  GPT-6.1 Terra joins the Dots model family

  OpenAI added GPT-6.1 Terra to the frontier model family powering Dots in an update to its Dots announcement on November 3. According to the announcement, a dot can use different models for different parts of its work; this is a new detail that expands the model coverage available to existing Dots users.

  Usage details

  Who can use it: Pro and Business Premium users with Dots access in eligible markets; administrator-enabled beta terms remain in place for Enterprise, Edu, and Healthcare.

  How to use it: Create a dot or open an existing one in the ChatGPT desktop app or on desktop web; no separate model-selection step is specified for GPT-6.1 Terra, which is used automatically once the support rollout reaches your account.

  Tip: Give the dot visual tasks, computer use, and general planning together; review critical side effects in Activity View and don’t leave them unapproved.

  ✓ Verified by official sourceModels: GPT-6.1 Terra, GPT-6 AstraSource: Dots duyurusu ve 3 Kasım güncellemesi
• 03 Nov
  APIOpenAI Go SDK

  Go SDK can collect MCP argument progress

  OpenAI Go SDK 3.92.0 adds support for collecting progress information for MCP tool call arguments in Responses streams. This SDK support passes intermediate progress to a Go application while the MCP call arguments are being generated.

  Usage details

  Who can use it: OpenAI Go SDK v3.92.0 users; Go applications using MCP tools in the Responses API.

  How to use it: Upgrade with `go get github.com/openai/openai-go/v3@v3.92.0`; read the stream items related to MCP argument progress in your Responses WebSocket event loop and display them in the interface.

  Tip: Use partial arguments only as a progress indicator; wait for complete and validated arguments before running the call.

  ✓ Verified by official sourceSource: OpenAI Go SDK v3.92.0 sürüm notları
• 03 Nov
  APIOpenAI Go SDK

  Go SDK adds support for typed existing-item references in Realtime

  OpenAI Go SDK 3.92.0 adds support for typed existing-item references to items referenced in Realtime events. This lets developers handle Realtime inputs using specific reference types that the SDK can parse, rather than generic, loosely typed ones.

  Usage details

  Who can use it: OpenAI Go SDK v3.92.0 users; Go applications working with the Realtime API.

  How to use it: Upgrade with `go get github.com/openai/openai-go/v3@v3.92.0`; parse Realtime events and item references through the new typed SDK models, and add a safe fallback for unknown item types.

  Tip: Don’t force all Realtime items into the same structure; preserve type distinctions to prevent the application from breaking when new event types arrive.

  ✓ Verified by official sourceSource: OpenAI Go SDK v3.92.0 sürüm notlarıSource: Realtime API başlangıç kılavuzu
• 03 Nov
  APIOpenAI Go SDK

  Go SDK adds optional final response reconstruction for WebSocket

  OpenAI Go SDK 3.92.0 adds optional final response reconstruction for the Responses WebSocket stream. Instead of merging individual delta events itself, an application can ask the SDK to reconstruct the completed response.

  Usage details

  Who can use it: OpenAI Go SDK v3.92.0 users; Go applications using Responses WebSocket.

  How to use it: Upgrade with `go get github.com/openai/openai-go/v3@v3.92.0`; use the version’s opt-in final response reconstruction API with a Responses WebSocket connection and read the completed response with `FinalResponse(ctx)`.

  Tip: Use raw delta events for low-latency interim output, and the reconstructed final response for validation and persistent storage.

  ✓ Verified by official sourceSource: OpenAI Go SDK v3.92.0 sürüm notlarıSource: Responses WebSocket modu kılavuzu
• 03 Nov
  APIOpenAI Python SDK

  Python SDK accumulates rich progress in Responses WebSocket

  OpenAI Python SDK 3.43.0 adds support for accumulating rich progress information in the Responses WebSocket stream. This makes progress events more useful to collect client-side in long-running, multi-step Responses streams.

  Usage details

  Who can use it: OpenAI Python SDK v3.43.0 users; applications using Responses WebSocket.

  How to use it: Upgrade with `pip install -U openai==3.43.0` and handle WebSocket events from `client.responses.connect()` in your existing event loop; read the complete response after `response.completed`.

  Tip: Instead of showing only a raw event log in the user interface, turn the accumulated progress into task status and a percentage indicator.

  ✓ Verified by official sourceSource: OpenAI Python SDK v3.43.0 sürüm notlarıSource: Responses WebSocket modu kılavuzu
• 03 Nov
  APIOpenAI Python SDK

  Python SDK adds overflow isolation for WebSocket lanes

  OpenAI Python SDK 3.43.0 adds lane overflow isolation support for Responses WebSocket. This is intended to prevent overload on one lane from affecting the progress of other lanes in clients using multiple streams.

  Usage details

  Who can use it: OpenAI Python SDK v3.43.0 users; applications using multiple `stream_id` values or parallel Responses WebSocket streams.

  How to use it: Upgrade with `pip install -U openai==3.43.0`; run your multiple WebSocket streams with separate `stream_id` values and test each lane’s error and reconnection behavior.

  Tip: Maintain separate timeouts, retries, and observability metrics for each lane; this lets you distinguish backpressure in one stream from other tasks.

  ✓ Verified by official sourceSource: OpenAI Python SDK v3.43.0 sürüm notları
• 02 Nov
  OtherSecurity Bug Bounty programı

  OpenAI increases Security Bug Bounty rewards and bonuses

  OpenAI increased the midpoint of the reward ranges for medium, high, and critical findings in its Security Bug Bounty program by an average of more than fourfold. The base reward for a critical vulnerability in ChatGPT, Codex, or API Platform is $30,000, while the base reward for exceptional critical findings can reach $100,000; a high-quality report, priority campaign, and five-tier loyalty bonuses can bring the total to $172,000, and eligible previous reports are being reassessed retroactively.

  Usage details

  Who can use it: Independent security researchers participating in the program; scope and supported configurations are listed on the OpenAI Security Bug Bounty page on Bugcrowd.

  How to use it: Read the scope and rules on OpenAI’s Bugcrowd Security Bug Bounty page; submit a report with a reproducible PoC, impact description, and steps using a currently supported configuration.

  Tip: For a high-quality report, clearly isolate the impact and include a working PoC and precise reproduction steps; this increases the chances of qualifying for the quality multiplier.

  ✓ Verified by official sourceSource: OpenAI’nin daha yüksek bug bounty ödülleri duyurusuSource: OpenAI Security Bug Bounty programı koşulları

New in this edition · 4

• 03 Nov
  APIMeta Haptics SDK for Unreal

  UE 5.8 support added to Meta Haptics SDK for Unreal 207.0

  Meta Haptics SDK for Unreal 207.0 adds support for a separate SDK package for Unreal Engine 5.8. The package provides the high-level API used to play and modify haptic clips created with Haptics Studio on Quest controllers.

  Usage details

  Who can use it: Developers using Unreal Engine for Quest; UE 5.8 projects.

  How to use it: Download Meta Haptics SDK for Unreal version 207.0 from Meta VR Developers downloads and add it to your UE 5.8 project.

  Tip: Match your project’s Unreal version to the SDK package’s UE 5.8 requirement; choose an earlier package version for older UE versions.

  ✓ Verified by official sourceSource: Meta Horizon OS geliştirici sürüm notları — Kasım 2026Source: Meta Haptics SDK for Unreal 207.0 sürüm notları
• 03 Nov
  APIMeta VR Developer Hub for Mac

  Meta Quest Developer Hub renamed Meta VR Developer Hub

  With Meta Quest Developer Hub for Mac 6.6.0, the product is now called Meta VR Developer Hub (MVDH). The release refreshes the Casting Window design, moves Performance Analyzer trace capture to named presets, signs and notarizes macOS packages, and fixes issues with file management, installation, connectivity, and stability.

  Usage details

  Who can use it: Users developing Meta Quest apps on Mac; version 6.6.0.

  How to use it: Download and install the Meta VR Developer Hub for Mac 6.6.0 package. Open Casting Window or Performance Analyzer to use the new interface and named trace capture presets.

  Tip: Update automation and existing capture workflows to use the new named presets; check how the individual options changed in 6.6.0.

  ✓ Verified by official sourceSource: Meta Horizon OS geliştirici sürüm notları — Kasım 2026Source: Meta VR Developer Hub for Mac 6.6.0 sürüm notları
• 03 Nov
  APIMeta VR Developer Hub for Mac

  `mqdh-perf capture` CLI command added for Performance Analyzer

  Meta VR Developer Hub for Mac 6.6.0 adds the `mqdh-perf capture` command to capture traces from scripts with Performance Analyzer. This makes it possible to automate trace collection outside the desktop interface.

  Usage details

  Who can use it: Quest developers using Meta VR Developer Hub for Mac 6.6.0.

  How to use it: First install Meta VR Developer Hub for Mac 6.6.0; then use the `mqdh-perf capture` command in the Performance Analyzer CLI to run your scripted trace capture workflow.

  Tip: Use the same named preset in CI or repeatable performance tests to compare traces across releases.

  ✓ Verified by official sourceSource: Meta VR Developer Hub for Mac 6.6.0 sürüm notlarıSource: Meta Horizon OS geliştirici sürüm notları — Kasım 2026
• 03 Nov
  RetiredMeta VR Developer Hub for Mac

  “GPU Surface Timing” preset removed from Performance Analyzer

  Meta VR Developer Hub for Mac 6.6.0 removes the legacy “GPU Surface Timing” (Standard VR) preset. Trace capture now falls back to the CPU Low Overhead preset instead.

  Usage details

  Who can use it: Quest developers using Meta VR Developer Hub for Mac 6.6.0; affects legacy GPU Surface Timing workflows.

  How to use it: Move commands and scripts tied to GPU Surface Timing to the CPU Low Overhead preset, then test the new trace capture workflow.

  Tip: Do not treat measurements from the old and new presets as equivalent in performance comparisons; take a new baseline after migrating.

  ✓ Verified by official sourceSource: Meta VR Developer Hub for Mac 6.6.0 sürüm notlarıSource: Meta Horizon OS geliştirici sürüm notları — Kasım 2026

New in this edition · 8

• 03 Nov
  AvailabilityKimi API

  Inference within India is now available for Kimi K3 on Amazon Bedrock

  According to AWS’s official announcement, Amazon Bedrock has made an in-country inference profile for Kimi K3 available. The `in.moonshotai.kimi-k3` profile processes requests in the Mumbai and Hyderabad regions, offering a new access option for workloads that require data residency in India.

  Usage details

  Who can use it: Amazon Bedrock customers; India geographic inference profile `in.moonshotai.kimi-k3`, with Mumbai and Hyderabad as target regions (AWS `ap-south-1` and `ap-south-2`). Kimi K3’s global and US profiles remain available as separate options.

  How to use it: Enable access to Kimi K3 in Amazon Bedrock; use `in.moonshotai.kimi-k3` as the model ID in a Bedrock Runtime call, choose a source region such as `ap-south-1`, and grant the `bedrock:InvokeModel` and `bedrock:InvokeModelWithResponseStream` permissions in IAM.

  Tip: If data must not leave India, use the India profile instead of `global.moonshotai.kimi-k3`; consider the global profile when broader access and cost are priorities.

  ✓ Verified by official sourceModels: Kimi K3Source: Introducing India-based inference for Kimi K3 on Amazon BedrockSource: Kimi K3 - Amazon Bedrock model card
• 02 Nov
  FeatureKimi Work

  Original paths and parent folders are shown for invalid artifact links

  When an artifact link is invalid, Kimi Work can now display the original file path. You can continue looking for the file by opening the parent folder from the same screen.

  Usage details

  Who can use it: Kimi Work desktop app versions 3.2.24 and later.

  How to use it: Open an invalid artifact link; check the original path shown and use the option to open the parent folder.

  Tip: Noting the original path before deleting or moving output folders makes it easier to recover files from old artifact links.

  ✓ Verified by official sourceSource: Kimi Work Release Notes
• 02 Nov
  SettingKimi Work

  Kimi Work network settings automatically follow the system proxy

  With Kimi Work 3.2.24, network settings dynamically follow the system proxy configuration. When the system proxy changes, there is no need to manually update the app’s connection settings.

  Usage details

  Who can use it: Kimi Work desktop app versions 3.2.24 and later.

  How to use it: Update Kimi Work to version 3.2.24 or later; the app will automatically use the operating system’s current proxy settings for network connections.

  Tip: If proxy changes are frequent on your corporate network, keep the system setting as the single source of truth instead of configuring a separate fixed proxy in Kimi Work.

  ✓ Verified by official sourceSource: Kimi Work Release Notes
• 02 Nov
  FeatureKimi Work

  Kimi Work preview now supports Markdown note properties

  With Kimi Work 3.2.24, Markdown files in the preview panel now support note properties. The editing and preview experience has also been improved.

  Usage details

  Who can use it: Kimi Work desktop app versions 3.2.24 and later.

  How to use it: Open a Markdown file in a workspace in Kimi Work and switch to the preview panel; view and edit note properties fields there.

  Tip: For structured notes, use note properties fields such as title, status, or tags to make files easier to scan.

  ✓ Verified by official sourceSource: Kimi Work Release Notes
• 02 Nov
  OtherKimi Work

  Success messages no longer appear before file downloads are complete

  Kimi Work 3.2.24 fixed an issue that caused a success message to appear before a file had finished downloading. This better aligns the success notification with the file being ready to use.

  Usage details

  Who can use it: Kimi Work desktop app versions 3.2.24 and later.

  How to use it: Update Kimi Work; when downloading a file or artifact, check that the file is complete after the success notification before opening it.

  Tip: For large files, verify the file’s size and that it opens instead of moving it as soon as the success notification appears.

  ✓ Verified by official sourceSource: Kimi Work Release Notes
• 02 Nov
  FeatureKimi Work

  Kimi Work Network Diagnostics screen can now open offline

  Kimi Work 3.2.24 allows the network diagnostics screen to open even without an internet connection. This makes it easier to access the diagnostic tool when connection problems occur.

  Usage details

  Who can use it: Kimi Work desktop app versions 3.2.24 and later.

  How to use it: Open the Network Diagnostics screen in Kimi Work; you can view the screen and inspect the current network status even when there is no connection.

  Tip: During corporate network outages, take a screenshot or capture the output from the diagnostics screen before sending it to the support team.

  ✓ Verified by official sourceSource: Kimi Work Release Notes
• 02 Nov
  CapabilityKimi Work

  Kimi Work Remote Control connection stability improved

  Kimi Work 3.2.24 improved the stability of Remote Control connections. Connection drops and reconnection behavior have been improved in sessions that use remote control.

  Usage details

  Who can use it: Kimi Work desktop app versions 3.2.24 and later; desktop and remote clients using Remote Control.

  How to use it: Update Kimi Work to version 3.2.24 or later and restart the Remote Control flow using the existing connection/QR connection.

  Tip: For long-running remote tasks, preventing the desktop device from going to sleep helps you make better use of the improved connection stability.

  ✓ Verified by official sourceSource: Kimi Work Release Notes
• 02 Nov
  OtherKimi Work

  Kimi Work system notification toggle issue fixed

  Kimi Work 3.2.24 fixed an issue where the system notifications toggle did not respond when clicked. The setting now responds correctly to user input.

  Usage details

  Who can use it: Kimi Work desktop app versions 3.2.24 and later.

  How to use it: Update the app to version 3.2.24 or later, then use the system notifications toggle in notification settings again.

  Tip: If you are not receiving notifications, check both the Kimi Work toggle and the operating system’s app notification permission.

  ✓ Verified by official sourceSource: Kimi Work Release Notes

New in this edition · 2

• 02 Nov
  RetiredGrok Imagine API

  grok-imagine-image-quality retired; requests routed to Imagine 2.0

  xAI retired the grok-imagine-image-quality model ID from the API on 2 Kasım; the old ID continues to work, but requests are served by grok-imagine-image-2.0 with quality: low. The request and response formats remain unchanged; this routing is 0,01 ABD doları cheaper per image than the previous model.

  Usage details

  Who can use it: All requests using the old ID on the /v1/images/generations and /v1/images/edits endpoints in the xAI API are affected. grok-imagine-image 1.0 is not affected; grok-imagine-image-pro also routes to Imagine 2.0 low through the chain.

  How to use it: Set the model field in your code to grok-imagine-image-2.0 and choose low, medium, or auto for quality; if you continue using the old ID, low is applied automatically. Log the model field in the response to verify the transition.

  Tip: If you want to lock in the cost and output, specify the quality value explicitly; if quality matters, use medium and call the new model directly rather than relying on the old ID in production.

  ✓ Verified by official sourceModels: grok-imagine-image-quality, grok-imagine-image-2.0, grok-imagine-image-proSource: grok-imagine-image-quality emekliliği için geçiş kılavuzuSource: xAI API sürüm notları
• 02 Nov
  AgentGrok Bot

  Shared Data Bot data science agent introduced in Grok Bot

  xAI announced Data Bot, a Team Bot trained by its data science team. Data Bot can query the data warehouse and generate analyses and charts/reports; teams can add it to Slack channels and receive scheduled reports.

  Usage details

  Who can use it: The announcement presents Data Bot for team use within xAI/SpaceXSI; it does not specify a public ready-made template or country/plan coverage. It offers an example use case for teams with the general Grok Bot Team Bot and Slack capabilities.

  How to use it: The announcement does not offer a public one-click setup for Data Bot. To build the same setup, select + → Create a Bot in Grok Bot, define the data role, sources, and approval boundaries in the first message; authorize your workspace via Connect apps → Slack and add the Bot to the relevant channel.

  Tip: Clearly document metric definitions, query logic, and data owners in shared skills; require read-only access to the data store and approval for external actions.

  ✓ Verified by official sourceSource: Grok Bot ile her ekibe bir veri bilimciSource: Grok Bot’un Data Bot duyurusuSource: Grok Bot oluşturma ve yönetme

New in this edition · 15

• 03 Nov
  FeatureQoder

  Qoder Fast mode offers a one-click fast task experience

  Qoder Fast was introduced as a new tier that delivers a fast task experience without asking users to select model and reasoning settings individually. In a 10-task test shared by Alibaba, Fast showed a 152% increase in generation speed over the previous Performance tier and took about half as long per task as Auto; quality scores were similar.

  Usage details

  Who can use it: Across the Qoder product family; access may vary by product, account, and current model configuration.

  How to use it: Open the model or working tier selector in the Qoder product you use, select Fast, and start the task.

  Tip: Choose Fast for quick idea validation, local code changes, and short feedback loops; use a stronger tier for deep architectural work.

  ✓ Verified by official sourceSource: Qoder Fast modu duyurusu
• 03 Nov
  Pricing / PlanQoder Lite

  Qoder Lite launches worldwide for $10 a month with 1,000 credits

  Qoder Lite began offering 1,000 monthly credits and access to selected cost-effective models for $10 a month worldwide. The plan includes Repo Wiki, Cloud Agents, and other Qoder features; a promotion offering 1,000 bonus credits on the first purchase and 500 on renewal was also announced.

  Usage details

  Who can use it: Individual users with a Qoder Global account worldwide; Lite, Pro, and higher-tier plans are available.

  How to use it: Open https://qoder.com/pricing with a Qoder Global account, click the Subscribe button for the Lite plan, and complete checkout.

  Tip: Preserve credits by choosing a cost-effective model such as Qwen3.8-Flash for routine tasks and a flagship model for long, complex tasks.

  ✓ Verified by official sourceModels: Qwen3.8-Flash, Qwen3.8-Max, DeepSeek-V4.1-Flash-1017, GLM-5.3-Flash, DeepSeek-V4-Pro, GLM-5.3, Kimi-K3, Kimi-K2.8-Preview, MiniMax-M3Source: Qoder Lite plan duyurusuSource: Qoder güncel fiyatlandırması
• 03 Nov
  CapabilityQoder CLI

  Qoder CLI preserves compressed history when reconnecting remotely

  Qoder CLI 1.1.82 fixed an issue that caused recent messages to disappear when resuming a compressed session after a remote connection was reestablished. Conversation context is expected to remain more complete after reconnecting during long sessions.

  Usage details

  Who can use it: Qoder CLI 1.1.82 and later; users with remote connections and compressed sessions.

  How to use it: Update the CLI to version 1.1.82 or later, resume the same session through the normal resume flow after a disconnection, and check that recent messages appear in the history.

  Tip: After reconnecting, verify that the last message and tool result are in the history before repeating tool calls with external effects.

  ✓ Verified by official sourceSource: Qoder CLI 1.1.82 resmi sürüm notları
• 03 Nov
  APIQoder CLI

  Qoder CLI can report terminal session status via OSC 7501

  Qoder CLI 1.1.82 added the ability to report session status to the terminal via the OSC 7501 protocol. Terminals or wrappers that support OSC 7501 can use these events to display or process session status.

  Usage details

  Who can use it: Qoder CLI 1.1.82 and terminal integrations that support OSC 7501.

  How to use it: Update Qoder CLI to version 1.1.82 or later and start a session in a terminal/wrapper that can read OSC 7501 events; status events will be emitted without requiring additional settings.

  Tip: If your terminal does not support OSC 7501, filter raw escape sequences or use a supporting terminal wrapper.

  ✓ Verified by official sourceSource: Qoder CLI 1.1.82 resmi sürüm notları
• 03 Nov
  AgentQwen Memory Agent

  Qwen Memory Agent introduced as an open-source, measurable persistent memory system

  Alibaba Cloud Community introduced Qwen Memory Agent, which runs on Qwen Cloud, as an open-source system offering persistent memory across sessions, invalidation of outdated information, and retrieval with a configurable token budget. The system provides HTTP and eight MCP tools, JSON/Markdown import and export, a live memory inspector, and a human-approved dreaming workflow.

  Usage details

  Who can use it: Open-source project; for developers using Qwen Cloud, Model Studio/DashScope, and Alibaba Cloud ECS. The official post provides links to the MIT-licensed source code and evaluations.

  How to use it: Get the source code via the Explore the project link in the official announcement, configure a Qwen Cloud/Model Studio API key, and deploy the FastAPI backend and live memory inspector.

  Tip: Keep dreaming changes subject to human approval rather than applying them automatically; start with a low retrieval token budget and adjust it to the task context.

  ✓ Verified by official sourceModels: Qwen Plus, qwen text-embedding-v3Source: Qwen Memory Agent duyurusu
• 03 Nov
  CapabilityQoder

  Qoder workspace and recent task lists no longer get stuck on refresh

  Qoder 0.5.3 fixed an issue that left workspace and recent task lists in an endless loading state during repeated updates. The goal is to make the list view more stable during refreshes.

  Usage details

  Who can use it: Qoder 0.5.3 and later; users of workspace and recent task lists.

  How to use it: Update Qoder to version 0.5.3 or later, then reopen and refresh the workspace or recent task list.

  Tip: Instead of refreshing the list repeatedly, wait for the status indicator to finish after a single refresh request.

  ✓ Verified by official sourceSource: Qoder 0.5.3 resmi sürüm notları
• 03 Nov
  CapabilityQoder

  Qoder can load old tasks with empty source session fields

  Qoder 0.5.3 fixed an issue that prevented the task list from loading because some past conversations had an empty source session value. These old records are now handled more safely instead of disrupting the list of valid tasks.

  Usage details

  Who can use it: Qoder 0.5.3 and later; users with past conversation and task records.

  How to use it: Upgrade Qoder to version 0.5.3 or later and reopen the past task list.

  Tip: On installations with historical data, update all devices to the same version; different client versions can make comparisons difficult.

  ✓ Verified by official sourceSource: Qoder 0.5.3 resmi sürüm notları
• 02 Nov
  AgentQoder Cloud Agents

  Qoder Cloud Agents introduces a continuous evaluation loop

  Qoder Cloud Agents introduced a continuous agent evaluation framework that uses the actual execution environment and evaluates traces, tool calls, responses, and outputs together. The release approach covers regression checks using isolated test sessions, baseline comparisons, custom datasets, and copies that do not affect production.

  Usage details

  Who can use it: Qoder Cloud Agents users; additional evaluation capabilities are expected to roll out gradually.

  How to use it: Create an evaluation dataset at https://qoder.com/cloud/quickstart, run representative cases, and compare the results from agent copies with the baseline.

  Tip: Include real production failures in the initial dataset, and check not only the final response but also the process and generated files.

  ✓ Verified by official sourceSource: Qoder Cloud Agents sürekli değerlendirme çerçevesi
• 02 Nov
  CapabilityQoder

  Startup, MCP, tool, and recovery speedups arrive for Qoder Fast

  Startup via bytecode, asynchronous preparation, Bash/Git warm-up, direct return of suitable WebFetch output, on-demand loading of MCP definitions, safe parallel tool execution, and interruption recovery have been improved in the Qoder Fast execution layer. Use of some optimizations depends on the entry point and configuration.

  Usage details

  Who can use it: Desktop clients, Agent SDK, and custom applications that use Qoder CLI’s shared session runner; some options depend on the entry point/configuration.

  How to use it: Select Fast from the model or tier selector in Qoder; for integrations using the CLI or SDK, start the task with the same session runner.

  Tip: If many MCP tools are connected, prefer loading tool definitions on demand; starting a new session for unrelated work reduces context.

  ✓ Verified by official sourceSource: Qoder Fast modunu hızlandıran harness güncellemeleri
• 02 Nov
  CapabilityQoder

  Qoder can resume stuck conversations after a background process crashes

  Qoder 0.5.2 fixes an issue where a conversation would get stuck and could not continue when a background execution process failed. The goal is to make the conversation flow reusable after a failed process.

  Usage details

  Who can use it: Qoder 0.5.2 and later; conversations that run tasks in the background.

  How to use it: Update the client to 0.5.2 or later; if a background process fails, reopen the same conversation and try the resume action again.

  Tip: For long-running tasks, check the latest tool output before resuming after the update; don’t automatically repeat commands with external side effects.

  ✓ Verified by official sourceSource: Qoder 0.5.2 resmi sürüm notları
• 02 Nov
  APIQwen Code SDK

  TypeScript SDK v0.1.27 bundles CLI 0.26.6

  Qwen Code TypeScript SDK v0.1.27 has been released and bundles Qwen Code CLI 0.26.6. Projects using the SDK can get the current runtime with this release without installing the CLI separately.

  Usage details

  Who can use it: TypeScript/JavaScript projects using Node.js 22 or later; @qwen-code/sdk on npm.

  How to use it: Run npm install @qwen-code/sdk@0.1.27 in your project and import the SDK from the @qwen-code/sdk package.

  Tip: Pin the version for reproducible builds and verify the bundled CLI version in CI after upgrading the package.

  ✓ Verified by official sourceSource: Qwen Code TypeScript SDK v0.1.27 sürümüSource: @qwen-code/sdk kurulum ve API belgesi
• 02 Nov
  CapabilityQwen Code

  Built-in review skill preserves model pairing in incremental reviews

  During marker recovery, the built-in review skill requires the fetch-pr command to pass --since-model along with --since. The instruction also uses the deltaFiles and interaction[] scope instead of the now-unused since..head range.

  Usage details

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

  How to use it: For an incremental review, run the fetch-pr command in the form --since <sha> --since-model <model>; get both values from the same marker or review cache record.

  Tip: Don’t infer the model identity from a separate source than the SHA; an incorrect pairing can cause the review to fall back to the full diff scope.

  ✓ Verified by official sourceSource: Qwen Code review skill anchor düzeltmesiSource: Qwen Code v0.26.6 sürüm notları
• 02 Nov
  CapabilityQoder

  Qoder fixes startup failure caused by invalid execution environment data

  Qoder 0.5.2 fixes an issue where invalid execution environment data in some older conversations caused startup and conversation-loading failures. Such historical records should no longer break app startup or conversation loading in the same way.

  Usage details

  Who can use it: Qoder 0.5.2 and later; users loading older conversation records.

  How to use it: Update Qoder to 0.5.2 or later, then reload the conversation that previously could not be opened.

  Tip: If the issue occurs only with older conversations, update the client before starting a new task; try reloading the records instead of deleting them.

  ✓ Verified by official sourceSource: Qoder 0.5.2 resmi sürüm notları
• 02 Nov
  CapabilityQoder

  A malformed task record no longer prevents other tasks from loading in Qoder

  Qoder 0.5.2 fixes an issue where malformed task records prevented other valid records in the task list from loading. The entire list should no longer become unusable because of a single corrupted record.

  Usage details

  Who can use it: Qoder 0.5.2 and later; all platforms that use the task list.

  How to use it: Upgrade the Qoder client to 0.5.2 or later, then reopen or refresh the task list.

  Tip: If refreshing the list doesn’t resolve the issue, open valid tasks first and back up critical outputs; consider removing the old record only as a last resort.

  ✓ Verified by official sourceSource: Qoder 0.5.2 resmi sürüm notları
• 02 Nov
  FeatureQwen Code

  VS Code session history now uses calendar weeks instead of a rolling 7 days

  Session history in Qwen Code Companion’s VS Code webview is now grouped by calendar week starting on Monday instead of a rolling 168 hours. As a result, the previous Saturday appears under Older rather than This Week at the start of the week.

  Usage details

  Who can use it: Qwen Code Companion’s VS Code webview session history.

  How to use it: Open the Qwen Code Companion chat view in VS Code and check the This Week and Older groups in the session history dropdown.

  Tip: On Mondays, look for sessions from the previous week under Older instead of This Week; search and the view layout are unchanged.

  ✓ Verified by official sourceSource: Qwen Code için VS Code takvim haftası düzeltmesiSource: Qwen Code v0.26.6 sürüm notları

New in this edition · 22

• 03 Nov
  Plugin / IntegrationDeepSeek Harness

  Change Request and Git worktree workflows are integrated with code review

  The experimental Change Request & Worktree feature lets you review local and PR diffs using a searchable file tree and file-by-file navigation. Selected code and comments can be sent to the Agent, and checks and review status can be tracked.

  Usage details

  Who can use it: DeepSeek Harness v0.2.2-alpha.3; experimental feature for local Git repositories and PR workflows.

  How to use it: Update to the latest version, open the Change Request & Worktree entry, and select a local or PR diff from the file tree; send selected code/comments to the Agent and track the checks.

  Tip: Keep the worktree separate before reviewing, and reduce context costs by sending the Agent only relevant files and comments.

  ✓ Verified by official sourceSource: DeepSeek Harness v0.2.2-alpha.3 sürüm notları
• 03 Nov
  SettingDeepSeek Harness

  Read-before-write and external-change checks are disabled by default for file changes

  Read-before-write and external-change protections are disabled by default; sandbox boundaries and the Review workflow remain in place. Profiles that want the old protections can explicitly restore the observation policy.

  Usage details

  Who can use it: DeepSeek Harness v0.2.2-alpha.3; profile-based file safety behavior.

  How to use it: Open your profile’s observation policy and explicitly enable the previous file protections; if you use the default behavior, approve changes in the Review view.

  Tip: Restore the previous read-before-write and external-change checks in production or shared repositories; don’t skip the Review check when prototyping quickly.

  ✓ Verified by official sourceSource: DeepSeek Harness v0.2.2-alpha.3 sürüm notları
• 03 Nov
  APIDeepSeek Harness SDK

  Command, plugin, and approval capabilities added to the TypeScript and Python SDKs

  The TypeScript and Python SDKs now support native commands and plugin management. Plan review, continuing toward a goal, and action approval are supported; the SDK must be restarted for plugin changes to take effect.

  Usage details

  Who can use it: TypeScript and Python SDKs included in DeepSeek Harness v0.2.2-alpha.3.

  How to use it: Update the SDK packages to versions compatible with v0.2.2-alpha.3, use native command/plugin management and approval workflows, and restart the SDK process after changing a plugin.

  Tip: Require plan review and action approval for automated tasks; deploy plugin updates as a separate restart step.

  ✓ Verified by official sourceSource: DeepSeek Harness v0.2.2-alpha.3 sürüm notları
• 03 Nov
  FeatureDeepSeek Harness

  The disabled-by-default apply_patch tool supports multi-file changes

  The new `apply_patch` tool can create, edit, delete, or move multiple files in a single call. You can review changes in the Review view, and the tool is disabled by default.

  Usage details

  Who can use it: DeepSeek Harness v0.2.2-alpha.3; optional tool enabled per profile.

  How to use it: Update to the latest version, explicitly enable the `apply_patch` tool in your profile, then request a multi-file change and open the Review view before applying it.

  Tip: Enable the tool only in trusted repositories, and pay particular attention to file deletions and moves before accepting the unified patch.

  ✓ Verified by official sourceSource: DeepSeek Harness v0.2.2-alpha.3 sürüm notları
• 03 Nov
  FeatureDeepSeek Harness

  Scheduled tasks moved to unified Host management

  Scheduled tasks are now managed through a single Host-level workflow. Users can create a task manually, edit it directly, or create it from a prefilled prompt in a session; drafts and conflict review are preserved.

  Usage details

  Who can use it: DeepSeek Harness v0.2.2-alpha.3; scheduled tasks run in reusable or new sessions.

  How to use it: Open Automation/Scheduled tasks to create or edit a task; optionally create one from a prefilled prompt in a session, then run it with an existing or new session.

  Tip: For complex scheduling expressions, save the draft and complete the conflict review; for simple name changes, keep the existing scheduling rule.

  ✓ Verified by official sourceSource: DeepSeek Harness v0.2.2-alpha.3 sürüm notları
• 03 Nov
  RetiredDeepSeek Harness

  The standalone Git worktree extension has moved to the unified workflow

  The Git worktree entry is now part of the Change Request & Worktree workflow. Users who previously enabled the standalone extension need to remove the old `@deepseek-ai/dsh-experimental-tool-worktree` entry from their profile.

  Usage details

  Who can use it: DeepSeek Harness v0.2.2-alpha.3; profiles using the old standalone worktree extension.

  How to use it: Open your profile file and remove the `@deepseek-ai/dsh-experimental-tool-worktree` entry from `dsh.profile.bundles`; then use the unified Change Request & Worktree entry.

  Tip: Back up your profile before migrating; don’t keep the old and unified worktree entries enabled at the same time.

  ✓ Verified by official sourceSource: DeepSeek Harness v0.2.2-alpha.3 sürüm notları
• 03 Nov
  FeatureDeepSeek Harness

  File previews now include a persistent folder tree and file location

  File previews now display a persistent folder tree and let you jump to the open file’s location in the tree. This makes it easier to navigate files in the same folder.

  Usage details

  Who can use it: DeepSeek Harness v0.2.2-alpha.3 preview release.

  How to use it: Open a text or Markdown file in the preview, use the pinned folder tree, and run the action to find/locate the current file in the tree.

  Tip: In large repositories, open the folder tree first and locate the target file; keep the preview context rather than searching for files from chat.

  ✓ Verified by official sourceSource: DeepSeek Harness v0.2.2-alpha.3 sürüm notları
• 03 Nov
  FeatureDeepSeek Harness

  Detailed diagnostics and the Host log are shown for plugin installation errors

  Plugin installation errors now show full diagnostic details and the location of the Host log. Installation failures are distinguished from failures to enable a plugin after installation.

  Usage details

  Who can use it: DeepSeek Harness v0.2.2-alpha.3; plugin manager.

  How to use it: When a plugin installation fails, open the error details, check the specified Host log, and determine whether the issue occurred during installation or activation.

  Tip: In support requests, share the full diagnostic text and Host log path, not just the error summary.

  ✓ Verified by official sourceSource: DeepSeek Harness v0.2.2-alpha.3 sürüm notları
• 03 Nov
  Plugin / IntegrationDeepSeek Harness

  Plugins can provide dynamic pi-ai headers based on session and request purpose

  Plugins can now send dynamic pi-ai HTTP headers based on the session ID and request purpose. Invalid headers are rejected before the request is sent.

  Usage details

  Who can use it: DeepSeek Harness v0.2.2-alpha.3; plugin developers using pi-ai.

  How to use it: Update your plugin for the alpha.3 API; tie header generation to the Session ID and request purpose, and handle validation errors before sending the request.

  Tip: Generate identity or authorization headers from session context instead of hardcoding them; catch invalid headers locally rather than leaving them to fail at the remote API.

  ✓ Verified by official sourceSource: DeepSeek Harness v0.2.2-alpha.3 sürüm notları
• 03 Nov
  CapabilityDeepSeek Harness

  Issues with legacy sessions, search, and loading compressed history fixed

  Alpha.3 fixes opening and searching sessions that contain legacy subagent definitions, continuing a chat after loading compressed history, and correctly naming and sorting empty sessions. These are usability and backward-compatibility improvements rather than new features.

  Usage details

  Who can use it: DeepSeek Harness v0.2.2-alpha.3; current and legacy sessions.

  How to use it: Update to the new version, open and search a legacy session, then send a new message after compressed history to use the recovery behavior.

  Tip: Export important sessions before updating; if the issue persists, include the Host log along with the session ID.

  ✓ Verified by official sourceSource: DeepSeek Harness v0.2.2-alpha.3 sürüm notları
• 03 Nov
  SettingDeepSeek Harness

  macOS Computer Use permissions are managed through a standalone app

  macOS Computer Use now requests system permissions through a standalone app. The app opens the relevant system setting, provides drag-and-drop guidance, and refreshes permission status when you return.

  Usage details

  Who can use it: DeepSeek Harness v0.2.2-alpha.3; macOS Computer Use.

  How to use it: Start Computer Use, go to the macOS system setting opened by the permission prompt, drag the indicated app into the relevant permissions list, and return to Harness.

  Tip: Refresh the status after returning from the permissions screen; authorize the standalone app shown rather than running the app directly from the terminal.

  ✓ Verified by official sourceSource: DeepSeek Harness v0.2.2-alpha.3 sürüm notları
• 03 Nov
  CapabilityDeepSeek Harness

  Markdown file links support line ranges and column positions

  Markdown file links in chat now accept line ranges and line-column suffixes. For invalid positions, the file still opens and the link remains a web link.

  Usage details

  Who can use it: DeepSeek Harness v0.2.2-alpha.3; chat file links.

  How to use it: Use a file link in chat with a line range or line-column suffix; for example, click a Markdown file link that specifies the target location.

  Tip: In code reviews, link only the relevant line range to give the Agent smaller, more focused context.

  ✓ Verified by official sourceSource: DeepSeek Harness v0.2.2-alpha.3 sürüm notları
• 03 Nov
  FeatureDeepSeek Harness

  Mobile sidebar and narrow-screen layout improved

  The mobile sidebar and narrow-screen layout have been redesigned. Session titles remain more stable, while model catalog entries and plugin discovery controls stay visible on narrow screens.

  Usage details

  Who can use it: DeepSeek Harness v0.2.2-alpha.3; mobile and narrow browser windows.

  How to use it: Update to the latest version and open Harness on a mobile device or in a narrow browser window; use the sidebar, model catalog, and plugin discovery screens directly.

  Tip: On a narrow screen, open the sidebar first and pin the session title; use visible filters for model and plugin searches instead of horizontal scrolling.

  ✓ Verified by official sourceSource: DeepSeek Harness v0.2.2-alpha.3 sürüm notları
• 03 Nov
  Plugin / IntegrationDeepSeek Harness

  Auto Review error before tool execution fixed on the OpenCode route

  Fixed an issue that caused Auto Review to fail before a tool ran on the OpenCode route. The review request is now sent with the relevant session ID and request purpose.

  Usage details

  Who can use it: DeepSeek Harness v0.2.2-alpha.3; OpenCode route and Auto Review.

  How to use it: Update to the latest version, start a session with the OpenCode provider, and use the Auto Review flow before a tool call; the session ID is passed automatically.

  Tip: Keep the tool and Auto Review flows in the same session to associate review decisions with the correct session.

  ✓ Verified by official sourceSource: DeepSeek Harness v0.2.2-alpha.3 sürüm notları
• 03 Nov
  FeatureDeepSeek Harness

  Unified menus for sessions, workspaces, and the sidebar

  v0.2.2-alpha.3 unified right-click and keyboard menus for sessions, workspaces, and the sidebar. The menu system also supports developer extensions.

  Usage details

  Who can use it: DeepSeek Harness v0.2.2-alpha.3 preview release.

  How to use it: Update to the latest version; right-click a session, workspace, or the sidebar, or use the relevant keyboard menu shortcut.

  Tip: Navigate faster on narrow screens by using the keyboard menu instead of the mouse for frequently used actions.

  ✓ Verified by official sourceSource: DeepSeek Harness v0.2.2-alpha.3 sürüm notları
• 03 Nov
  CapabilityDeepSeek Harness

  pi-ai conversations automatically drop older images when they exceed the image limit

  If a session’s image count exceeds the request limit for models connected through pi-ai, the oldest images are automatically dropped and the request continues. This prevents repeated errors caused by the image limit.

  Usage details

  Who can use it: DeepSeek Harness v0.2.2-alpha.3; models connected through the pi-ai provider.

  How to use it: Use a session with images and a pi-ai model; if the image count exceeds the request limit, the version automatically drops older images.

  Tip: In long image sessions, re-add critical images later; automatic dropping affects the oldest images.

  ✓ Verified by official sourceSource: DeepSeek Harness v0.2.2-alpha.3 sürüm notları
• 03 Nov
  CapabilityDeepSeek Harness

  Subcalls can be collapsed individually in the Trajectory view

  Trajectory now lets you collapse subcalls independently while keeping the parent call and its summary visible. You can reopen a subcall through search or by navigating from another view.

  Usage details

  Who can use it: DeepSeek Harness v0.2.2-alpha.3; developer tools and the Trajectory view.

  How to use it: Open a session’s Trajectory view and use the collapse control for the relevant subcall; reopen it from a search result or a cross-view link.

  Tip: For long agent runs, leave open only subcalls that failed or invoked tools; this makes the summary stream faster to scan.

  ✓ Verified by official sourceSource: DeepSeek Harness v0.2.2-alpha.3 sürüm notları
• 03 Nov
  FeatureDeepSeek Harness

  Plugin settings pages support custom navigation icons

  Plugins can provide a navigation icon for their settings pages. The default icon automatically returns when a plugin is removed.

  Usage details

  Who can use it: DeepSeek Harness v0.2.2-alpha.3; plugin developers and installed plugins.

  How to use it: Add the navigation icon to your plugin’s settings page definition and update Harness; check that the default icon returns when the plugin is removed.

  Tip: Use a consistent icon style across a plugin family; customize an icon only when it genuinely helps distinguish the settings page’s function.

  ✓ Verified by official sourceSource: DeepSeek Harness v0.2.2-alpha.3 sürüm notları
• 03 Nov
  CapabilityDeepSeek Harness

  Menus and floating panels now stay within the visible area

  Menus and floating panels track browser zoom, scrolling, and on-screen keyboard changes to stay within the visible area as much as possible. This improves accessibility, especially on touch devices and small screens.

  Usage details

  Who can use it: DeepSeek Harness v0.2.2-alpha.3; web interface.

  How to use it: Update to the new version; open a panel in a window with zoom enabled, scrolled, or with the on-screen keyboard open to use automatic positioning.

  Tip: If a panel is partly off-screen on mobile, close and reopen it instead of resizing the window; the new layout adapts to the visible area.

  ✓ Verified by official sourceSource: DeepSeek Harness v0.2.2-alpha.3 sürüm notları
• 03 Nov
  FeatureDeepSeek Harness

  Text and Markdown previews preserve reading position after refresh

  Text and Markdown file previews now preserve the current reading position after a refresh. Even if the file temporarily gets shorter, the view no longer unnecessarily jumps back to the beginning.

  Usage details

  Who can use it: DeepSeek Harness v0.2.2-alpha.3; text and Markdown previews.

  How to use it: Open a file in preview, scroll down, then refresh or update the file; the preview keeps your place.

  Tip: Refresh while monitoring long log or output files without having to scan for changes from the beginning each time.

  ✓ Verified by official sourceSource: DeepSeek Harness v0.2.2-alpha.3 sürüm notları
• 03 Nov
  CapabilityDeepSeek Harness

  Session updates and long-response streaming use less processing overhead

  Alpha.3 reduces duplicate emissions and catalog operations in session state updates. Streaming and assembling long responses also incurs lower runtime overhead.

  Usage details

  Who can use it: DeepSeek Harness v0.2.2-alpha.3; long responses and intensive session states.

  How to use it: Update to the new version and run a long streaming response or a session with many updates; the performance improvement is applied automatically.

  Tip: Reduce unnecessary parallel session emissions during long tasks; compare streaming latency on the same task after updating.

  ✓ Verified by official sourceSource: DeepSeek Harness v0.2.2-alpha.3 sürüm notları
• 02 Nov
  AgentDeepSeek Harness

  Create plugins from chat with Creator Mode in DeepSeek Harness

  DeepSeek Harness introduced Creator Mode, which turns ideas described in natural language into usable plugins. The official announcement showcases examples such as a design workspace, a sandbox game, and a 3D LLM visualizer.

  Usage details

  Who can use it: DeepSeek Harness users; offered as a worldwide public preview on the product page.

  How to use it: Open DeepSeek Harness, select Creator mode in a new session, and describe the plugin you want to create in natural language; install and validate the resulting plugin.

  Tip: In your initial request, define the plugin’s purpose, interface, and security boundaries together; check the generated files and permissions in the Review view before installing.

  ✓ Verified by official sourceSource: DeepSeek’in Creator Mode duyurusuSource: DeepSeek Harness resmî ürün sayfası

New in this edition · 28

• 03 Nov
  SettingZCode

  Subtask permissions retain the same restrictions as the main session

  Subtask permissions now match the main session’s permissions. In Plan Mode, subtasks remain subject to the same restrictions.

  Usage details

  Who can use it: ZCode v3.17.2 and later; users who use subtasks or multiple agents.

  How to use it: Start a multi-agent task in Plan Mode and check that subtask permissions match the main session’s.

  Tip: Before starting parallel subtasks, keep the main session’s access scope to the minimum necessary.

  ✓ Verified by official sourceSource: ZCode Releases & Updates — v3.17.2
• 03 Nov
  FeatureAutoClaw

  Goal Mode introduced in AutoClaw for multi-step tasks

  AutoClaw Goal Mode takes a verifiable output and completion criteria from the user, then plans, executes, and repeatedly evaluates the task. If evidence or conditions are missing, it can start another work cycle.

  Usage details

  Who can use it: AutoClaw users; available in a new conversation. No plan or country restrictions specified.

  How to use it: Open a new conversation, select Goal Mode from the input field, set a suggested or custom goal, add inputs and completion criteria, and submit.

  Tip: Write the goal not just as a task, but with acceptance evidence such as a file location, test result, or source link.

  ✓ Verified by official sourceSource: How to Use AutoClaw Goal Mode for Multi-Step Tasks
• 03 Nov
  CapabilityZCode

  Multi-session cursor support for Computer Use

  Computer Use now supports separate cursors for multiple sessions. This reduces interference between simultaneous or parallel computer interactions.

  Usage details

  Who can use it: ZCode v3.17.2 and later; users who use Computer Use.

  How to use it: Start multiple Computer Use sessions and carry out tasks using each session’s own cursor.

  Tip: Assign different tasks to each session and clearly specify its target application.

  ✓ Verified by official sourceSource: ZCode Releases & Updates — v3.17.2
• 03 Nov
  SettingZCode

  MCP settings detection restricted to registered workspaces

  Access to MCP settings detection has been restricted to registered workspaces only. This reduces the chance of settings in other locations being read accidentally.

  Usage details

  Who can use it: ZCode v3.17.2 and later; workspaces where MCP settings are detected.

  How to use it: Register the workspace in ZCode, then have it detect MCP settings through the configuration interface.

  Tip: Keep MCP configuration files only in the workspaces where you need them.

  ✓ Verified by official sourceSource: ZCode Releases & Updates — v3.17.2
• 03 Nov
  Plugin / IntegrationZCode

  Start MCP servers on computers without Node installed

  MCP servers can now start normally on computers without Node installed. This reduces setup barriers on remote or restricted machines that use MCP.

  Usage details

  Who can use it: ZCode v3.17.2 and later; computers that use MCP servers. No separate operating system or plan restriction was specified.

  How to use it: Add the MCP server to your ZCode configuration and start it; Node does not need to be installed separately on the target computer.

  Tip: Still check the MCP server’s own runtime requirements in its installation notes.

  ✓ Verified by official sourceSource: ZCode Releases & Updates — v3.17.2
• 03 Nov
  Pricing / PlanZCode

  Off-peak packages no longer renew automatically when they expire

  Off-peak packages no longer renew automatically after they expire. This reduces the risk of unwanted renewal charges for expired packages.

  Usage details

  Who can use it: ZCode Off-peak package users; v3.17.2 and later. Regional payment terms were not specified.

  How to use it: Use the package as usual; when it expires, check the plan or payment screen to confirm that it has not renewed automatically.

  Tip: Still check your account and payment history regularly to verify the package status.

  ✓ Verified by official sourceSource: ZCode Releases & Updates — v3.17.2
• 03 Nov
  SettingZCode

  Permission confirmation required for scripts in custom commands

  Scripts run by custom commands now require permission confirmation before execution. This reduces the risk of unexpected code execution through custom commands.

  Usage details

  Who can use it: ZCode v3.17.2 and later; users who use custom commands.

  How to use it: Run the custom command, review the permission prompt shown, and approve only the expected script.

  Tip: Regularly review the script contents and file access of custom commands you use frequently.

  ✓ Verified by official sourceSource: ZCode Releases & Updates — v3.17.2
• 03 Nov
  SettingZCode

  High-risk actions can no longer be approved in Plan Mode

  The behavior that allowed high-risk actions to be approved accidentally in Plan Mode has been fixed. These actions are now blocked under plan constraints.

  Usage details

  Who can use it: ZCode v3.17.2 and later; all users who use Plan Mode.

  How to use it: Run a task in Plan Mode and confirm that the approval flow blocks the action when a high-risk action is proposed.

  Tip: Use the planning phase only for review and preparation; initiate actual changes in a separate, controlled execution phase.

  ✓ Verified by official sourceSource: ZCode Releases & Updates — v3.17.2
• 03 Nov
  SettingZCode

  Access scope for local web previews narrowed

  The scope of local web page previews’ access has been restricted for security. This change reduces unnecessary access to local files and resources.

  Usage details

  Who can use it: ZCode v3.17.2 and later; users who use local web previews.

  How to use it: Open the local web preview as usual, then verify that it accesses only resources within the permitted scope.

  Tip: If the preview does not work, move the required resource into the saved workspace instead of sharing files broadly.

  ✓ Verified by official sourceSource: ZCode Releases & Updates — v3.17.2
• 03 Nov
  CapabilityZCode

  ZCode automatically resumes workflows paused by quota limits

  Workflows paused because of quota limits now resume automatically when the quota resets. Users do not need to restart the task manually.

  Usage details

  Who can use it: ZCode v3.17.2 and later; workflows that use quotas. Quota terms may vary by plan.

  How to use it: Run a workflow as usual. If it pauses because of a quota limit, expect the same workflow to resume automatically when the quota renews.

  Tip: For long workflows, monitor quota renewal times and any additional usage caused by automatic resumption.

  ✓ Verified by official sourceSource: ZCode Releases & Updates — v3.17.2
• 03 Nov
  Plugin / IntegrationZCode

  One-click website deployment with the ZCode Sites plugin

  ZCode v3.17.2 adds the official ZCode Sites plugin. The plugin supports deploying generated websites with one click.

  Usage details

  Who can use it: Desktop users running ZCode v3.17.2; no plan or platform restrictions specified.

  How to use it: Install the official ZCode Sites plugin from the plugin store, then use the plugin’s one-click website deployment action.

  Tip: Before deployment, check the preview and the files that will be sent to the production environment.

  ✓ Verified by official sourceSource: ZCode Releases & Updates — v3.17.2
• 03 Nov
  SettingZCode

  Kimi K3.1 Pro and MiniMax M3.1 Flash settings in ZCode

  New model configuration options have been added to ZCode for Kimi K3.1 Pro, MiniMax M3.1 Flash, and other models. Users can now select these providers and models in the configuration flow.

  Usage details

  Who can use it: ZCode v3.17.2 and later; users with access to supported models. No separate plan or country list was provided.

  How to use it: Open the model configuration screen or model picker, enter the required access details for Kimi K3.1 Pro or MiniMax M3.1 Flash, and save.

  Tip: For long coding tasks, compare context windows, speed, and quota limits before selecting a model.

  ✓ Verified by official sourceModels: Kimi K3.1 Pro, MiniMax M3.1 FlashSource: ZCode Releases & Updates — v3.17.2
• 03 Nov
  FeatureZCode

  Options to reveal files in Finder/Explorer

  File cards, inline links, and the open menu now offer an option to reveal a file in Finder or Explorer.

  Usage details

  Who can use it: ZCode v3.17.2 and later; users of the macOS and Windows file explorers.

  How to use it: Right-click the file in a file card, inline link, or the open menu, then select Show in Finder/Explorer.

  Tip: If there are multiple similar files, reveal the file’s location to quickly verify the correct output.

  ✓ Verified by official sourceSource: ZCode Releases & Updates — v3.17.2
• 03 Nov
  CapabilityZCode

  Security-blocked responses now return an error quickly instead of retrying

  When a response is blocked by the security policy, ZCode now reports an error quickly instead of retrying repeatedly. This lets users see the reason for the block sooner.

  Usage details

  Who can use it: ZCode v3.17.2 and later; responses blocked by the security policy.

  How to use it: Submit a task that may be blocked by the security policy; when a block occurs, review the error notification.

  Tip: Instead of resubmitting the same request, narrow down the blocked content or action safely.

  ✓ Verified by official sourceSource: ZCode Releases & Updates — v3.17.2
• 03 Nov
  CapabilityZCode

  Repetitions without progress automatically stopped and reported

  Repeated executions that make no progress are now automatically stopped, and users are notified. This is intended to limit wasted time and token usage.

  Usage details

  Who can use it: ZCode v3.17.2 and later; tasks experiencing repeated execution.

  How to use it: Run the task as usual; if the system detects no progress, it will stop execution and show a notification.

  Tip: After an automatic stop, narrow down the faulty step or target condition instead of repeating the task with the same instructions.

  ✓ Verified by official sourceSource: ZCode Releases & Updates — v3.17.2
• 03 Nov
  CapabilityZCode

  More detailed causes and solutions for MCP startup errors

  MCP startup failures now show more specific causes and suggested solutions. Troubleshooting relies less on generic error messages.

  Usage details

  Who can use it: ZCode v3.17.2 and later; users who use MCP.

  How to use it: Start an MCP server. If an error occurs, follow the displayed cause and solution steps to fix the MCP configuration.

  Tip: Include the server name, workspace, and permission details from the error message in your support ticket.

  ✓ Verified by official sourceSource: ZCode Releases & Updates — v3.17.2
• 03 Nov
  CapabilityZCode

  Stop and restart remote device services from the menu

  Controls for stopping and restarting the relevant remote services have been added to the remote device menu. This reduces the need to go to the device to troubleshoot issues.

  Usage details

  Who can use it: ZCode v3.17.2 and later; users with a remote device connection.

  How to use it: Open the device menu in the remote devices list under Settings, then select Stop service or Restart service.

  Tip: Before restarting, check whether active tasks on that device could be interrupted.

  ✓ Verified by official sourceSource: ZCode Releases & Updates — v3.17.2
• 03 Nov
  SettingZCode

  Remote data synchronization consolidated in Settings

  Options related to remote data synchronization have been consolidated in one place in ZCode Settings. This simplifies access to synchronization configuration.

  Usage details

  Who can use it: ZCode v3.17.2 and later; users with a remote session or device.

  How to use it: Open the Settings page and manage the relevant options in the remote data synchronization section.

  Tip: If you use multiple remote devices, check the synchronization behavior before starting a task.

  ✓ Verified by official sourceSource: ZCode Releases & Updates — v3.17.2
• 03 Nov
  Plugin / IntegrationZCode

  WeChat automation result notifications are working again

  Notifications for the results of WeChat automation tasks have been restored. This brings back the ability to receive results through WeChat when a task is complete.

  Usage details

  Who can use it: ZCode v3.17.2 and later; users of the WeChat automation integration.

  How to use it: Run a WeChat automation task and check the result notification in the linked WeChat account when the task is complete.

  Tip: If no notification arrives, first check WeChat authorization and the task account connection.

  ✓ Verified by official sourceSource: ZCode Releases & Updates — v3.17.2
• 03 Nov
  CapabilityZCode

  Built-in tool calls and results fully visible

  The model’s process for calling built-in tools and the results of those calls are now fully shown to users. This makes it easier to monitor the task flow.

  Usage details

  Who can use it: ZCode v3.17.2 and later; tasks that use built-in tools.

  How to use it: Run a task that uses built-in tools, then open and review the tool call and result sections in the conversation.

  Tip: If you see unexpected results, check which tool the model called and what inputs it used.

  ✓ Verified by official sourceSource: ZCode Releases & Updates — v3.17.2
• 03 Nov
  SettingZCode

  Bulk project management and data cleanup in ZCode Settings

  The Settings page now lets users manage projects in bulk. An option has also been added to delete associated data when deleting a project.

  Usage details

  Who can use it: ZCode v3.17.2 and later; desktop users who manage projects.

  How to use it: Open project management on the Settings page, select multiple projects, and check the option to delete data when deleting them.

  Tip: Before deleting, separate projects you no longer need from work data you need to keep.

  ✓ Verified by official sourceSource: ZCode Releases & Updates — v3.17.2
• 03 Nov
  FeatureZCode

  Update all ZCode plugins with one click

  Plugin management can now update all installed plugins in a single operation. This eliminates the need to update plugins one at a time.

  Usage details

  Who can use it: ZCode v3.17.2 and later; users who use the plugin manager.

  How to use it: Open the plugin management or store screen and run the option to update all plugins.

  Tip: Before bulk updating, finish any running tasks and note the versions of critical plugins.

  ✓ Verified by official sourceSource: ZCode Releases & Updates — v3.17.2
• 03 Nov
  FeatureZCode

  Annotate ZCode image previews and send them as attachments

  Image previews now support annotation and markup edits. The edited image can be sent in the conversation as an attachment.

  Usage details

  Who can use it: ZCode v3.17.2 and later; users who use image previews.

  How to use it: Open an image in preview, use the annotation editor, and send the result in the conversation as an attachment.

  Tip: When reviewing code, mark the problematic area and send it with a short instruction.

  ✓ Verified by official sourceSource: ZCode Releases & Updates — v3.17.2
• 03 Nov
  FeatureZCode

  ZCode moves remote devices to a searchable compact list

  Remote devices are now displayed in a compact, searchable list that takes up less space. This makes it easier to choose from many devices.

  Usage details

  Who can use it: ZCode v3.17.2 and later; users managing remote devices.

  How to use it: Open the remote devices section in Settings and type the device name in the search field to find it.

  Tip: Give devices clear names to narrow down search results faster.

  ✓ Verified by official sourceSource: ZCode Releases & Updates — v3.17.2
• 03 Nov
  SettingZCode

  Draft MCP configuration interface added to ZCode

  ZCode has added a draft configuration interface for managing MCP servers. Because the interface is a draft, its behavior or fields may change in the future.

  Usage details

  Who can use it: ZCode v3.17.2 and later; users who use MCP. The feature is marked as a draft.

  How to use it: Open the MCP configuration interface in ZCode Settings, enter the server settings, then save and test the connection.

  Tip: When using the draft interface, also keep a backup of the MCP configuration in a separate file.

  ✓ Verified by official sourceSource: ZCode Releases & Updates — v3.17.2
• 03 Nov
  FeatureZCode

  Preview cards now open when you click anywhere on the card

  Preview cards can now be opened by clicking anywhere on the card, rather than only on a specific link.

  Usage details

  Who can use it: ZCode v3.17.2 and later; users who see preview cards.

  How to use it: Click anywhere on a preview card to open it.

  Tip: Click directly on the card body instead of looking for the small link.

  ✓ Verified by official sourceSource: ZCode Releases & Updates — v3.17.2
• 03 Nov
  SettingZCode

  Unread filter for ZCode tasks

  A new filter was added to show only unread tasks in the task list.

  Usage details

  Who can use it: ZCode v3.17.2 and later; all task list users.

  How to use it: Open the Tasks view and select the Unread filter from the filter options.

  Tip: Use this filter to quickly scan notifications for work completed in the background.

  ✓ Verified by official sourceSource: ZCode Releases & Updates — v3.17.2
• 03 Nov
  SettingZCode

  ZCode tray badge removed; unread status remains on the taskbar

  The unread red badge is no longer shown on the ZCode system tray icon. Unread status remains visible on the Windows taskbar.

  Usage details

  Who can use it: ZCode v3.17.2 and later; Windows desktop users.

  How to use it: Track tasks completed in the background using the unread status on the Windows taskbar; don’t look for a badge in the system tray.

  Tip: Pin ZCode to the taskbar and keep taskbar badges enabled so you don’t miss notifications.

  ✓ Verified by official sourceSource: ZCode Releases & Updates — v3.17.2