AI briefing, 18 November: GPT-6.2, Gemini tasks and Claude linked billing

Checked 18 November 2026. Three announcements dated 17 November change how businesses can choose models, delegate tasks and pay for connected AI services.

GPT-6.2 arrives in Work, Codex and the API

OpenAI launched GPT-6.2 Astra and Sol. Work access covers Plus, Pro, Business, Enterprise and Edu, with Enterprise and Edu administrators required to enable the models. Codex and Work share usage. OpenAI positions Astra for difficult reasoning and Sol for everyday coding and writing; these are vendor characterisations, not Tecrave test results.

Standard API rates list Astra at US$8 per million input tokens and US$40 per million output tokens, versus US$2 and US$10 for Sol. Other service tiers and regional processing change the bill. API tool calling requires the Responses API, and migration changes need developer review.

Tecrave analysis: Compare both models on one existing task, such as turning meeting notes into a checked project brief. Record corrections and total usage cost before switching a workflow. A stronger model does not remove the need to verify commitments and figures.

Sources: OpenAI’s 17 November release, API changelog and current API pricing.

Gemini expands task delegation, with regional limits

Google announced a free task-feature rollout across the US, Japan, Korea, Canada, Australia and India, with advanced features starting in the US. Its examples include calling businesses, arranging appointments and making purchases through connected services. The UK is not among the named launch countries for this update.

Google says purchases require confirmation or pre-approval, with spending caps available. These are vendor-described controls. Calling is unavailable in Indiana, Louisiana, Minnesota, Montana and Nebraska; Google also acknowledges tasks can fail or miss the mark.

Tecrave analysis: An owner in an eligible region could test a low-risk administrative task with a clear budget and an independently checked result. Verify account eligibility and connected-app permissions first. This personal-assistant announcement does not establish approval to connect confidential business accounts or a guarantee that a booking or payment completed.

Source: Google’s task-feature announcement, 17 November 2026.

Claude linked billing removes API-key handover

Anthropic introduced linked billing in beta. Supported third-party platforms can charge Claude API usage to a customer’s linked Claude Platform organisation without receiving that customer’s API key. An Owner, Admin or Billing user approves the link. Customers can set platform-level monthly spend limits and unlink through Console; usage draws on an existing commitment or pay-as-you-go billing.

The important caveat is data control: requests run in the platform’s organisation. The customer’s own organisation settings for IP allowlists, encryption keys and data retention do not carry across.

Tecrave analysis: Before linking an automation tool, check its data-handling terms separately from its billing approval. Start with a modest spend cap and non-sensitive records. Removing key-sharing reduces one credential-handling burden, but it does not establish that the platform inherits your security configuration.

Source: Anthropic’s linked-billing announcement, 17 November 2026.

Prepared with AI assistance from linked primary sources. Tecrave’s business implications are analysis. We have not hands-on tested these releases or independently verified vendor performance claims. No affiliate links are included.

Explore tools for existing business tasks · Our editorial policy