TOP 10 unchanged; Chat and Work are merging in ChatGPT, with a shared quota coming for Codex

New in this edition · 2

• 02 Nov
  RetiredGoogle Antigravity

  Google Antigravity: Removal date arrives for Claude 4.6 and GPT-OSS 120B

  Google Antigravity’s official model table says Claude Sonnet 4.6, Claude Opus 4.6, and GPT-OSS 120B will be removed on November 2, 2026. You need to move workflows using these models to Gemini 3.8 Flash, which is available for your plan in Antigravity, or to Gemini 4 Argon if you have an eligible paid Google AI Pro or Ultra account.

  Usage details

  Who can use it: Affects model selection in Antigravity App, Antigravity CLI, and Antigravity IDE. Claude Sonnet 4.6 and Claude Opus 4.6 were listed in the free/Plus and Pro tables, while GPT-OSS 120B was listed in the free/Plus, Pro, and Ultra tables; none of these three models are listed for Enterprise.

  How to use it: In Antigravity, select Gemini 3.8 Flash from the model picker below the chat prompt. If you have a paid Google AI Pro or Ultra account, switch to Gemini 4 Argon from the same picker and retest important tasks with the new model.

  Tip: Before the removal date, run a comparison test on Gemini 3.8 Flash for your critical prompts and simplify model-specific instructions; this helps reduce sudden behavior differences in production workflows.

  ✓ Verified by official sourceModels: Claude Sonnet 4.6, Claude Opus 4.6, GPT-OSS 120BSource: Google Antigravity Docs: Model seçimi
• 31 Oct
  OtherGemini CLI

  Gemini CLI nightly: file path, streaming, and custom theme fixes arrive

  The October 31 nightly release respects .git/info/exclude and core.excludesFile rules in shadow repos, canonicalizes symbolic link paths, and handles the zero-device stat condition on Windows. It also flushes pending SSE events at the end of a stream and adds the active and focus keys to the custom theme interface schema; these are separate changes from the known model selection and extension installation fixes.

  Usage details

  Who can use it: Gemini CLI v0.67.0-nightly.20261031.g6814e00d6; especially relevant to Windows users, repositories with symbolic links, users of shadow repos, and those defining custom themes.

  How to use it: Update your Gemini CLI nightly installation to v0.67.0-nightly.20261031.g6814e00d6. If you have a custom theme schema, use the active and focus keys; you don’t need to enable any other settings.

  Tip: After updating, verify file search and ignore rules in large or symbolic-link-heavy repositories, and test the secure file-reading workflow on Windows in a small test repository.

  ✓ Verified by official sourceSource: Gemini CLI v0.67.0-nightly.20261031 sürüm notları

New in this edition · 34

