Welcome back. It turns out OpenAI’s agents were pushing so much code that the company ended up rebuilding its own Git backend. Now, they’re sharing what they learned along the way. Meanwhile, DeepSeek wants to make building plugins as easy as typing a prompt.
Also: MIT researchers make a tiny but surprising edit to an AI model’s weights, an AI phone aiming to replace your iPhone, and a 12-stage AI security engineering roadmap.
Today’s Brief
What devs can learn from Proton’s AI push
7 underrated perks of having an Apple developer account
Learn to build your own Claude Code software factory (tutorial)
Build a design system for coding agents (cookbook)

TODAY IN PROGRAMMING
DeepSeek lets you build agent plugins with a prompt: The Chinese AI lab just rolled out Creator Mode for DeepSeek Harness, letting you create plugins simply by describing what you want in a text prompt. While models decide what to do, a harness is what gets the job done. DeepSeek’s open-source Harness takes an “everything is a plugin” approach, so whether you need a tool, skill, or interface tweak, the agent will build it for you. It’s still in preview, though, so expect API changes. Try it here.
OpenAI rebuilds Git to keep up with its agents: The ChatGPT maker’s AI agents were pushing so much code that its Git setup started to buckle, with reliability sometimes dipping below 90%. So OpenAI built Pando, a new server designed to handle all that parallel agent traffic without changing how engineers or agents use Git. And it’s paying off. The company says pushing code now takes nearly 80% less time. Pando is staying internal for now, but OpenAI is sharing its Git fixes with the community.
Hume wants to replace your audio model stack: The voice AI startup just unveiled its Audio Decision API model, letting you ask questions about a recording in plain language. That means figuring out how many people are speaking, whether a caller sounds frustrated, or even if someone laughed. Instead of stitching together 10+ models, you now need one API call on live audio or hours of recordings. Trained on 10M+ human judgments, it scored 82% on the company’s benchmark, edging out Gemini 3.8 Flash at 78%. Join the waitlist.

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
Why Proton’s AI push sparked a backlash, and what devs can learn from it

Source: X.com
Speed at what cost. Proton, the Swiss company behind Proton Mail, is going all in on AI and things are getting messy. A 404 Media investigation published last week revealed that CEO Andy Yen dismissed an engineer’s request to pentest new code as “loser thinking.” And that was just the beginning. He also told staff that 2026 would be the last year Proton hires engineers and announced AI re-interviews that could decide who keeps their job. Unsurprisingly, that didn’t go down well.
A quick U-turn. Users started canceling subscriptions and calling for Yen’s resignation. A day later, he scrapped the re-interviews, admitted a communication failure on his part, and Proton apologized publicly. But the AI push isn’t going anywhere. Employees say the re-interview criteria are being folded into performance reviews.
The real takeaway. CTO Bart Butler’s leaked manifesto is worth your attention. Here are the ideas you can put to work:
Direct the code, don’t type it. Butler compares writing code by hand to memorizing phone numbers. Programming is dead, he writes, but engineering and expertise are not.
Manage agents like direct reports. When one fails, update your repo context files, shared prompts, and skills so the team never hits that failure again.
Keep your judgment in the loop. Models hallucinate and get misled by malicious inputs. Your experience catches what they miss.
Hunt down the next bottleneck. Faster coding just moves the slowdown. Look at your CI, specs, approvals, and code review, and redesign them around AI.
Two sides to it. Reactions have been mixed. Ruby on Rails creator DHH defended the push, while Clean Code author Robert “Uncle Bob” Martin echoed the manifesto’s core argument. Critics, meanwhile, focused on Proton’s workplace culture. Either way, if you’re an engineer in 2026, there’s plenty worth borrowing from Butler’s full manifesto.

IN THE KNOW
What’s trending on socials and headlines

Meme of the day.
Clean Machine: This open-source macOS tool turns your cluttered desktop into a robot vacuum’s playground, sorting files and tossing the junk as you want it (2.9K likes).
AI Fixes AI: MIT researchers let GPT-6 Astra rewrite another model’s weights like code, and what one tiny edit accomplished is turning heads (5.3M views).
Apple Unlocked: This dev’s breakdown reveals 7 underrated perks hiding inside the $99 Apple developer account, including free CI/CD and much more (1.2K likes).
Cold War: Hackers struck Europe’s supermarket freezers again, and what they did across 6+ countries is costing stores millions (2.2M views).
iPhone Killer: A YC startup unveiled an AI phone built to replace your iPhone, and the founder says you’ll never need to touch it (2.7K likes).
Job Security: A developer claims learning AI security engineering will make you future-proof, sharing a 12-stage roadmap on where to start (4.4K bookmarks).
Reality Check: A new benchmark put AI agents through the world’s most valuable work, and even the top model failed spectacularly (1.6M views).

TOP & TRENDING RESOURCES
Top Tutorial
How to build your own Claude Code software factory: This tutorial shows how to stop babysitting coding agents and build a workflow where a linear ticket kicks off the work, multiple agents build in parallel, and you only step in when a decision actually needs you. You’ll learn how to combine Claude Code, T3 Code, PStack, cloud sandboxes, playbooks, and verification into one repeatable setup.
Top Repo
NanoUI: Build tiny cross-platform desktop apps in Zig with either native GPU-drawn UI or a web frontend. It runs on macOS, Windows, and Linux, ships as a single binary, and includes headless testing and screenshots so coding agents can build and verify interfaces without opening a window.
Trending Cookbook
How to build a design system for coding agents: This guide shows how to turn the design decisions in your head into a system an agent can reliably use. You’ll learn how to structure primitives, semantic tokens, components, reusable blocks, rules, and skills so agents stop guessing and start building interfaces that actually feel like your product.

AI CODING HACK
How to get real performance fixes from Claude Code
Tell Claude Code to “make it faster” and it usually adds a cache. A dev shared a perf-review prompt that names the exact structures to ask for instead.
Step 1: Save it as a reusable slash command. Create a file at “claude/commands/perf-review.md” and paste the full prompt. The short version:
Do a performance review of this project:
1. Profile first. Find the 5 slowest spots.
2. Match each spot to one case only:
- Uses a cache → redesign, don't add more caches
- Hot loop hitting hash tables → flat array + indices
- Many objects, few fields read → struct of arrays (SoA)
- Serial awaits → run in parallel
- No match → data-oriented rewrite
3. Report current time, matched case, file + lines,
expected speedup. Don't change anything yet.Step 2: Run “/perf-review” in any project. Claude profiles first, matches each hotspot against the cases, and reports before touching code.
Expect a report with files, lines, and estimated speedups. Approve the changes you want, skip the rest.

IN CASE YOU MISSED IT
Our most-clicked story from yesterday
Anthropic is expanding watermarks across Claude outputs starting Nov. 3, and this post breaks down what you need to watch for.
Whenever you're ready to dive deeper
If you enjoyed this newsletter, you should definitely check out our IT and cybersecurity newsletters. Subscribe using the links below:
We put together 20+ hands-on guides covering coding agents, agentic engineering, and leadership frameworks to help you level up your career. You can get them here.
Advertise with us: Join companies like Google, IBM, and Datadog. Showcase your product to our 350K+ 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





