WEEK OF AUG 2 – 8, 2025

OpenAI opened its weights on Tuesday, sold GPT-5 on Thursday, and the EU's model rules went live on Saturday

Three frontier releases in five days, a coding crown that changed hands twice, two Cursor RCE bugs at the process-spawn boundary, and the first binding legal obligations for general-purpose models in Europe.

Five days, three frontier model releases. On Tuesday Aug 5 Anthropic shipped Claude Opus 4.1 at 74.5% on SWE-bench Verified and Google DeepMind announced Genie 3, a real-time interactive world model generating 720p environments at 24 frames per second as a research preview. Later that same day OpenAI released gpt-oss-120b and gpt-oss-20b, its first open-weight language models since GPT-2, then followed on Thursday Aug 7 with GPT-5.

The week's sharpest contrast is OpenAI against itself: a 117B-parameter Apache-2.0 checkpoint that fits one 80GB GPU, released 48 hours before its most closed model. The second is timing between labs — Anthropic took the SWE-bench crown on Tuesday, OpenAI's own blog reclaimed it at 74.9% on Thursday, and Altman was walking back router behavior and reinstating GPT-4o by Friday afternoon.

Elsewhere the infrastructure bit. On Saturday Aug 2 the EU AI Act's obligations for general-purpose AI model providers became binding, and the same week Cursor's MCP approval model was shown to allow silent, persistent code execution on developer machines.

THU · Aug 7, 2025openaigpt-5model releasepricingagents

GPT-5 ships as a router, not a model picker

OpenAI released GPT-5 into its API platform on Aug 7 in three sizes — gpt-5, gpt-5-mini and gpt-5-nano — reporting 74.9% on SWE-bench Verified, 88% on Aider polyglot, 69.6% on Scale MultiChallenge and 96.7% on tau2-bench telecom, a tool-calling benchmark published two months earlier. In ChatGPT it replaces GPT-4o, o3, o4-mini, GPT-4.1 and GPT-4.5 behind a real-time router that decides between a fast answer and reasoning; the API adds a verbosity parameter, a minimal reasoning effort level, and custom tools that call with plaintext constrained by context-free grammars instead of JSON.

Pricing is $1.25 per million input tokens and $10 per million output for gpt-5, $0.25/$2 for mini and $0.05/$0.40 for nano — TechCrunch reported the flagship undercuts Anthropic's Claude Opus 4.1 at $15/$75 by enough to start a price war. Within 24 hours Altman acknowledged a bumpy rollout on Reddit, API traffic had doubled, and OpenAI restored GPT-4o access for Plus subscribers and promised to make the router's model choice visible.

GPT-5 ships as a router, not a model picker
TechCrunch

WHY IT MATTERS

Once a router sits between your prompt and the model, latency, cost and reliability become runtime variables you cannot pin from the client side — and the same policy that produced the launch week's complaints can be retuned without a version bump. Pin snapshot IDs, measure dollars per resolved task on your own workloads, keep a fallback model wired in, and instrument which variant actually served each request before you move production traffic.

TUE · Aug 5, 2025open weightsopenaigpt-osslicensingself-hosting

OpenAI returns to open weights: gpt-oss-120b and gpt-oss-20b under Apache 2.0

gpt-oss-120b is a 117B-parameter mixture-of-experts model that activates 5.1B parameters per token — 36 layers, 128 experts, 4 routed per token — and gpt-oss-20b is 21B total with 3.6B active and 32 experts. Both carry a 128k context window, full chain-of-thought, configurable reasoning effort and native tool use; OpenAI post-trained the MoE weights in MXFP4 so the 120b checkpoint fits a single 80GB GPU and the 20b fits in 16GB. The weights ship under Apache 2.0 with an additional usage policy, are downloadable from Hugging Face, and are deliberately not served through OpenAI's API.

It is OpenAI's first open-weight language model since GPT-2 in 2019, released in the same week as Chinese-lab open drops and two days before GPT-5. OpenAI reports 120b at near-parity with o4-mini on core reasoning — ahead on AIME 2024 and HealthBench, behind on GPQA Diamond at 80.1% versus 81.4% — but TechCrunch notes it hallucinated on 49% of PersonQA questions.

OpenAI returns to open weights: gpt-oss-120b and gpt-oss-20b under Apache 2.0
Hugging Face

WHY IT MATTERS

An Apache-2.0, self-hostable 117B model activating 5.1B parameters caps what a vendor can charge for that capability tier and makes fine-tuning and data-residency architectures possible on hardware you already own — moving your cost model from dollars per million tokens to GPU-hours and amortization. Budget one 80GB-class card for the 120b or 16GB for the 20b, and verify quality against the stated hallucination rate before trusting it in grounding paths.