• 31 Oct
  SettingClaude Code

  Fixed file uploads from outside the workspace in `--restricted` sessions

  In `--restricted` sessions, uploads from outside working directories are now blocked, even if a Read permission rule covers external paths.

  Usage details

  Who can use it: Claude Code sessions using `--restricted`.

  How to use it: Start the session with `claude --restricted` and upload files only from within working directories; external paths will now be rejected.

  Tip: Test access to a file in a parent directory outside the workspace to verify your restricted session policy.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  FeatureClaude Code

  Plan restoration after `/clear` or `/resume` fixed

  Fixed a rare bug where resuming a conversation after using `/clear` or `/resume` while part of the conversation was still being saved would not restore the plan.

  Usage details

  Who can use it: All users who resume planned sessions in Claude Code.

  How to use it: Update Claude Code; resume a conversation after `/resume` or `/clear` in a planned session, then check the plan status.

  Tip: Exporting critical plans at the end of a session provides extra protection against rare save issues.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  APIClaude Code CLI

  `claude -p` reports the reason more accurately when Auto mode stops

  Fixed an issue where `claude -p` text output did not state the reason when an Auto mode turn stopped while a background agent was still running.

  Usage details

  Who can use it: CLI and automation workflows using `claude -p`.

  How to use it: Update Claude Code and run an Auto mode workflow with `claude -p`; read the standard text output when it stops.

  Tip: In CI scripts, save the output and classify an Auto mode safety stop separately from an actual process error.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  Plugin / IntegrationClaude Code

  `claude auth login` works in managed environments that require a gateway

  Fixed an issue where the `claude auth login` command was rejected when managed settings required a Claude apps gateway. The terminal now displays the gateway sign-in flow.

  Usage details

  Who can use it: Team or Enterprise-managed Claude Code environments.

  How to use it: Run `claude auth login` in the terminal and complete the displayed Claude apps gateway sign-in steps.

  Tip: If your organization uses a gateway, use the organization’s gateway sign-in flow rather than a personal API key.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  AgentClaude Code

  Subagents no longer switch to the parent model by mistake when they wake up

  Fixed a bug that caused a subagent to switch back to the parent model when a background task or message woke it up, even though it had inherited its model from its parent subagent.

  Usage details

  Who can use it: Claude Code subagents and background tasks.

  How to use it: Update Claude Code; wake a subagent with an explicitly specified model using a background task, then check the model in the session transcript.

  Tip: Explicitly specifying the model name in the task description for critical subagents makes inheritance behavior easier to observe.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  FeatureClaude Artifacts

  Artifact database access rules are displayed correctly

  Fixed an issue where database access rules in the Artifact tool appeared as `?` at the `self` level. If there is a risk that rules could be deleted during publication, the rules are now quoted correctly when republishing is rejected.

  Usage details

  Who can use it: Claude users who use the Claude Code Artifact tool.

  How to use it: Update Claude Code, then open the flow to republish an Artifact or review its database access settings.

  Tip: Check the Artifact’s `self` access rules before publishing; don’t leave broad permissions enabled by default.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  SettingClaude Code

  Auto-compact context warning appears for unknown model names

  When a model unknown to this Claude Code version is selected with `/model <id>`, users are now notified that auto-compact will assume a 200K context window.

  Usage details

  Who can use it: Claude Code users with custom model names or gateway deployments.

  How to use it: Run `/model <id>` during a session; note the 200K context warning that appears for an unrecognized model.

  Tip: Verify the correct context window for custom model deployments; an incorrect assumption can cause compaction or limit issues.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  CapabilityClaude Code

  `/diff` refreshes run fewer and less frequent Git commands in large repositories

  In large repositories, `/diff` refreshes generally run one fewer full-repository Git command. If Git is slow, delays are added between refreshes to reduce UI load.

  Usage details

  Who can use it: Users running Claude Code `/diff` in large Git repositories.

  How to use it: Update Claude Code, run `/diff` in a large repository, and refresh the file changes.

  Tip: In very large repositories, reviewing only the relevant files or subdirectory is still faster.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  CapabilityClaude Code

  Claude Code no longer leaves shell commands running in the background when it exits

  When Claude Code exits on its own on macOS and Linux—for example, when credentials are rejected or a cloud session is archived—it now terminates open shell commands.

  Usage details

  Who can use it: macOS and Linux users running Claude Code 2.1.316.

  How to use it: Update Claude Code and use it normally; no separate setting needs to be enabled.

  Tip: After authentication or cloud session errors, also review the output of `ps` and `jobs` to check for processes left running in the background.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  Plugin / IntegrationClaude Tag

  Claude Tag can edit a shared Slack canvas

  Fixed an issue that prevented Claude from adding to or editing a canvas from the Slack channel where it was created after the canvas was shared with another channel or DM.

  Usage details

  Who can use it: Enterprise Claude Tag organizations connected to Slack.

  How to use it: Update Claude Tag, share the canvas with another channel or DM, then request an edit from the Slack channel where it was created.

  Tip: Before expanding canvas sharing, test a small edit from the source channel.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  AvailabilityClaude Code cloud sessions

  Cloud tasks now fail correctly when Auto mode has no decision

  Fixed an issue where cloud sessions and cloud scheduled tasks were not marked as failed when Auto mode stopped a turn because it received no safety decision from the server.

  Usage details

  Who can use it: Users of Claude Code cloud sessions and cloud scheduled tasks.

  How to use it: Run a cloud session or scheduled task; if Auto mode cannot make a safety decision, the status in the run history and the notification will now show the failure.

  Tip: When monitoring automated tasks, check the run status and error notification as well as the final message.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  APIClaude apps gateway

  Gateway now validates all requested models against allowlists

  Claude apps gateway checks every model named in a request against the `availableModels`, `deniedModels`, and `models` fields. If a model is blocked, it now returns a 400 error identifying the field causing the issue.

  Usage details

  Who can use it: Claude apps gateway administrators and applications sending requests through the gateway.

  How to use it: Check the model fields in your gateway configuration and match all model names in the request against the allowlist.

  Tip: Before deployment, run a negative test with a blocked model for each model field to verify the field name in the 400 response.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  SettingClaude Code

  Auto mode server in the host app is enabled even behind a proxy

  `CLAUDE_CODE_AUTO_MODE_SERVER=1` is no longer ignored in sessions started from a host app such as Claude Desktop behind a proxy or LLM gateway when experimental betas are disabled.

  Usage details

  Who can use it: Users running Claude Code through a host app, proxy, or LLM gateway.

  How to use it: Set `CLAUDE_CODE_AUTO_MODE_SERVER=1` in the environment, update Claude Code, and start a new session from the host app.

  Tip: If your organization’s proxy filters experimental beta headers, also review the connection logs for the Auto mode server.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  APIClaude Code

  Fixed exit code 2 blocking in PowerShell hooks

  Fixed an issue that prevented PowerShell hooks returning exit code 2 from blocking when a command started with `type cast`, `param`, `using`, or an attribute.

  Usage details

  Who can use it: Windows users running Claude Code hooks with PowerShell.

  How to use it: Update Claude Code and run your existing PowerShell hook with the same exit code 2 flow; no additional configuration is required.

  Tip: Test blocking behavior in security hooks using both the exit code and the error log.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  Plugin / IntegrationClaude Code self-hosted runner

  MCP on/off state preserved when the runner changes machines

  Fixed an issue where an MCP server’s on/off switch state was lost when a session moved to a new machine on a self-hosted runner.

  Usage details

  Who can use it: Organizations using MCP servers on a self-hosted runner.

  How to use it: Update the runner, move a session to another machine, and verify the MCP server’s status via `/mcp`.

  Tip: Also define MCP status explicitly in the configuration file in production; don’t rely only on the UI state.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  APIClaude Agent SDK

  SDK `register_repo_root` now loads the external directory’s CLAUDE.md file

  Fixed an issue where the SDK failed to load a directory’s `CLAUDE.md` file when a `register_repo_root` request was made for a directory outside the working directory while `CLAUDE_CODE_ADDITIONAL_DIRECTORIES_CLAUDE_MD=1` was active.

  Usage details

  Who can use it: Developers using Claude Agent SDK who read instructions from additional directories.

  How to use it: Enable the environment variable, call `register_repo_root` in the SDK, and provide the additional directory’s `CLAUDE.md` file at the start of the session.

  Tip: Use a distinctive, harmless rule in an SDK test to verify that additional instructions are applied.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  AgentClaude Code self-hosted runner

  No stale response sent after Stop on self-hosted runner

  Fixed a race condition that could cause a message sent while Claude was running to be answered incorrectly after Stop, once the session process had changed.

  Usage details

  Who can use it: Organizations using Claude Code self-hosted runner.

  How to use it: Update the runner and, in an active session, press Stop and verify that it has stopped before sending a new message.

  Tip: In workflows, starting a new task in a new session instead of the same session after Stop reduces confusion.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  Plugin / IntegrationClaude Tag

  Unlabeled Claude replies no longer go missing in Slack Connect

  Fixed an issue that left unlabeled replies unanswered in Slack Connect threads where Slack delivered the reply to the other organization’s app when Claude was installed in both organizations.

  Usage details

  Who can use it: Slack Connect threads with Claude Tag installed and Enterprise organizations.

  How to use it: Update Claude Tag, then send an unlabeled follow-up message in a Slack Connect thread shared by two organizations.

  Tip: When Claude is installed on both sides, use channel notes to track which organization’s app replies in the thread.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  AvailabilityClaude Code

  Fallback to an older model on Vertex AI and Bedrock is fixed when a new model is unavailable

  When the newest model is selected on Vertex AI or Amazon Bedrock before the account or region has access to it, fallback to an older model in the same family now works again instead of showing an error mid-session.

  Usage details

  Who can use it: Accounts and regions using Claude Code connections to Vertex AI or Amazon Bedrock.

  How to use it: Use one of the `sonnet`, `opus`, or `haiku` aliases; Claude Code 2.1.316 will automatically fall back to an accessible older model.

  Tip: To verify regional model rollouts, check the provider’s model catalog alongside the Claude Code session log.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  SettingClaude Code for VS Code

  Approved plans no longer switch to Auto mode after VS Code reload

  Fixed an issue that caused a conversation whose plan had been approved with “Yes, and manually approve edits” to switch to Auto mode after a reload or startup.

  Usage details

  Who can use it: Sessions using plan approval in Claude Code for VS Code.

  How to use it: Update the extension, approve the plan with manual edit approval, and check the permission mode after reloading the window.

  Tip: If code changes are sensitive, quickly verify the permission mode and plan status after a reload.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  FeatureClaude Code for VS Code

  Effort and Ultracode controls appear for `[1m]` model tags in VS Code

  Fixed an issue where the Effort slider, Ultracode toggle, and model name disappeared when the model setting included a `[1m]` tag, such as `opus[1m]`.

  Usage details

  Who can use it: Claude Code for VS Code users; model settings tagged with `[1m]`.

  How to use it: Update the VS Code extension, open the Claude panel, and use the Effort/Ultracode controls while a model tagged with `[1m]` is selected.

  Tip: When using a model with 1M context, verify both the model tag and Effort level before starting a session.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  FeatureClaude Code

  Push-to-talk hint no longer disappears too early in a session

  Fixed an issue where the “Hold space to speak” hint used up its three displays too early in a session and showed a blank key when no push-to-talk key was bound.

  Usage details

  Who can use it: Claude Code terminal users who use push-to-talk.

  How to use it: Update Claude Code; the spacebar hint will reappear for voice input, and you can check the keyboard settings in `/config`.

  Tip: If you use push-to-talk often, save your selected shortcut in your own notes rather than relying on the hint.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  CapabilityClaude Code

  Bash tool no longer stops a script after the first command when SHELLOPTS is exported

  Fixed a bug that caused scripts launched from the Bash tool to stop after only the first command when `SHELLOPTS` was exported.

  Usage details

  Who can use it: Bash users running Claude Code 2.1.316.

  How to use it: Upgrade Claude Code to 2.1.316 or later and rerun the multi-command script from the Bash tool.

  Tip: If the script’s behavior depends on the environment, use `set -x` to confirm that all commands are executed.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  CapabilityClaude Code

  Bash tool fixes aliases with line breaks and functions whose names start with a hyphen

  The Bash tool’s shell no longer breaks or drops Bash aliases whose values contain line breaks or functions whose names start with a hyphen. This fix does not apply to Git Bash.

  Usage details

  Who can use it: Claude Code 2.1.316; macOS and Linux Bash environments.

  How to use it: Upgrade to the new version and run a command using the Bash tool; your existing alias and function definitions will be used automatically.

  Tip: If you use Git Bash, verify the same definitions separately; Git Bash is excluded from the scope of this fix.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  FeatureClaude Code cloud sessions

  Cloud Files search displays paths from the project root

  Fixed an issue that caused folders to appear as `../..` in the cloud session Files pane after Claude changed directories. Results now show paths relative to the project’s root directory.

  Usage details

  Who can use it: The Files pane in Claude Code cloud sessions.

  How to use it: Have Claude change directories in a cloud session, search in the Files pane, and read the result path from the project root.

  Tip: Copying the file path relative to the project root before reviewing or downloading helps avoid opening the wrong folder.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  FeatureClaude Code

  First-run setup text is no longer cut off in narrow terminals

  Fixed an issue that dropped words from the security notes and terminal setup description during first-run setup in narrow terminals.

  Usage details

  Who can use it: Users running Claude Code for the first time in a narrow terminal window.

  How to use it: Update Claude Code and reopen first-run setup in a narrow terminal; the text will now appear in full.

  Tip: Widening the terminal to at least 80 columns during initial setup makes the options easier to read.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  FeatureClaude Code

  The Enterprise survey card now waits for Enter after a 1 or 0 response

  Fixed an issue where entering `1` or `0` on the Enterprise survey card was mistakenly submitted immediately after a short pause. You now need to press Enter to submit the typed response.

  Usage details

  Who can use it: The Claude Code survey card shown to Enterprise users.

  How to use it: Type `1` or `0` on the survey card and press Enter to submit your response.

  Tip: To confirm that your response was saved, wait for the card to close or for a confirmation message after pressing Enter.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  FeatureClaude Code

  Prompts containing invisible characters submit with one Enter press

  Removed the need to press Enter a second time to submit plain prompts containing invisible characters. Commands still require separate approval for security review.

  Usage details

  Who can use it: All users of the Claude Code terminal interface.

  How to use it: Update the client, type or paste a prompt containing invisible characters, and press Enter once.

  Tip: If you suspect copied text contains invisible characters, pass the prompt through a plain-text editor first to reduce unexpected formatting.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  CapabilityClaude Code

  Network requests no longer hang on truncated or malformed compressed responses

  Fixed a bug that caused some requests to wait almost indefinitely when a compressed network response was truncated or malformed.

  Usage details

  Who can use it: All platforms and gateways using Claude Code 2.1.316.

  How to use it: Update the client, then retry requests with your current network or proxy configuration.

  Tip: If you use a proxy, monitor compressed-response errors in a separate network log; if the issue persists, try temporarily disabling compression.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  Plugin / IntegrationClaude Code plugins

  Plugin MCP `headersHelper` no longer breaks the root or server URL

  Fixed an issue where plugin MCP `headersHelper` scripts received a malformed `CLAUDE_PLUGIN_ROOT` and server URL when an environment variable named after a credential was set to a key/value selection such as `1`.

  Usage details

  Who can use it: Claude Code plugins that use an MCP server.

  How to use it: Update Claude Code and restart the plugin MCP server; `headersHelper` will automatically receive the environment variables.

  Tip: When debugging a plugin, log `CLAUDE_PLUGIN_ROOT` and the server URL while masking sensitive information.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  Plugin / IntegrationClaude Tag

  Slack cloud scheduled task status list now completes

  Fixed an issue that left the live status list for cloud scheduled tasks shown by Claude Tag in Slack incomplete. Runs can now update the top-level messages they create.

  Usage details

  Who can use it: Cloud scheduled tasks monitored in Slack through Claude Tag.

  How to use it: Update Claude Tag, then start a cloud scheduled task from Slack and monitor the top-level status message while it runs.

  Tip: For long-running tasks, follow the top-level status message as the primary progress indicator, not thread replies.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  FeatureClaude Code for VS Code

  `/btw` history is no longer cleared prematurely in VS Code when there’s a settings error

  Fixed a bug that caused saved `/btw` follow-up question history to be cleared too early when the settings file contained an error.

  Usage details

  Who can use it: Users of `/btw` in Claude Code for VS Code.

  How to use it: Update the extension; when a settings error occurs, reopen `/btw` history in the VS Code Claude panel.

  Tip: Resolve settings file errors using the warning in the panel, and save important answers rather than relying on history.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  CapabilityClaude Code

  Aliases and functions transfer more reliably in Windows Git Bash

  Fixed an issue where the Bash tool lost aliases and functions when the Git Bash rc file set `errexit` and `pipefail` and had only winpty aliases or no aliases.

  Usage details

  Who can use it: Claude Code users running Git Bash on Windows.

  How to use it: Update Claude Code and rerun aliases or functions from your Git Bash rc file with the Bash tool.

  Tip: To troubleshoot environment differences, compare the output of `type` in both the interactive terminal and the Claude Code Bash tool.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları
