All updates

Who can use it: Claude Code 2.1.314 and later.

How to use it: Enable permissions.blockWritesOutsideWorkingDirectories in managed or user settings.

Tip: Explicitly define working directories and enforce this setting in CI and on shared machines.

Who can use it: Gemini API users; projects using the Interactions API and GenerateContent API.

How to use it: Add the Computer Use tool from the Gemini API documentation to your request’s tool configuration.

Tip: Before deploying to production, restrict action permissions and steps requiring human approval with separate security policies.

Who can use it: Existing users are unaffected during the transition period; K2 access will be closed to newly registered users after October 31.

How to use it: Migrate API applications using K2 to the Kimi K3 or Kimi K3.1 Pro model IDs.

Tip: Test the migration before the end of December by changing the model ID in the configuration file.

Who can use it: For users of Claude Code in VS Code and the Claude Desktop Code tab; coverage has expanded subject to provider and telemetry conditions.

How to use it: Update Claude Code; leave the Idle compaction option in /config enabled in settings.

Tip: Before pausing a long task, check context usage with /context and /usage.

Who can use it: Kimi Code CLI 2.4.1 users.

How to use it: Increase the max_chars value in the [read] section of config.toml.

Tip: For large log or data files, increase max_chars carefully to preserve context instead of splitting the file into chunks.

Who can use it: Personal accounts with access to the Gemini app, Workspace Individual, and Google Workspace users; in all supported languages.

How to use it: Ask Gemini to create the file type you want in a chat; open the preview full-screen, select text, and request edits.

Tip: Check the structure and sources in the Gemini preview before exporting a presentation or spreadsheet.

Who can use it: ChatGPT Pro 100, Pro 200, and Pro 500, and Business Premium; depends on the plan and account status.

How to use it: No action is required; the new usage allowance is applied to your account automatically.

Tip: Instead of saving intensive Work or Codex tasks for the end of the month, use the new allowance for longer-running tasks.

Who can use it: Beta for Claude Console and Claude Enterprise organizations; the analytics-usage-cost-2026-08-24 beta header is required.

How to use it: Send POST requests to the /v1/organizations/analytics/usage and /v1/organizations/analytics/cost endpoints with the relevant beta header.

Tip: Track costs by workspace and service account as well as by model to identify budget variances.

Who can use it: Support continues for existing users; the new Analytics API is recommended for new integrations.

How to use it: Follow the Migrate from the Usage and Cost API guide to move to the new usage and cost endpoints.

Tip: Instead of removing the old endpoints immediately, compare their results with the new API for a while during migration.

Who can use it: In the ChatGPT Chat experience, depending on account and phased rollout status.

How to use it: In ChatGPT, use the GPT-6-based Chat experience from the model selector; no additional setting needs to be enabled.

Tip: To make responses even shorter, specify the target length and format clearly in your prompt.

Who can use it: Kimi Code CLI 2.4.0 users.

How to use it: Run the /import-sessions command or the kimi import-sessions command, then select the time range.

Tip: Back up the old tool’s session folders before migrating; import only the date range you need.

Who can use it: Phased beta rollout to Pro users in the US.

How to use it: Open the dot profile in ChatGPT and select Texting; enable iMessage on iPhone or RCS on Android.

Tip: Review your dot instructions and connected plugins to limit proactive updates sent by message.

Who can use it: For now, selected cyber defenders and Fairwind Program partners; general user and developer access is not yet available.

How to use it: Once general access is available, use the Gemini 4 Carbon model selection in the Gemini API, product surfaces, or developer consoles.

Tip: For cybersecurity use, add independent security testing and human approval before automatically applying model outputs.

Who can use it: Kimi Code CLI 2.4.0 users.

How to use it: Enable Plan mode yourself using the plan setting in the session or the relevant command, then approve the suggestion.

Tip: If you want to review a plan before files are touched, this change provides a safer review workflow.

Who can use it: Claude Enterprise organizations; eligibility may vary with configurations such as HIPAA or customer-managed encryption.

How to use it: Enable Smart reports, surveys, and pooled group budgets in admin settings; select a team and date range to create a report.

Tip: Use reports to identify repeatable skills and missing connectors, not to measure individual performance.

Who can use it: Members using Kimi Code CLI 2.4.0 and Tower.

How to use it: Set the task model and max_running_tasks value in the Tower configuration.

Tip: When running many tasks at once, start with a low max_running_tasks value to control costs and quotas.

Who can use it: Eligible ChatGPT Pro and Business subscribers; credit amount and eligibility vary by account and offer.

How to use it: Connect your own API organization in ChatGPT or the API Platform and activate the subscription benefit.

Tip: Use the credits first for low-risk prototypes, and check the API organization's billing settings separately.

Who can use it: Kimi Code Desktop 1.2.0 users.

How to use it: Enable the sleep prevention setting under Settings → General.

Tip: Turn it on when running a long build or background task, then turn it off when the work is done to reduce battery consumption.

Who can use it: Users with Gemini in Sheets enabled on Business Standard/Plus, Enterprise Standard/Plus, Google AI Pro/Ultra, Google AI Pro for Education, and AI Expanded Access.

How to use it: In Google Sheets, open the Ask Gemini icon in the upper right and fill cells with AI function; sources appear in the cells.

Tip: Before using generated data, verify the source links in cells by sampling them.

Who can use it: Claude for Legal and Claude Enterprise teams; subject to organization configuration and relevant connectors.

How to use it: Open the Artifacts gallery in Claude or the Claude for Legal page, then choose a legal template.

Tip: Use the automated initial review as a source-linked preliminary step, not as a substitute for a lawyer’s assessment.

Who can use it: All users on web and mobile; the full experience is available in English, Indonesian, Hindi, Brazilian Portuguese, French, and Simplified Chinese. In other languages, the experience is in English.

How to use it: Open the Students section from the Gemini menu or go to gemini.google.com/immersive-explorations.

Tip: When studying a topic, move from large-scale concepts to atomic details to build a concept map step by step.

Who can use it: First-party Claude API.

How to use it: Send the request body directly, ensuring it does not exceed the 128 MB limit; also check your client and gateway limits.

Tip: For large requests, still count tokens in advance and test timeout and proxy limits.

Who can use it: Kimi Code Desktop 1.2.0 users.

How to use it: Turn on the automatic image mention setting under Settings → Agent & Sessions → Composer.

Tip: Keep this setting on so you don’t have to select an image separately when requesting edits based on a screenshot.

Who can use it: Available to API teams using Chat Completions and Responses API; unavailable for multi-agent models and some deferred requests.

How to use it: Add the `guidelines` array to the request body; for each item, send the `type: "policy"`, relevant `category`, and `behavior: "decline"` fields.

Tip: Send only the categories you want to change; unspecified categories retain their default behavior.

Who can use it: Developers with a Gemini API key; installation options are available for macOS, Linux, and Windows.

How to use it: Install the gemini-api CLI and set the GEMINI_API_KEY environment variable; use the generate, analyze, image, or agent commands.

Tip: Pin a specific CLI version in automations; beta releases may introduce backward-incompatible changes.

Who can use it: All ChatGPT plans; on web, desktop app, and iOS.

How to use it: Open the apps or plugins section in ChatGPT and connect iCloud Mail and iCloud Calendar.

Tip: Before making calendar changes, verify the write permission requested by the plugin and the event details.

Who can use it: Available in Singapore on iOS, Android and muse.ai; basic use is free, with subscription plans available for higher usage.

How to use it: Open the Muse app or muse.ai and connect the relevant apps and connectors in settings.

Tip: Before making a purchase or reservation, ask Muse to compare prices, options and terms.

Who can use it: Users covered by Model Studio’s International scope; API usage is subject to charges.

How to use it: Select qwen-audio-3.1-realtime-flash as the model ID in Model Studio and connect to the real-time audio API.

Tip: Enable function calling for voice customer service and have the agent confirm the outcome of an action during the conversation.

Who can use it: Financial advisor teams and organizations; connector access depends on the relevant provider and Claude organization permissions.

How to use it: Install the Claude for Financial Advisors plugin from Claude Marketplace and select the providers you’ll use during setup.

Tip: Limit recommendations from every Skill that works with portfolio or client data to the advisor’s final decision.

Who can use it: Rolling out gradually; it may not be available to all developers at the same time.

How to use it: Reconnect the MCP connection and ask the agent you use to create a new Meta integration; approve write operations one by one.

Tip: Do not share your app secret in the agent chat; Meta requires you to retrieve it from App Dashboard.

Who can use it: Phased rollout in ChatGPT Work and Codex to Plus, Pro, Business, Enterprise, and Edu plans; available to developers in the API.

How to use it: Select GPT-6.1 Terra from the model list in ChatGPT Work or Codex; use `gpt-6.1-terra` in the API.

Tip: For visual and computer-use workflows, evaluate Standard and Fast modes separately to measure the latency-cost tradeoff.

Who can use it: Kimi subscribers; quota is reset for users whose usage is below 25%.

How to use it: No action is required; check your account quota on the Kimi subscription or usage screen.

Tip: When checking your quota, also track how changes to subagent calls after launch affect task consumption.

Who can use it: New Gemini API projects on the paid tier; existing projects retain their previous settings.

How to use it: Add store=false to the request body or turn off Generate Content API logging in AI Studio > Logs and Datasets > Settings.

Tip: For production calls containing sensitive data, explicitly set the storage preference before deployment.

Who can use it: Verified nonprofit organizations; installed automatically on Team and Enterprise plans at no extra cost. A separate discount was announced for verified nonprofits in low- and middle-income countries.

How to use it: Ask Claude to map where your organization stores its information; other nonprofit Skills use this map.

Tip: Before submitting grant applications, check figures cited by Claude against the original documents.

Who can use it: Kimi Work accounts using an IP allowlist managed by corporate workspace administrators.

How to use it: On the access restriction screen, choose Try again or Return to personal workspace.

Tip: For teams working outside the corporate network, separate personal and corporate workspaces in advance.

Who can use it: Kimi Code CLI 2.3.2, Desktop 1.1.3, and relevant web sessions.

How to use it: Enable Swarm mode with the /swarm command or in the multi-agent mode settings.

Tip: Leave Swarm off for simple tasks to reduce quota consumption; enable it deliberately for parallel research.

Who can use it: For accounts using Grok Bot; the relevant desktop app version must be 0.75.2 or later.

How to use it: Open and approve the Auto-review rule suggestion shown on an approval card; rules can also be edited in Grok Bot settings.

Tip: Add rules for repeated, low-risk actions, but keep irreversible actions such as sending money or external messages subject to manual approval.

Who can use it: Users of Kimi.com and the Kimi mobile app; access may depend on account and regional support.

How to use it: Open 3D Make in Kimi, provide text, a sketch, or a reference image; then preview, edit, and export the model.

Tip: Verify dimensions and geometry in desktop 3D software before 3D printing.

Who can use it: Pay-as-you-go Kimi API customers; prices are per million tokens and exclude taxes.

How to use it: Choose a model; for requests with long intervals, use the 1h option with prompt_cache_options.ttl; switch to Batch API for batch jobs.

Tip: Increasing cache hits for repeated long system prompts can significantly reduce costs.

Who can use it: Developers using Kimi API; turning off thinking is not supported for K3.1 Pro.

How to use it: Send the top-level reasoning_effort field in the request as low, high, or max; choose the kimi-k3.1-pro or highspeed model ID.

Tip: Start with low to reduce response latency, and move up to high or max for complex planning and coding tasks.

Who can use it: Kimi.com, Kimi mobile apps, Kimi Work, Kimi Code, and Kimi API; Kimi Enterprise administrators must enable access separately.

How to use it: Use /model in Kimi Code, the kimi-k3.1-pro ID in the API, or the model picker in the app and on the web.

Tip: For long tasks, set the thinking level to max and use the extended context only when truly necessary.

Who can use it: Kimi.com, Kimi Work, Kimi Code, and Kimi API; Pro/Allegretto or higher access in Kimi Code.

How to use it: Use the kimi-k3.1-pro-highspeed model ID in the API or the model picker in Kimi Code.

