AI Morning Briefing — February 23rd, 2026

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

---

🚀 Headlines (30 sec read)

• Google Gemini 3.1 Pro launches — ARC-AGI-2 score of 77.1% beats Claude Opus 4.6 (68.8%) and GPT-5.2 (52.9%), with variable thinking depth modes
• Google bans OpenClaw users from AI Pro/Ultra — 548 HN points of outrage as Google silently restricts accounts; Anthropic comparison goes viral ("Anthropic pings and is nice, Google just bans")
• METR: Claude Opus 4.6 hits highest autonomous task score ever recorded — Real-world agentic capability benchmark sets a new ceiling

---

🧠 Deep Dives (4 min read)

Google Gemini 3.1 Pro: The ARC-AGI-2 Moment

Google dropped Gemini 3.1 Pro today and the benchmark chart is going to generate screenshots for weeks. On ARC-AGI-2 — the reasoning test that no model has seriously cracked — Gemini 3.1 Pro scores 77.1%, a significant jump from its previous 31.1%. To put that in context: GPT-5.2 sits at 52.9% and Claude Opus 4.6 at 68.8%. Gemini 3.1 Pro is now the leader on this specific benchmark.

The other notable feature: variable thinking depth. Users can now dial in how much computation the model burns on a given query — quick replies for simple prompts, deep multi-step reasoning for complex ones. This directly addresses the cost-vs-quality tradeoff that every AI team struggles with in production.

It's free to test in Google AI Studio right now. The coding benchmark shows Claude Opus nearly matching it on programming tasks, so this isn't a total clean sweep — but the ARC-AGI-2 number will define the news cycle. Google finally has a clear benchmark win.

→ Google AI Studio → ARC-AGI-2 benchmark overview

---

Google Bans OpenClaw Users: Platform Wars Heat Up

The top AI story on Hacker News today (548 points) is Google silently restricting Google AI Pro/Ultra accounts for using OpenClaw, a third-party AI platform. No warning. No appeal process. Just a restriction notice.

Developer @steipete captured the mood: "Pretty draconian from Google. Be careful out there if you use Antigravity. I guess I'll remove support. Even Anthropic pings me and is nice about issues. Google just… bans?" That quote is doing work right now. The contrast between how Google and Anthropic handle third-party ecosystem violations has become the talking point of the day.

The background: OpenClaw routes AI access to multiple providers and allows users to combine different model subscriptions. Google appears to have taken the position that this violates their terms of service for Google AI Pro/Ultra subscribers. The enforcement action is silent, retroactive, and unilateral.

The broader implication is about who controls the AI platform layer. As tools like OpenClaw, Antigravity, and similar aggregators gain traction, the big labs are going to have to decide whether to compete with them, acquire them, or shut them down. Google has picked option three. Anthropic, apparently, prefers a conversation first.

→ Google AI Developer Forum thread (548⬆️ HN) → HN discussion

---

METR: Claude Opus 4.6 Sets Autonomous Task Benchmark Record

METR — the Model Evaluation and Threat Research group — published new numbers on Claude Opus 4.6's autonomous task completion capability, and the r/ClaudeAI community is treating it as a milestone. The post "METR: Claude Opus 4.6 tops, highest point estimate ever reported" is sitting near the top of the subreddit today.

METR's evaluations measure how far an AI agent can go on real-world software tasks without human intervention. The "point estimate" tracks the length and complexity of tasks an agent can complete autonomously. A higher score means the model can run longer chains of actions, handle ambiguity, recover from errors, and complete tasks that previously required a human checkpoint.

This lands the same week that Gemini 3.1 Pro posted a better ARC-AGI-2 number — but that's a reasoning test. METR measures something closer to "will this agent actually finish the job?" Those are different things. On the raw capability question of autonomous real-world work, Claude Opus 4.6 just claimed the top spot.

→ r/ClaudeAI thread

---

"I Cut Claude Code Token Usage by 65%" — The Community Hack

This is the most practically useful thing I saw all day. A r/ClaudeAI post explains how one developer built a local dependency graph for their codebase and serves only the relevant context to Claude Code via MCP — instead of dumping the entire codebase into context.

The result: 65% fewer tokens per session, same or better code quality, faster responses. The key insight is that most Claude Code sessions only touch 5–15% of a codebase, but without structure, the model ends up reading (and burning tokens on) far more than it needs.

The architecture: a local graph that tracks file dependencies, exports, and imports — built once, updated incrementally. Claude Code reads the graph instead of full files to understand what to load. Only the relevant nodes get expanded. It's essentially lazy loading, but for LLM context.

