TOP 10 unchanged; Google is shutting down Jules, Qwen is coming to iPhone

New in this edition · 2

• 30 Oct
  FeatureGemini in Google Slides

  Gemini edits an entire presentation in Google Slides with a single prompt

  Gemini in Google Slides can now edit multiple slides or an entire presentation with a single prompt. It can update fonts, backgrounds, and colors in bulk; refresh content based on Drive files; combine and expand slides; and apply changes to native, editable slides.

  Usage details

  Who can use it: The feature is available on desktop and initially only in English. It is rolling out to Business Standard and Plus, Enterprise Standard and Plus, Google AI Pro and Ultra, and Google AI Pro for Education accounts; the expanded rollout across Rapid Release and Scheduled Release domains began on October 29, 2026. Workspace customers are getting a promotional higher limit for creating multiple slides through at least December 1, 2026.

  How to use it: On desktop, open a presentation in Google Slides, click `Ask Gemini` in the upper-right corner, and describe the change you want in the side panel—for example, make all headings the same font size or summarize slides 5–7 on a single slide. Click `Submit`; when the task is complete, a summary of the changes will appear in the side panel, and you can review the edits using `Undo` or version history.

  Tip: Clearly specify the scope in your prompt: include slide numbers, the desired tone or colors, and, if needed, a reference file in Drive. Make a copy of the presentation before applying major changes, and check the summary of the results.

  ✓ Verified by official sourceSource: Edit entire presentations with Gemini in Google Slides — Google Workspace UpdatesSource: Generate and edit slides with Gemini in Google Slides — Google Docs Editors Help
• 29 Oct
  RetiredJules

  Jules will be discontinued on December 31 and become read-only on November 11

  Google is discontinuing Jules to consolidate its agentic coding work in Antigravity. Users can finish their sessions through November 11, 2026; after that date, Jules will be read-only, and the service will shut down completely on December 31, 2026. Settings, environment variables, repositories, memories, scheduled tasks, and session history stored in Jules can be exported to a local folder.

  Usage details

  Who can use it: All Jules users are affected. The deadline to finish new sessions is November 11, 2026; from November 11 through December 31, access will be read-only, and Jules will be unavailable after December 31. Code, branches, and pull requests on GitHub will remain in place.

  How to use it: To export your data, install Jules Tools in a terminal with `npm install -g @google/jules` and sign in with `jules login`. Then run the export prompt from the official announcement in a CLI coding agent; the process saves settings, environment variables, connected repositories, memories, setup scripts, and all session history to a local `jules-export` folder.

  Tip: Finish ongoing sessions and export your data before November 11. Keep the export folder private, since `env-variables.json` may contain secrets.

  ✓ Verified by official sourceSource: Jules Turndown — Jules resmi değişiklik günlüğüSource: Google is sunsetting its AI coding agent, Jules — The Verge

New in this edition · 24

• 31 Oct
  SettingClaude Code

  Default effort level for subagents can now be configured

  The CLAUDE_CODE_SUBAGENT_EFFORT environment variable sets the effort level subagents use when no other setting is specified. This means subagents do not have to automatically inherit the main session’s level.

  Usage details

  Who can use it: Developers and team administrators using Claude Code subagents.

  How to use it: Set the CLAUDE_CODE_SUBAGENT_EFFORT variable to your preferred effort level before launching Claude Code; if a level is specified separately when calling a subagent, that level takes precedence for that call.

  Tip: Try a lower level for subagents to reduce cost and improve speed, and a higher level for complex tasks, on a per-project basis.

  ✓ Verified by official sourceSource: Claude Code değişiklik günlüğü
• 31 Oct
  Plugin / IntegrationClaude Code cloud sessions

  Anthropic cloud tasks can load Claude.ai plugins

  Scheduled tasks running in Anthropic cloud now load the plugins enabled in the claude.ai account. This helps tasks run more consistently with the user’s active plugin configuration.

  Usage details

  Who can use it: Users with Scheduled tasks running in Anthropic cloud; plugins must be enabled in the claude.ai account, and organization policy must allow them.

  How to use it: Enable the plugins you want in your Claude.ai account, then create or run a Scheduled task in Anthropic cloud.

  Tip: Before running the task in production, verify that the enabled plugins are available in the cloud session with a small test task.

  ✓ Verified by official sourceSource: Claude Code değişiklik günlüğü
• 31 Oct
  SettingClaude Code

  Default rule behavior changed for the Auto mode allow list

  When the autoMode.allow list does not include $defaults, it no longer removes the built-in rule from scheduled task prompts. This helps preserve more consistent security behavior in scheduled tasks.

  Usage details

  Who can use it: Claude Code users and administrators who use Auto mode and scheduled tasks.

  How to use it: Check the autoMode.allow list in managed settings; explicitly use $defaults to preserve built-in rules, then test with a scheduled task.

  Tip: When adding custom allow rules, verify with a test task that the default security rule has not been unintentionally disabled.

  ✓ Verified by official sourceSource: Claude Code değişiklik günlüğü
• 31 Oct
  APIClaude apps gateway

  Input tagging support added for Bedrock guardrails

  For Bedrock upstreams, the Claude apps gateway option guardrail.input_tagging wraps prompts in the input tags expected by the Amazon Bedrock guardrail prompt-attacks filter. The all_messages_and_system option also tags the system prompt.

  Usage details

  Who can use it: Claude apps gateway administrators who use Amazon Bedrock guardrails.

  How to use it: Enable guardrail.input_tagging in the relevant Bedrock upstream configuration; select all_messages_and_system to include the system prompt as well.

  Tip: Run separate test requests with a regular user prompt and a system instruction to verify which message sections the guardrail scans.

  ✓ Verified by official sourceSource: Claude Code değişiklik günlüğü
• 31 Oct
  SettingClaude Tag

  Participation setting renamed in Claude Tag

  The Respond automatically toggle in a Slack channel has been replaced with the How Claude participates option on the channel’s Configure page and in Claude Tag admin settings. This makes it clearer how Claude can participate in the channel.

  Usage details

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

  How to use it: Open the Slack channel’s Configure page or Claude Tag admin settings, then choose a participation mode from How Claude participates.

  Tip: When changing automatic response behavior for a channel, also check the relevant Claude Tag spend limit and access policies.

  ✓ Verified by official sourceSource: Claude Code değişiklik günlüğü