Tip: Choose Highspeed for interactive code fixes and rapid prototyping, and standard K3.1 Pro for in-depth analysis.

Who can use it: For Grok Bot users; Vault and bot email features are available in version 0.75.2 or later.

How to use it: Open Vault from Settings; ask a Bot to fill out a login or payment form, or forward an email from its own inbox.

Tip: Save only the information in Vault that automation actually needs, and keep Auto-review approval enabled for payment submissions.

Who can use it: Claude Enterprise organizations; requires an Admin API key, the read:claude_tag or write:claude_tag scope, and the experimental-claude-tag-2026-10-21 beta header. Not available for Claude Console organizations.

How to use it: Call the /v1/organizations/claude_tag/ endpoints with an appropriate Admin API key.

Tip: Before changing channel settings, use the API to check whether the active value comes from the workspace or the channel.

Who can use it: Developers with Google Cloud projects and an eligible Anthropic-managed Claude Models setup.

How to use it: Enable Anthropic-managed Claude Models in your Google Cloud project, then configure IAM permissions and Marketplace billing.

Tip: Compare Anthropic API, Google-managed, and Anthropic-managed options based on your latency, IAM, and billing requirements.

Who can use it: For users with Grok Bot access; sharing permissions are subject to team administrator policies.

How to use it: In a Bot conversation, ask it to create a Page in report or dashboard format, or a video from a description or image; use the sharing menu for Pages.

Tip: For a report that needs ongoing updates, use a Page as a living workspace rather than a one-off file.

Who can use it: OpenAI API developers; became generally available on October 22.

How to use it: Use the `v1/decisions` endpoint and the `gpt-6-luna` model; provide `input_json` for structured context.

Tip: Define classification or routing options in advance as a limited, mutually exclusive schema.

Who can use it: Business Standard/Plus, Enterprise Standard/Plus, Google AI Pro/Ultra, Frontline Plus, Google AI Pro for Education, AI Expanded Access and AI Ultra Access; regional and age restrictions apply.

How to use it: During a meeting, open the translation control in the Meet toolbar; administrators can manage the feature via Apps > Google Workspace > Google Meet > Gemini settings.

Tip: For multilingual meetings, ask each participant to select their preferred target language in advance.

Who can use it: Developers using QwenCloud; China and International accounts/keys are separate.

How to use it: Start the /auth flow in Qwen Code, then select the key type and China/International region.

Tip: Make sure the API key’s region matches the workspace endpoint.

Who can use it: Teams that develop enterprise WeCom apps; relevant deployment support is required.

How to use it: Add your WeCom app to the Channel configuration and define the permissions needed to receive and reply to messages.

Tip: In production, limit the app identity’s scope by granting only the necessary group and user permissions.

Who can use it: Available to Model Studio International users; API access and pricing depend on account/region configuration.

How to use it: Call the qwen-audio-3.1-tts-next model through the Model Studio API; include text, timestamps, and reference audio data in the request.

Tip: Combine dialogue and ambient audio in the same generation to create drafts that don’t require separate mixing afterward.

Who can use it: For Grok Bot users; each connector’s own account, region, and permission requirements apply.

How to use it: Connect Zoho CRM, GitHub, Gmail, or Google Calendar from Connect Apps; ask the Bot to perform the relevant action in a chat.

Tip: Select the correct regional data center for your account before signing in to Zoho CRM; choosing the wrong region may cause connection issues.

Who can use it: The Agent Skills standard is publicly available and can be used with Claude and other agent platforms that support the standard.

How to use it: Create Skills based on SKILL.md and share them according to the agentskills.io standard.

Tip: For enterprise Skills, keep instructions, scripts, and reference files separate and versioned.

Who can use it: Qwen Code v0.26.0; the experimental Mods setting and workspace trust are required.

How to use it: Turn on Mods in Settings and restart; trust the workspace before using a plugin.

Tip: Before enabling a third-party plugin, review which files and tools its commands can access.

Who can use it: Qwen Code v0.25.3/v0.26.0; disabled as an experimental setting and not yet available in managed/remote/sandbox sessions.

How to use it: Turn on Generated UI in Experimental settings and restart Qwen Code.

Tip: Adjust variables such as rent, per-person costs, or server traffic in the card to compare alternatives side by side.

Who can use it: Local terminal and standard Web Shell sessions; directories within the same trusted Git repository.

How to use it: Open the project from a subdirectory; workflows saved at the root will automatically appear in the session list.

Tip: Keep a single validation workflow at the root instead of copying a separate workflow for each component.

Who can use it: Qwen Code Channel users with a QQ bot installed.

How to use it: Send a supported file directly to the QQ bot or mention the bot in a group.

Tip: Control token usage by uploading a long document and first asking it to extract sections or fields, then to summarize.

Who can use it: Local Qwen Code Web Shell users.

How to use it: Start with qwen daemon start; manage the service with qwen daemon status, logs, or restart --port <port>.

Tip: Use start --wait in CI or local scripts to avoid starting tests before the service is ready.

Who can use it: Open to applications from enterprise customers and companies building solutions around Grok; partnership access is subject to application and evaluation.

How to use it: Review and apply to the Transformation Partners or Marketplace Partners program at x.ai/partners.

Tip: If you’re planning an enterprise rollout, clarify upfront whether you fall under product integration or consulting/implementation services.

Who can use it: Organizations with Business Plus, Enterprise Standard/Plus, Frontline Standard/Plus, Enterprise Essentials Plus, Education Fundamentals/Standard/Plus, and the Vault add-on.

How to use it: In Vault > Search, select Gemini in Workspace from the service list, then start an Export using custodian user/OU and date filters.

Tip: Limit the export scope to the smallest necessary OU and date range to avoid collecting unnecessary sensitive data.

Who can use it: Claude Platform developers; the API version is available for Claude 4.7 and later.

How to use it: Apply the SDK and client changes in the Migration to API version 2026-10-21 guide.

Tip: Before upgrading the client in production, compare both the old and new API versions using the same test suite.

Who can use it: Research preview and waitlist; initially for Pro and Max subscribers in the US, on iOS, Android, and claude.ai.

How to use it: Join the Claude Duet waitlist and connect your apps with an approval flow.

Tip: Start with reversible, low-risk tasks and clearly define which situations should trigger a notification.

Who can use it: Existing Cloud API integrations will continue working until October 13, 2027; the transition affects all WhatsApp business developers.

How to use it: Accept the Marketing Messages API for WhatsApp terms, validate the live integration on the new endpoint, and update routing for reclassified traffic.

Tip: Do not wait until the deadline to transition; Meta says most integrations take about two weeks.

Who can use it: Business Standard/Plus, Enterprise Standard/Plus, Google AI Pro/Ultra, Google AI Pro for Education and AI Expanded Access.

How to use it: Open Docs Live in the Google Docs mobile app and describe your document’s purpose and the context to use aloud.

Tip: In your voice prompt, specify the target document type, audience, and delivery format from the outset.

Who can use it: Kimi Work Enterprise workspaces.

How to use it: In an Enterprise workspace, start the custom plugin creation or upload flow from the plugin marketplace.

Tip: Test organization-specific MCP connections in a limited workspace first, then publish them to the marketplace.

Who can use it: Rolling out globally to all user tiers on web, mobile, and Windows/macOS desktop apps; many connected apps are English- and US-focused, while some are available in additional English-speaking regions, Brazil, and India.

How to use it: Open the left navigation menu in Gemini and go to Customize; adjust settings in the Skills or Connected apps sections.

Tip: Regularly remove app connections you don’t use and keep only the necessary permissions enabled.

Who can use it: For API users on Model Studio International.

How to use it: Use the qwen-audio-3.1-tts-plus model and audio control tags in the request body.

Tip: Generate the same text with different persona and emotion tags to create a short comparison set for your brand voice.

Who can use it: The market expansion was announced for advertisers; exact eligibility varies by Ads Manager account and country.

How to use it: Apply for ChatGPT Ads through Ads Manager using an advertiser account in an eligible country.

Tip: Before launching a campaign, check that the target country is enabled in Ads Manager and review local advertising policies.

Who can use it: Kimi Work users connected to multiple Enterprise workspaces.

How to use it: Open the avatar menu and select the target workspace from the Enterprise group.

Tip: Check the active workspace label before starting a task to avoid accidentally sending personal files to a corporate workspace.

Who can use it: Google Workspace, Workspace Individual and personal Google account users.

How to use it: In the Notebook Studio panel, select Slide Deck or Video; enable Review outline or Review producer notes.

Tip: For long reports, review the first draft’s structure and narrative tone before generating to reduce the cost of regenerating.

Who can use it: Kimi Code CLI 2.3.0 users and plugin developers.

How to use it: Update skill calls to the <pluginID>:<skillName> format.

Tip: Scan existing AGENTS.md files and automations, and update old unqualified skill names before upgrading.

Who can use it: OpenAI API organization and project administrators.

How to use it: Configure service tier permissions at the project or organization level in Platform settings.

Tip: In production projects, disable high-cost tiers such as Ultrafast by default and enable them only for projects that need them.

Who can use it: CLI users using Kimi Code Remote Control.

How to use it: Start a Remote Control connection and watch the live stream from the connected device; use the 100 MiB limit for larger transfers.

Tip: On a mobile connection, test with text and small files first to monitor data usage.

Who can use it: Users of the User Profiles API on Claude Platform.

How to use it: Use the enforcement_status[] filter on the GET /v1/user_profiles endpoint.

Tip: Before applying restrictions across an organization, log profile records associated with end-customer IDs.

Who can use it: Vietnam; only for Go, Plus, and Pro subscriptions purchased through chatgpt.com.

How to use it: When purchasing a subscription on the web, select MoMo from the payment methods.

Tip: For subscriptions purchased on iOS or Android, manage the payment method through your app store account.

Who can use it: Kimi Work 3.2.18 users.

How to use it: Change the task process view under Settings > Other > General.

Tip: Hide the process for tasks where you want to see the result quickly; keep it visible when debugging.

Who can use it: API customers using supported models in the Responses API.

How to use it: Select a 12-hour cache duration in the prompt caching configuration.

Tip: Cache long, frequently repeated system instructions and avoid unnecessary 12-hour write costs for short tasks.

Who can use it: Announced as a sample workflow for Grok Bot users; production use depends on the relevant support system and permission connections.

How to use it: Connect the support queue and status page, then define periodic monitoring for IncidentWatch and scope, exclusions, and approval steps for IncidentSweep.

Tip: Have a person approve sample tickets, excluded records, and the exact response text before IncidentSweep sends anything.

Who can use it: Rolling out to Free, Go, Plus and Pro users on web, iOS, Android, and the new macOS/Windows desktop app.

How to use it: Open a chat’s three-dot menu and select Lock chat.

Tip: Remember that locking a chat does not exempt it from the data retention policy; review data controls separately for sensitive content.

Who can use it: Claude Console organization administrators and Managed Agents; if web fetch is disabled, an API request returns 400, while an agent call returns an error result.

How to use it: Configure Allow web search and web fetch, along with domain lists, under Claude Console > Capabilities.

Tip: Limit the allowlist to the hosts your agent actually needs instead of using broad wildcards.

Who can use it: Available to developers as an open-source Rust/Python package.

How to use it: Upgrade to deepseek-recipe 0.2.0; use ConversionOptions.model_versions_by_name or with_model_alias for custom model names.

Tip: When migrating from 0.1, check the changed APIs for ConversationRequest and stream generators.

Who can use it: Claude Enterprise organizations.

How to use it: Follow the Inference hooks setup in the Claude Platform documentation and configure hooks for your organization.

Tip: Measure latency and errors in hooks; test rules that could block critical production calls in shadow mode first.

Who can use it: Claude Platform organizations; contact the Anthropic account team and use the webhooks-2026-10-07 header for beta access.

How to use it: Register a webhook destination at the /v1/organizations/webhooks endpoints.

Tip: Implement signature verification, retries, and an idempotency key in your webhook receiver.

Who can use it: Claude Code 2.1.304 and later; Code Review levels are for Team and Enterprise organizations.

