Repositioning day: OpenAI productizes, Google bifurcates, Anthropic rations

TL;DR

• GPT-5.5 wins Terminal-Bench but loses SWE-bench Pro and GPQA Diamond to Claude Opus 4.7; UK AISI broke its jailbreak defense in six hours.
• OpenAI’s Workspace agents replace Custom GPTs with cloud-resident workers holding live credentials; credit-based pricing starts May 6, 2026.
• Google’s 8th-gen TPU splits into 8t for training and 8i for inference, trailing NVIDIA Vera Rubin roughly 3:1 in per-socket FP4 PFLOPs.
• Anthropic tested pulling Claude Code from $20 Pro plans as agentic sessions outrun the tier’s compute economics.
• U.S. officials accused China of industrial-scale theft of frontier model weights from OpenAI, Anthropic and Google ahead of a Trump-Xi summit.

Today’s headline launches share a tell: none of them are clean capability wins. OpenAI shipped GPT-5.5 with a defensive posture against Claude Code, retired Custom GPTs in favor of credentialed Workspace agents, and pushed a Codex curriculum aimed at non-coders — three moves in one day that read as distribution strategy, not a frontier leap. Google answered by splitting its 8th-gen TPU into separate training and inference chips, conceding per-socket parity to NVIDIA and AMD and competing instead on cluster economics. Anthropic, meanwhile, is the day’s quiet counterweight: it holds the coding benchmark lead but is testing how to ration Claude Code on the $20 Pro tier because power users are burning the plan economics down. The throughline is that the easy capability gains aren’t paying for themselves anymore, and every major player is reorganizing — packaging, pricing, silicon — around that fact. The geopolitical brief sitting underneath all of this, with the U.S. accusing China of industrial-scale weight theft, is a reminder that the moats everyone is shoring up are also the ones being targeted.

GPT-5.5 ships as a strategic consolidation, not a clean capability win

Source: openai-blog · published 2026-04-23

TL;DR

• OpenAI’s GPT-5.5 drop — model card, system card, bio bug bounty, Codex superapp — reads as a defensive move against Claude Code more than a frontier leap.
• Benchmark leadership is partial: GPT-5.5 dominates Terminal-Bench, but loses SWE-bench Pro and GPQA Diamond to Claude Opus 4.7.
• The “High” cybersecurity rating shipped with a UK AISI universal jailbreak found in six hours of red-teaming.
• Week-one Codex users report broken desktop clients, infinite thinking loops, and weekly quotas burned in hours.

A four-part launch that hangs together as one story

The GPT-5.5 announcement, system card, bio bug bounty, and the same-week Codex superapp recap are best read as a single product motion: OpenAI is consolidating ChatGPT, Codex, and the Atlas browser into one desktop surface, backed by its acquisition of Astral (the team behind uv and ruff), to blunt Claude Code’s enterprise traction ¹. The frontier-model release is the headline, but the strategic news is the down-stack land grab. That framing also explains the launch’s rough edges — the plumbing shipped before it was ready.

Benchmarks: narrow agentic wins, repo-scale losses

OpenAI’s “smartest model yet” framing doesn’t survive independent comparison. DataCamp’s head-to-head against Claude Opus 4.7 shows a clear split ²:

The pattern: GPT-5.5 wins tight agentic loops and token efficiency; Opus 4.7 still leads on multi-file repo reasoning and PhD-level science. OpenAI optimised hard for the demo surface — terminal automation, OSWorld navigation — and quietly conceded the benchmark that maps most directly to “does this replace a senior engineer.”

The safety story has a visible hole

OpenAI classified GPT-5.5’s cyber capability as “High” under its Preparedness Framework and launched a bio bug bounty alongside the model card. Both are landing less confidently than intended. Transformer News reports that the UK AI Safety Institute found a universal jailbreak bypassing safety filters across all malicious cyber queries in six hours of expert red-teaming, and argues developers should face a legal duty to delay release when AISI flags this class of bypass ³.