• 31 Oct
  FeatureClaude Code Code Review

  Severity card added to Code Review analytics

  The Code Review analytics page now includes a card showing total findings for the period, a daily stacked chart by severity, and the count at each level.

  Usage details

  Who can use it: Teams using Claude Code Code Review analytics.

  How to use it: Open the Code Review analytics page and review the period and daily breakdown in the findings-by-severity card.

  Tip: Prioritize based not only on total findings but also on the daily trend in high-severity findings.

  ✓ Verified by official sourceSource: Claude Code değişiklik günlüğü
• 31 Oct
  SettingClaude Code cloud sessions

  Enterprise members can manage network secrets in cloud environments

  Enterprise members can now add and delete network secrets in their own cloud environments, in addition to viewing them. Previously, these actions were limited to users with administrator access.

  Usage details

  Who can use it: Enterprise members who use Claude Code cloud sessions; organization policies may restrict this feature.

  How to use it: Open the cloud environment settings and add a new secret or delete an existing one in the network secrets section.

  Tip: Keep secret values only in the network secrets section rather than pasting them into session text, and regularly remove those no longer needed.

  ✓ Verified by official sourceSource: Claude Code değişiklik günlüğü
• 31 Oct
  SettingClaude apps gateway

  Layered merge mode added for gateway policies

  The managed.policy_mode: layered setting applies all policies that match a developer and merges them, with lower-priority policies taking precedence. Unlike the previous behavior, which stopped at the first match, multiple rules now take effect.

  Usage details

  Who can use it: Team and Enterprise administrators managing layered policies in the Claude apps gateway.

  How to use it: Set managed.policy_mode to layered in the gateway’s managed policy configuration, then check the policy order from the lowest-priority rule upward.

  Tip: Review conflicting permissions with a small test group first; clearly document which fields the higher layer overrides.

  ✓ Verified by official sourceSource: Claude Code değişiklik günlüğü
• 31 Oct
  Pricing / PlanClaude apps gateway

  Shared monthly budget introduced for groups

  The Claude apps gateway now supports a single monthly budget shared by group members, in addition to per-person limits. This budget is configured using the pooled_budget field in the spend limits management API.

  Usage details

  Who can use it: Organization administrators who manage the Claude apps gateway and enforce group-based spending limits.

  How to use it: Add the pooled_budget value to the relevant group record in the spend limits management API; members’ individual limits remain in place separately.

  Tip: Track the shared budget separately from per-person limits; reassess the rate at which it is used when group size changes.

  ✓ Verified by official sourceSource: Claude Code değişiklik günlüğü
• 31 Oct
  AgentClaude Code cloud sessions

  MCP form requests appear as cards in cloud sessions

  When an MCP server requests a form, the cloud session now displays a form card instead of silently canceling the request. Users can fill out the card or decline the request.

  Usage details

  Who can use it: Claude Code cloud session users whose MCP servers request forms.

  How to use it: Fill in and submit the fields in the form card that appears during a cloud session; if you do not want to proceed, decline the request through the card.

  Tip: If an authentication or configuration form appears unexpectedly, check the MCP server’s source and the requested fields before submitting.

  ✓ Verified by official sourceSource: Claude Code değişiklik günlüğü
• 31 Oct
  SettingClaude Code

  Approval and validation flow changed for server-managed settings

  In Team and Enterprise sessions, server-managed settings retrieved from the Anthropic API are now applied without prompting for approval. If a stored copy cannot be validated, it is rejected rather than starting a session without applying the policy.

  Usage details

  Who can use it: Claude Code users who use Anthropic Team or Enterprise sign-in and server-managed settings.

  How to use it: Sign in with a Team or Enterprise account and wait for managed settings to be retrieved. If there is a connection or validation issue, check the integrity of the locally stored copy and the management server.

  Tip: Include the source and signature/validation status of managed settings in your organization’s deployment process; do not try to bypass a validation error by copying the local file.

  ✓ Verified by official sourceSource: Claude Code değişiklik günlüğü
• 31 Oct
  FeatureClaude Code for VS Code

  Sign in to the gateway from the VS Code chat panel

  A sign-in flow for the Claude apps gateway that does not require a terminal has been added to the Claude Code chat panel in VS Code. Authentication can now be started directly from the editor interface.

  Usage details

  Who can use it: VS Code users connecting to the Claude apps gateway.

  How to use it: Open the Claude Code chat panel in VS Code, select the gateway sign-in option, and complete the authentication flow in your browser.

  Tip: When switching teams, use this flow instead of terminal-based sign-in to verify that the VS Code profile is connected to the correct gateway.

  ✓ Verified by official sourceSource: Claude Code değişiklik günlüğü
• 31 Oct
  CapabilityClaude Code Skills

  /claude-api skill reads the Managed Agents workflow first

  The Managed Agents examples in the /claude-api skill require reading the relevant Managed Agents workflow run before changing the agent. This reduces the risk of making changes without understanding the current run.

  Usage details

  Who can use it: Claude Code users who manage Managed Agents workflows with the /claude-api skill.

  How to use it: Run the /claude-api skill in Claude Code and ask to change a Managed Agents agent; provide the workflow run details the skill requests, then apply the change.

  Tip: Record the workflow’s current steps and failure points before making changes to avoid unnecessary reconfiguration of the same run.

  ✓ Verified by official sourceSource: Claude Code değişiklik günlüğü
• 31 Oct
  FeatureClaude Code cloud sessions

  Catching up indicator added to Cloud and Remote Control sessions

  When messages are updating as you return to a Cloud or Remote Control session, a Catching up… line is now displayed. This clearly indicates that the session is not yet up to date.

  Usage details

  Who can use it: Claude Code users who use Cloud sessions or Remote Control sessions.

  How to use it: Return to a previously open cloud/Remote Control session; the Catching up… line appears automatically while syncing.

  Tip: Do not make decisions based on an old message while this indicator is displayed; check the latest state after the update completes.

  ✓ Verified by official sourceSource: Claude Code değişiklik günlüğü
• 31 Oct
  SettingClaude Code

  Option added to preserve looped system certificates

  CLAUDE_CODE_DISABLE_LOOPED_CROSS_CERT_DROP prevents mutually validating looped system cross-certificates from being dropped. It helps maintain connection compatibility when a custom CA chain requires one of these certificates.

  Usage details

  Who can use it: Claude Code environments using a custom CA and a looped cross-certificate chain.

  How to use it: Set the CLAUDE_CODE_DISABLE_LOOPED_CROSS_CERT_DROP variable in the environment that launches Claude Code, then retry the connection in a new session.

  Tip: Verify the CA chain before enabling this option broadly; use it only for affected installations rather than preserving unnecessary certificates.

  ✓ Verified by official sourceSource: Claude Code değişiklik günlüğü