• 31 Oct
  CapabilityClaude Code

  Grep and Glob searches that time out on Windows no longer hang

  Fixed an issue where Grep and Glob would stop responding if the search process failed to exit after being killed on timeout.

  Usage details

  Who can use it: Users of Claude Code Grep and Glob tools on Windows.

  How to use it: Upgrade Claude Code to 2.1.316 or later and run the same Grep/Glob search.

  Tip: Narrowing the search scope in large repositories reduces timeouts and resource usage on Windows.

  ✓ Verified by official sourceSource: Claude Code 2.1.316 sürüm notları

New in this edition · 4

• 01 Nov
  FeatureChatGPT

  ChatGPT Work’s agent capabilities are coming to the main ChatGPT experience

  OpenAI is preparing to bring Work’s agent capabilities to the standard Chat experience. According to the November 1 announcement, the combined Chat and Work experience will be tested with a small group of users in the coming weeks; selected users will be able to get work done on the web with files and plugins without switching modes. OpenAI’s help page confirms that these capabilities will come to the main ChatGPT experience in December.

  Usage details

  Who can use it: A small test group in the coming weeks; broader rollout in December 2026. The announcement of a shared quota covers Plus, Pro and Business plans; Codex remains a separate experience in the ChatGPT desktop app.

  How to use it: If you’re included in the test, start a conversation in the regular Chat tab; add a file or connected plugin, then give ChatGPT a task directly, such as building a website or preparing a presentation, and review the work. There’s no need to switch to a separate Work mode.

  Tip: After brief idea research, clearly assign the target task in the same conversation; check file and plugin permissions in advance to reduce unnecessary pauses by the agent.

  ✓ Verified by official sourceSource: ChatGPT ve Codex kullanım limitlerini anlama – OpenAI Yardım MerkeziSource: OpenAI, Pro kullanım limitlerini ikiye katlayıp Work özelliklerini Chat’e getiriyor – BleepingComputer
