AI Morning Briefing — February 22nd, 2026

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

---

🚀 Headlines (30 sec read)

• Claude Code celebrates its 1st birthday — Anthropic's 13,000-builder hackathon crowns "Built with Opus 4.6" winners in San Francisco
• Karpathy coins "Claws" — A new abstraction layer on top of LLM agents goes viral with 271 HN points today
• 40,000+ AI agents exposed on the open internet — Security researchers document a massive unsecured agent deployment crisis

---

🧠 Deep Dives (4 min read)

Claude Code Turns One — And the Builders Are Serious

Exactly one year since Claude Code shipped, Anthropic wrapped up its largest community event to date: an online hackathon that drew 13,000+ registered builders. The top six finalists flew to San Francisco to pitch their projects to the Claude Code team at SHACK15, with submissions built on Opus 4.6 spanning full agentic coding workflows, automated PR review pipelines, and multi-modal applications.

The event is a data point that Claude Code has escaped "internal Anthropic tool" territory and become a genuine platform with a real developer community. Twitter's @AlexReibman was on the ground: "Claude Code just turned 1! To celebrate, Anthropic hosted an online hackathon for 13,000+ builders. The 6 top finalists came to San Francisco to show what they made."

The Hacker News community is weighing in too — "How I use Claude Code: Separation of planning and execution" from boristane.com sits at 417 points today, documenting one developer's structured workflow for consistent results. The separation principle: planning pass first (no code), then execution pass (no planning). Simple, repeatable, powerful.

→ Claude Code Hackathon Winners → How I use Claude Code

---

Karpathy Coins "Claws" as the Next Abstraction Above Agents

Andrej Karpathy's tweet — "Claws are now a new layer on top of LLM agents" — is today's most-discussed AI concept on Hacker News (271 points). The core idea: as LLM agents proliferate, we need a structured meta-layer that defines how agents grip onto systems, data, and other agents. "Claws" is Karpathy's framing for the capability substrate — the mechanism by which agents reach out and act on the world.

This isn't just terminology. It's a sign that the field is converging on new abstractions. Tool use was the first wave. Agent orchestration was the second. "Claws" — or whatever the community settles on — is about the interface layer that makes agents composable and auditable in production. r/LocalLLaMA's reaction? "They have Karpathy — we are doomed ;)" — a nod to how much weight his framing tends to carry.

The timing is pointed: this lands the same week that 40,000 AI agents are running exposed on the internet, and a Cline release shipped with a malicious package injection. When you give agents claws, you need to know what they're gripping.

→ Karpathy tweet → HN discussion → r/LocalLLaMA reaction

---

40,000 AI Agents Are Running Exposed on the Open Internet

Security researchers documented a number that should make everyone pause: 40,000+ AI agents publicly reachable on the internet, running with full system access and zero authentication. These aren't honeypots or test sandboxes — these are production deployments spawned from vibe-coded setups where someone got the agent working and shipped without a security pass.

This week also brought a supply chain warning: a recent Cline release had a malicious package injected. The r/LocalLLaMA thread called out what this pattern means: agentic tools are shipping updates at high velocity, and security review is not keeping pace. When a code agent installs dependencies automatically, a bad actor with access to one package can reach into your environment with full execution rights.

The picture emerging: we've normalized giving LLMs "claws" — file system access, shell execution, network calls — without normalizing the security review that should accompany it.

→ 40,000+ AI Agents exposed → PSA: Cline package injection

---

The "Am I Being Replaced?" Reckoning Hits r/ClaudeAI

Two posts cracked the top of r/ClaudeAI today and they're both about the same thing: the speed at which AI is outpacing human developer output.

A software dev director — 24 years in, 12 years in leadership, team of 8 — posted about struggling with team morale as Claude handles work that used to require full sprints. 406 comments. Another post: "I'm seeing the human-in-the-loop vanish faster than I expected" — a manager describing Claude Code replacing significant chunks of what used to be all-hands engineering review.

Multiple reports this week put Claude Opus 4.6 handling 4-hour senior dev tasks in under 10 minutes. The productivity math is changing faster than teams can absorb, and the r/ClaudeAI community is where that dissonance is landing in real time.

→ Dev director morale thread

---

📅 Coming Up This Week