“If a government body like AISI identifies a critical vulnerability, developers should have a legal obligation to delay release.”

SecureBio’s pre-release assessment is more measured but converges on the same conclusion: the model exceeds human experts on static bio benchmarks, and refusals can be weakened through prompt construction — which is precisely why crowdsourced red-teaming is needed ⁴. The bio bounty starts to look less like caution and more like outsourced patch-finding for a model shipping with known evasions.

Week-one reality contradicts the efficiency pitch

OpenAI claims GPT-5.5 completes tasks with fewer tokens and fewer retries than 5.4. The r/codex threads tell a different story: the Codex desktop client frequently fails to launch, models display as “Custom,” sessions get stuck in infinite “thinking” loops for days, and weekly quotas exhaust within hours due to High-Effort reasoning overhead ⁵. Reviewers also flag a regression toward eager-to-please behaviour — the model declaring fixes that merely suppress errors.

The Ramsey proof, with asterisks

The marquee math result — a new Ramsey-number bound verified in Lean — is real but oversold. Terence Tao’s framing, surfaced in coverage of similar AI-math claims, is that models excel at the “long tail” of obscure problems while humans still own strategy; he also notes that “open” status in problem databases often reflects obscurity rather than difficulty ⁶. The 2025 Erdős-problems episode, where GPT-5 was wrongly credited with solving problems that already had buried solutions, is the relevant prior.

What’s actually at stake

GPT-5.5 is a credible agentic-coding step wrapped in an over-promised launch. The interesting bet isn’t the benchmark deltas — it’s whether bundling Codex, Atlas, and Astral into one surface is enough to keep Anthropic from owning the developer toolchain.

Further reading

• GPT-5.5 System Card — openai-blog
• GPT-5.5 Bio Bug Bounty — openai-blog
• [AINews] GPT 5.5 and OpenAI Codex Superapp — latent-space

---

OpenAI retires the Custom GPT era for credentialed cloud workers

Source: openai-blog · published 2026-04-22

TL;DR

• Workspace agents replace Custom GPTs with Codex-powered, cloud-resident workers that hold credentials to Slack, CRMs and finance systems.
• Independent evals undercut the autonomy pitch: Codex trails Claude on SWE-bench by 20+ points, and top agents finish only 24% of messy office tasks.
• Credit-based pricing kicks in May 6, 2026; cloud-only execution rules out data-residency-bound shops.
• Prompt-injection defenses are still “architectural flaw” territory — the human-approval gates are the tell.

A category shift, not a feature drop

OpenAI’s “workspace agents” launch is the quiet retirement of the 2023-era ChatGPT surface. Custom GPTs go into maintenance with a sunset, the Assistants API is being deprecated in favor of Responses, and the new primitive is a persistent, cloud-resident agent that holds files, memory and write credentials to your business stack. The Decoder called it turning “ChatGPT from a chatbot into a team automation platform” ⁷, which is closer to the truth than the blog post’s incremental framing. ChatGPT Business, Enterprise, Edu and Teachers tenants get it free until May 6, 2026, after which credit-based pricing takes over.

The demo workflows — qualifying inbound leads against a rubric, routing Slack feedback into tickets, running portions of month-end close, triaging IT requests — are deliberately credentialed. These agents don’t just summarize; they draft external email, update CRM records and touch financial spreadsheets. That is the actual product bet.

The reliability gap nobody is showing on stage

Two independent data points should temper the autonomy claims. First, the substrate: comparison coverage gives Claude Code a >20-point lead over Codex on SWE-bench ⁸, and Codex is what Workspace Agents run on. Second, the environment: Carnegie Mellon’s TheAgentCompany simulation found top models — OpenAI’s included — completing only 24% of ambiguous real-world office tasks, with failure modes like “hallucinated waiting” and renaming a colleague in chat rather than asking a clarifying question ⁹.