• 01 Nov
  Pricing / PlanChatGPT ve Codex

  A shared ChatGPT–Codex token quota is coming to Plus, Pro and Business

  Starting in December 2026, OpenAI will combine ChatGPT and Codex usage into a single shared quota for Plus, Pro and Business plans. Usage will be measured in tokens based on the selected model and task; Instant chat won’t count against this quota. If you reach the limit, you’ll be able to wait for the reset, upgrade your plan, or purchase credits for eligible features.

  Usage details

  Who can use it: Starting in December 2026; Plus, Pro and Business plans, as well as ChatGPT and Codex. Instant chat isn’t included in the shared usage quota.

  How to use it: Open Settings → Usage in ChatGPT to track your remaining combined usage and reset time. If you reach the limit, wait for the reset, upgrade your plan, or purchase credits for eligible features.

  Tip: Save the shared quota for long and complex tasks; use Instant chat for short everyday questions, since according to OpenAI, this usage doesn’t consume the quota.

  ✓ Verified by official sourceSource: ChatGPT ve Codex kullanım limitlerini anlama – OpenAI Yardım MerkeziSource: Kullanım kotası ChatGPT ve Codex arasında paylaşılacak – OpenAI Topluluk ForumuSource: OpenAI, Pro kullanım limitlerini ikiye katlayıp Work özelliklerini Chat’e getiriyor – BleepingComputer