How to use it: Run /auto-mode-setup in a Claude Code session; in Code Review settings, select Quick, Standard, or Deep for the repository.

Tip: Run Auto mode setup on a trusted sample project, and don’t generalize its recommendations without reviewing the suggested rules.

Who can use it: Business Standard/Plus, Enterprise Standard/Plus, Google AI Pro/Ultra, Google AI Pro for Education, and AI Expanded Access; BigQuery query permission is required.

How to use it: In a spreadsheet connected to BigQuery, open the Gemini side panel and ask a question or request a dashboard in natural language.

Tip: For large datasets, first verify the results with a sample query and date range, then generate the dashboard.

Who can use it: China subscription plans; Go does not include Kimi Code, while Plus and higher do. Existing Andante and higher plans retain the old rules.

How to use it: Check your plan and credit usage in Kimi via avatar → Settings → Subscription or in the app via Me → Membership Plan → Subscription.

Tip: Agent, Kimi Work, and Kimi Code draw from the same credit pool, so avoid piling long tasks into a single plan period.

Who can use it: Google Workspace for Education Fundamentals, Standard and Plus; only for Gemini Notebooks assigned through Classroom.

How to use it: The administrator must enable Gemini Notebook for the relevant OU/group; teachers should use the assigned Notebook’s insight summaries section in Classroom.

Tip: Before incorporating AI summaries into lesson plans, compare them against relevant student transcripts using a sample.

Who can use it: Business Starter/Standard/Plus, Enterprise Starter/Standard/Plus, Google AI Pro for Education and Google AI Plus/Pro/Ultra users.

How to use it: Open a compatible spreadsheet on iOS and tap the Gemini spark icon; enter a suggested prompt or your own.

Tip: First check the data structure with ‘Summarize this table’, then enter more targeted chart prompts.

Who can use it: All Google Workspace customers, including those in the EEA, Workspace Individual and personal Google account users; the administrator must enable access to Gemini and Gemini Notebook.

How to use it: Open New notebook from the left panel of the Gemini app; Workspace administrators should enable the Gemini and Gemini Notebook settings.

Tip: After the rollout in the EEA, also verify data sharing and the administrator’s OU/group policies.

Who can use it: Google Workspace, Workspace Individual and personal Google account users with access to the Gemini app; web, Android and iOS.

How to use it: Open the interactive app in Gemini and select Export > Google Sites.

Tip: Before publishing, check the sharing permissions and content visibility of the Sites draft.

Who can use it: DeepSeek web/app and compatible agent environments using the model.

How to use it: Specify the complete project goal, tools to use, and delivery criteria in a single prompt, and run it in an agent environment with file access.

Tip: Clearly define the working directory, dependency rules, and test commands before generating code and assets.

Who can use it: Developers with access to Hugging Face or ModelScope; local execution requires suitable hardware and inference infrastructure.

How to use it: Load the deepseek-ai/DeepSeek-V4.1-Flash-1017 model from Hugging Face with Transformers, vLLM, or SGLang.

Tip: Factor the model card’s approximately 763B parameters and 1M context requirements into your hardware plan.

Who can use it: Available via API through deepseek-flash and in the official web/app models.

How to use it: Run deepseek-flash calls without changing the model name; use an up-to-date agent environment for tool-based coding.

Tip: For long agent tasks, measure output length and total task duration to compare costs with the previous version.

Who can use it: DeepSeek web and app users; accounts using deepseek-flash via API.

How to use it: Keep the model name as deepseek-flash in the API; no additional settings are needed on the app or web.

Tip: To track behavioral changes in results, compare important prompts again with outputs from before 1017.

Who can use it: Available to developers with a DeepSeek API key and sufficient balance.

How to use it: Call POST https://api.deepseek.com/v1/tools/fetch with a Bearer key and provide an HTTP/HTTPS url field in the JSON body.

Tip: Set up a small test workflow first, keeping in mind that failed calls or calls that produce no content are not charged.

Who can use it: Available to developers with a DeepSeek API key and sufficient balance.

How to use it: Call POST https://api.deepseek.com/v1/tools/search with a Bearer key; query is required, count can be 1–50, and need_content is optional.

Tip: Use the site:, lang:, after:, and before: query operators to improve source quality.

Who can use it: All developer accounts with an API balance; calls within tools are free until October 31, 2026 at 16:00 UTC.

How to use it: Call the separate Search or Fetch endpoint; requests that return a 200 status code and actual results are deducted from the balance.

Tip: Increasing the Search count does not change the price; cache results yourself to avoid unnecessary repeat calls.

Who can use it: Developers using these agent and coding tools; the tools’ own access requirements apply.

How to use it: Upgrade DeepSeek Harness to 0.2.1-rc.1 or later and select the deepseek-flash model; use the DeepSeek API connection in CodeBuddy/WorkBuddy.

Tip: When comparing different agent environments on the same repository, keep tool permissions and the context window fixed.

Who can use it: Users of DeepSeek Harness, Claude Code, or Codex who use the DeepSeek API; the free period lasts until October 31, 2026, at 16:00 UTC.

How to use it: Configure a supported agent tool with a DeepSeek API key and enable server-side web search.

Tip: Measure production traffic before November 1 and budget for Search and Fetch costs under the new pricing.

Who can use it: Applies to all accounts using the Search and Fetch APIs.

How to use it: Queue requests below 100 QPS for Search and 25 QPS for Fetch; wait and retry on HTTP 429 responses.

Tip: Remember that multi-agent traffic shares the account-level quota; implement client-side backoff and retries.

Who can use it: Developers using the Agents API; Ultrafast is available only on supported models and within eligible rate limits.

How to use it: Select a hosted sandbox environment; to use the speed tier, set `service_tier` to `ultrafast` in the agent configuration.

Tip: For document generation, edit the output with the Artifact SDK, then validate the formatting before delivering the final file to the user.

Who can use it: Rolling out on web and desktop to eligible Pro, Business and Enterprise users with Space access.

How to use it: In Work, ask ChatGPT to create a presentation in Space.

Tip: Add a sample deck or brand guidelines to the initial prompt to establish the layout and visual style from the outset.

Who can use it: For eligible ChatGPT Pro users; in managed workspaces, availability depends on administrator and deployment settings.

How to use it: Select GPT-6 Pro in the Chat tab and request a task that can be divided into parallel subtasks.

Tip: Break the task into clear, independent subtasks to speed up parallel work.

Who can use it: All API customers; voice generation is billed at standard GPT-Live session rates.

How to use it: Use the Audio voices endpoint or Voice Playground to create a voice from a text description and connect it to a GPT-Live session.

Tip: Describe the desired pace, age, emotion and pronunciation using brief, concrete wording.

Who can use it: Model Studio API users; supported regions include Germany (Frankfurt) and US (Virginia). No separate region is specified for Türkiye.

How to use it: Connect to the Chat Completions or Responses API using the workspace endpoint for your selected region and the API key for that region.

Tip: When using the service from Türkiye, compare Frankfurt with other supported regions based on latency and data residency requirements.

Who can use it: Claude Code 2.1.302 and later.

How to use it: Use CLAUDE_CODE_AUTO_MODE_MODEL for Auto mode; turn idle compaction on or off under /config > Idle compaction.

Tip: When changing the classifier model, compare safety refusal and latency metrics on the same project.

Who can use it: Claude Code 2.1.302 and later; terminal, Agent SDK, desktop, and VS Code surfaces.

How to use it: Set CLAUDE_CODE_FORK_SUBAGENT=0 to disable the default; no action is needed to enable it.

Tip: Separate task boundaries and working branches to prevent write conflicts in shared files during parallel subtasks.

Who can use it: Claude Opus 5.5 users; Claude Platform and Microsoft Foundry Azure deployments. Preview status continues for Claude Opus 5 and 4.8.

How to use it: Enable Fast mode in a Claude Opus 5.5 request; the fast-mode-2026-02-01 header is no longer required.

Tip: Use the speed boost for non-critical, latency-sensitive tasks; monitor the Fast mode rate limit during periods of heavy traffic.

Who can use it: Claude Team and Enterprise; an administrator must enable it in Claude Code settings and install the GitHub App.

How to use it: Enable Code Review in Claude Code settings, install the GitHub App, and select the repositories to review; reviews will start automatically on new PRs.

Tip: Start with Deep for critical repositories and Quick for small, frequently changing repositories, then monitor review times.

Who can use it: Rolling out in ChatGPT Voice; the voice list varies by region and account.

How to use it: Select an available voice at Settings > Voice > Voice.

Tip: If accent accuracy is important, set the Voice language at Settings > Voice > Language before you start speaking.

Who can use it: The weights are available through Hugging Face, Amazon SageMaker AI, Google Cloud Model Garden and Microsoft Foundry Models; hosted inference is available through Baseten, Fireworks AI, Groq, Modal, Nebius, OpenRouter and Together AI. The Muse Model License applies.

How to use it: Download the model from Hugging Face or run it with one of the supported providers; SGLang, vLLM, TensorRT-LLM, Transformers, MLX, llama.cpp and Unsloth are supported.

Tip: For local use, first choose the NVFP4, BF16 or GGUF version suited to your hardware; a 1 million-token context is practical only with enough memory.

Who can use it: Experimental feature, disabled by default; macOS/Linux and compatible agent installations.

How to use it: Turn on Enable Agent Collaboration in Settings and restart; create a teammate on the Agents page and call it with @ in a conversation.

Tip: Assign one agent to write code and another to review it so you can track changes and validation in the same conversation.

Who can use it: Web Shell users running multiple local or remote Qwen Code services.

How to use it: Start Qwen Code servers with --allow-origin and add the instances to Web Shell.

Tip: Leave a long build running on a separate machine and track its progress from your laptop on the same page.

Who can use it: Claude Enterprise; requires an existing Compliance Access Key and the read:compliance_user_data scope.

How to use it: Call the GET /v1/compliance/organizations/{org_uuid}/user_preferences endpoint.

Tip: When exporting user instructions, apply your access and retention policies for personal or sensitive content.

Who can use it: Kimi Work 3.2.17 users.

How to use it: Add an image to a conversation or run a task that includes an image; it will appear in the conversation stream.

Tip: For image-based reviews, check that the image loaded correctly in the conversation stream before asking for a description.

Who can use it: Claude Models API users; the field returns true or false depending on the supported model.

How to use it: Read capabilities.thinking.types.between_tools in the GET /v1/models response and choose the thinking setting accordingly.

Tip: Read this capability field to select compatible models dynamically instead of hard-coding model IDs.

Who can use it: ChatGPT Plus and Pro; usage and storage limits still apply.

How to use it: Create a new Site from the Sites area in ChatGPT; no additional setting is required.

Tip: When creating many Sites, use a consistent naming convention for folders or workspaces to keep content and permissions organized.

Who can use it: Qwen Code CLI users.

How to use it: Run qwen --disable-mcp-server github or, using a comma-separated list, qwen --disable-mcp-server github,postgres.

Tip: When debugging, first disable only the suspected MCP server to narrow down the source of the issue.

Who can use it: Users of Kimi Work Remote Control.

How to use it: Use the Agent Swarm mode selector in a Remote Control session on your phone or remote device.

Tip: Inform users about the expected increase in credit usage and task duration before switching to parallel tasks.

Who can use it: Eligible life sciences labs at US universities.

How to use it: Complete the Rosalind lab application form as the principal investigator or lab manager.

Tip: Before applying, clarify the lab members and the research use case that requires GPT-Rosalind.

Who can use it: No longer available in ChatGPT, Work, or Codex; API access is unchanged.

How to use it: Select a new model in ChatGPT or Codex; API users should check model status in their platform settings.

Tip: Reassess production workflows pinned to the old model with the new GPT-6 family, and rerun output tests.

Who can use it: Affects API customers using the older versioned slug; new applications should use 3.0 or `latest`.

How to use it: Change the `model` field in requests to `grok-voice-3.0` or `grok-voice-latest`.

Tip: If you use a versioned model in production, validate the migration in a test environment; `latest` makes automatic upgrades easier but does not provide version pinning.

Who can use it: Available to Speech to Speech API users; priced at 0,08 US dollars per minute, and `grok-voice-latest` routes to this model automatically.