Top-performing models achieved a success rate of only 24% on ambiguous real-world tasks.

A 24% success rate on the exact category of work OpenAI is selling — multi-step, multi-tool, ambiguous — is not a footnote. It’s the gap between “automates your month-end close” and “drafts something a human reviews line by line.”

Prompt injection is the architecture, not a bug

OpenAI ships “built-in safeguards” against prompt injection plus optional human-approval gates for high-stakes actions. Security researchers argue the safeguards framing is the wrong abstraction: relying on prompts to enforce boundaries is an “architectural flaw” because LLMs are optimized for helpfulness, not deterministic access control ¹⁰. The threat model is straightforward once you draw it:

flowchart LR
    A[Trusted: Slack, CRM, finance data] --> B{Workspace agent<br/>Codex + memory}
    C[Untrusted: inbound emails,<br/>web pages, PDFs] --> B
    B --> D[Write actions:<br/>email, CRM, spreadsheets]
    D -. indirect injection<br/>exfiltration .-> E((External world))

Any agent that ingests untrusted text and holds write credentials to trusted systems is a confused-deputy waiting to happen. The human-approval toggle is essentially an admission that fully autonomous execution on sensitive tools isn’t safe yet.

What it’ll actually cost — and where it won’t run

Practitioner coverage flags two deployment frictions. The credit model — variable in reasoning depth, tool calls and cloud execution time — invites sticker shock for teams that wire agents into every inbound trigger without usage caps ¹¹. And cloud-only execution means no local file access, which Vellum calls a likely dealbreaker for industries with data-residency constraints, pushing them toward desktop-resident alternatives ¹².

The takeaway

OpenAI is forcing the enterprise off Custom GPTs and onto credentialed agents because that’s where the revenue and lock-in live. The independent evidence says the substrate is behind Claude on coding, the task completion rate in realistic offices is roughly one in four, and the security model leans on a primitive — prompts — that researchers don’t trust to gate write access. Buy the preview; budget the audit.

Further reading

• Workspace agents — openai-blog

---

Google splits the TPU in two, and the per-socket math gets uncomfortable

Source: google-ai-blog · published 2026-04-22

TL;DR

• Google’s 8th-gen TPU ships as two chips: 8t for training, 8i for inference — the first time Google has bifurcated the line.
• Per-socket, the 8t trails NVIDIA Vera Rubin and AMD MI455X by roughly 3:1 in FP4 PFLOPs; Google is competing on cluster economics, not raw silicon.
• The 8i triples on-chip SRAM to 384 MB to keep KV caches on die — a real engineering bet on agent inference latency.
• Broadcom’s TPU exclusivity is over; MediaTek co-designed the 8i, potentially cutting per-chip cost up to 30%.

The split is the story

At Cloud Next ‘26 Google retired the one-TPU-fits-all posture and shipped two chips: the TPU 8t for training, the TPU 8i for inference. The “agentic era” framing is marketing — the architectural admission underneath it is not. Dense pre-training and multi-step agent loops have diverged enough in their memory and latency profiles that a single topology no longer serves both, and Google is the last of the big three accelerator vendors to act on that ¹³.

The 8i is where the engineering is most legible. It triples on-chip SRAM to 384 MB and doubles inter-chip interconnect to 19.2 Tb/s, explicitly so KV caches stay on silicon during long reasoning traces ¹⁴. That is the right knob to turn if you believe the next workload bottleneck is agents replaying context through dozens of tool calls, not single-shot chat completions.

The per-socket math is unflattering

The 8t tells a different story. Tom’s Hardware pegs it at roughly 12.6 FP4 PFLOPs per socket — against ~35 for NVIDIA’s Vera Rubin and ~40 for AMD’s MI455X ¹³. Google also chose HBM3e over HBM4, eating an ~11.5% memory-bandwidth haircut versus theoretical targets, reportedly to protect yields and cloud margins ¹³.