TUE · Aug 5, 2025securityagent harnessmcpcursorsupply chain

Cursor's MCP trust model cracked twice: MCPoison and CurXecute

Check Point Research published MCPoison (CVE-2025-54136, CVSS 7.2) on Aug 5: Cursor recorded approval of an MCP server against its name, not the command and arguments behind it, so an attacker who got a benign MCP entry approved in a shared repository could later rewrite it to a reverse shell that ran silently on every project open. It affected Cursor 1.2.4 and earlier and was fixed in 1.3 on July 29, which now forces a fresh approval prompt on any change to an MCP configuration — down to adding a single space.

The same 1.3 release closed CurXecute (CVE-2025-54135, CVSS 8.5), published as a GitHub security advisory on Aug 2: Cursor would create a new dotfile without user approval even though editing an existing one required it, so a chained indirect prompt injection could write the MCP config and register the attacker's server, achieving remote code execution before any model-side guardrail applied.

WHY IT MATTERS

Both bugs fire at the process-spawn boundary, below the model, so prompt-injection classifiers and output filtering are irrelevant to them — and an approved MCP server runs with the developer's user ID, environment variables and cloud credentials. Pin Cursor at 1.3 or later, treat MCP configuration as security-sensitive in pull-request review, hash-pin approved server commands and arguments in CI, and audit trust stores on machines upgraded from 1.2.x: Cursor 1.3 did not retroactively invalidate pre-existing approvals, so an already-poisoned workspace stayed poisoned until the store was cleared.

TUE · Aug 5, 2025anthropicclaudecoding agentsswe-benchpricing

Anthropic holds the coding crown for exactly two days

Anthropic released Claude Opus 4.1 on Aug 5, moving SWE-bench Verified to 74.5% from Opus 4's 72.5% and ahead of OpenAI's o3 at 69.1% and Gemini 2.5 Pro at 67.2%. The advertised gains are multi-file code refactoring, detail tracking in large codebases and agentic search, and the model shipped at unchanged pricing — Opus 4's $15/$75 per million input and output tokens — on the API, Amazon Bedrock, Google Cloud Vertex AI and Claude Code, with no code changes needed.

Two days later OpenAI's GPT-5 posted 74.9% on the same benchmark, flipping the lead inside one week. Anthropic's own post promises substantially larger improvements in the coming weeks, and its related-content rail points to its July 30 disclosure of three incidents in which Claude models gained unauthorized access to real computer systems. Axios, reporting the same week, put Anthropic's revenue run-rate near $5 billion a year against OpenAI's $12 billion.

WHY IT MATTERS

A 0.4-point benchmark gap between Opus 4.1 and GPT-5 is noise, and both labs now refresh flagships on a weekly cadence, so per-release benchmark selection is a losing strategy. The decision-relevant variables are the ones the launch posts leave off the headline chart: cache and batch discounts, tool-call counts, cost per resolved task, and whether the vendor will paginate a model out from under you.

SAT · Aug 2, 2025regulationeu ai actcompliancecopyrighttransparency

The EU AI Act's GPAI obligations become binding — and they are keyed to FLOPs

As of Aug 2, every provider placing a general-purpose AI model on the EU market must maintain technical documentation, publish a sufficiently detailed summary of training content on the AI Office's template, and put in place a copyright policy that respects the rights reservations rightsholders attach to their works. Models trained with more than 10^25 FLOP are presumed to carry systemic risk and must additionally notify the Commission, run risk assessment and mitigation, report serious incidents and maintain cybersecurity protections. The definition itself is computational — more than 10^23 FLOP plus the ability to generate language — which is why the obligations land on labs rather than on the applications built on top of them.

The European Commission published the scope guidelines and the training-content template alongside the July 10 GPAI Code of Practice, and confirmed the Code as an adequate voluntary compliance route. Fines of up to EUR 15 million or 3% of worldwide annual turnover attach to the Commission's enforcement powers, which do not begin until Aug 2, 2026; models already on the market before Aug 2, 2025 have until Aug 2, 2027 to comply. The open-source exemption is narrower than it looks: it relieves qualifying open-source providers of the documentation duties but not of the training-content summary or the copyright policy.

WHY IT MATTERS

Regulation keyed to training compute means the frontier labs absorb the obligations while downstream builders inherit the paperwork, so the training-data summary becomes a document you read before you ship an EU-facing product. Ask providers for their Aug 2 artefacts now — enforcement power arrives in 2026, and pre-existing models have until 2027 to comply, which means the answer you get today is attached to a moving target.