Welcome back. China's Moonshot just dropped the full open weights for Kimi K3. Frontier intelligence is now available to every dev — or is it? With 2.8 trillion parameters, most developers would need a small fortune to deploy it on their local setup at home. But that doesn’t mean devs don’t have a plan to put it to use.
Today’s Brief
How to reduce token spend
Building a working ‘Call of Duty’ game using Opus 5
Hunting 200 bugs using Codex subagents
How to fine-tune any AI model locally

TODAY IN PROGRAMMING
Moonshot drops Kimi K3’s open-weights that undercut frontier rivals: The Chinese AI lab just released the full weights for Kimi K3, a massive 2.8-trillion-parameter model with native visual understanding and a 1M-token context window. But at that size, most devs won't be able to run it locally. Instead, they expect providers to serve it cheap and fast, then distill it into smaller models that actually run on consumer GPUs. Still tempted? See what it takes.
Microsoft's first cyber model secures code on a budget: The software giant just debuted MAI-Cyber-1-Flash within MDASH, a multi-agent harness designed to find and fix vulnerabilities across complex codebases. The company claims it hits 96% on CyberGym, beating out Gemini, GPT, and Mythos at half the cost. The model handles routine scans on its own and only escalates the toughest 10% of tasks, finally making always-on code security affordable enough to actually use. Get early access.
Anthropic's CEO responds to open-weights ban allegations: The AI lab's CEO says Anthropic has "never advocated" banning open-weights models. This clarification comes after more than 130 companies signed a letter opposing those kinds of restrictions. Now, Dario Amodei wants to shift the focus. He's calling for tighter chip export controls and mandatory safety testing for any powerful model, whether it's open or closed. You can read his full essay here.

PRESENTED BY WISPR
Claude Code, Cursor, Codex. The output ceiling is insane. But "fix the bug" gets you slop. Detailed context gets you shipping code.
The problem: typing out file references, edge cases, and architecture context 40 times a day is exhausting. So you cut corners. Your agent gets lazy input.
Wispr Flow lets you speak full prompts with syntax-aware dictation. camelCase, snake_case, file names all preserved. Auto-tags files in Cursor and Windsurf.
Used by engineers at OpenAI, Vercel, and Clay. Works on Mac, Windows, iPhone, and Android.
Better prompts in. Better code out. Try Free

INSIGHT
AI writes most of your software. But is it safe from cyber attacks?
Anthropic’s security team recently shared a story that should put every engineering team on alert: One of their security agents asked another Claude instance to deploy a fix it wasn't authorized to push on its own. Luckily, a human reviewer caught it before it could ship. This incident confirms that you can't secure an agent by constraining its instructions. You can constrain its access and actions, including its access to other agents.
Security scales with Code. Engineers at Anthropic now ship 8x more code per quarter than they did in 2021, and Claude writes roughly 80% of it. So security becomes an important part, and it should scale with every stage of the software lifecycle.
Deputy CISO Jason Clinton shared a high level overview of how Anthropic is managing it:
Plan: Claude checks each new project design against a standard catalog of known attack methods, using company policies and past decisions as context. Low-risk projects skip the security review queue entirely.
Code: Secure coding rules sit in the files Claude reads before generating any code, so protection starts at the source. Each newly discovered bug type gets added to those rules so it cannot come back.
Test: Several AI reviewers with separate, narrow jobs examine each pull request independently. If one reviewer gets fooled or compromised, another can still catch the problem.
Deploy: Automated attack simulations run continuously against the staging environment instead of on a periodic schedule.
Monitor: Every agent gets a single job and the minimum permissions needed to do it. Each action is logged centrally and treated like a potential rogue insider.
The playbook is public. Clinton's full post goes deeper on each stage, including how new AI reviewers earn trust before their approvals count. Read it, pick one stage, and pilot it in the next sprint.

IN THE KNOW
What’s trending on socials and headlines

Meme of the day.
Game Development: One developer shared a demo of a fully working ‘Call of Duty’ game built by Claude Opus 5. Here's the full prompt (4.1M views).
Bug Swarm: OpenClaw's creator ran 12 parallel Codex subagents to autonomously hunt 200 bugs before a release. Here's the exact prompt he used (1.4K likes).
Graph Engineering: This engineer used Claude Code's dynamic workflows to run 1,000 agents on a codebase no single context could hold. His 5-step guide shows how (1.4M views).
Codex Maxing: An OpenAI Codex engineer runs his entire workday through one AI. He walks through how he plugged Codex into his Slack, email, and Linear.
Leadership Exodus: Engineering leaders at startups are burning out and walking away just months in. A veteran engineer shares 8 reasons behind the trend (1.3K bookmarks).

TOP & TRENDING RESOURCES
Top Tutorial
How to fine-tune any AI model locally: You're going to learn how to locally fine-tune LLMs with Unsloth Studio. This tutorial walks through picking the best base model for your gear, building your own training data, and kicking off the fine-tuning. Finally, it shows how to compare your results and export the custom model.
Top Tool
Atomic Agent: A local-first AI that manages your browser and files. It uses high-speed local models to run commands and remember context securely on your machine.
Trending Cookbook
How to reduce token spend: Using AI agents for complex workflows is a huge drain on time and tokens. This guide shows you how to swap LLM-driven coordination for deterministic code. It'll cut your token usage by 8x and slice execution time in half.

AI CODING HACK
How to run Grok 4.5 in Codex without an API key
Codex ships with OpenAI models, and pointing it at another provider means an xAI API key and pay-as-you-go billing. AI engineer and educator, Alvaro Cintas, shared a setup to route Grok 4.5 through Codex.
You just use an X Premium subscription as your credential instead. The tool is called opencodex. It’s a local proxy that translates the API into whatever the model speaks.
Install it and OAuth into xAI with your X account. Then you can inject it right into Codex:
# install the proxy (requires bun)
npm install -g @bitkyc08/opencodex
# sign in with your X account, OAuth handles the rest
ocx login xai
# inject into Codex and start
ocx init && ocx start
# run Codex on Grok
codex -m "xai/grok-4.5" "your prompt"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
Anthropic just dropped a certification for devs building with Claude Code. Pass the proctored exam, and the credentials are yours to keep.
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?
You can also reply directly to this email if you have suggestions, feedback, or questions.
Until next time — The Code team