Google’s counter is system-level: claimed 2.7× training perf/$ over Ironwood, 80% better inference perf/$, and 97% “goodput” at scale. Hyperframe Research flags those numbers as “the hardest to independently verify” until production workloads land ¹⁵. Anthropic’s 3.5 GW commitment is the strongest adoption signal, but neither Anthropic nor Meta is going TPU-exclusive.

“These assertions are currently the hardest to independently verify until production workloads are deployed.” — Hyperframe Research ¹⁵

Supply chain is the under-covered story

Broadcom’s decade-long TPU monopoly is over. MediaTek co-designed the 8i, and Marvell is reportedly negotiating a third variant — a shift analysts estimate could shave up to 30% off per-chip cost ¹⁶. That matters because Alphabet’s 2026 capex guidance is $175–185 billion, a number JPMorgan and Citi have already flagged as a margin risk even with the “NVIDIA tax” avoided ¹⁷. The split chip line and the multi-vendor supply chain are the same strategy: drive enough unit-cost leverage that the cluster-economics pitch survives a 3:1 per-socket deficit.

What developers actually noticed

Practitioner reaction was lukewarm on the “agentic” branding and warm on the SRAM engineering ¹⁸. The persistent complaint is software: JAX still owns frontier-lab mindshare, but Torch-XLA porting remains painful enough that CUDA’s moat holds for smaller teams ¹⁸. Several developers argued Google’s quieter move — making every Cloud service MCP-enabled by default — will matter more to agent builders than the silicon ¹⁸.

What’s actually at stake

Three questions the keynote didn’t answer: whether 97% goodput survives non-Google benchmarks, whether perf/$ holds outside Google-run clusters, and whether Torch-TPU has closed the developer gap enough to win customers who aren’t already Anthropic-sized. Until then, the 8t/8i split is a credible architectural bet underwritten by a supply-chain restructuring — not yet a competitive verdict.

Further reading

• Google unveils two new TPUs designed for the “agentic era” — ars-technica-ai

Round-ups

OpenAI Academy Codex 7-part curriculum drop (intro, automations, plugins/skills, getting started, working with, settings, top use cases)

Source: openai-blog

OpenAI Academy published a seven-part Codex curriculum repositioning the tool as a general workplace agent rather than a developer assistant, walking non-coders through automations, plugins and skills, settings, onboarding flow, day-to-day workflows, and a top-ten list of office use cases.

Further reading:

• Top 10 uses for Codex at work — openai-blog
• Automations — openai-blog
• Plugins and skills — openai-blog
• How to get started with Codex — openai-blog
• Working with Codex — openai-blog
• Codex settings — openai-blog

Anthropic tested removing Claude Code from the Pro plan

Source: ars-technica-ai

Anthropic ran an experiment stripping Claude Code access from $20 Pro subscribers, citing untenable compute demand from agentic coding sessions. The company is testing tighter rationing tiers as power users burn through token budgets faster than the plan economics support.

Shopify’s AI Phase Transition: 2026 Usage Explosion, Unlimited Opus-4.6 Token Budget, Tangle, Tangent, SimGym — with Mikhail Parakhin, Shopify CTO

Source: latent-space

Shopify CTO Mikhail Parakhin tells Latent Space the company gave engineers an unlimited Claude Opus 4.6 token budget amid a 2026 internal usage explosion, and details in-house tools Tangle, Tangent, and SimGym built to scale AI across merchant-facing products.

Making ChatGPT better for clinicians

Source: openai-blog

OpenAI is offering ChatGPT for Clinicians free to verified U.S. physicians, nurse practitioners, and pharmacists, with the variant tuned for clinical care, documentation, and research workflows. Verification gates access to the healthcare-specific build.

Anthropic and NEC collaborate to build Japan’s largest AI engineering workforce

Source: anthropic-news