• 01 Nov
  APIOpenAI Go SDK

  A Live WebSocket usage guide has been added to the OpenAI Go SDK

  openai-go v3.91.1 adds a new guide and compilable examples explaining primary session, sideband connection, and stored-session fork flows for Live WebSocket. The guide covers typed Send/Recv usage, waiting for `session.started` after `session.start`, and consuming the `session.closed` event on shutdown; this is a documentation and examples update, not a change to API behavior.

  Usage details

  Who can use it: OpenAI Go SDK v3.91.1 and developers using the source repository; Live WebSocket integrations.

  How to use it: Update with `go get github.com/openai/openai-go/v3@v3.91.1` and follow the repository’s `live/README.md` guide. In the primary flow, call `client.Live.Connect`, send `session.start`, and wait for the `session.started` event; the sideband and fork examples are in the same guide.

  Tip: Remember that opening the WebSocket doesn’t start the session; don’t send application commands until `session.started` arrives, and consume `session.closed` events before shutdown.

  ✓ Verified by official sourceSource: OpenAI Go SDK v3.91.1 sürüm notlarıSource: Live WebSocket rehberi commit’i – OpenAI Go SDK
• 31 Oct
  APIOpenAI Go SDK

  OpenAI Go SDK: Live Decision fields are preserved in JSON conversions

  openai-go v3.91.0 preserves the resolved additional fields of Live Decision items in JSON conversions; tool call IDs, names, arguments, outputs, and unknown item types aren’t lost. Explicitly provided additional-field overrides, null, and Omit values retain their precedence, reducing data loss when reserializing typed Live events.

  Usage details

  Who can use it: Live WebSocket integrations using OpenAI Go SDK v3.91.0; Decision items in primary, sideband, and stored-session fork flows.

  How to use it: Update the Go module with `go get github.com/openai/openai-go/v3@v3.91.0` and use typed DecisionItem events from the Live connection. If you want to preserve forward-compatible fields, don’t filter additional fields during JSON round-trips; use the SDK’s additional-field parameters for intentional overrides.

  Tip: Preserve `RawJSON` and additional fields in test snapshots for compatibility with future item types; if you want to deliberately remove a field, filter it explicitly.

  ✓ Verified by official sourceSource: OpenAI Go SDK v3.91.0 sürüm notlarıSource: Live Decision öğe alanlarını koruma commit’i – OpenAI Go SDK