How to use it: Use `model=grok-voice-3.0` or `model=grok-voice-latest` in a WebSocket Speech to Speech connection; existing API parameters remain unchanged.

Tip: Start with `grok-voice-latest` for low-latency customer service scenarios; pin the versioned slug if you don’t want version changes.

Who can use it: Linux, macOS, and Windows Desktop users; Remote Control is enabled in settings.

How to use it: Install the Linux package; enable Remote Control in Settings; open the File Tree panel from the right sidebar.

Tip: When working on a server or remote Linux machine, restrict the Remote Control connection securely using a QR code or link.

Who can use it: Claude Console and Claude Managed Agents users; beta.

How to use it: Add an OpenTelemetry destination in Claude Console and enable span settings in the SDK you use.

Tip: Mask prompt content in traces and store only latency, token, and tool-call metrics by default.

Who can use it: Kimi Code CLI users; the experimental setting must be enabled in new sessions.

How to use it: Enable NotifyUser from the /experiments panel in the TUI.

Tip: Enable it to see interim status during long tasks; leave it off to avoid unnecessary noise in sessions that require short responses.

Who can use it: Kimi Code Desktop 1.1.0 users.

How to use it: Turn on the progress updates option under Settings → Lab.

Tip: Enable it to improve visibility during long coding tasks; turn it off when you want to keep the screen uncluttered.

Who can use it: Mac and Windows users with Grok Bot access; the 200 MB total message limit and plan limits still apply separately.

How to use it: Attach files to a Bot chat as usual; skills are selected automatically from installed plugins.

Tip: Before sending large videos, check the 1 GB limit and the requirement that the Bot be able to view the video.

Who can use it: By reservation at Pinacoteca di Brera in Milan, Italy; AI glasses are available as part of the pilot Tuesday through Friday, 10:00 a.m.–4:30 p.m.

How to use it: Reserve the Grande Brera tour and enable artwork recognition on the glasses; choose Meta AI or Be My Eyes for additional help.

Tip: Use open-ear headphones for museum directions and artwork descriptions so you can continue hearing sounds around you.

Who can use it: Developers using Kimi Code CLI and Desktop.

How to use it: Run kimi app or kimi app /project/path in the terminal.

Tip: After exploring with the CLI, specify the folder path to move the same workspace into the GUI.

Who can use it: Claude Platform on AWS users.

How to use it: Create a scheduled deployment for Managed Agents and select the AWS Platform environment as the target.

Tip: Use idempotent operations and safeguards against duplicate runs for scheduled tasks.

Who can use it: English; personal Google accounts for users aged 18 and over and eligible work accounts; regions where Antigravity is supported.

How to use it: On a Mac, click Antigravity at the top of the Gemini app, approve the agent's plan, and bring the result back into the Gemini chat.

Tip: Limit the agent's write and execution permissions to only the project folder it needs.

Who can use it: Paid Gemini API tier and Google AI Studio; not available on the free API tier.

How to use it: Set the model field to gemini-4-argon; for difficult tasks, use generation_config.thinking_level, and for long outputs, use background=true with max_output_tokens.

Tip: Remove temperature, top_p, and top_k from existing integrations, then reassess the quality-cost balance using thinking_level.

Who can use it: Paid Gemini API tier; Gemini 4 Argon is not available on the free tier.

How to use it: Use the gemini-4-argon model on the paid Gemini API tier; include thinking tokens in cost estimates.

Tip: First measure cost and quality with low or medium thinking_level, and use high only for difficult tasks.

Who can use it: Google AI Pro and Google AI Ultra subscribers; country, age, and language restrictions apply to some features.

How to use it: Select Gemini 4 Argon from the model picker in the Gemini app; switch the chat to Tasks mode for eligible tasks.

Tip: For longer tasks, check interim outputs and progress updates to correct misdirection early.

Who can use it: Personal and Workspace accounts in the Gemini app; a new date for Workspace Skills has not yet been announced, and age and license requirements apply.

How to use it: Use the Skills help flow in the Gemini app; Workspace administrators should wait for a new rollout announcement for Skills.

Tip: Teams using Gems should back up their existing Gems workflows during the transition and test Skills equivalents separately.

Who can use it: Rolling out gradually to Facebook Feed and Reels users; it may not appear, depending on the account and region.

How to use it: Open the three-dot menu on a post in Feed or Reels and go to Your algorithm; add topics or give Interested/Not interested feedback.

Tip: Write measurable preferences instead of general statements, such as 'less local politics, more Turkish-language AI training.'

Who can use it: Available immediately to new customers; being rolled out gradually to existing SuperGrok, Cursor, and X Premium subscribers, with global availability targeted for the days following the announcement.

How to use it: Compare plans at x.ai/pricing; existing subscribers can see the option to switch and, if applicable, a prorated refund offer under Billing settings.

Tip: If you use Grok and Cursor heavily together, check the shared usage pool and note that third-party model usage is billed separately.

Who can use it: For Muse Code subscribers; Maximum Usage and Power Usage plans include access to Muse Wonder Full. The announcement did not specify the price.

How to use it: Select the Maximum Usage or Power Usage plan on the Muse Code subscription page; choose Muse Wonder Full from the model selector.

Tip: Use the 80-times limit for extended, multi-file coding tasks; a lower plan may be enough for short tasks.

Who can use it: Muse Wonder is available in Meta Model API and Muse Code; API pricing is $4 per 1 million input tokens and $20 per 1 million output tokens. Muse Wonder Full is available only with a Muse Code subscription, on the Power Usage and Maximum Usage plans.

How to use it: Use muse-wonder-1.0 as the model ID in Meta Model API; in Muse Code, select the model from the relevant subscription plan.

Tip: For long tasks, clearly state the goal, constraints and key approval points in the first prompt; make use of Active Focus generating alternative plans.

Who can use it: Model Studio International API users.

How to use it: Select the qwen-audio-3.1-tts-flash model in the API call and play the streaming response chunk by chunk.

Tip: Reduce perceived latency in voice assistants by starting playback without waiting for the first audio chunk to finish.

Who can use it: Kimi Work users.

How to use it: Start a task while a page is open in the built-in browser, then send the app to the background.

Tip: Keep the browser tab open when doing web research and generating files at the same time.

Who can use it: Kimi Work 3.2.16 users.

How to use it: Open a PDF in Work preview and use the zoom, text selection, or quote controls.

Tip: When preparing a sourced report, select the quote bubble directly and link it to the relevant section.

Who can use it: For Grok Bot users; some email and connector capabilities depend on plan or administrator policies.

How to use it: Request an email address or ask for an X search from within Grok Bot; enable app cards through Connect Apps.

Tip: Use date, like, and repost filters in X search to narrow large result sets.

Who can use it: Users with Grok Bot access; payment and finance connectors are subject to account, region, and approval policies.

How to use it: Connect QuickBooks Online from Connect Apps; during payment, select X Money or Stripe Link from the approval card.

Tip: In payment flows, use Auto-review to require approval for every purchase and money transfer step.

Who can use it: Affected Model Studio users; accounts using the relevant models in the China (Beijing) and Singapore regions.

How to use it: Check the retired models on the Model Studio > Model Monitoring page and migrate production model IDs to current versions.

Tip: To avoid confusion, track fixed-date or currently supported model IDs in production and monitor retirement notices.

Who can use it: Developers using OpenAI-hosted sandboxes in the Agents API.

How to use it: Enable pre-warm configuration for the sandbox before connecting it to the agent session.

Tip: Test prewarming for independent turns that require long waits, and keep it off for short tasks to avoid unnecessary resource consumption.

Who can use it: Beta; requires the managed-agents-2026-04-01 beta header and a workflows enabled configuration in the multiagent field.

How to use it: Set multiagent: {type: multiagent_20261001, workflows: {type: enabled}} in the agent definition and monitor workflow_run events.

Tip: Test the workflow on a small set of documents and verify stage outputs and reruns of failed agents.

Who can use it: Qwen Code and an eligible Bailian/DashScope account; charges apply to the API account.

How to use it: Run the /batch-api command with a task description, approve the sampling plan, and wait for the result files.

Tip: Send hundreds of independent documents to batch instead of waiting for them one by one; use a regular conversation for dependent tasks.

Who can use it: Qwen Code Web Shell; mailbox and allowlist configuration required.

How to use it: Connect a mailbox in Web Shell and add your email address to the allowlist.

Tip: For initial testing, use the email channel only for reversible tasks, such as a harmless log summary.

Who can use it: Mac and Linux with the Chrome extension; Windows is not supported.

How to use it: Install the Qwen Code extension from the Chrome Web Store and request a browser task in a conversation.

Tip: First verify the correct tab and account scope with a read-only summarization task, then allow form submission.

Who can use it: Qwen Code Web Shell and desktop; a Bailian DashScope Realtime API key is required.

How to use it: Open Live in the left menu, paste your DashScope Realtime API key and click Save; then use Open Live Voice and screen sharing.

Tip: When sharing an error window, make sure personal notifications and secrets aren’t visible.

Who can use it: Users covered by Model Studio International; the open-weight version can also run on their own infrastructure.

How to use it: Select the qwen-image-2.1-turbo model in Model Studio, or use Qwen’s open-weight repository for local inference.

Tip: When generating transparent PNG assets and product images, try requesting the background as a separate layer.

Who can use it: Personal accounts; model access varies by plan. This change, based on Google's support documentation, was reported by reputable technology news outlets.

How to use it: Check the model picker in the Gemini app and your Google AI plan; AI Pro or AI Ultra is required for more powerful Pro models.

Tip: If you rely on critical workflows on the free or Plus plan, compare prompt and output quality before the model change.

Who can use it: Qwen Code Web Shell users.

How to use it: After a run, open the Trajectory tab in the right panel and click the time interval you want to inspect.

Tip: Identify whether latency comes from the model, a tool, or a subagent, then optimize only the bottleneck layer.

Who can use it: Dashboards is in beta on paid plans; Motion is in beta on Team and Enterprise. An Enterprise administrator must enable it in Artifacts settings.

How to use it: Request a dashboard in the chat box or type /motion to open the Motion option.

Tip: Verify the query and last refresh time for every chart in a dashboard before sharing it.

Who can use it: Free, Pro, Max, Team, and Enterprise; on Enterprise, availability depends on administrator policies, with the default enablement date specified as October 15, 2026.

How to use it: Request Docs, Slides, or Design in any conversation, or choose a template from the Artifacts tab.

Tip: Before sharing team templates, have the Enterprise administrator check Artifacts and sharing policies.

Who can use it: Developers using managed agents in the Gemini API Interactions API.

How to use it: Replace the agent parameter in the interactions.create call with one of the recommended new Deep Research agents.

Tip: During migration, compare report length, source count, cost, and latency using the same test questions.

Who can use it: Gemini API and Google AI Studio users; the old endpoint has not been shut down, but automatic redirection is in effect.

How to use it: Change the model string in your code from gemini-3.7-flash to gemini-3.8-flash and reevaluate the outputs.

Tip: Rather than relying on automatic redirection, manage the version migration with controlled testing and a fixed evaluation set.

Who can use it: Beta on all paid Claude plans; in Team and Enterprise, an owner or primary owner must enable the connectors.

How to use it: Install the add-on from Google Workspace Marketplace and use Extensions > Claude > Open Claude; to edit from chat, enable the Google connectors.

Tip: Keep the default Ask before edits mode and review each change in the approval card.

Who can use it: All API users, subject to rate limits and supported data residency.

How to use it: Send `service_tier: "ultrafast"` with `gpt-6.1-sol` in a Responses request.

Tip: For real-time streams, use Ultrafast only for requests where latency matters more than cost.

Who can use it: Gemini API and Google AI Studio users; automatic routing is available for the old endpoint.

How to use it: Use gemini-3.6-flash or, when appropriate, gemini-3.8-flash instead of gemini-3.5-flash in requests.

Tip: Re-measure token consumption, latency, and structured output behavior with the new model.

Who can use it: Grok Bot users; Google Slides delivery depends on the permissions of the connected Google account.