Date	Event
Feb 22–28	Claude Code Security preview expected to expand beyond initial Enterprise users
This week	MWC Barcelona 2026 — AI-on-device and carrier AI announcements expected
Feb 26	DeepSeek next model — rumors circulating, watching for any official drop
Mar 2026	OpenAI $100B fundraise expected to close — valuation dynamics vs. Anthropic rumored round
This week	Google Gemma new version — a Google dev hinted "releasing soon" on r/LocalLLaMA

---

🛠️ Try This Today

Structure Your Claude Code Workflow: Plan First, Execute Second

The top HN post today (417 points) outlines a clean approach to getting consistent Claude Code output by separating concerns:

1. Planning pass — Ask Claude to read the relevant files, understand the problem, and produce a detailed plan. Explicitly tell it: "Do not write any code yet."
2. Review the plan — Read what Claude produced. Edit it. Add constraints. Remove bad ideas. This is your chance to course-correct before any code is written.
3. Execution pass — Hand Claude back the approved plan: "Now implement exactly this plan. Follow it step by step."
4. Review output — Check against the plan. Ask Claude to diff its output against what it proposed.

Why it matters: Claude (and most LLMs) conflate planning and execution when asked to "just do it" — leading to over-engineered solutions or missed edge cases. Separating the phases gives you a review checkpoint and produces cleaner, more predictable output.

→ Full post with examples

---

⚡️ Quick Links (2 min read)

GitHub Trending

• anthropics/claude-code — Terminal-based agentic coding tool — Shell — 68,569 stars (trending on Claude Code's birthday week)
• vxcontrol/pentagi — Fully autonomous AI Agents for penetration testing — Go — 6,011 stars
• obra/superpowers — Agentic skills framework & software dev methodology — Shell — 57,246 stars
• huggingface/skills — Skills repository from Hugging Face — Python — 1,771 stars
• ggml-org/ggml — Tensor library for machine learning (ggml team, now at HF) — C++ — 14,091 stars

Reddit Hot

• [r/ClaudeAI] Claude Code Hackathon Winners ("Built with Opus 4.6") — Top 6 from 13,000+ builders, results in → Discussion
• [r/ClaudeAI] Software dev director struggling with team morale — 406 comments, the human side of the AI productivity wave → Discussion
• [r/LocalLLaMA] 40,000+ AI Agents Exposed to the Internet with Full System Access — Security researchers sound the alarm → Discussion
• [r/LocalLLaMA] "They have Karpathy, we are doomed ;)" — r/LocalLLaMA reacts to Karpathy's latest move in the AI space → Discussion
• [r/MachineLearning] Practical failure-mode map for production LLM pipelines — 16 patterns, MIT-licensed, for RAG and agent debugging → Discussion

Hacker News Top

• How I use Claude Code: Separation of planning and execution (417⬆️) — Clean two-phase framework for structured Claude Code workflows
• Claws are now a new layer on top of LLM agents (271⬆️) — Karpathy's new meta-abstraction for the agentic era
• Llama 3.1 70B on a single RTX 3090 via NVMe-to-GPU bypassing the CPU (215⬆️) — Direct NVMe-to-VRAM inference, no system RAM bottleneck
• zclaw: personal AI assistant in under 888 KB, running on an ESP32 (152⬆️) — Minimalist AI at the edge, no cloud required

---

🦞 TL;DR

The narrative today: Claude Code turns one and the receipts are real — 13,000 builders, 6 finalists pitching in SF, and the top HN post about how to actually use it. Meanwhile Karpathy is naming the next layer of the stack, and the security industry is realizing what 40,000 exposed agents actually means.

My take: The "Claws" framing is going to stick. Every major AI shift gets a vocabulary moment — "transformer," "RLHF," "RAG," "MoE" — and "claws" might be what defines agent-to-world interfaces in the post-tool-call era. Watch it show up in papers within weeks.

The 40,000 exposed agents story is the one I'd lose sleep over. Security researchers didn't find bots answering customer service tickets. They found agents with full system access, open to the internet, no auth. That's not a bug report — that's the industry's current deployment culture expressed numerically.

And the r/ClaudeAI team morale thread is the human signal in all the technical noise. The gap between what AI can do and what teams have emotionally processed is where the real disruption is happening right now. 406 comments on a director's post about team morale is not a tech story — it's a management crisis in slow motion.

What I'm watching: Whether the "Claws" abstraction lands in CrewAI, Autogen, and LangGraph within the next two weeks. And whether the 40k exposed agents story triggers any coordinated security response — or just becomes another number in the "ship it and forget it" era.

Stay informed. Stay curious.