Welcome back. Earlier this month, we witnessed the first documented case of agentic ransomware: a cyberattack driven completely by an LLM. And now Hugging Face reported a breach carried out by OpenAI’s latest models to score on benchmarks. Today we cover what exactly happened.

Also: Give your agents a company brain, cut your token usage in GitHub Copilot, and the 10 AI repos blowing up on GitHub.

TODAY IN PROGRAMMING

Made with Midjourney.

OpenAI's models hacked Hugging Face to cheat a benchmark: A few days ago, we reported that an AI agent breached Hugging Face's servers. The ChatGPT maker just revealed that GPT-5.6 Sol and an unreleased model were the attackers. These models escaped their sandbox during a cyber evaluation and broke into Hugging Face's servers looking for test answers.

Google's new models make AI agents cheaper to run: The search giant just dropped Gemini 3.6 Flash and 3.5 Flash-Lite to reduce high token costs for production agents. The company claims its Gemini 3.6 Flash model uses 17% fewer output tokens than its predecessor and performs better at coding and computer tasks. They also released Flash Cyber, a specialized security model that finds and patches vulnerabilities, though the company currently limits its rollout to government agencies and trusted partners.

Anthropic teaches Claude to watch and learn: The AI lab just shipped two major screen-focused updates. In Claude Cowork, you can now record yourself performing a task and narrate your steps. Claude then converts that workflow into a reusable skill. Simply click “Record a skill” in the desktop app to start. Meanwhile, Claude Code now supports iOS simulators. This allows Claude to run your app, navigate through it, and iterate until the code works perfectly.

AI is in your engineering workflow. While the token spend shows it, the throughput doesn't. The human is very much still in the loop, and that's a context problem.

  • The 8 levels of context maturity: where most teams are stuck and what the ceiling looks like at each stage

  • Why more MCPs, rules, and skills provide agents access but not understanding

  • How leading engineering teams are using a context engine to make the most of their agents

INSIGHT

Skipping AI code reviews makes your project harder to understand later. Here’s how to fix it:

Source: The Code, Superhuman

The lights-out gamble. "Dark factory" is the phrase taking over engineering circles this week. It refers to AI agents writing and shipping code that no human ever reads. Former Google director Addy Osmani just mapped the idea in his viral essay. His warning is that a team that stops reading its code slowly stops understanding it.

Free everywhere but one place. The rot starts with a basic imbalance. Generating code, running tests, and security scans now cost almost nothing. Human review is the only stage that stays expensive, because attention doesn't scale. So Osmani sets a strict limit. An agent gets only as much freedom as you can cheaply verify, and not one inch more.

Proof from the floor. The essay draws on the insights from HumanLayer co-founder Dex Horthy. In a talk at the AI Engineer World's Fair, he explored why software factories fail. Horthy has seen it happen himself. He once ran a fully automated factory for four months without anyone reading a single line of code. Even though the tests stayed green, the team slowly lost their understanding of the system. Fixing it took painstaking manual debugging. Osmani calls this gap comprehension debt.

Read the blueprint first. Osmani's answer is to keep humans wherever mistakes are expensive. Review the plan before the agent builds. That way, you're judging the decision itself. If you skip it, you'll be digging that same decision out of thousands of lines of code later. His outer loop essay goes deeper, and Horthy's 12-factor agents guide shows how to build loops that can safely run in the dark.

Recently, a vibe-coded app leaked 1.5M API keys because nobody reviewed the code.

Your team ships AI-written code every day. Superblocks keeps it governed:

  • Security agents scan every app before it ships

  • Secrets stay in a managed vault, never in the code

  • Runs in your own AWS account, with SSO and audit logs on every build

IN THE KNOW

What’s trending on socials and headlines

Meme of the day.

  • Copilot Hacks: This 13-minute video covers the Copilot feature that cuts your token costs and why most developers accidentally break it.

  • Repo Radar: These 10 AI repos blew up on GitHub this week. One already has 90K stars (3.7K bookmarks).

  • Karpathy's Secret: OpenAI cofounder and now Anthropic researcher Andrej Karpathy shared the "lazy" prompting habit that gets him better results (2.1M views).

  • Company Brain: This 6-step guide shows you how to become an AI-native company, starting with a "company brain" your agents can pull from (3.8K bookmarks).

  • Unplugged AI: This open-source tool runs AI models on your Mac fully offline. No cloud, no accounts, no subscriptions.

  • Context Trap: A senior engineer explains why stuffing your AI's massive context window might be backfiring. Here’s the fix (1.1K likes).

  • Failed Interview: A Meta engineer posted an honest postmortem of bombing a big tech interview and the assumption that cost him the job.

TOP & TRENDING RESOURCES

Click here to watch the tutorial.

Top Tutorial

4 repos to cut token usage (by a Microsoft engineer): You'll learn how to slash token costs while using AI coding agents. The tutorial walks through setting up four tools: RTK for trimming command outputs, Headroom for compressing chat history, Ponytail for writing more concise code, and Graphy for quickly mapping out projects for the AI. 

Top Tool

FogLamp Scan: This tool creates an interactive map of your repository with just one prompt. You don't need to install anything or create an account to get started.

Top Repo

Show me your work (by a Cursor engineer): A plugin that helps you navigate large repositories. It establishes a standard for maintaining a clear audit trail of decisions during long or automated agent sessions. 

Trending Cookbook

How to run large code migrations with Claude Code (by Anthropic): Code migrations are getting faster. Bun ported 1M lines of Zig to Rust in under two weeks with all tests passing, while another Python codebase was moved to 165k lines of TypeScript over a single weekend. Anthropic has now shared a six-step workflow to help manage these large-scale migrations.

AI CODING HACK

How to teach Codex your team's code review rules

Reviewers often repeat the same PR comments, like warnings about field renames or logging customer data. Codex Code Review now fixes this by reading your custom rules from AGENTS.md and citing them directly in its feedback.

  • Step 1: Enable Codex Code Review on your repo if it isn't already.

  • Step 2: Add a "Code Review Rules" section to your AGENTS.md. This example comes straight from the Codex repo:

## Code Review Rules

### Breaking changes

Search for breaking changes in external integration surfaces:

- raw response item events (`rawResponseItem/*`), even while experimental
  • Step 3: Swap the bullet for your own rules, stating both the risk and the safe alternative.

  • Step 4: Open a PR. Codex flags violations and links back to the rule behind each one.

P.S. Get 50+ AI coding hacks for Claude Code, Cursor, and Codex here.

IN CASE YOU MISSED IT

Our most-clicked story from yesterday

Check out Coinbase's new playbook on their AI-native engineering interview process. 

Grow customers & revenue: Join companies like Google, IBM, and Datadog. Showcase your product to our 300K+ engineers and 150K+ followers on socials. Get in touch.

What did you think of today's newsletter?

Your feedback helps us create better emails for you!

Login or Subscribe to participate

You can also reply directly to this email if you have suggestions, feedback, or questions.

Until next time — The Code team

Keep Reading