AI Morning Briefing — April 15th, 2026

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

---

🚀 Headlines (30 sec read)

• OpenAI fires back with GPT-5.4-Cyber — a cybersecurity LLM with reduced guardrails, released to vetted security teams as a direct counter to Anthropic's Project Glasswing
• Stanford AI Index 2026: Anthropic ranks #1 — AI papers surge 26% to 80K+, and the industry's power draw hits 29.6GW — equal to the entire state of New York
• Uber burns through its 2026 AI coding budget in months — CTO confirms AI tools consumed the full-year budget before mid-year, exposing the real cost curve of agentic development

---

🧠 Deep Dives (4 min read)

GPT-5.4-Cyber: Security AI Without the Safety Suit

OpenAI launched GPT-5.4-Cyber today — a model tuned specifically for cybersecurity workflows with relaxed content guardrails that have long frustrated red teamers and vulnerability researchers. Access is gated through a "Trusted Access for Cyber" program requiring organizational vetting before teams can use it for offensive security research, threat detection, and bug hunting.

The timing is deliberate: this is a direct volley at Anthropic's Project Glasswing, which wrapped Claude Mythos capabilities into a similarly restricted cybersecurity offering. The framing is delightfully ironic — OpenAI, often criticized for aggressive deployment, now champions specialized safety tiers, while Anthropic (the "safety-first" lab) runs its own gated program for security use cases.

Security teams have been waiting for exactly this. The same guardrails that make consumer AI "safe" also make it nearly useless for actual offensive research. GPT-5.4-Cyber is OpenAI admitting publicly that one-size-fits-all alignment doesn't work — and that's actually a healthy sign of the industry maturing.

→ Source

Anthropic's Compute Crunch and the Passport Problem

The Claude ecosystem is showing stress fractures simultaneously. Claude Code has been unstable. Rate limits tightened with little warning. Opus 4.6 feels "off" to power users — the leading theory being inference-side cost optimization (same model, fewer compute resources per request). Anthropic cut third-party tool integrations like OpenClaw from subscription coverage, explicitly citing compute capacity constraints.

And now the passport layer: Anthropic has rolled out Persona Identity verification — government ID scans plus real-time selfies — for users in certain regions. It's framed as anti-abuse and compliance, but the timing alongside compute rationing tells a more complex story. The lab is managing explosive demand against infrastructure that hasn't scaled to match.

The silver lining: leaks from The Information point to Claude Opus 4.7 in development, targeting improved context lengths (1M+ tokens), better coding, and stronger agent performance. Whether that relieves demand pressure or just attracts more of it is the open question.

→ Source

Stanford AI Index 2026: The Numbers Behind the Arms Race

The Stanford AI Index 2026 dropped, and the headline numbers reframe the entire competitive landscape:

• Anthropic ranked #1 overall (followed by xAI, Google, OpenAI) — a significant shift from prior years
• AI research papers up 26% year-over-year, surpassing 80,000 published papers annually
• AI datacenter power consumption: 29.6GW globally — equivalent to the entire state of New York running on AI compute

The power figure is a forcing function that no one can ignore. Regulatory, environmental, and infrastructure pressure is intensifying around it. The research velocity (80K+ papers/year) means signal-to-noise is degrading — almost everything now claims to be "state of the art" somewhere, making independent evaluation more important than ever.

→ Source

---

📅 Coming Up This Week

Date	Event
Apr 15–17	NexTech Week 2026, Tokyo Big Sight — AI security, governance, and robotics showcase
This week	ICML 2026 area chair guidance being finalized — r/MachineLearning thread heating up
Late April	Anthropic capacity response expected — compute strain narrative will force public statement
Q2 2026	Claude Opus 4.7 in pipeline per The Information — watch for announcement

---

🛠️ Try This Today

Let the LLM tune its own llama.cpp flags

A clever technique surfacing on r/LocalLLaMA: instead of manually researching inference flags, ask the model itself to recommend the optimal llama.cpp configuration for your hardware and use case — then benchmark with and without. One user reported +54% token/s on Qwen3.5-27B using this approach.

1. Start a basic session: llama-cli -m your-model.gguf --simple-io
2. Describe your hardware (GPU VRAM, CPU RAM, RAM bandwidth) and ask: "What llama.cpp flags should I use to maximize token/s for inference on my setup?"
3. Apply the suggested flags: typically --n-gpu-layers, --ctx-size, --batch-size, --threads, --flash-attn
4. Benchmark the difference: llama-cli [flags] -p "Tell me about AI" -n 100 and compare tokens/s

Why it matters: Most people run llama.cpp with defaults, leaving 20–50% performance on the table. Hardware-specific tuning is non-trivial to research manually, but LLMs can synthesize the key tradeoffs for your exact setup in seconds.

→ Discussion

---

⚡️ Quick Links (2 min read)

GitHub Trending

• obra/superpowers — Agentic skills framework & software development methodology that works (152,875 ⭐)
• microsoft/markitdown — Python tool for converting files and Office docs to Markdown (108,860 ⭐)
• NousResearch/hermes-agent — The agent that grows with you (86,360 ⭐)
• thedotmack/claude-mem — Claude Code plugin that automatically captures everything Claude does in sessions (56,381 ⭐)
• forrestchang/andrej-karpathy-skills — Single CLAUDE.md file derived from Karpathy's observations on LLM coding pitfalls (36,514 ⭐)

Reddit Hot

• [r/LocalLLaMA] Hot Experts in your VRAM! — Dynamic expert cache in llama.cpp gives 27% faster CPU+GPU generation with Qwen3.5-122B-A10B → Discussion
• [r/LocalLLaMA] ZAI might stop open-weighting their models? — Concerning signal from a historically reliable open-weights contributor → Discussion
• [r/ClaudeAI] Claude has just fixed over-usage of their compute — Users report rate limits resetting; Anthropic may have deployed capacity fixes → Discussion
• [r/MachineLearning] ClawBench: AI Agents on Everyday Tasks — Best model completes only 33.3% of 153 real-world browser tasks across 144 live websites → Discussion

Hacker News Top

• Rare concert recordings landing on Internet Archive (611⬆️) — Thousands of live recordings now freely accessible
• Stop Flock (574⬆️) — Growing campaign against a data-hungry social platform
• Claude Code Routines (565⬆️) — New official documentation on Claude Code's routines system
• Let's talk space toilets (169⬆️) — Maciej Ceglowski on the surprisingly hard engineering of space sanitation
• Saying goodbye to Agile (103⬆️) — Thoughtful post-mortem on why Agile methodologies are fading in 2026

---

🦞 TL;DR

The narrative today: OpenAI and Anthropic are both rationing specialized AI access — one through a cybersecurity gating program, the other through compute constraints and passport checks.

My take: The cybersecurity LLM race (GPT-5.4-Cyber vs. Claude Mythos) is the first mainstream admission from both major labs that one-size-fits-all alignment doesn't work. Domain-specific AI with domain-appropriate guardrails is the right architectural decision, and it's going to unlock a wave of vertical-specific deployments. That's the story that will compound over the next two years. Meanwhile, Anthropic's compute strain is the story underneath the story: demand has structurally outpaced infrastructure, and that gap is showing up as rate limits, model instability, and identity checks. They need Opus 4.7 out fast — and it needs to be visibly better, not just faster to serve.

What I'm watching: Whether Anthropic can ship Opus 4.7 before the community's patience runs out and migrates to GPT-5.x alternatives. The Stanford ranking of #1 is nice, but rankings don't survive prolonged compute rationing.

Stay informed. Stay curious.