Proud Dad to Two Awesome Boys on the Spectrum (Autism Spectrum Disorder) // Sr Director, Global Product Design @JumpCloud
Recently launched @buildFeedTech
GitHub has a front-row seat to how code is changing now that everyone—and their army of agents—can ship code. In March alone, agents created 17 million pull requests on the platform.
That’s why I was thrilled @hammer_mt was on hand to interview @github COO @kdaigle at Microsoft Build for a behind-the-scenes look at how the platform is helping developers manage the influx without dictating which pull requests they should trust or merge.
This week on @every’s AI & I, Mike gets into:
- The 14x commit explosion. GitHub hit 1 billion commits last year. Kyle says they’re on pace for 14 billion this year—and he doesn’t think that curve is plateauing.
- GitHub is committed to letting open-source maintainers set their own standards. Agent PRs are flooding communities, but GitHub’s philosophy is to leave code maintainers in control.
- The developer/non-developer distinction is collapsing. GitHub’s own legal and finance teams are using Copilot to build apps, one example of how AI has expanded the definition of who counts as a developer.
- Per-seat pricing doesn’t survive a world where agents run while you sleep. Kyle thinks automatic model routing—swapping in Haiku for simple tasks instead of always calling the expensive model—is the best way to make the economics make sense.
- Daigle runs a daily self-improvement loop with an AI he named Baxter. Every day, Baxter reads 7 days of his emails and Slack messages, flags his communication patterns, and checks whether Kyle followed last week’s advice.
This is a must-watch for anyone running agents in their dev workflow—and curious how GitHub is handling the explosion of commits on its platform.
Watch below!
Timestamps:
Introduction: 00:00:52
The agentic PR flood: 00:03:27
GitHub’s approach to helping open-source maintainers manage the surge: 00:04:33
What 14 billion commits means for code quality: 00:06:15
Moving from per-seat licensing to usage-based pricing: 00:08:03
Kyle's dual role as GitHub COO and Microsoft's chief marketing officer for developers: 00:09:45
Developer choice as competitive moat: 00:13:03
How to balance dogfooding your own tools with staying honest about the competition: 00:14:57
Hill climbing, frontier tuning, and solving the model-routing problem: 00:19:45
Kyle's agentic communication hack: 00:24:45
Stepped away from managing agents yesterday to summit our first 14'er! Mount Blue Sky just opened after 18 months, you can drive the majority of the way up and hike to the summit in about 30mins.
Update 5:05 PT: The attack has now expanded well beyond @TanStack and @Mistral.
373 malicious package-version entries across 169 npm package names, including @uipath, @squawk, @tallyui, @beproduct, and more.
The malware propagates by stealing your CI credentials and using them to publish new compromised versions.
Full IOCs, affected package list, and detection steps: https://t.co/jWG9DUCu3x
Three months ago, Codex was trash for knowledge work. Now it's my daily driver.
I use it for writing, recruiting, deep engineering work, and everything in between. It even keeps me at inbox 0.
I chatted with @every's head of growth Austin @tedescau on @every's AI & I about what changed, and why he now spends 80% of his working time in the Codex desktop app too.
We get into:
- How Codex went from making Austin feel like an idiot to being the place he goes to get stuff done, including complex tasks like writing go-to-market plans using existing material from Slack, Notion, and meeting transcripts.
- Why the Codex’s desktop app, which is faster and more reliable than Claude Desktop/Cowork, is the real differentiator.
- How I source candidates with Codex by having it identify career arcs, not keywords—my go-to move is identifying organizations likely to teach the skills Every needs for a role, and then find candidates from that pool who have since gone on to work in AI.
This is a must-watch for anyone who's wondering whether it’s finally time to give Codex a try.
Watch below!
Timestamps
How Codex went from a tool for senior engineers to a daily driver for knowledge work: 00:00:57
How Claude Code proved that a great coding agent works for any knowledge work: 00:02:42
Austin's switch to Codex: 00:07:24
How Austin set up Codex with folders, keys, and reviewer agents: 00:13:48
Using Codex to brainstorm automations across Gmail, Slack, and Notion: 00:18:24
How Austin manages the human review step when Codex is drafting communications: 00:22:42
Using Codex to build specialized agents inspired by product executive Claire Vo: 00:28:54
Synthesizing meeting transcripts and Slack threads into a go-to-market plan: 00:31:09
Building a live KPI tracker in Notion that agents can read: 00:40:15
Using Codex for recruiting: 00:44:54
Hey everyone!
Mystyleshaus is now live.
I’ve finally launched my website dedicated to curated Midjourney style codes. This is my very first launch, and I’m a bit nervous but excited to share it with the community.
The library already features over 400 free and premium styles designed to help you discover new visual directions for your projects.
Since this is the initial launch, I’m still fine-tuning the experience. If you have any questions or run into any issues, feel free to reach out — I’ll do my best to respond as quickly as possible.
Thank you for your support!
https://t.co/y1mCcbMlCL