How to use it: Ask a Bot to prepare a presentation, choose the example-slide approach, and get the final output as PowerPoint or Google Slides.

Tip: Before generating a presentation, specify the target audience, slide count, and brand template clearly; keep final sharing subject to human approval.

Who can use it: Claude API, Amazon Bedrock, Claude Platform on AWS, Google Cloud, and Microsoft Foundry; Türkiye is on the list of supported regions, but no separate rollout for Türkiye was specified for this release.

How to use it: Use the claude-haiku-5-5 model ID on Claude Platform; in Claude apps, select Haiku 5.5 from the model picker.

Tip: Try Haiku 5.5 as a helper model alongside more expensive models for summarization, classification, compaction, and subagent tasks.

Who can use it: Global rolling rollout: Plus, Pro, Business, and Enterprise on October 7; Free and Go plans starting October 8. Enterprise access depends on admin settings.

How to use it: Ask ChatGPT Chat to explain or compare a topic, or to create an interactive tool.

Tip: Use specific prompts such as “interactive comparison,” “calculator,” or “step-by-step visual” to determine the result format.

Who can use it: The official announcement covers Max, Ultra, and Team; the help article details eligibility for Max and Team. Free, Pro, and Enterprise are not eligible.

How to use it: Use claude.ai > Settings > Billing or, for Team, Organization settings > Billing > API credits > Link organization.

Tip: Since you can link the credit to only one Console organization, check your choice before selecting a production or testing organization.

Who can use it: Beta for Python and TypeScript SDK users; Haiku 5.5 is especially targeted at fast, high-volume use.

How to use it: Subclass the browser use or computer use toolset class in the SDK and implement your own automation method.

Tip: Before using these with real accounts, verify URL permissions and the human approval callback in a limited test environment.

Who can use it: Claude API and Claude Platform surfaces with token-based pricing.

How to use it: No changes are needed to existing prompt caching requests; monitor Sonnet 5.5 usage at the new price.

Tip: Get more value from the discount by caching shared system instructions for long tasks.

Who can use it: OpenAI API customers; the snapshot may change regularly alongside model updates in ChatGPT.

How to use it: Use the `chat-latest` model ID in an API request, or switch to one of the fixed GPT-6 model IDs for production.

Tip: If stable production behavior is required, consider a dated or fixed model ID instead of `chat-latest`.

Who can use it: Muse users on iPadOS; app and some connectors may vary by account, region, and phased rollout.

How to use it: Install the latest version of Muse from the App Store and open the app on your iPad; add connectors in the app settings.

Tip: Use the large screen to review and edit a marketing plan or product page draft prepared by Muse at the same time.

Who can use it: Claude Managed Agents; limited network environments with web tools enabled.

How to use it: Add the required hosts to allowed_hosts in the environment definition, and bring the URL into context through a user message or web_search result before calling web_fetch.

Tip: Test allowed_hosts and allowed_domains together to verify redirect and subdomain behavior.

Who can use it: Paid ChatGPT subscriptions and workspaces; availability depends on region, client version, workspace settings, and model support.

How to use it: Attach a supported audio file to a conversation and enter your request for a transcript, summary, or Q&A.

Tip: Before relying on key meeting decisions, compare the transcript with the recording; transcription errors may occur.

Who can use it: Cybersecurity professionals and organizations whose eligibility is verified; an application and program approval are required.

How to use it: Verify your organization and intended use through the Cyber Verification Program application process.

Tip: Clearly document the defensive scope, human approval points, and abuse-prevention controls in your application.

Who can use it: For Microsoft Foundry users in Global Standard and US Data Zone Standard deployments; short-context pricing starts at 2 US dollars for input and 6 US dollars for output per 1 million tokens.

How to use it: Select and deploy the `grok-4.7` model in the Foundry Models catalog; call it in your application using Foundry APIs and Microsoft Entra ID or an API key.

Tip: Teams with US Data Zone requirements should also test long-context and regional pricing differences when choosing a deployment region.

Who can use it: Rolling out across Gemini app, Google AI Studio, Gemini API, Google Search AI Mode, Google Ads, Google Flow, and Google Stitch; regional and plan restrictions vary by product.

How to use it: Select the gemini-nano-banana-2.1 model in the API; in the Gemini app, prompt it to generate or edit an image.

Tip: For character or product consistency, explicitly specify reference images and the target aspect ratio in the prompt.

Who can use it: All OpenAI API organizations; automatic tier upgrades depend on credit purchases.

How to use it: In the API Platform, check whether your organization is at the Build, Launch, or Grow level on the Usage tiers or rate limits page.

Tip: Before buying credits unnecessarily to move up a tier, first measure your actual monthly usage and rate limit needs.

Who can use it: Free and Go plans on web, iOS, and Android in the U.S.

How to use it: Open the Finances experience in ChatGPT and connect supported financial accounts.

Tip: Before making financial decisions, check which connected accounts are covered and when the data was last updated.

Who can use it: Gemini API developers; a shutdown date for the old model has not yet been announced.

How to use it: Use the gemini-nano-banana-2.1 model ID instead of gemini-3.1-flash-image in requests.

Tip: Migrate after testing image quality, resolution, and cost differences with your production use cases.

Who can use it: Claude Models API users.

How to use it: Read the capabilities.server_tools.web_search and code_execution fields in the response to GET /v1/models or GET /v1/models/{model_id}.

Tip: Automatically configure the toolset based on these fields instead of including unsupported tools in the request body.

Who can use it: Eligible API organizations; scope and service eligibility depend on OpenAI’s BAA terms.

How to use it: In the API Platform, start the BAA acceptance and HIPAA support flow from Organization settings > General.

Tip: Before enabling compliance, confirm with your legal and security teams which endpoints and data flows are covered.

Who can use it: In Grok Bot’s Language options, for supported accounts and client versions.

How to use it: Select Marathi, Tamil, Telugu, Swahili, or Hausa from Settings → Language.

Tip: If you use Follow System to match the system language, make sure your computer’s language is one of the supported options.

Who can use it: Expert mode is available on grok.com; Fast mode is available to paid subscribers.

How to use it: In a grok.com chat, select Expert or, if you’re on a paid plan, Fast from the model/mode selector.

Tip: Try Expert for lengthy coding and research tasks, and Fast for short, time-sensitive questions.

Who can use it: SuperGrok Plus and SuperGrok Heavy subscribers.

How to use it: Sign in to grok.com; open an existing Bot or chat thread from the Bots section of the sidebar.

Tip: Enable browser notifications so you don’t miss a Bot’s completed tasks while the tab is in the background.

Who can use it: Affects API customers using the old 1.0 slug; routing is applied automatically at the same price.

How to use it: Set `model` to `grok-voice-transcribe-2.0` in your client code, or use the existing default routing.

Tip: After automatic routing, compare the language, timestamps, and diarization output against your production samples again.

Who can use it: Available through the Model Studio International API.

How to use it: Select the qwen-image-2.1-pro model in a Model Studio request; include reference images and local mask inputs in the request.

Tip: For an e-commerce image, provide the product, model, and accessories as separate references and combine them in a single composition.

Who can use it: In ChatGPT’s web and mobile apps.

How to use it: Tap Try on in a product listing and add a photo. Use Favorites or folders to save products.

Tip: For more consistent comparisons, use a reference photo taken from the front in the same lighting as your virtual try-on.

Who can use it: Grok Bot desktop and web users; the apps shown may vary based on account and team permissions.

How to use it: Open Connect Apps in Grok Bot, select an app by category or search, and complete the connection.

Tip: Before connecting a connector, check the card to see which account and permissions the Bot will use.

Who can use it: Rolling out on iOS.

How to use it: In mobile ChatGPT, open the camera, select Scan from the three-dot menu, and capture the pages in succession.

Tip: Fit the document edges fully in the frame and capture pages in a consistent order; check the preview before the PDF is created.

Who can use it: Users with access to Grok Bot; Primary Bot setup required.

How to use it: Use the starred Primary Bot during Grok Bot setup or in Bot details; approve the task from the suggested task card.

Tip: Start with low-risk, repetitive tasks for proactive suggestions; require approval for external communications and financial decisions.

Who can use it: Claude Code 2.1.287 and later; trusted marketplace plugins and local plugins.

How to use it: Install a mod plugin or install one from the marketplace with /plugin install; run /reload-plugins when needed.

Tip: Because Mods run code with your permissions, install them only from sources you trust and review the manifest.

Who can use it: Claude Models API users.

How to use it: Read the line field in the model list response; its value may be null for models that do not belong to a family.

Tip: For routing that can handle new model releases, use the line field instead of extracting family names from ID strings with regex.

Who can use it: Available in India at meta.com, ray-ban.in, and select electronics and optical stores; starting price 44.300 INR. Ray-Ban Meta Audio coming soon.

How to use it: Buy Gen 3 from Meta or Ray-Ban stores in India and pair it with the Meta AI app.

Tip: Configure noise reduction from the six microphones for crowded or windy environments, and set up the action button for quick Meta AI access.

Who can use it: Dreams research preview; Managed Agents access and an account for a supported model are required.

How to use it: Select a model from a supported model family in the Dreams configuration.

Tip: Have a person review automatically generated workflow suggestions before adding them to production Skills.

Who can use it: The model will be available in the Claude API until November 30, 2026; it is planned to be retired from the API afterward.

How to use it: Replace the model ID with claude-sonnet-5-5 and apply the differences in thinking and tool_choice documented in the Sonnet 5.5 migration guide.

Tip: Before the retirement date, compare staging and production responses using the same evaluation set.

Who can use it: Trusted cyber defenders and testers under the Fairwind Program; developer, business, and consumer access will follow in later stages.

How to use it: Until general access opens, eligible users can apply through the Fairwind Program; general users should follow the app/API announcement on October 13.

Tip: While model access is limited, document security assessments and usage limits before incorporating it into real workflows.

Who can use it: Kimi Work users who use Notion or Feishu; the relevant plugin and authorization are required.

How to use it: Open a Notion or Feishu document from the homepage sidebar; if a plugin created it, select its artifact card.

Tip: Check document comments and page context before AI editing to avoid changes being made in the wrong section.

Who can use it: Personal and Workspace accounts in the Gemini app; eligible Business, Enterprise, and education licenses for Workspace Skills, with an 18+ requirement.

How to use it: Use the Skills creation help flow in the Gemini app; in Workspace, create a separate Skill through Skill Builder.

Tip: For recurring tasks, save brand voice, format, and quality criteria in a Skill, then layer different Skills in the same conversation.

Who can use it: Claude Platform developers; stable client.organization and ant organization surfaces are available in new SDK releases and the ant CLI.

How to use it: Upgrade to the relevant version of the Python, TypeScript, C#, Go, Java, PHP, or Ruby SDK and use client.organization.

Tip: Rather than removing old beta calls immediately, compare response schemas with the stable methods for a while.

Who can use it: Team Bot owners and authorized managers on Teams and Enterprise plans.

How to use it: Add a teammate from the Managers section in Team Bot details; choose a shape and color in the avatar editor.

Tip: Grant the manager role only to people who will oversee the Bot’s permissions and connector scope.

Who can use it: Teams and Enterprise plans using Team Bots; automatic updates are available in the desktop app.

How to use it: Use the voice call button in a Team Bot chat; you can turn off automatic updates in Settings → Updates.

Tip: If update timing is critical on corporate computers, align the Automatic Updates setting with your IT policy.

Who can use it: Developers using the Agents API; also available in Codex and ChatGPT Work on Pro 500 and Enterprise plans.

How to use it: Enable the computer-use tool in the Agents API and manage site access approvals and authentication flows in your application.

Tip: Give the browser agent access only to the domains it needs, and require explicit user approval before irreversible actions.

Who can use it: New Pro 500 subscriptions are subject to account eligibility; Ultrafast is available from the plan selector.

How to use it: In ChatGPT, select Pro 500 under Settings > My Plan; turn on Ultrafast from the model selector in Work or Codex.

Tip: Since Ultrafast uses its allowance faster than standard mode, use it only for latency-sensitive tasks.