• 31 Oct
  SettingClaude Code

  Environment variable added to disable the ultrathink keyword

  The CLAUDE_CODE_DISABLE_ULTRATHINK environment variable disables Claude Code’s activation of the ultrathink keyword. This lets teams disable the trigger for policy or cost reasons.

  Usage details

  Who can use it: Claude Code 2.1.316 users and administrators.

  How to use it: Add the CLAUDE_CODE_DISABLE_ULTRATHINK variable to your environment before launching Claude Code, then start a new session.

  Tip: To apply the variable only to specific projects, define it in the project’s launch script instead of the global profile.

  ✓ Verified by official sourceSource: Claude Code değişiklik günlüğü
• 31 Oct
  CapabilityClaude Code for VS Code

  Runs with ultrathink xhigh effort in VS Code

  The ultrathink keyword in VS Code now runs the relevant turn at the xhigh effort level and uses a rainbow indicator in the chat box, like in the terminal.

  Usage details

  Who can use it: Users of the ultrathink feature in the Claude Code VS Code extension.

  How to use it: Use the ultrathink keyword in a prompt in Claude Code chat in VS Code; the turn will run with xhigh effort, and the indicator will appear in the chat box.

  Tip: Use it for long, challenging turns that require reasoning; use normal effort for routine requests to avoid unnecessary consumption.

  ✓ Verified by official sourceSource: Claude Code değişiklik günlüğü
• 30 Oct
  RetiredClaude Platform API

  Claude Opus 4.8 fast mode is being deprecated

  Fast mode for Claude Opus 4.8 was deprecated as of October 30 and will be removed on November 30, 2026. After removal, requests with speed="fast" for this model will fail; they will not automatically fall back to standard speed.

  Usage details

  Who can use it: Affects developers using Opus 4.8 fast mode on the Claude API and related managed platforms; Opus 5.5 fast mode remains available.

  How to use it: In /v1/messages requests, stop using model Claude Opus 4.8 with speed="fast" and switch to Claude Opus 5.5; you can use the same speed="fast" parameter with Opus 5.5.

  Tip: Test the model migration and cost/response speed differences in a staging environment before November 30.

  ✓ Verified by official sourceModels: Claude Opus 4.8, Claude Opus 5.5Source: Claude Platform release notesSource: Fast mode belgeleri
• 30 Oct
  AvailabilityClaude Code cloud sessions

  Cloud sessions can start despite a failed setup script

  Cloud sessions started from web, desktop, and mobile apps are no longer considered complete failures when the setup script exits with an error code. The session can start, allowing the user to address the setup error afterward.

  Usage details

  Who can use it: Users of Claude Code cloud sessions in web, desktop, and mobile apps; organization policy must not disable the feature.

  How to use it: Run your setup script as usual when starting a Cloud session; even if the script ends with an error, enter the session and check the working environment and error output.

  Tip: Don’t treat the session starting as a sign of success; first verify dependencies, the working directory, and setup logs.

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

  Gateway upstreams gain a routing setting for IdP groups

  An optional groups list has been added to Claude apps gateway upstream definitions. This lets only developers in the specified identity provider groups be routed to the relevant upstream; the rule is also preserved during failover.

  Usage details

  Who can use it: Teams managing Claude apps gateway and organizations using IdP group mapping.

  How to use it: Add the groups list that determines developer access to the gateway upstream configuration and match the IdP group names to your existing management configuration.

  Tip: Test with authorized and unauthorized accounts to verify that the same group restriction applies during failover.

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

  guardrail_trace added to Bedrock upstreams

  The guardrail_trace option has been added to Claude apps gateway Bedrock upstreams. It records which Amazon Bedrock guardrail filter was triggered during a request, but does not log the matching text.

  Usage details

  Who can use it: Claude apps gateway administrators using an Amazon Bedrock upstream.

  How to use it: Add the guardrail_trace option to the relevant Bedrock upstream configuration and review the resulting traces in your gateway monitoring/logging system.

  Tip: Track filter names for security diagnostics; since sensitive matching text is not recorded, correlate the incident’s underlying content with separate access-controlled logs.

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

  Claude Code’s built-in API and dataviz skills updated

  The Datadog API monitoring setup in the built-in /claude-api skill now sends the dd-llmobs-enabled: true header and removes the old macOS xattr step. The built-in dataviz skill also recommends printing axis labels more legibly and using sorted bars or segmented bars for pie/donut requests.

  Usage details

  Who can use it: Users of Claude Code’s built-in Skills package, as well as teams using the /claude-api skill.

  How to use it: Use the /claude-api or dataviz skill in a Claude Code session; the updates come with the built-in package, so no separate installation is needed.

  Tip: When checking Datadog traces, verify that the dd-llmobs-enabled header was received; prefer the new bar formats for category comparisons in charts.

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

  Confirmation required when editing the organization settings file

  Claude Code’s file tools now ask for confirmation before editing a local copy of the organization’s server-managed settings. This behavior is now consistent with the protection for users’ own settings files.

  Usage details

  Who can use it: Claude Code users whose organization applies server-managed settings.

  How to use it: When Claude Code asks to write to the organization settings file, review the permission prompt and approve only the expected change.

  Tip: When possible, update the policy in its management source instead of directly changing the managed settings file.

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

  Include completed button added to the Scheduled tasks page

  On the Scheduled tasks page in Cloud sessions, an Include completed button appears only when completed one-time tasks are hidden. The button makes completed tasks visible without opening the Sort menu.

  Usage details

  Who can use it: Users of the Scheduled tasks view in Claude Code cloud sessions.

  How to use it: Open the Scheduled tasks page; if completed one-time tasks are hidden, click the Include completed button.

  Tip: Use this button to review one-time task history; continue using the existing sort options to filter recurring tasks.

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

New in this edition · 4

• 31 Oct
  RetiredOpenAI API Evals platformu

  Existing evaluations on the Evals platform are now read-only

  As the next phase of the planned retirement, existing Evals evaluations switched to read-only mode on October 31; they can no longer be edited. The Evals dashboard and API are scheduled to shut down on November 30, 2026.

  Usage details

  Who can use it: API developers using Evals can read existing evaluations but cannot edit them; access to the platform’s dashboard and API will continue until the planned shutdown on November 30.

  How to use it: Review existing results and manually migrate the evaluation to a Promptfoo configuration; then run it with `promptfoo eval -c promptfooconfig.yaml --no-cache` and open the results with `promptfoo view`.

  Tip: Before shutdown, recreate the graders, test data, and expected outputs, then compare the results; scores from manually migrated graders may not match exactly.

  ✓ Verified by official sourceSource: OpenAI API deprecations — Evals platformuSource: OpenAI Evals’tan Promptfoo’ya geçiş rehberi
