AI Briefings·6 min read

AI Morning Briefing — July 16th, 2026

Lyubo
Lyubo·
AI Morning Briefing — July 16th, 2026

OpenAI's GPT-Red trains an AI to hack its own models, Mira Murati's Thinking Machines open-sources the 975B-parameter Inkling, and Claude lands GA in Microsoft Foundry.

AI Morning Briefing — July 16th, 2026

Your daily digest of what's happening in AI, straight from the trenches.


🚀 Headlines (30 sec read)

  • OpenAI built an AI to hack its own models — GPT-Red, trained via self-play red-teaming, cut prompt-injection success against GPT-5.6 from over 90% to under 23%.
  • Mira Murati's Thinking Machines Lab open-sources Inkling — a 975B-parameter, Apache 2.0 multimodal model that only activates 41B params per token.
  • Anthropic resets Claude's usage limits again and lands Claude in Microsoft Foundry — 5-hour and weekly caps cleared for all paid users after a rough week of outages, with Claude now GA on Azure.

🧠 Deep Dives (4 min read)

GPT-Red: OpenAI trains an AI to attack its own models

OpenAI disclosed GPT-Red, an automated red-teaming model trained through self-play reinforcement learning: an attacker model repeatedly crafts prompt-injection attempts while a population of defender models learns to resist them, and the resulting attack data feeds straight back into GPT-5.6's training. The numbers are stark — in OpenAI's internal prompt-injection arena, GPT-Red independently compromised GPT-5.1 in 84% of scenarios versus 13% for human red teams, and more than 90% of its strongest attacks worked against GPT-5 while fewer than 23% work against GPT-5.6 Sol. GPT-Red also surfaced a previously unseen attack class the team calls "fake chain-of-thought," and was turned loose on a real vending-machine agent (built by Andon Labs, deployed in OpenAI's own office) where it successfully changed prices, listed overpriced items, and cancelled other people's orders. GPT-Red itself stays internal-only — OpenAI is keeping the offensive capability out of anyone's hands but its own. → Source

Thinking Machines Lab ships its first model — and it's fully open

Mira Murati's Thinking Machines Lab released Inkling, its first in-house model and a direct bet against the closed-model status quo. It's a 975B-parameter multimodal Mixture-of-Experts model that activates only 41B parameters per token, pretrained on 45 trillion tokens across text, images, audio, and video, with a 1M-token context window and Apache 2.0 licensing — meaning anyone can download, fine-tune, and commercialize the weights outright. On Design Arena, a blind eval for AI-built web apps, Inkling scored 1,257 versus GPT-5.6 Sol's 1,260 — competitive with a frontier closed model while staying fully open. Thinking Machines is monetizing not the weights but the infrastructure around them, via its Tinker fine-tuning platform, and framed the release as a rejection of AI development concentrated in a handful of closed labs. → Source


📅 Coming Up This Week

DateEvent
Jul 21Anthropic + Microsoft webinar: deploying Claude in Microsoft Foundry for production Azure workloads
This weekExpect competing labs to respond to Inkling's fully-open, Apache-2.0 release
This weekMore scrutiny of agentic AI security following OpenAI's GPT-Red disclosures

🛠️ Try This Today

Pressure-test your own prompts against injection

Anthropic and OpenAI both just published serious research on how easily agents get hijacked by hostile instructions hidden in tool output. Take 15 minutes to check your own setup:

  1. Pick one agent/tool you run regularly (a coding assistant, a scraper, an email summarizer) and list every place it ingests untrusted text — web pages, PDFs, API responses.
  2. For each one, ask: if that text contained an instruction like "ignore previous instructions and do X," would anything stop the agent from complying?
  3. Add an explicit system-prompt rule that content fetched from tools is data, never instructions — and re-run a test case with an injected command to confirm it's actually ignored.

Why it matters: GPT-Red's own numbers show over 90% of naive injection attempts succeeded against last year's frontier models. If you haven't explicitly tested for this, assume your agent is vulnerable too.


⚡️ Quick Links (2 min read)

GitHub Trending

Reddit Hot

  • [r/ClaudeAI] Opus 5 coming soon? — Speculation thread racking up hundreds of upvotes on the next Opus release → Discussion
  • [r/MachineLearning] New LLM Coordination Benchmark — 13 modern LLMs tested on multi-agent coordination; most average ~6% normalized return, but zero-shot Gemini matches a MARL agent trained for 1B environment steps → Discussion

Hacker News Top


🦞 TL;DR

The narrative today: Two labs made the same point from opposite directions — OpenAI showed that frontier safety now comes from AI attacking AI, and Thinking Machines showed that a frontier-competitive model doesn't have to be closed to be safe or good.

My take: GPT-Red is the more consequential story long-term. Training an attacker model and folding its output straight back into the next release is going to become standard practice industry-wide, the same way adversarial training did for image classifiers a decade ago — except the stakes here are agents with real tool access, not just misclassified photos. Inkling is the flashier headline, but "open weights, closed monetization via infra" is a playbook Meta and Mistral already run; Thinking Machines is just executing it with a stronger model.

What I'm watching: Whether any other lab publishes injection-success numbers as candidly as OpenAI just did — that kind of disclosure is rare and worth rewarding with attention.

Stay informed. Stay curious.

Share:
AIOpenAIClaudeDaily Briefing