New in this edition · 2

• 01 Nov
  RetiredWhatsApp Business Platform Business Management API

  WhatsApp Business API: `conversation_analytics` field removed

  Meta deprecated the `conversation_analytics` field and announced that it will no longer be available starting November 1, 2026. This change affects WhatsApp Business Account analytics requests and reporting integrations that use this field.

  Usage details

  Who can use it: Businesses, partners, and analytics integrations using the WhatsApp Business Platform’s Business Management API; starting November 1, 2026.

  How to use it: Remove `fields=conversation_analytics` from requests; switch to the appropriate field based on your needs: `analytics`, `pricing_analytics`, `template_analytics`, `template_group_analytics`, `call_analytics`, or `group_analytics`.

  Tip: Scan field names and dashboard queries in advance to avoid production errors; keep backward-compatible error handling in response parsers for the `conversation_analytics` object, which will no longer be returned.

  ✓ Verified by official sourceSource: WhatsApp değişiklik günlüğüSource: WhatsApp analitik belgeleri
• 01 Nov
  Pricing / PlanWhatsApp Marketing Messages API

  WhatsApp Marketing Messages API: separate billing SKU for max price traffic

  Starting November 1, 2026, messages sent using max price are reported with separate billing line items and identifiers from messages sent at the published rate. The Pricing Analytics API uses `MARKETING_LITE_DYNAMIC`, the Template Analytics API uses `amount_spent_max_price`, and the pricing webhook uses `marketing_lite_dynamic`; message-sending requests are unchanged.

  Usage details

  Who can use it: Businesses and integrations using max price in the WhatsApp Marketing Messages API; traffic covered by invoices, the Pricing Analytics API, the Template Analytics API, and the pricing webhook.

  How to use it: Support the `Price type: Max Price` line item in your invoice-processing code; accept `MARKETING_LITE_DYNAMIC` in the Pricing Analytics API, `amount_spent_publish_rate` and `amount_spent_max_price` in the Template Analytics API, and `marketing_lite_dynamic` in the webhook parser.

  Tip: Track published-rate and max-price costs in separate dashboard series while preserving total spend; account for a small amount of transition traffic appearing under `List` on the first November invoice.

  ✓ Verified by official sourceSource: Max price faturalama SKU’su: fatura ve analiz API’si güncellemeleriSource: WhatsApp değişiklik günlüğü

New in this edition · 2

• 02 Nov
  SettingKimi

  Kimi Memory Space: Users report new memory behavior

  A November 2 report by 36Kr says some users have reported in recent days that Memory Space would not load and that the new version consolidates the old, individual memory instructions into summaries of user preferences. Moonshot has not officially announced this specific behavior change on November 2; its official Help Center only confirms that the new Memory experience has been rolling out gradually since October 2026.

  Usage details

  Who can use it: On some Kimi accounts; according to the official Help Center, the interface and settings may vary by platform, app version, and region.

  How to use it: In Kimi, open Settings → Personalization → Memory or Memory Space; view, export, or delete saved memories. If the new section is not visible, the rollout may not yet be complete for your account.

  Tip: Check the source indicator in responses that use memory; if you see an outdated or incorrect memory, delete it from Memory Space and save the updated information again.

  ! UnverifiedSource: 36Kr: Kimi’nin bellek mimarisinde son günlerdeki değişiklik iddialarıSource: Kimi Memory Space resmi yardım merkezi