• 30 Oct
  ModelChatGPT Work, Codex ve OpenAI API

  GPT-6 Rosalind Research launches in Work/Codex and the API

  GPT-6 Rosalind Research brings GPT-6 reasoning to multistep life sciences research, with safeguards designed for biological work, and is available in Work, Codex, and the API to a limited number of approved Research customers. It is not available in the Chat tab; existing customers can continue using GPT-5.5 Rosalind Research, and its API identifier is `gpt-6-rosalind`.

  Usage details

  Who can use it: Available to a limited number of Business and Enterprise customers whose organizations and users are approved for Rosalind Research; in Enterprise, a two-week Admin Preview starts off disabled. API access is limited to internal research use by separately approved organizations; the Rosalind Academic Plan does not include API access or API credits.

  How to use it: In Work or Codex, select GPT-6 Rosalind Research from the model picker; in Codex, install Plugins > Life Sciences Research Plugin if needed. For the API, after your organization and project have been separately approved for access, set the model parameter in your request to `gpt-6-rosalind`.

  Tip: Instead of loading large omics or biological datasets directly into the context, point to approved storage or a database and ask targeted research questions; let the model use scientific tools and sources.

  ✓ Verified by official sourceModels: GPT-6 Rosalind Research, gpt-6-rosalindSource: Model Release Notes — GPT-6 Rosalind ResearchSource: ChatGPT Business yayın notları — GPT-6 Rosalind ResearchSource: ChatGPT Enterprise ve Edu yayın notları — GPT-6 Rosalind Research
• 30 Oct
  AvailabilityChatGPT iOS ve Android uygulamaları

  Account switching is expanding to the iOS and Android apps

  Rolling out gradually to ChatGPT mobile apps, account switching lets you keep up to two accounts signed in at once and switch between them without logging out. Each account keeps its own chats, memory, settings, and subscription; accounts are not merged.

  Usage details

  Who can use it: Rolling out gradually in the ChatGPT iOS and Android apps; organization policies may apply in managed workspaces.

  How to use it: In the app, go to Settings > Switch account and add a second account; then select the active account from the account menu.

  Tip: To keep work and personal accounts separate, check the active account before switching; chats, files, and memory are not transferred to the other account.

  ✓ Verified by official sourceSource: ChatGPT yayın notları — Account switching on iOS and Android
• 29 Oct
  CapabilityOpenAI Model Spec

  The Model Spec has been reorganized around five core values

  OpenAI has reorganized its Model Spec guidance around the values of faithfulness to human intent, minimizing harm, honesty and transparency, human autonomy, and care. New guidance on context, oversight, and autonomy has been added; most detailed style guidance has been removed, and OpenAI notes that the document describes intended behavior that models do not yet fully reflect.

  Usage details

  Who can use it: Applies to the public Model Spec and intended model behavior; there is no specific plan, region, or on/off setting, and full behavioral rollout is not guaranteed.

  How to use it: Review the updated document at https://model-spec.openai.com/2026-10-29.html; there is no separate setting in ChatGPT to enable it.

  Tip: State your preferred tone, perspective, and boundaries explicitly; many of the guide’s defaults can be steered with user or developer instructions, but you should not expect them to be implemented fully in every model.

  ✓ Verified by official sourceSource: Daha yetenekli ve faydalı AI için güncellenmiş Model SpecSource: Model Release Notes — Updates to the OpenAI Model Spec (October 29, 2026)

New in this edition · 1

• 29 Oct
  AvailabilityMeta AI gözlükleri

  Access to and training on AI glasses expanded in Canada through CNIB partnership

  Meta launched a program with CNIB to help blind, deafblind, or partially sighted people in Canada try AI glasses at work and in daily life. Through CNIB’s Come to Work program, the initiative will provide donated glasses, peer training, accessible guides, and feedback to Meta’s product teams.

  Usage details

  Who can use it: The program is aimed at blind, deafblind, or partially sighted people in Canada, especially those participating in the CNIB Come to Work program. The announcement describes targeted access and training through CNIB, not an automatic nationwide rollout or sale for general users.

  How to use it: This is not a feature enabled through a general Meta AI setting. Interested people should apply to the training and demonstration process through the CNIB Come to Work program; eligible glasses should be paired with the Meta AI mobile app. The announcement does not provide a separate self-service activation menu or a public application URL.

  Tip: During program demonstrations, try existing AI glasses use cases—such as reading text, recognizing objects, and describing surroundings—with real work tasks. Use the accessible guides and feedback channel to tell CNIB which tasks are not adequately supported.

  ✓ Verified by official sourceSource: Meta ve CNIB, Kanada’da AI gözlüklerine erişimi destekliyor

New in this edition · 6

• 31 Oct
  AvailabilityKimi API

  K2 series closed to new API users starting October 31

  Starting October 31, 2026, K2 series models are no longer available to newly registered users; existing users are unaffected. Moonshot plans to retire the entire K2 series by the end of December 2026.

  Usage details

  Who can use it: API accounts created after October 31 cannot use Kimi K2.7 Code, Kimi K2.7 Code Highspeed, or Kimi K2.6; users who registered earlier are unaffected until the planned retirement date.

  How to use it: K2 models cannot be selected in new API accounts; switch to the Kimi K3 or Kimi K3.1 Pro model IDs for new integrations. Migrate existing K2 integrations before the end of December.

  Tip: During migration, retest the model ID, context limit, and thinking/streaming parameters in your client code against the K3 or K3.1 Pro documentation.

  ✓ Verified by official sourceModels: Kimi K2.7 Code, Kimi K2.7 Code Highspeed, Kimi K2.6Source: Kimi API model çıkarım fiyatları — K2 erişim duyurusuSource: Kimi API model listesi
• 30 Oct
  CapabilityKimi Code Desktop

  Kimi Code Desktop reduces context usage for long Chinese files

  Kimi Code Desktop 1.2.1 reduces the amount of context used when reading long Chinese files. Built-in prompts were also optimized in the same release.

  Usage details

  Who can use it: Desktop users running Kimi Code Desktop 1.2.1 or later; the release notes do not specify an operating system.

  How to use it: Update Kimi Code Desktop to 1.2.1; the improvement is applied automatically when reading long Chinese files and requires no additional settings.

  Tip: For very long files, attaching only the relevant sections or files to the task can still make context usage more predictable.

  ✓ Verified by official sourceSource: Kimi Code Desktop değişiklik kaydı — 1.2.1 (30 Ekim 2026)