Who can use it: Codex Cloud on Plus, Pro, Business, Healthcare, Education, and Enterprise plans; the new CLI on all plans; Security Cloud on Pro, Business, Enterprise, and Edu.

How to use it: Set up a repository and reusable environment in Codex Cloud; open the `/agents` view in the CLI, Code Review on desktop, or Security Cloud on the web or desktop.

Tip: Pin approved tools, dependencies, and permissions in reusable environment templates for cloud tasks.

Who can use it: Pro and Business Premium in eligible markets; beta in Enterprise, Edu, and Healthcare workspaces with admin enablement.

How to use it: Create a dot in the ChatGPT desktop app or on the web, connect your apps, and assign it a task from its profile.

Tip: Before giving a dot ongoing access, limit its task scope, connected apps, and which actions require approval.

Who can use it: Plugin Extensions, creation, and MCP Events are available on all plans; plugin use in Sites is available on Business, Enterprise, Healthcare, and Edu.

How to use it: Developers can set up Extensions and MCP Events flows using the Plugins developer documentation; Site owners can add supported plugins to a Site.

Tip: Publish plugin actions with only the permissions they need, and limit automation triggers to reversible actions.

Who can use it: API customers; subject to rate limits, EU and other regional inference residency are unavailable.

How to use it: Send `gpt-6-astra` with `service_tier: "ultrafast"` in a Responses request.

Tip: For workloads that require EU data residency, use Standard or another supported model.

Who can use it: Plus, Pro, Business, Enterprise, and Edu in ChatGPT Work and Codex; also available in the OpenAI API as gpt-6.1-sol.

How to use it: Select GPT-6.1 Sol from the model list in Work or Codex; use `gpt-6.1-sol` in the API.

Tip: For long coding tasks, measure cached context costs alongside lower reasoning effort levels.

Who can use it: On Go, Plus, and Pro plans; actual limits depend on the account, abuse safeguards, and current plan terms.

How to use it: Open ChatGPT Voice as usual; use your plan’s GPT-Live limit instead of selecting a separate intelligence level.

Tip: Track limit usage during long conversations, and have a plan to switch to text-based ChatGPT if the task is critical.

Who can use it: Sharing features depend on the account, plan, and workspace permissions.

How to use it: Open the sharing dialog for a file or folder in Library, then select access for a person or workspace and the Viewer/Editor role.

Tip: For shared folders, check in advance who will retain the file if ownership changes or access is removed.

Who can use it: In the US and Canada, where Meta offers Muse; basic use is free, with subscription plans available for higher usage. Connectors may vary by account and region.

How to use it: In the Muse app, connect business tools and Meta business accounts from the connectors list in settings, then provide a business goal.

Tip: For the first task, ask it to create a measurable growth plan for the coming period using sales, advertising, and social media data.

Who can use it: Teams using Team Bots and a Slack connection; admin approval and channel permissions are required.

How to use it: Add the Team Bot to a Slack channel; respond to the card when approval is required, or ask the Team Bot to send a message to another Bot.

Tip: Grant approval authority only to people who will assess the action; in public channels, prefer sending sensitive results to a private message.

Who can use it: @ChatGPT for Business and Enterprise; Meetings beta on macOS desktop for Pro and Business; profiles for Free, Go, Plus, Pro, Business, and Enterprise.

How to use it: Ask your admin to enable @ChatGPT; open Meetings in the macOS desktop app and profiles in your ChatGPT profile area.

Tip: Align retention and sharing settings for sensitive audio data in meeting notes with your team policy.

Who can use it: Space and Pages are available on Pro, Business, and Enterprise plans; team tasks are available on Business and Enterprise plans.

How to use it: Create a Space or Page in ChatGPT and invite team members; configure team tasks with connected tools and schedules.

Tip: Check Space, Page, and task permissions separately before sharing personal chats in a shared workspace.

Who can use it: Eligible Enterprise customers; subject to application and approval.

How to use it: Submit an enterprise application through the OpenAI Marketplace interest form.

Tip: Before purchasing, clarify the partner software’s data access, license scope, and terms for applying charges against the OpenAI commitment.

Who can use it: US and Canada; iOS, Android, web, and surfaces supported by Muse. Basic use is free, with subscription plans available for higher usage.

How to use it: Open the Muse app or muse.ai and check availability in your account region.

Tip: For business use in Canada, first verify the Instagram professional account, Facebook Page, and email calendar connections separately.

Who can use it: Claude API, Amazon Bedrock, Claude Platform on AWS, Google Cloud, and Microsoft Azure; Türkiye is on the list of supported regions, with no dedicated Türkiye rollout specified. Text watermarking is applied to new models in the EU.

How to use it: Use the claude-sonnet-5-5 model ID on Claude Platform; in Claude apps, select Sonnet 5.5 from the model picker.

Tip: Start with Low or Medium effort for routine coding and document tasks, and increase effort only for complex tasks.

Who can use it: Public beta on Teams and Enterprise plans.

How to use it: Configure a Grok Bot for your team, add the required plugins, credentials, files, and skills, then share it as a Team Bot.

Tip: Give the Team Bot only the files and permissions it needs for its role; test the sharing settings to confirm that personal conversations remain private.

Who can use it: A new platform for businesses and developers; detailed plan, regional, and pricing information has not yet been provided in the announcement.

How to use it: Follow Meta Enterprise Platform channels for enterprise access and product announcements; use Meta Model API and Muse Code for current developer access.

Tip: When planning enterprise use, document model access, data privacy, and agent approval workflows as separate requirements.

Who can use it: Reported only for the China ecosystem workflows mentioned in the article, involving Quark and Qwen; access in Türkiye/EU has not been confirmed.

How to use it: The news source describes invoking Quark Cloud Drive with @ on the Qwen home page and, if necessary, enabling the Quark Cloud Drive Management skill.

Tip: Before granting access to cloud files, check which folders Qwen will be able to read and write.

Who can use it: Grok Imagine users; the plan’s video-generation allowance and rate limits apply.

How to use it: Select the Loop tile on the Imagine home page, or open an image’s Make Video menu and use Loop.

Tip: For scenes suited to looping, such as product rotations or location transitions, keep the start and end images in the same composition.

Who can use it: Grok Bot users; a connected Outlook account and sending permissions are required.

How to use it: Connect Outlook through Connect Apps, ask the Bot to prepare a draft, and use the Send email option on the chat card.

Tip: When using it for the first time, check the sender address, recipients, and signature on the draft card.

Who can use it: Available to developers using the API; the legacy `user` field continues to be accepted.

How to use it: Add an opaque value generated by your application for each end user to the `safety_identifier` field.

Tip: Do not put an email address or directly identifying personal data in the identifier field; use an irreversible, opaque application ID.

Who can use it: Developers on paid Claude plans; a single MCP connector or a plugin bundle hosted on GitHub can be submitted.

How to use it: Submit your plugin at claude.ai/directory/manage/new, fix the automated validation results, and publish it after approval.

Tip: Run the pre-submission test suite to validate MCP 2.0, MCP Apps, and Enterprise Managed Auth extensions early.

Who can use it: API and Codex users; the new model behavior is applied automatically.

How to use it: Rerun workflows that use image inputs; repeat your evaluations if needed.

Tip: For image evaluations, compare old and new outputs using the same test set.

Who can use it: Qwen Code v0.24.1–v0.24.4; Web Shell workflow users.

How to use it: In Web Shell, go to Workflows history and select either Retry Failed Path or Rerun All.

Tip: For workflows that take hours, retry failed subagents first instead of rerunning everything.

Who can use it: Developer preview; early access registration is required, and access is rolling out gradually.

How to use it: Sign up at dev.meta.ai/products/connectors and define the actions on your API or MCP server that Meta AI can call.

Tip: Enable only the actions needed in the connector, and require explicit user approval for write operations.

Who can use it: Global developer access; Geographic Use Policy restrictions by country and enterprise compliance requirements apply.

How to use it: Create an API key through dev.meta.ai and connect to Meta Model API endpoints; select an available model ID from the model catalog.

Tip: Check country restrictions and Standard/Contributor data-use terms before moving to production.

Who can use it: Muse Code users; Windows support announced with Connect, alongside macOS and Linux. Plan and usage limits may vary by subscription or usage.

How to use it: Install Muse Code from dev.meta.ai; open a repository in the Windows, macOS, or Linux client and assign a multi-step engineering task.

Tip: Break tasks into independently testable subtasks to prevent parallel workers from conflicting.

Who can use it: Kimi Work users.

How to use it: Open version history management for the Office file in the workspace, then view or restore a previous version.

Tip: Create a version checkpoint before a major AI edit.

Who can use it: Developers configuring custom providers for Qwen Code.

How to use it: Set the provider to openai-responses or add wireApi: responses to the model entry.

Tip: Test Responses compatibility first with a small, read-only tool call.

Who can use it: Qwen Code Web Shell; local, server, or team computers with SSH access.

How to use it: When adding a workspace, enter the SSH address as the directory path; Trust the workspace to write files and run commands.

Tip: Before connecting to a production server, prefer a separate verification user with read-only permissions by default.

Who can use it: The Sora API is unavailable after September 24, 2026; the web and app experiences are also unavailable.

How to use it: Export Sora content through sora.chatgpt.com/sunset during the final export window.

Tip: Prepare a plan to migrate to an alternative video workflow before leaving legacy Sora integrations in production.

Who can use it: Kimi Work Remote Control users.

How to use it: Open Remote Control on desktop, then use the file preview or upload button in the phone session.

Tip: When connected on mobile, verify that the file was added to the correct project on desktop before sending large files.

Who can use it: Available to developers building AI glasses apps; can be used with supported display and displayless glasses.

How to use it: Add the integration to your existing mobile app using the Device Access Toolkit 1.0 documentation in Wearables Developer Center.

Tip: First test workflows that don't require a phone screen with a small prototype that combines camera, audio, and motion data.

Who can use it: Coming soon; submission and approval details have not yet been released, and selected experiences will be published.

How to use it: Create an account in Wearables Developer Center and submit your experience when approval applications open.

Tip: Design an experience that can be understood with a one-sentence voice discovery prompt on the glasses and completed without looking at a screen.

Who can use it: Kimi Work 3.2.14 users.

How to use it: Open the + panel and select Side Chat; continue your question there, independently of the main session.

Tip: Use Side Chat to try an alternative solution or ask a sensitive follow-up question without disrupting the main task.

Who can use it: Qwen Code users; macOS/Linux environments with Docker/Podman installed.

How to use it: Set QWEN_AGENT_EXECUTION_BACKEND=docker before launching; verify the sandbox boundaries and disabled features.

Tip: Use this mode when inspecting untrusted repository code; run production workflows that require MCP and skills in a separate session.

Who can use it: CLI and Web Shell users on Qwen Code v0.24.1–v0.24.4.

How to use it: Run /context or /context detail in a session.

Tip: When context fills up, first reduce the QWEN.md, memory, or extension with the highest token cost.

Who can use it: WebMCP developer preview; for Meta Ray-Ban Display web apps and Meta AI integrations.

How to use it: Expose only the necessary functions in your web app through WebMCP and test them using the Wearables Developer Center documentation.

Tip: Separate functions into read and write operations; require approval for write actions such as purchases, sending, or account changes.

Who can use it: Users of the Kimi Work built-in browser.

How to use it: Open a web page in the Work browser, add an annotation, and transfer the quote to the input box.

Tip: In long research sessions, note important passages and send them to the Agent with their source context.

Who can use it: Kimi Work users.

How to use it: Enable the feature in Power or Keep Awake settings only for tasks that need it.

Tip: Turn it on for long Remote Control sessions; keep it off during everyday use to reduce battery and energy consumption.

Who can use it: Kimi Code CLI users.

How to use it: If hot reload is needed, use [watch] enabled = true or KIMI_CODE_WATCH=1; mark the workspace as trusted.

Tip: Keep watching disabled in untrusted repositories and open only the folder you need as a workspace.

Who can use it: Rolling out gradually; each connected app’s country, language, account, and age requirements apply.

How to use it: Connect apps from Gemini Settings or call the relevant app with @ during a chat.