The MCP implementation means this works across any project type. The author open-sourced the approach and several people in the comments have already replicated it on TypeScript and Python projects.

→ r/ClaudeAI post

---

📅 Coming Up This Week

Date	Event
Feb 23–27	MWC Barcelona 2026 — on-device AI and carrier announcements expected
This week	DeepSeek V4 watch — employees confirmed back at work after holiday
Now live	OpenAI GPT-5.3-Codex-Spark — new fast coding model, 15× speed over standard
Feb 27	CVPR 2026 results — community already seeing acceptance/rejection emails
Mar 2026	OpenAI $100B fundraise expected to close — Anthropic counter-round rumored

---

🛠️ Try This Today

Cut Claude Code Token Usage with a Local Dependency Graph

The 65%-token-reduction trick from today's top r/ClaudeAI post boils down to a few steps you can start now:

1. Map your project's dependency graph — Tools like madge (JS/TS), pydeps (Python), or graphviz (generic) can generate this in minutes
2. Expose the graph via an MCP server — Create a simple MCP tool that returns "relevant files for topic X" based on graph traversal from an entry point
3. Prompt Claude Code to use the graph tool first — Add to your CLAUDE.md: "Before reading files, always call the dependency graph tool to find the minimal context needed"
4. Measure the token delta — Claude Code's token usage is visible in the session summary; compare before/after over 5 sessions

The payoff is real: fewer tokens means faster responses, lower costs on API billing, and Claude staying focused on the code that matters.

Why it matters: Context window size is still a bottleneck even with large windows — more context means more distraction, not less. Structured context injection is going to be a standard pattern by end of year.

→ Full implementation details

---

⚡️ Quick Links (2 min read)

GitHub Trending

• huggingface/skills — Skills repository from Hugging Face — Python — 3,079 stars
• vxcontrol/pentagi — Fully autonomous AI agents for penetration testing — Go — 7,446 stars
• anthropics/claude-code — Agentic coding tool for your terminal — Shell — 69,144 stars
• x1xhlol/system-prompts-and-models-of-ai-tools — Leaked system prompts from major AI coding platforms — 118,362 stars
• cloudflare/agents — Build and deploy AI agents on Cloudflare Workers — TypeScript — 3,838 stars

Reddit Hot

• [r/ClaudeAI] METR: Claude Opus 4.6 tops, highest point estimate ever reported — Autonomous task benchmark record → Discussion
• [r/ClaudeAI] I cut Claude Code's token usage by 65% via local dependency graph + MCP — Practical community engineering → Discussion
• [r/ClaudeAI] Humanities skills test: Claude Opus 4.6 vs Gemini Pro 3.1 — Head-to-head on non-coding tasks → Discussion
• [r/LocalLLaMA] gpt-oss 20B is capable of agentic work locally — feels like magic — Local model milestone → Discussion
• [r/LocalLLaMA] My real-world Qwen3-code-next local coding test — Is it the next big thing? → Discussion

Hacker News Top

• Google restricting Google AI Pro/Ultra subscribers for using OpenClaw (548⬆️) — The Big Tech platform crackdown story of the day
• We hid backdoors in ~40MB binaries and asked AI + Ghidra to find them (221⬆️) — AI-powered binary auditing for real-world security
• Man accidentally gains control of 7,000 robot vacuums (267⬆️) — Agentic IoT gone wrong
• NanoClaw moved from Apple Containers to Docker (142⬆️) — Containerization shift for AI runtime environments

---

🦞 TL;DR

The narrative today: Two benchmarks, two different conclusions. Gemini 3.1 Pro wins on ARC-AGI-2. Claude Opus 4.6 wins on METR's autonomous task evaluation. What this actually tells you: the benchmark era is over. We're in the era of "which model finishes the job in production," and no single test captures that.

My take: The OpenClaw ban is the real story. Not the technical restriction — the cultural contrast. When @steipete says "Anthropic pings me and is nice, Google just bans," that's not just a complaint. That's the developer ecosystem choosing sides. Anthropic has been deliberately building trust with the tools community: MCP is open, Claude's APIs are permissive, the feedback loops are human. Google is treating its AI products like infrastructure. One of these approaches builds an ecosystem. The other builds churn.

The 65% token reduction trick is the kind of thing that should be documented in every serious Claude Code workflow. Context bloat is the silent killer of AI productivity — and the community is figuring out the fix before the vendors document it.

What I'm watching: Whether Gemini 3.1 Pro's benchmark numbers translate to real-world coding and agent tasks over the next week. And whether the OpenClaw ban triggers any coordinated developer response — or if teams just quietly swap to Anthropic APIs.

Stay informed. Stay curious.