• 29 Oct
  AgentKimi Work

  Kimi Work asks users for critical information before a task

  With Kimi Work 3.2.22, Agent gained the Ask user feature, which confirms critical information with the user before running a task. This lets missing or ambiguous inputs be clarified before the task starts.

  Usage details

  Who can use it: Users running Kimi Work desktop app version 3.2.22 or later.

  How to use it: Update Kimi Work to 3.2.22 and start a task; review the Ask user confirmation that appears before execution and provide the necessary information.

  Tip: For tasks that affect external systems or take a long time, carefully review the assumptions and scope in the confirmation screen before running them.

  ✓ Verified by official sourceSource: Kimi Work sürüm notları — 3.2.22 (29 Ekim 2026)
• 29 Oct
  Pricing / PlanKimi Work / Kimi üyeliği

  Manually purchase an Extra Usage pack after a quota warning

  Extra Usage packs became available with Kimi Work 3.2.22; subscribers can purchase additional usage balance when they receive a quota warning. The balance is shared across Kimi on web, browser extension, desktop, and mobile, as well as Kimi Code.

  Usage details

  Who can use it: Subscribers only; available for personal accounts on web, in the browser extension, desktop and mobile apps, and in Kimi Code. Enterprise plans are not currently supported.

  How to use it: On the web, open the Extra Usage Credit Pack section on Kimi’s Subscription page and select an amount. In Kimi Code, use the Buy Extra Usage Pack button that appears when you exceed 80% of the rolling 5-hour usage limit or the weekly limit on the old plan; then activate Extra Usage Credit Pack on the web.

  Tip: To limit unexpected spending, open Settings in the Extra Usage section on the web and enable Monthly spending cap.

  ✓ Verified by official sourceSource: Kimi Work sürüm notları — 3.2.22 (29 Ekim 2026)Source: Extra Usage paketi: ek kullanım satın alma yardım sayfası
• 29 Oct
  FeatureKimi Work

  Scheduled section consolidated as Task Center

  In Kimi Work 3.2.22, Scheduled was renamed Task Center. Conversation tasks, widget tasks, and other automation tasks can be viewed and managed in one place.

  Usage details

  Who can use it: Users running Kimi Work desktop app version 3.2.22 or later; the relevant task feature is also available in Kimi.

  How to use it: Open Task Center in Kimi Work; enable or pause tasks, run them once, edit them, or delete them. Conversation and widget tasks are also listed in the same center.

  Tip: Before enabling a new automation, test its output using Run once now on the task card.

  ✓ Verified by official sourceSource: Kimi Work sürüm notları — 3.2.22 (29 Ekim 2026)Source: Kimi görevleri yardım sayfası
• 29 Oct
  SettingKimi Work

  Add custom DIY skins to the Kimi Work desktop pet

  Kimi Work 3.2.22 lets users customize the desktop pet’s appearance and add their own DIY skins.

  Usage details

  Who can use it: Users running Kimi Work desktop app version 3.2.22 or later.

  How to use it: Update the app to 3.2.22; add your own DIY skin from the desktop pet customization area. The release notes do not specify the exact menu path.

  Tip: Try a small, simple skin first; if display issues occur, switch back to the default skin.

  ✓ Verified by official sourceSource: Kimi Work sürüm notları — 3.2.22 (29 Ekim 2026)

New in this edition · 1

• 29 Oct
  AvailabilityGrok Bot

  Grok Bot 0.78.1 begins stable rollout: shopping and subscription templates

  Grok Bot 0.78.1 began rolling out gradually on the stable channel following an announcement dated October 28, 2026, at 23:27:36 UTC; this corresponds to October 29 in Istanbul. The release shows product results as cards/carousels with photos, ratings, prices, and store information; users can make approved purchases with Buy now and track deliveries. It also adds templates for subscription trials, finding unused subscriptions, and tracking renewal prices.

  Usage details

  Who can use it: The stable release is rolling out to accounts with Grok Bot access; xAI has not published a separate country list. Access depends on Grok Bot plans such as The X Subscription Premium/Super/Ultra, eligible legacy Cursor plans, and linked SuperGrok or X Premium+ accounts; the feature may appear gradually depending on the account’s rollout and the desktop or mobile Grok Bot app you use.

  How to use it: Update Grok Bot and ask a Bot to search for a product; open a product from the results card, select Buy now, and approve the confirmation card. Connect Shop Pay through Settings → Vault → Payments; then select it in the Pay with field or make it the Bot’s first payment method. For subscription templates, ask a Bot which templates can help with subscriptions, then add one of the Try it, don’t pay for it, Find unused subscriptions, or Watch subscription prices templates.

  Tip: Set purchases and subscription cancellations to Ask first in Auto Review. If you want separate approval for every payment, don’t save the card permanently to Vault; a saved card may be filled in during payment without additional confirmation.

  ✓ Verified by official sourceSource: Grok Bot changelog — v0.78.1: Shopping cards and subscription templatesSource: Grok Bot 0.78.1 is now stable and rolling outSource: Approvals, security, and privacy — purchases and payment handling

New in this edition · 11

• 31 Oct
  AvailabilityQwen / Apple Intelligence

  Qwen is coming to the China version of Apple Intelligence

  Apple announced that it will add Alibaba’s Qwen support to select parts of the Apple Intelligence experience in China. Users will be able to use Qwen’s text and image understanding capabilities in Siri, Writing Tools, and Visual Intelligence; ask Siri questions about photos, PDFs, and presentations; and generate original content in Writing Tools.

  Usage details

  Who can use it: It will be tested in the iOS developer beta on supported iPhones in China starting November 4, 2026, and will roll out to users with iOS 27.3 in December 2026. Siri and the device language must be set to English or Simplified Chinese; other platforms will be supported after the necessary approvals.

  How to use it: Install the relevant iOS developer beta on a supported iPhone and enable Apple Intelligence. When the Qwen experience appears, sign in with a Qwen account or use the Sign in with Apple option; then invoke it from Siri, Writing Tools, or Visual Intelligence.

  Tip: Starting questions about photos, PDFs, or presentations through Siri, and rewriting or generating content from scratch in Writing Tools, makes it easier to use Qwen’s new integration surfaces separately.

  ✓ Verified by official sourceSource: Apple: Apple Intelligence Çin’de kullanıcılara geliyor