Tip: Before connecting, review what data each app is permitted to read or modify through Gemini.

Who can use it: Coming to AI glasses in the coming months; it was not yet generally available at the time of the announcement, and region and model eligibility apply.

How to use it: When Muse support for glasses becomes available for your account, say the agent's name and ask a question or give a task about the object you're looking at.

Tip: Before using information seen by the glasses for actions such as making a purchase or filling out a form, verify the result on screen or by voice.

Who can use it: Introduced for Muse surfaces in the Connect 2026 announcement; rollout is gradual and regional availability applies.

How to use it: Start a voice conversation in the Muse app and describe your preferred pace, tone, or accent during the conversation.

Tip: Check important steps of a background task with written confirmation before it is completed, rather than during the voice conversation.

Who can use it: US preorders for Ray-Ban Meta Audio, with shipments on October 13; Gen 3 on sale on announcement day. Countries and optical options may vary by region; the announcement says expansion to Türkiye will come later.

How to use it: Order through Meta.com or authorized Ray-Ban channels and pair with the Meta AI app.

Tip: Consider the Audio model if battery life and open-ear comfort are priorities, and Gen 3 if the camera and quick AI access are priorities.

Who can use it: Coming to supported AI glasses via a software update later in 2026; model and regional availability may vary.

How to use it: When the update reaches your account, start a normal video recording with the glasses’ camera; Dolby Atmos capture will be applied automatically.

Tip: To preserve the spatial audio effect, record in a crowded or active environment and test playback with compatible headphones.

Who can use it: Coming to the US later in 2026; Hearing enhancement will be available on supported glasses for 149,99 US dollars or with a Meta One subscription, with HSA/FSA eligibility noted.

How to use it: On supported glasses, turn on Hearing enhancement, audio balance, or mono audio in the audio or accessibility settings of the Meta AI app.

Tip: Calibrate hearing enhancement in a quiet environment for your personal comfort, and don’t completely block out surrounding sounds in crowded places for safety.

Who can use it: Kimi Code CLI 2.1.0 users.

How to use it: Select fullscreen in the TUI mode setting in /settings, or use tui_mode = fullscreen in ~/.kimi-code/tui.toml.

Tip: Enable it to navigate long Agent outputs like a document; the standard interface may be faster for short sessions.

Who can use it: Announced at Connect 2026 for release in the coming months; device, language, and regional availability may vary.

How to use it: When the features become available on your account, call up Meta AI on the glasses and give a voice task about running, cycling, nutrition, or a product you’re looking at.

Tip: For shopping, ask for a voice summary comparing prices and reviews, then confirm the purchase separately.

Who can use it: Kimi Code Desktop 1.0.3 users.

How to use it: Click a local HTML file in the transcript; manage the download from the download history in the address bar.

Tip: Verify the web interface created by the Agent in the built-in browser without exporting the file.

Who can use it: On sale in the United States, Canada, and the United Kingdom; on sale in France, Italy, and Germany starting October 13, 2026. The announcement says “later” for Türkiye.

How to use it: Order through Meta.com or authorized optical/retail channels in supported countries; pair the glasses with the Meta AI app.

Tip: If you plan to buy from Türkiye, wait for stock and compatibility announcements on the official country page; warranty and features may differ for orders from outside the region.

Who can use it: Introduced as a technology and Muse experience in the Connect announcement; not all example avatars are available in the Muse app.

How to use it: When the avatar feature becomes available for your account in Muse, select a reference image and start a real-time voice conversation.

Tip: Before sharing generated avatars, check Meta's invisible Video Seal watermark and terms of use.

Who can use it: Kimi Code Desktop users; the free-account warning appears on applicable plans.

How to use it: Turn off the automatic session title setting in Settings; on the free plan, follow the upgrade prompt when a subscription model is selected.

Tip: Keep title generation off if you don’t want project names changed automatically.

Who can use it: Not yet generally available or accessible via API; no release date announced.

How to use it: There is nothing to enable right now; follow Qwen’s official announcements and the Model Studio model catalog.

Tip: Do not treat the roadmap as a replacement for existing Qwen3.8 models; wait before changing production integrations.

Who can use it: Claude Platform, Amazon Web Services, Google Cloud, and Microsoft Azure; verification programs apply to high-risk work such as cybersecurity and life sciences.

How to use it: Use the claude-opus-5-5 model ID on Claude Platform; in Claude Code or Claude apps, select Opus 5.5 from the model picker.

Tip: Route context-heavy work such as long, open-ended code migrations to Opus 5.5, and narrow, repetitive tasks to Sonnet or Haiku.

Who can use it: Gemini API and Google AI Studio; rollout has begun in Gemini Notebook and Google Vids, with Gemini Enterprise access coming in a later phase.

How to use it: Select the model in the AI Studio speech generation area or use the model IDs in the Gemini API speech generation guide.

Tip: For long-form content, verify voice and character consistency with a short segment before generating the full piece.

Who can use it: Plus, Pro, Business, Enterprise, and Edu in ChatGPT Work and Codex; GPT-6 Luna in the desktop app on Free and Go; gpt-6-sol and gpt-6-luna in the API.

How to use it: Select Sol or Luna from the Work or Codex model list; use the relevant model ID in the API.

Tip: Test the same task with Sol and Luna to create task-based routing rules for quality, speed, and token cost.

Who can use it: Gemini API and Google AI Studio; AI Studio voice replication is unavailable in Illinois, Texas, the EEA, the United Kingdom, Switzerland, and India.

How to use it: Query the /v1beta/voices endpoint; follow the consent verification workflow in the voice design or voice replication guide.

Tip: Before replicating a real person’s voice, retain records of explicit consent and usage rights.

Who can use it: Available to Grok Bot users through Settings → Language.

How to use it: Select a language in Settings → Language, or turn on Follow System.

Tip: For shared team use, check the client language and the Bot’s response language separately.

Who can use it: For API teams on the global endpoint and US regional endpoint; the applicable long-context price applies to context of up to 500,000 tokens in the public API.

How to use it: Use `model: "grok-4.7"` in a Responses API request; set the `reasoning_effort` field to low, medium, high, or xhigh.

Tip: Reduce cost and latency in long agent loops by using `prompt_cache_key` and, when needed, Context Compaction.

Who can use it: Copilot Pro, Pro+, Max, Business, and Enterprise SKUs; phased rollout and Business/Enterprise admin policies apply.

How to use it: Select Grok 4.7 from the model picker in a supported Copilot client; a Business or Enterprise admin can manage access through the Copilot model policy.

Tip: Monitor your team’s quota, taking usage-based provider pricing and the model’s phased rollout into account.

Who can use it: Model Studio International API users; supported languages and dialects vary by model.

How to use it: Choose the model ID qwen-audio-3.1-asr-flash, -streaming, -filetrans, or -message according to your needs.

Tip: Use filetrans for meeting archives, streaming for live captions, and the message variant for short voice messages.

Who can use it: In Model Studio, Singapore and China (Beijing); a separate API key is required for each region. No separate regional deployment for Türkiye or the EU is specified.

How to use it: For WebSocket, add ?model=qwen3.8-omni-flash-realtime to the workspace URL, or use the WebRTC/AOQ connection flow; configure turn detection with semantic_vad.

Tip: If visual detail is not critical, use video aggregation to reduce real-time inference costs.

Who can use it: API users within Model Studio International.

How to use it: In a real-time connection similar to the 3.0 Plus integration, change the model name to qwen-audio-3.1-realtime-plus.

Tip: If you use voice cloning, verify the reference audio’s authorization and speaker identity in advance.

Who can use it: Open weights are available through Hugging Face, GitHub, and ModelScope; access to the hosted versions on Qwen Chat and Model Studio may vary separately.

How to use it: Use the model weights and sample code in the Qwen-Image-2.1 repository; for the API, select the relevant model ID in Model Studio.

Tip: Combine multiple references into a single composition for a poster or product catalog, then use a mask to limit the final touch-ups.

Who can use it: SuperGrok Heavy subscribers.

How to use it: Open the Bots section in the grok.com sidebar; chat directly with a Bot or add multiple Bots to a group.

Tip: Connect the resources the Bot needs without leaving the chat, and enable browser notifications for long-running tasks.

Who can use it: Text Edit beta and Precise Edit are available on all plans; video keyframes are available on paid plans.

How to use it: Open an image in Imagine and select Text Edit or Precise Edit; on a paid plan, lock an image as an intermediate keyframe when editing a video.

Tip: For posters and social media images, use Text Edit to change text instead of regenerating it, preserving character and layout consistency.

Who can use it: Kimi Code Desktop 1.0.2 users.

How to use it: Open the built-in browser panel and ask the Agent to search for or show a web page.

Tip: For research tasks, make sources visible in the transcript so you can check which pages the Agent used.

Who can use it: Kimi Code Desktop 1.0.2 users.

How to use it: Configure your search provider in Providers settings, then ask Agent to search in the built-in browser.

Tip: If you need enterprise or regional results, check the search provider before starting the task.

Who can use it: Accounts with access to Grok Bot and the relevant Cloud Agent; plan and team policies apply.

How to use it: Ask the Bot in chat to start a Project and plan the work and distribute it to Cloud Agents.

Tip: Clearly specify the success criteria, file scope, and stopping conditions for the work sent to the Cloud Agent.

Who can use it: Speech-to-Text API users; batch is $0.10/hour, streaming is $0.20/hour.

How to use it: Use `grok-voice-transcribe-2.0` in the Speech-to-Text API; to stay on the older version, explicitly pin the `grok-voice-transcribe-1.0` slug.

Tip: Enable key terms and diarization options for phone calls and short multilingual commands, then send the output directly into your workflow.

Who can use it: Available through the API and demo; 60 languages are supported for input and 29 for audio output, with Turkish included in both lists.

How to use it: Use the qwen3.8-livetranslate-flash-realtime model in a DashScope real-time session; set the target language and optional audio output in session.update.

Tip: For meeting translations, retain the source text as well so you can verify names and technical terms later.

Who can use it: Qwen AI Platform and Model Studio API; Model Studio regions and plans are listed in separate documentation. The announcement reported that audio-visual input prices had dropped significantly compared with the previous version.

How to use it: Try the model in Qwen Studio or make a Chat Completions/Responses call to the Qwen3.8-Omni-Flash API; for long videos, use the agent’s evidence-gathering workflow.

Tip: For videos lasting hours, reduce unnecessary frame-processing costs by clearly stating the question and the evidence to look for first.

Who can use it: Claude Enterprise; a Compliance Access Key and the read:compliance_user_data scope are required. The cache diagnostics beta header is available to API users.

How to use it: Filter Compliance sessions with product_surface=claude_in_chrome; read the diagnostics field using the cache-diagnosis-2026-04-07 header.

Tip: When storing Chrome transcripts, separately review user privacy, access scope, and retention period.

Who can use it: API users who have actively used Gemini 2.5 models before; access may be limited for new projects.

How to use it: For new projects, switch model selection to Gemini 3.5 Flash-Lite or Gemini 3.8 Flash; check access for existing 2.5 workflows.

Tip: Inventory dependencies on older models and run backward-compatibility, quality and cost tests with the new model.

Who can use it: Developers using the Antigravity managed agent in the Gemini API Interactions API.

How to use it: Use antigravity-preview-09-2026 in the agent field; implement the new tool schema in clients that handle local tools and function_call.

Tip: Test remote and local operating modes separately before October 5, the sunset date for the 5-2026 release.

Who can use it: Initially available for macOS Apple Silicon/Intel and Windows; the Linux version followed on October 14.

How to use it: Download Kimi Code Desktop, open a project folder, and start an Agent session.

Tip: On first use, select the Always Ask or Ask When Needed permission mode to review file and command changes.

Who can use it: All Google Workspace customers, Workspace Individual and personal Google accounts; an administrator must enable Gemini and Gemini Notebook. EEA access was added in the October 19 update.

How to use it: In the Gemini app, select New notebook from the left panel, then add a focus area and sources.

Tip: Create a separate notebook for each project or course to keep source context from getting mixed up.

Who can use it: Sessions using Qwen Code CLI, Web Shell, and Goal; the settings are disabled by default.