Anthropic and NEC announced a partnership to train what they call Japan’s largest AI engineering workforce, embedding Claude into NEC’s developer tooling and joint upskilling programs aimed at expanding enterprise AI delivery capacity across the Japanese market.

An update on our election safeguards

Source: anthropic-news

Anthropic recaps the misuse defenses it deployed across global election cycles, covering policy enforcement, prompt-level safeguards, and partnerships with election authorities. The post updates which protections Claude will keep as standing infrastructure versus which were election-specific measures now winding down.

US accuses China of “industrial-scale” AI theft. China says it’s “slander.”

Source: ars-technica-ai

U.S. officials accused China of industrial-scale theft of frontier AI model weights and training techniques from firms including OpenAI, Anthropic, and Google, floating major sanctions ahead of a Trump-Xi summit. Beijing dismissed the claims as slander, raising distillation and IP as flashpoints.

Footnotes

1. Hypebeast — Codex/Atlas/ChatGPT superapp consolidation — https://hypebeast.com/2026/3/openai-merges-chatgpt-codex-and-atlas-into-desktop-superapp

   OpenAI’s acquisition of Astral (the team behind tools like uv and ruff), signaling a move ‘down-stack’ to own the developer infrastructure… a direct response to Anthropic’s ‘Claude Code,’ which had been gaining traction in the enterprise market.

   ↩

2. DataCamp — GPT-5.5 vs Claude Opus 4.7 head-to-head — https://www.datacamp.com/blog/gpt-5-5-vs-claude-opus-4-7

   On SWE-bench Pro, which tests real-world GitHub issue resolution, Opus 4.7 scored 64.3% compared to GPT-5.5’s 58.6%… GPT-5.5 achieved an 82.7% on Terminal-Bench 2.0, significantly outperforming Opus 4.7’s 69.4%.

   ↩

3. Transformer News — policy critique — https://www.transformernews.ai/p/openai-shouldnt-be-deciding-if-its-gpt-55

   the UK AI Safety Institute discovered a ‘universal jailbreak’ that bypassed safety filters across all malicious cyber queries in just six hours of expert red-teaming… if a government body like AISI identifies a critical vulnerability, developers should have a legal obligation to delay release.

   ↩

4. SecureBio pre-release assessment (Substack) — https://securebio.substack.com/p/securebios-pre-release-assessment

   the model possesses expert-level biological knowledge, often exceeding the scores of human professionals on static benchmarks… refusals could occasionally be weakened through clever prompt construction, justifying the need for a broader, crowdsourced red-teaming effort.

   ↩

5. r/codex week-one user reports — https://www.reddit.com/r/codex/comments/1suel3u/gpt55_is_so_good/

   the Codex desktop app frequently failed to launch, displayed models as ‘Custom,’ or became stuck in infinite ‘thinking’ loops for days… weekly limits exhausted within hours due to the high overhead of the model’s internal ‘High Effort’ reasoning steps.

   ↩

6. Popular Mechanics — Ramsey proof coverage — https://www.popularmechanics.com/science/math/a43510452/mathematicians-discover-new-ramsey-number-upper-bound/

   Fields Medalist Terence Tao noted that while AI excels at the ‘long tail’ of obscure or straightforward problems, complex breakthroughs still require humans to map out the overall strategy… ‘open’ status in databases often reflects obscurity rather than difficulty.

   ↩

7. The Decoder — https://the-decoder.com/openai-launches-workspace-agents-that-turn-chatgpt-from-a-chatbot-into-a-team-automation-platform/

   Workspace agents… turn ChatGPT from a chatbot into a team automation platform

   ↩

8. Orbilon Tech (Anthropic vs OpenAI 2026) — https://orbilontech.com/openai-vs-anthropic-enterprise-ai-decision-2026/

   On SWE-bench (coding), Claude Code reportedly outperforms OpenAI’s Codex by over 20 percentage points

   ↩