• 30 Oct
  Plugin / IntegrationQwen CUA Driver

  CUA Driver v0.27.0 ships ready-to-use binaries, SDK, and MCP packages

  Qwen CUA Driver v0.27.0 ships ready-to-use binaries for macOS, Linux, and Windows; the same release also offers `@qwen-code/cua-sdk` for Node.js, a browser SDK, and `@qwen-code/node-repl-mcp`. Text-based MCP payload filtering options have been added for relative coordinates and model API routes.

  Usage details

  Who can use it: On macOS, it includes a signed and notarized universal binary and `QwenCuaDriver.app`; on Linux, it requires an x86_64/arm64 glibc 2.31 base; on Windows, it includes an x86_64/arm64 UIAccess worker. Windows worker deployment requires signing and establishing trust on the target machine; Node.js packages are published as release assets.

  How to use it: Install the v0.27.0 asset for your operating system, or add `@qwen-code/cua-sdk` to your Node.js project and, if needed, `@qwen-code/node-repl-mcp` for MCP. For relative coordinates, use `CUA_DRIVER_RS_COORDINATE_SPACE=1` and optionally `CUA_DRIVER_RS_COORDINATE_SCALE=1000`; for payload filtering on model API routes, use `MCP_MODEL_PAYLOAD_FILTER=1`.

  Tip: Enable relative coordinates only if the target app’s scaling behavior requires them; on Windows, complete signing and the trust chain before deploying the UIAccess worker to production.

  ✓ Verified by official sourceSource: Qwen CUA Driver v0.27.0 sürüm notları
• 29 Oct
  CapabilityQwen Code CUA

  Cursor and live macOS PiP enabled by default in CUA

  Qwen Code v0.26.4 enables default cursor behavior and a live picture-in-picture view on macOS in computer-use (CUA) workflows. This makes it easier to monitor the model’s screen interactions and see the active target.

  Usage details

  Who can use it: Available in macOS CUA workflows using Qwen Code v0.26.4; the release note specifically identifies live PiP support as a macOS feature.

  How to use it: Update Qwen Code to v0.26.4 and start a CUA session on macOS; `default cursor` and `live macOS PiP` behavior are enabled with the release.

  Tip: Before starting a CUA task, verify the active app and target area in the PiP window; visually check actions that are difficult to reverse, especially deleting or sending files.

  ✓ Verified by official sourceSource: Qwen Code v0.26.4 sürüm notları
• 29 Oct
  AvailabilityQwen Code

  Generated UI cards now use theme-compatible interactive views

  Qwen Code v0.26.4 presents Generated UI views in card frames that follow the host theme, can be localized, and can be reshaped. Cards can open as interactive views when users want to adjust values, marking the next step for the previous editable-card capability in the stable release.

  Usage details

  Who can use it: Available in the Generated UI host/WebShell surfaces of Qwen Code v0.26.4; some newer default Generated UI behaviors are available only in the October 29 nightly preview.

  How to use it: Update to v0.26.4 and create a Generated UI card in WebShell. Open the interactive view inside the card to edit values directly; the release applies the host theme and card frame.

  Tip: Adjusting parameters in the card and sending a follow-up question through the same card is faster than writing a new long prompt for every change.

  ✓ Verified by official sourceSource: Qwen Code v0.26.4 sürüm notları
• 29 Oct
  Plugin / IntegrationQwen Code

  Qwen Code can install and update unscoped npm extensions

  With Qwen Code v0.26.4, npm extensions without a scope can be installed and updated through the CLI and daemon. The source can be specified as a package name, a specific version, or a tag; updates retain the registered package source and registry.

  Usage details

  Who can use it: Applies to CLI and daemon users running the stable Qwen Code v0.26.4 release; scoped and unscoped extensions published to the npm registry are supported.

  How to use it: In the extension installation or update workflow, use `package-name`, `package-name@version`, or `package-name@tag` as the source. The same npm source formats apply to daemon installations.

  Tip: For reproducibility in production, pin a version with `package-name@version`; use the `@latest` and `@beta` tags only in controlled update workflows.

  ✓ Verified by official sourceSource: Qwen Code v0.26.4 sürüm notlarıSource: Qwen Code PR #15781: scope’suz npm kurulumu ve güncellemeleri
• 29 Oct
  FeatureQwen Code

  Qwen Code expands WebShell workspace and session management

  v0.26.4 displays sessions without workspaces alongside workspaces in WebShell, lets embedded hosts select a workspace directory, and adds independent worktrees for Managed parent sessions. The same release also raises the workspace skill installation limit.

  Usage details

  Who can use it: Applies to WebShell, Managed sessions, and host applications embedding Qwen Code when using Qwen Code v0.26.4.

  How to use it: Open the `Session Overview` view in WebShell to manage sessions without workspaces; use the `workspace directory` selection in embedded host integrations. Choose the `independent worktree` option for Managed parent sessions.

  Tip: Using independent worktrees while handling multiple tasks or branches at once helps prevent file changes from getting mixed together.

  ✓ Verified by official sourceSource: Qwen Code v0.26.4 sürüm notları
• 29 Oct
  SettingQwen Code DWS

  Quoted reply setting now configurable by conversation type

  Qwen Code v0.26.4 supports configuring quoted replies by conversation type in DWS workflows. This lets you manage separately whether to quote a previous message in each conversation format.

  Usage details

  Who can use it: Available in bot and conversation workflows that use DWS integrations in Qwen Code v0.26.4.

  How to use it: Set the `quoted replies` behavior for `conversation type` in the DWS conversation configuration; enable quoting for the conversation types that need it and disable it for others.

  Tip: Enable quoting in support or review conversations where it is critical to identify which message a reply refers to; disable it in quick chats to reduce unnecessary context.

  ✓ Verified by official sourceSource: Qwen Code v0.26.4 sürüm notları
• 29 Oct
  AgentQwen Code Managed Agent

  Phased upgrade command added to Managed Agent

  Qwen Code v0.26.4 adds a phased upgrade command for Managed Agent in the reference deployment. Upgrades can now be carried out through defined stages instead of in a single step.

  Usage details

  Who can use it: Available to developers and administrators using Qwen Code’s v0.26.4 reference Managed Agent deployment.

  How to use it: Upgrade the reference deployment to v0.26.4 and run the `phased upgrade` command in the Managed Agent management workflow; do not proceed to the next stage until the current stage is complete.

  Tip: Before upgrading production, run the same phases in staging and verify session and runtime state at each stage.

  ✓ Verified by official sourceSource: Qwen Code v0.26.4 sürüm notları