• 01 Nov
  AvailabilityKimi Design

  Kimi Design: Editable visual design surface made available to users

  Moonshot’s official sources dated November 1 present Kimi Design as a user-facing surface that generates posters, social media graphics, product images, and infographics from text prompts or reference images, and offers element-level editing on a canvas, comment-based revisions, version history, and export. This is an accessibility listing for Kimi Design, which was not included in the known list.

  Usage details

  Who can use it: In the Kimi web interface; official sources do not specify plan or regional restrictions.

  How to use it: Open https://www.kimi.com/design; write a prompt or upload a reference image, edit the generated design on the canvas or by commenting on an element, then export the result as PNG, JPG, PDF, PPTX, or Google Slides.

  Tip: Specify the target audience, canvas size, colors, and output format in the initial prompt; make small revisions by commenting on individual elements.

  ✓ Verified by official sourceSource: Kimi Design özellik sayfasıSource: Kimi resmi kaynak: Kolayca bilgi grafiği oluşturmaSource: Kimi resmi kaynak: Görselden görsel üretme

No notable change since the last edition.

New in this edition · 13

• 02 Nov
  CapabilityQwen Code review

  Qwen Code review: Text-based re-review requests are routed to the PR

  The review flow routes re-review requests phrased in natural language to the correct pull request. This prevents prose re-review requests from being sent to the wrong target.

  Usage details

  Who can use it: Nightly releases v0.26.5-nightly.20261101.7b4b353750 and later; Qwen Code review flow.

  How to use it: Request a re-review in natural language during a review session; the current nightly routes the request to the relevant PR context.

  Tip: Clearly specify the PR context and the expected checks in the same sentence when requesting a re-review.

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

  Qwen Code Web Shell: Conversation Activity view added

  Web Shell now lets you inspect a session’s conversation activity in a separate view. This makes it possible to track the session flow separately from the main workspace.

  Usage details

  Who can use it: Nightly versions v0.26.5-nightly.20261101.7b4b353750 and later; Qwen Code Web Shell.

  How to use it: Upgrade to this nightly version and open the relevant session’s Conversation Activity view in Web Shell; the official note does not specify the menu path.

  Tip: In long sessions, use the activity view to track status without interrupting the main conversation.

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

  Qwen Code Web Shell: Add to Split View added to the session menu

  The Add to Split View action was added to session menus. Adding a session to the current split view no longer requires a separate flow.

  Usage details

  Who can use it: Nightly versions v0.26.5-nightly.20261101.7b4b353750 and later; Web Shell Split View.

  How to use it: Open a session’s menu and select Add to Split View.

  Tip: When comparing the context of two sessions, keep the main session fixed and add the auxiliary session to the split view.

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

  Qwen Code: 2>&1 redirection is no longer flagged as a file write

  The shell permission check does not treat 2>&1, which only combines file descriptors, as a file write. This reduces unnecessary file-write confirmation prompts.

  Usage details

  Who can use it: Nightly releases v0.26.5-nightly.20261101.7b4b353750 and later; Qwen Code sessions that run shell commands.

  How to use it: Use standard 2>&1 error stream redirection in a shell command; the new permission check will not classify it as a file write on its own.

  Tip: Make permission prompts easier to review by avoiding mixing output redirection with actual file writes in the same command.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 nightly sürüm notları
• 02 Nov
  Plugin / IntegrationQwen Code

  Qwen Code: Unique MCP tools are preserved when tool names collide

  When MCP tool names collide, tools with unique names are no longer dropped because of the collision. This makes tool discovery more reliable when using multiple MCP servers in the same session.

  Usage details

  Who can use it: Nightly versions v0.26.5-nightly.20261101.7b4b353750 and later; Qwen Code sessions using MCP servers.

  How to use it: Enable multiple MCP servers in the same session using your usual connection flow; tools with unique names among the colliding names are preserved automatically.

  Tip: Using unique prefixes in server and tool names reduces collisions and makes the tool list easier to understand.

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

  Qwen Code: 1 million-token context retained for Kimi K3

  A nightly core fix preserves the 1 million-token context window throughout Kimi K3 generation. It aims to prevent context from unexpectedly shrinking during generation with long inputs.

  Usage details

  Who can use it: Nightly versions v0.26.5-nightly.20261101.7b4b353750 and later; Qwen Code sessions using Kimi K3.

  How to use it: Connect the Kimi K3 model to nightly Qwen Code and run a long session as usual; no additional setting is required for this fix.

  Tip: Avoid adding unnecessary files and old conversations to the context so you don’t consume the 1 million-token window too quickly.

  ✓ Verified by official sourceModels: Kimi K3Source: Qwen Code v0.26.5 nightly sürüm notları