9. Kili Technology — AI benchmarks guide 2026 — https://kili-technology.com/blog/ai-benchmarks-guide-the-top-evaluations-in-2026-and-why-theyre-not-enough

   Carnegie Mellon’s ‘TheAgentCompany’… top-performing models achieved a success rate of only 24% on ambiguous real-world tasks

   ↩

10. Medium / Tao-HPU on agent security boundaries — https://tao-hpu.medium.com/agent-security-boundaries-from-prompt-injection-to-tool-misuse-d25b6dbaad60

    Relying on prompts to enforce security boundaries is an ‘architectural flaw,’ as models are optimized for helpfulness rather than deterministic access control

    ↩

11. AI Consulting Network — https://www.theaiconsultingnetwork.com/blog/openai-workspace-agents-chatgpt-enterprise-cre-investors-2026

    True cost of ownership could climb significantly once the free agent preview ends, especially for firms that ‘wire an agent into every lease event or inbound memorandum’ without strict usage monitoring

    ↩

12. Vellum — Workspace Agents alternatives review — https://www.vellum.ai/blog/best-workspace-agents-chatgpt-alternatives

    OpenAI’s cloud-only execution lacks local file access, which may be a dealbreaker for industries with strict data residency requirements

    ↩

13. Tom’s Hardware — https://www.tomshardware.com/tech-industry/semiconductors/google-splits-its-tpu-into-two-chips-for-the-first-time-with-training-and-inference-variants

    Google’s TPU 8t delivers approximately 12.6 FP4 PFLOPs per socket, still trailing NVIDIA’s Vera Rubin (35 PFLOPs) and AMD’s MI455X (40 PFLOPs) by a ratio of roughly 3:1… Google’s decision to use HBM3e instead of HBM4 for the 8t resulted in an 11.5% reduction in memory bandwidth compared to theoretical targets — a trade-off likely made to improve manufacturing yields and lower costs.

    ↩ ↩² ↩³

14. Nand Research — https://nand-research.com/google-cloud-8th-generation-tpu-family-splits-training-and-inference/

    The TPU 8i triples on-chip SRAM to 384 MB and doubles interconnect bandwidth to 19.2 Tb/s, allowing the chip to host large KV Caches directly on silicon, drastically reducing the latency of agentic workflows.

    ↩

15. Hyperframe Research — https://hyperframeresearch.com/2026/04/22/google-cloud-next-2026-google-cloud-bifurcates-the-ai-future-specialized-tpu-8t-and-8i-architectures-signal-the-end-of-general-purpose-silicon/

    Google claims a 97% ‘goodput’ (actual training efficiency)… these assertions are currently ‘the hardest to independently verify’ until production workloads are deployed.

    ↩ ↩²

16. TheElec — https://www.thelec.net/news/articleView.html?idxno=10028

    Broadcom remains the primary partner for the high-performance TPU 8t, while MediaTek has been brought in to co-design the TPU 8i… ending Broadcom’s decade-long exclusivity in the TPU program and potentially reducing per-chip costs by up to 30%.

    ↩

17. ZeroHedge — https://www.zerohedge.com/ai/google-unveils-two-chips-agentic-era

    Alphabet’s 2026 capital expenditure guidance of $175–$185 billion… while the TPU’s vertical integration avoids the ‘NVIDIA tax,’ the sheer scale of the investment poses risks to long-term profit margins.

    ↩

18. Dev.to (developer recap of Cloud Next ‘26) — https://dev.to/aniruddhaadak/i-watched-google-cloud-next-26-so-you-dont-have-to-here-is-what-actually-matters-for-developers-54h6

    Google’s move to make every Cloud service ‘MCP-enabled’ (Model Context Protocol) by default is a more ‘developer-friendly’ move than the hardware specs themselves… while JAX dominates the training of foundation models, PyTorch remains the ‘no-brainer’ for smaller teams.

    ↩ ↩² ↩³