• 29 Oct
  AvailabilityQwen Code

  Generated UI becomes the default and WebShell workflows expand in nightly release

  The October 29 preview, `v0.26.4-nightly.20261029.70be140e14`, makes Generated UI the default and lets users continue conversations using card values. The same nightly release adds Session Overview and Split View keyboard shortcuts, a background agent counter, live message pagination in WebShell, one-click update coverage, and Russian localization for the Goal card.

  Usage details

  Who can use it: Available only in the Qwen Code nightly/preview channel; it is not automatically available to stable v0.26.4 users.

  How to use it: Install the exact `v0.26.4-nightly.20261029.70be140e14` asset from the GitHub Releases page. In WebShell, use `Session Overview`, `Split View`, the Goal card, and background agent status; if the one-click option is unavailable on the update screen, follow the manual steps shown.

  Tip: Try the nightly build in a separate QWEN_HOME or test environment rather than your stable installation; verify card interactions before bringing the Generated UI default into production sessions.

  ✓ Verified by official sourceSource: Qwen Code v0.26.4 nightly sürüm notları
• 29 Oct
  FeatureQwen Code verify-pr

  Model and tool versions are stamped on verify-pr reports

  Qwen Code v0.26.4 adds the versions of the model, CLI, and skill used to published verify-pr reports. This makes it easier to reproduce the report with the same toolchain and audit it later.

  Usage details

  Who can use it: Available to developers using the verify-pr reporting flow in Qwen Code v0.26.4.

  How to use it: Update to v0.26.4 and publish a verify-pr report; the model, CLI, and skill version fields are included automatically in the report output.

  Tip: Keep these version fields unchanged when sharing the report; do not treat results obtained with a different model or skill version as the same review.

  ✓ Verified by official sourceSource: Qwen Code v0.26.4 sürüm notları
• 29 Oct
  FeatureQwen Code

  Model timings added to WebShell Token Usage panel

  Qwen Code v0.26.4 now displays model timing inline in the Token Usage view in WebShell. Users can monitor the timing of a model call in the same place where they view token consumption.

  Usage details

  Who can use it: Available to Qwen Code v0.26.4 WebShell users.

  How to use it: Open the `Token Usage` panel in a WebShell session; model timing information appears inline in the usage view.

  Tip: When comparing the same prompt across different models, track model timing alongside token counts to distinguish whether latency comes from the model or output length.

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

New in this edition · 2

• 31 Oct
  AvailabilityDeepSeek API

  The free period for Search/Fetch in Harness, Claude Code, and Codex is ending

  The free period for server-side Search/Fetch calls by DeepSeek API users through DeepSeek Harness, Claude Code, and Codex ends on October 31, 2026, at 16:00 UTC; per-request billing will begin after that threshold. Direct Search and Fetch API calls cost $0.75 per 1,000 successful requests.

  Usage details

  Who can use it: Users who use the DeepSeek API and call Search/Fetch through DeepSeek Harness, Claude Code, or Codex are affected. In Istanbul time, the threshold is October 31, 2026, at 19:00; direct API endpoints are already subject to billing rules.

  How to use it: No settings need to be enabled; continue using your existing integrations. For direct use, include a DeepSeek API key in calls to `POST https://api.deepseek.com/v1/tools/search` or `POST https://api.deepseek.com/v1/tools/fetch`, and check your account balance before and after the threshold.

  Tip: Cache results in agent workflows instead of repeatedly searching for or fetching the same page. Only successful requests that return results are billed; empty results, errors, and timeouts are not billed.

  ✓ Verified by official sourceSource: DeepSeek-V4.1-Flash-1017 resmî duyurusuSource: Search & Fetch API kullanım kılavuzu
• 29 Oct
  AvailabilityQoder’da DeepSeek-Flash

  Qoder extends the DeepSeek-Flash free usage period through October 31

  Qoder International has extended its daily free usage promotion for individual users of DeepSeek-Flash (DeepSeek-V4.1-Flash-1017) through the end of October 31, 2026, at 24:00 (UTC+8). Usage within the daily free quota consumes 0.0× credits; the standard credit rate applies when the quota or promotion period ends.

  Usage details

  Who can use it: Individual accounts on Qoder International’s Free, Pro Trial, Lite, Pro, Pro+, and Ultra plans are eligible; Teams and Enterprise accounts are excluded. The promotion is available in Qoder, Qoder IDE, the JetBrains plugin, CLI, Cloud Agents, Mobile, and the web app.

  How to use it: In the Qoder product you use, select `DeepSeek-Flash` from the model picker and start a task. The promotion is applied automatically; no application or additional settings are required, and eligible individual accounts with a zero credit balance can also use the daily quota.

  Tip: Plan your use of the daily free quota before it expires; maximum reasoning effort also consumes 0.0× credits within the quota, but the standard credit rate applies once the quota is exceeded and after November 1.

  ! UnverifiedModels: DeepSeek-V4.1-Flash-1017Source: Qoder: DeepSeek-Flash sınırlı süre ücretsiz

New in this edition · 8

• 30 Oct
  Pricing / PlanAutoClaw

  AutoClaw offers rewards of up to 80M tokens in its Halloween campaign

  A new 40M-token reward (4,000 credits) can be claimed during the October 31–November 8 UTC+8 period. If the previous week's reward has not yet been claimed, the total can reach up to 80M tokens across both rewards; the older weekly reward expires on November 1 at 23:59 UTC+8.

  Usage details

  Who can use it: AutoClaw users can claim the new reward starting October 31. The new campaign runs through November 8 at 23:59 UTC+8; the previous reward has a separate expiration date.

  How to use it: Log in to AutoClaw starting October 31 UTC+8 and claim the new 40M-token reward. If you also claimed the previous week's 40M reward, use it before November 1 at 23:59 UTC+8; the two rewards may not be combined into a single balance.

  Tip: Track the expiration dates of the two rewards separately: November 1 for the old credit and November 8 for the new campaign.

  ✓ Verified by official sourceSource: Halloween sürprizi: 80M tokene kadar talep edin
