Every change we detect, newest first. Times are Eastern (ET). Archive
What to do: Explore the new Artifact SDK and skills in the Agents API sandboxes, and consider setting agent.service_tier to "ultrafast" for lower token latency.
What to do: If you use fast mode with Claude Opus 5.5 on Azure-hosted Microsoft Foundry deployments, you can drop the beta header, though requests that still send it keep working.
What to do: Remove the fast-mode beta header from Claude Opus 5.5 requests if you no longer need it, but keep sending it for Claude Opus 5 and Claude Opus 4.8 fast mode requests.
What to do: If you use the Compliance API for Claude Enterprise, call the new user_preferences endpoint with your Compliance Access Key and the read:compliance_user_data scope.
What to do: Review the DPoP adoption guide and SKILL.md to add DPoP binding for refresh tokens in your Google OAuth integrations.
What to do: Review the Muse Model License terms and try the model via a hosted inference partner or download the weights from Hugging Face.
What to do: Call it as nemotron-3.5-super-vl-120b-a12b.
What to do: Not on the API; download the weights to run it yourself.
What to do: Not on the API; download the weights to run it yourself.
What to do: Not on the API; download the weights to run it yourself.
What to do: Not on the API; download the weights to run it yourself.
What to do: Try Timestral via the GitHub repository if you need CPU-based time-series forecasting, or use Mistral Forge for domain fine-tuning.
What to do: Remove the fast-mode-2026-02-01 beta header from Claude Opus 5.5 fast mode requests if you no longer need it, and check the Models API for between_tools thinking support.
What to do: If you run Apigee hybrid 1.17.0 or later and want agentic API access, enable MCP via Helm in a maintenance window, upgrading the apigee-operator chart before the apigee-org chart.
What to do: Add an OpenTelemetry destination in the Claude Console and instrument your SDK calls to start tracing requests.
What to do: No action needed unless you want to pin a specific version; otherwise sessions on grok-voice-latest upgrade automatically.
What to do: Check requests that use Batch API with gemini-2.5-flash-preview-tts.
What to do: Add an OpenTelemetry destination in the Claude Console to start receiving spans, and review your organization's web search domain restrictions.
What to do: Review the What's new in Gemini 4 Argon guide for API changes, pricing, and migration guidance before adopting the new model.
What to do: Review the model card and developer guide for gemini-4-argon specifications, token limits, and migration instructions, and consider adopting the .agents/skills plus /goal overnight workflow on your o…
What to do: Explore Gemini 4 Argon on Google's developer platforms if you're building robotics or physical-reasoning applications.
What to do: Review the Gemini API documentation for the new continuation protocol and try Argon in AI Studio if you need long-context, multi-step agentic workloads.
What to do: Check the Gemini API Developer Guide for setup details if you want to build with the new model on the paid tier.
What to do: Check requests that use Prompt caching with gemini-3.8-flash-tts.
What to do: Check requests that use Prompt caching with gemini-3.8-flash-lite-tts.
What to do: Add the managed-agents-2026-04-01 beta header and enable the multiagent workflows field to try dynamic workflows, and monitor runs through workflow_run.* events.
What to do: If you need lower inter-token latency, try service_tier: "ultrafast" with gpt-6.1-sol and review the Ultrafast pricing.
What to do: Try the Developer Knowledge API via the gcloud CLI quickstart, agent skill installer, or client libraries to ground your agents in fresh Google documentation.