How to use it: Set model.goalMaxTurns and model.goalMaxActiveMinutes in settings; in Web Shell, approve the Goal suggestion.

Tip: For autonomous coding tasks, set token, turn, and time limits to reduce unexpected costs.

Who can use it: macOS/Linux; Windows requires WSL. A Claude Code or Codex account and installation are required.

How to use it: Request a claude-code or codex subagent in the conversation; for a custom agent, define an executor under .qwen/agents.

Tip: Use Codex as a read-only review agent before asking it to make code changes.

Who can use it: Developers using Qwen Code workflows and extensions.

How to use it: Use a slash command such as /audit for a saved workflow; add a limit like +500k to the end of the message.

Tip: For costly workflows, run a test with a low token cap first.

Who can use it: Qwen Code Web Shell users.

How to use it: Open web preview in the right panel and enter the local development URL; select a version from the HTML delivery cards.

Tip: Check desktop and mobile views side by side before submitting a set of changes.

Who can use it: Sessions using Qwen Code’s web_search tool.

How to use it: Set the tools.webSearch.maxPerSession value in settings.

Tip: For long research tasks, combine queries and reduce duplicates before raising the search limit.

Who can use it: Kimi Code Desktop 1.0.1 users.

How to use it: Open a browser call or image card in the transcript; hover over a link to view its URL and actions.

Tip: For image-based code reviews, use gallery view to compare with previous screenshots.

Who can use it: Gradual rollout; initially available on web, desktop, and mobile for Pro and Max. In Team beta and Enterprise, the Chat and Cowork unified setting must be enabled.

How to use it: In Claude, write the desired output directly; manage connected apps under Customize > Connectors and global instructions under Settings > Your Claude.

Tip: For tasks with real-world impact, check the Auto/Manual permission setting in the message box and approve critical steps.

Who can use it: Artifacts is available on all plans, including Free; Docs, Slides, and Design are in beta on Enterprise and remain off until an administrator enables them.

How to use it: Ask for a design, deck, or doc in a conversation, or select Output > the relevant template from the message box.

Tip: For enterprise visual consistency, first import your design system on the Artifacts page.

Who can use it: Grok Build users; activates in new sessions.

How to use it: Start a new session to continue working with Grok Build; view notes with `/memory` and edit them with `/dream`.

Tip: Explicitly ask it to save project conventions and test commands to memory; don’t turn temporary task statuses into persistent notes.

Who can use it: Discoverable on Claude, Codex, and ChatGPT; it may not be available to everyone due to a phased rollout. It was released for development and testing workflows, not for production-scale messaging.

How to use it: Add WhatsApp Business Tools MCP to your agent’s MCP configuration and sign in with Facebook Login for Business.

Tip: During initial setup, have the agent check the Terms of Service, payment method, and Business Verification status in advance.

Who can use it: OpenAI API organization and project administrators.

How to use it: Configure the API key creation governance and maximum key lifetime policies in Platform settings.

Tip: Apply short lifetimes and regular rotation to production keys; check that existing keys are not affected by these changes.

Who can use it: Gemini API and Google AI Studio; on the product side, Gemini Live, Search Live and select Workspace experiences. Plan, language, age and regional restrictions vary by product.

How to use it: Select the gemini-3.8-live or gemini-3.8-live-extended-thinking model in the Gemini Live API guide.

Tip: Use Live for low-latency customer conversations and Extended Thinking for complex background tasks.

Who can use it: Plans are available globally; individual product plans start at 2,99 US dollars per month, individual bundles at 7,99 US dollars, and creator/business bundles at 14,99 US dollars. Pricing, benefits, and availability may vary by country, app, and account.

How to use it: Open Meta One or the subscription flow in the relevant app and choose one of the Core, Premium, Essential, Advanced, Expert, or Max options listed on your account.

Tip: If you only need a higher Meta AI generation limit, compare the Core or Premium plan instead of business tools.

Who can use it: Beta on all paid Claude plans; requires approval through Salesforce’s beta program and setup by an organization administrator.

How to use it: Have an administrator request access through AgentExchange, connect Salesforce for the organization, and install the plugin from Claude Marketplace.

Tip: Keep the default approval step for CRM writes and limit automatic updates to low-risk fields.

Who can use it: Eligible Business and Enterprise plans, Google AI, Pro and Ultra, Enterprise Essentials Plus and certain education add-ons; administrator activation is required.

How to use it: Manage third-party connectors in the admin console at Apps > Google Workspace Marketplace apps > Apps list; users can access them from the Gemini side panel in Workspace.

Tip: Enable MCP connections by OU or group using a least-privilege policy.

Who can use it: Grok Bot users with a connected Google Drive, OneDrive, or Gmail account.

How to use it: Connect the relevant app through Connect Apps, then ask the Bot to upload the file or attach it to a Gmail draft.

Tip: Test corporate folder permissions and sharing scope with a low-sensitivity file first.

Who can use it: Grok Bot accounts that can use Routines.

How to use it: In the Routines section of Bot details, right-click the relevant routine and select Pause or Resume.

Tip: Pause a routine instead of deleting it during temporary maintenance periods; check connected connector sessions before enabling it again.

Who can use it: Claude API beta; requires the compact-2026-09-04 beta header.

How to use it: Send the compaction parameter at the top level of the request, then use the returned signed compaction block as the first block in the next request.

Tip: To preserve short-term context, leave the latest user and tool turns intact and compact only the older section.

Who can use it: Kimi Work 3.2.9 users; supported file types and operating system menus.

How to use it: For a file, select Share to Kimi from the share menu or Open with Kimi from the right-click menu.

Tip: Use the operating system’s share workflow directly instead of copying the file to the Work folder first.

Who can use it: Kimi Work 3.2.9 users.

How to use it: Turn on Keep Awake After Screen Off in power settings.

Tip: Use it to turn off the screen while long tasks continue; monitor power consumption on portable devices.

Who can use it: Kimi Work 3.2.9 users.

How to use it: Open a PDF, then select a section or page number from the viewer’s index panel.

Tip: In long reports, use the page field to jump directly to a page number provided by Agent.

Who can use it: Claude API beta; especially for Claude Fable 5.1 and new accounts using preserved thinking.

How to use it: Send the thinking-binding-controls-2026-08-01 header and log thinking_mismatch_allowed records in input_transformations.

Tip: Before moving to enforcement, measure which client or history edit each mismatch record came from.

Who can use it: Kimi Work users; the desktop pet feature must be enabled.

How to use it: Enable the desktop pet and open its speech bubble; send a quick reply directly from the bubble.

Tip: Use the pet for brief reminders and commands, and the main Work window for longer file tasks.

Who can use it: Grok Imagine users; video generation limits and plan entitlements apply.

How to use it: After adding an image in the Imagine creator, choose its role: First frame, Last frame, Loop, or Reference.

Tip: Try the starting/ending frame to control camera movement, or Reference mode for character consistency.

Who can use it: Accounts using the Grok Bot desktop app; team admins can restrict this with network controls.

How to use it: Turn on Route egress through this desktop in Settings → Computer.

Tip: Before enabling this setting, test local network permissions and verify that the Bot can’t run when the computer is off.

Who can use it: Grok Bot users; subject to the relevant repository and provider permissions.

How to use it: When the bot requests access, select a provider from the repository connection card, sign in, and allow the task to continue.

Tip: Grant the bot access only to the required repository and read/write scope rather than opening access to your entire organization.

Who can use it: 1 million token context across all Kimi Code membership tiers; thinking can be set to low, high, or max.

How to use it: Use the kimi-for-coding model ID in Kimi Code; set thinking effort to low, high, or max.

Tip: Start a new session and verify K2.8 Preview behavior before changing existing integrations.

Who can use it: Kimi Work users; the website deployment plugin must be installed.

How to use it: Install the website deployment plugin from the plugin marketplace, then select the deployment action in the project task.

Tip: Before going live, check the local preview and the files that will be shared in the production environment.

Who can use it: European users with a GreenPT account; the provider’s EU hosting and pricing terms apply.

How to use it: In the GreenPT API, set the base URL to https://api.greenpt.ai/v1 and send the model name as deepseek-v4.1-flash.

Tip: Before enterprise use, confirm the data processing location, retention policy, and image/long-context behavior with the provider.

Who can use it: Kimi Work 3.2.7 users.

How to use it: Take a screenshot from Launcher, then click the OCR button in the editor or pin the image to the desktop.

Tip: Send the OCR result to Agent as context instead of typing out screenshot text by hand.

Who can use it: Kimi Work users.

How to use it: Drag a file or folder from Finder/Explorer onto the Work window.

Tip: Add a folder directly instead of selecting multiple files in it one by one.

Who can use it: Kimi Work users.

How to use it: Configure conversation settings once, then check that they’re applied automatically in a new Work conversation.

Tip: Use this inheritance behavior to standardize model, permission, and display settings for recurring tasks.

Who can use it: Public beta for all developers; there is no additional Agents API fee, and tokens and tools used are billed separately.

How to use it: Follow the Agents API quickstart and define the model, tools, environment, and task in a single agent session request.

Tip: For long sessions, write task status and persistent files to the sandbox to make it easier to continue work after context compaction.

Who can use it: Developers with Hugging Face access; local or compatible hosted use under the MIT license.

How to use it: Pull the deepseek-ai/DeepSeek-V4.1-Flash model from Hugging Face and follow the model card’s Transformers, vLLM, or SGLang instructions.

Tip: Given the model’s substantial hardware requirements, prototype with the provider API first, then calculate the cost of local deployment.

Who can use it: Available through the DeepSeek API, official web/app channels, and open-weight distribution.

How to use it: Use deepseek-flash as the model name in the API; for local deployment, follow the inference instructions on the Hugging Face model card.

Tip: For long agent tasks, measure lower active parameter usage and total task duration against previous V4 models.

Who can use it: Users of Windows 10 and 11; a Google AI subscription, age and regional requirements apply to Spark, image and video features.

How to use it: Download the Windows app from gemini.google/desktop; launch it with Alt + Space.

Tip: Test the shortcut to ensure it does not conflict with a key combination you use frequently, and review file permissions.

Who can use it: OpenAI API customers; voice sessions cost $0.05/minute, with backend usage billed separately.

How to use it: Start a full-duplex voice session using the Live sessions API or GPT-Live guide.

Tip: Track voice session and backend agent costs with separate metrics; end the session when the user is inactive.

Who can use it: Claude Managed Agents; server-side permission policies.

How to use it: Add an auto rule to the permission policy and process the evaluation and evaluated_permission fields in the agent event stream.

Tip: For tools that can write data or incur costs, start with rules that require approval rather than auto.

Who can use it: Qwen Code teams using Channel integration; requires sessionScope=user and multiSession=true.

How to use it: Create a task with /session new <name>, switch to it with /session use <name>; add --worktree for file isolation.

Tip: Name one task for code review and another for implementation, and run each in a separate worktree.

Who can use it: Bailian Standard API Key or Token Plan users; Coding Plan requires additional configuration.

How to use it: Start a session with Standard API Key or Token Plan authentication; for Coding Plan, configure the Bailian provider.

Tip: Track web search charges to the key you use separately in your team budget.

Who can use it: DeepSeek API users; the continuation of V4 Pro service was announced in the official changelog.

How to use it: Continue using model=deepseek-v4-pro in the API; check the Models & Pricing page for current pricing and version information.

Tip: Compare V4 Pro and V4.1-Flash outputs on the same task set to reassess the quality-cost trade-off.

Who can use it: Old model names work through a temporary compatibility route; use deepseek-flash for new integrations.

How to use it: Replace old model names in your code with deepseek-flash; during the transition, log which version the old names route to.

Tip: Don’t rely on old names permanently; update the model name explicitly to reduce behavioral differences after retirement.

Who can use it: Developers using the open-weight model or the V4.1-Flash route in the DeepSeek API; actual limits may vary by provider and client.

How to use it: Use the model card’s 1M context_window value as a guide to send long documents in one request or in controlled sections.

Tip: Control input costs with relevance ranking and caching instead of filling the 1M context completely.