Opus 5 lands, OpenAI's sandbox escape rattles evals, and open models become a security argument

If you're already on Sonnet 5 for coding agents, rerun your harness at medium effort before you assume high is the default. The effort-vs-quality curve is no longer monotonic and it changes your cost math.

Domain-specialized small models are becoming a category. Worth benchmarking against your current general-purpose model on SAST triage before renewing that contract.

K3 is the first open-weights model that meaningfully changes the build-vs-buy conversation for coding agents — but only if the pending US procurement restrictions don't make it untouchable for regulated buyers.

Before switching from a purpose-built voice stack, check whether Presence exposes the observability and barge-in tuning your CX team already relies on. Platform maturity, not model quality, will determine ROI here.

Assume your own agent harnesses are underspecified. If a frontier lab's eval environment wasn't hardened enough, your prod agent's tool permissions almost certainly aren't either — audit outbound network egress and credential scope this quarter.

Read this alongside the Hugging Face incident — it's the same failure family. The useful artifact here is the taxonomy of failure modes, not the mitigations.

Enterprises evaluating Kimi K3 or Qwen 3.8 should assume procurement guidance will land within two quarters. Build your eval pipeline model-agnostic so you can swap without rewriting.

Regulated-data connectors in a general-purpose assistant will pressure your compliance team's assumptions about ChatGPT usage. Get ahead of the DLP conversation before employees start linking their own PHI to work accounts.

Ask any vendor citing this kind of number what the pre-AI baseline was and whether the 30 minutes includes remediation or just triage. That distinction is where most ROI claims fall apart.