• 29 Oct
  AvailabilityAutoClaw / GLM-5.3-FlashX-Legal

  GLM-5.3-FlashX-Legal is now available directly in AutoClaw

  GLM-5.3-FlashX-Legal has entered the stage where GLM-Legal can be used directly in AutoClaw. The model can review contracts, cross-check evidence, and conduct compliance research; with AutoClaw's agent runtime and document tools, it can produce tracked changes and comments in Word files.

  Usage details

  Who can use it: Available directly to AutoClaw users. Access to the model API under the `glm-5.3-flashx-legal` identifier is open to selected enterprise customers by application; specialized MCP services for legal work and AutoClaw Legal Assistant are also recommended.

  How to use it: Open AutoClaw and provide your legal task and source documents. If using the API, use `glm-5.3-flashx-legal` as the model parameter and apply for selected enterprise trial access at https://z.ai/consultation/legal.

  Tip: Provide source files together for contract and evidence tasks; enable tracked changes and comments for document revisions, and have a legal professional approve the final text.

  ✓ Verified by official sourceModels: GLM-5.3-FlashX-Legal, GLM-Legal, GLM-5.3-FlashSource: GLM-5.3-flashX-Legal AutoClaw'da kullanıma açıldıSource: GLM-5.3-Flash/FlashX ve GLM-5.3-FlashX-Legal API kılavuzu
• 23 Oct
  Pricing / PlanAutoClaw

  AutoClaw unlocks a 40M-token weekly reward with a single login

  During the October 26–November 1 UTC+8 event, users can receive a 40M-token reward worth 4,000 credits by logging into their account once. The reward expires on November 1 at 23:59 UTC+8.

  Usage details

  Who can use it: AutoClaw users can claim it once during the event; the reward is still active as of the October 31 check date.

  How to use it: Log in to AutoClaw between October 26 and November 1 and claim the weekly reward; each account can claim it once, and the credits must be spent before they expire.

  Tip: Claim the reward as early as possible; even if it overlaps with the next campaign, don't miss the November 1 deadline for the previous 40M credits.

  ✓ Verified by official sourceSource: Haftalık ayrıcalık: girişle 40M token
• 19 Oct
  Pricing / PlanAutoClaw

  AutoClaw offers an 85M-token reward for daily logins

  During the October 19–25 event, users could claim 3,000 credits (30M tokens) per day on October 19–20 and 500 credits (5M tokens) per day on October 21–25. Daily rewards expired at midnight UTC+8.

  Usage details

  Who can use it: It was open to all AutoClaw users; the event ran from October 19–25 UTC+8 and had ended as of October 31.

  How to use it: Users had to log in to AutoClaw on event days and claim that day's reward. Each daily reward became invalid at 24:00 UTC+8 that day; the campaign is now closed.

  Tip: For short-lived rewards, plan to claim and use them on the same day; don't leave them until the next day.

  ✓ Verified by official sourceSource: 85M token: günlük giriş etkinliği
• 16 Oct
  RetiredFine-tuning / Private Instance Deployment

  Fine-tuning and custom sample operations have been discontinued

  Starting October 16, the platform no longer supports creating new fine-tuning tasks or datasets, or creating, modifying, or deleting custom samples; existing information can still be viewed. Fine-tuning and deployment services are scheduled to shut down completely on November 16, 2026.

  Usage details

  Who can use it: Existing records can be viewed. Users with a previously signed cloud-private service agreement are exempt under the agreement's terms; other users can no longer start new operations.

  How to use it: Do not try to create new tasks, datasets, or custom samples. To export existing data or make another request, open a support ticket at https://open.bigmodel.cn/ticket-submit and request the necessary data before shutdown.

  Tip: Export custom models and datasets before the November 16 shutdown; users with a cloud-private agreement should confirm migration terms with the support team.

  ✓ Verified by official sourceSource: Model fine-tuning hizmeti kapanış duyurusuSource: Model deployment hizmeti kapanış duyurusu
• 16 Oct
  APIZ.ai API / GLM Coding Plan

  Standard API and Coding Plan keys are now separated

  Starting October 16, API keys for the standard model API and GLM Coding Plan are managed through separate entry points. The new key's type determines billing; old keys were classified automatically, their values did not change, and no mandatory reconfiguration was required.

  Usage details

  Who can use it: Pay-as-you-go or resource package users should use Standard API Key. For an individual Coding Plan, use API Keys → Personal Coding Plan; for a team plan, use the Team Coding Plan → My Plan key.

  How to use it: For standard usage, create a Standard API Key at https://z.ai/manage-apikey/apikey-list. For an individual plan, use the Personal Coding Plan tab on the same page; for a team plan, use Team Coding Plan → My Plan. The standard endpoint is https://api.z.ai/api/paas/v4, and the Coding Plan endpoint is https://api.z.ai/api/coding/paas/v4.

  Tip: To avoid charges to your account while you have Coding Plan quota, check the key type and base URL together; Standard API Key does not use plan quota.

  ✓ Verified by official sourceSource: API anahtarı yönetimi kılavuzu
• 12 Oct
  ModelGLM-Legal

  GLM-Legal opens beta access for legal workflows

  Z.ai introduced GLM-Legal, built on GLM-5.3-Flash with legal-domain mid-training and reinforcement-learning post-training. The model focuses on multistep legal work such as contract review, evidence analysis, compliance research, and document drafting, and is accepting applications for beta access.

  Usage details

  Who can use it: Law firms, legal technology companies, in-house legal teams, and independent practitioners were invited to the beta program. API access is offered to selected users by application, while AutoClaw trials are available through the channel specified in the announcement; no public model identifier or open weights were announced.

  How to use it: Apply for API beta access at https://z.ai/consultation/legal. For a ready-made workflow, open AutoClaw, provide a contract, evidence, or compliance task, and attach the source documents.

  Tip: Clearly identify legal sources and documents when providing them to the model; have an authorized legal professional review the results.

  ✓ Verified by official sourceModels: GLM-Legal, GLM-5.3-FlashSource: GLM-Legal: Ajan tabanlı hukuk zekâsı (resmî duyuru)Source: AutoClaw'da GLM-Legal beta duyurusu
• 10 Oct
  Pricing / PlanAutoClaw

  AutoClaw offers weekly rewards of up to 132M GLM-5.3-Flash tokens

  During its October 13–16 campaign, AutoClaw let all users claim 8 million GLM-5.3-Flash tokens (800 credits) each day. Eligible paid members could receive an additional daily reward based on their active membership tier; rewards expired at midnight UTC+8 on the day they were claimed.

  Usage details

  Who can use it: All AutoClaw users were eligible for the base reward. AutoClaw monthly or group subscribers and GLM Coding Plan individual Lite, Pro, and Max members were eligible for an additional reward; multiple memberships could not be combined.

  How to use it: Users had to log in to AutoClaw on campaign days and claim the daily reward; each account could claim once per day. The reward had to be used by midnight UTC+8 that same day.

  Tip: Claim the daily reward right after logging in and use it before starting long-running tasks; it did not carry over to the next day.

  ✓ Verified by official sourceModels: GLM-5.3-FlashSource: AutoClaw haftalık ayrıcalıkları: 132M token ve üye ödülleri