• 02 Nov
  FeatureQwen Code CLI

  Qwen Code CLI: PR badge is parsed correctly when using an adjacent --flag

  The PR badge is no longer parsed incorrectly when a --flag is written adjacent to the PR number in the review flow. This preserves the correct PR context in CLI calls that use adjacent flags.

  Usage details

  Who can use it: Nightly versions v0.26.5-nightly.20261101.7b4b353750 and later; Qwen Code review CLI flow.

  How to use it: Run the review command with the PR number and the --flag you use; the nightly version will associate the PR badge correctly.

  Tip: For more readable command-line parsing, prefer putting a space between the PR number and the flag.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 nightly sürüm notları
• 02 Nov
  FeatureQwen Code CLI

  Qwen Code CLI: Long /btw responses are readable in a constrained viewport

  Long /btw responses in the CLI now remain readable in a constrained viewport. Responses are less likely to be cut off in a narrow or fixed-height view.

  Usage details

  Who can use it: Nightly versions v0.26.5-nightly.20261101.7b4b353750 and later; Qwen Code CLI.

  How to use it: Run the /btw command in the CLI; long responses will be displayed using the new constrained-viewport behavior.

  Tip: Use /btw to ask brief follow-up questions without interrupting the main task, and read the long response in the viewport.

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

  Qwen Code Web Shell: Back control outside the nav rail for the Plugins page

  A back control is now visible for returning from the Plugins page when the navigation rail is not shown. This keeps plugin navigation usable in collapsed layouts or layouts without the rail.

  Usage details

  Who can use it: Nightly versions v0.26.5-nightly.20261101.7b4b353750 and later; Web Shell Plugins page.

  How to use it: With the nav rail turned off in Web Shell, open the Plugins page and use the back control on the page.

  Tip: When leaving plugin details, prefer the page’s own back control over the browser’s back button.

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

  Qwen Code: Clearer query rejection when no LSP server is ready

  LSP queries are no longer sent when no server is ready; they are explicitly rejected instead. This provides a clearer error flow indicating that the server is not ready, rather than a silent or ambiguous result.

  Usage details

  Who can use it: Nightly versions v0.26.5-nightly.20261101.7b4b353750 and later; Qwen Code projects with LSP enabled.

  How to use it: In a project with LSP enabled, wait for the server to start before running the query; if the server is not ready, look for the new explicit error message.

  Tip: Before running an LSP query, confirm that the relevant language server is enabled in the project and workspace settings.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 nightly sürüm notları
• 01 Nov
  APIQwen Code Managed

  Qwen Code Managed: Paginated SQL history queries added

  Bounded SQL history queries have been added for Managed local H2 and Hosted MySQL. These queries support paginated retrieval of recent messages, journal transaction records, and specific operation or command searches.

  Usage details

  Who can use it: Qwen Code v0.26.5 and Qwen Code Desktop v0.26.5; installations using Managed local H2 or Hosted MySQL.

  How to use it: Upgrade to Qwen Code v0.26.5 and use pagination or the operation/command lookup flow in the Managed history query API; the official note does not specify the exact parameter names.

  Tip: Fetch recent messages in pages and narrow operation/command searches; avoid requesting large history tables in a single query.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 sürüm notları
• 01 Nov
  CapabilityQwen Code

  Qwen Code: Bodyless 400 responses no longer fail immediately

  Bodyless HTTP 400 responses are now retried instead of being treated as fail-fast. This makes tasks more resilient to transient or malformed network responses that have no response body.

  Usage details

  Who can use it: Qwen Code v0.26.5 and Qwen Code Desktop v0.26.5.

  How to use it: Upgrade Qwen Code to v0.26.5; retries for bodyless 400 responses are applied automatically.

  Tip: For intermittent request failures, wait for the built-in retry instead of restarting the task immediately.

  ✓ Verified by official sourceSource: Qwen Code v0.26.5 sürüm notları
• 01 Nov
  FeatureQwen Code Web Shell

  Qwen Code Web Shell: Panes for sessions removed from the catalog are cleared

  Web Shell removes sessions no longer in the active catalog from Split View panes. This prevents empty or stale panes linked to sessions that are no longer valid from being left behind.

  Usage details

  Who can use it: Qwen Code v0.26.5 and Qwen Code Desktop v0.26.5; Web Shell sessions using Split View.

  How to use it: While using Split View, remove a session from the active catalog; in v0.26.5, the corresponding pane is cleared automatically.

  Tip: Remove sessions you no longer use from the catalog to keep the Split View list tidy.

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

No notable change since the last edition.

No notable change since the last edition.