Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

SaaS isn’t dead, it just needs to become agent-native. Linear (Linear) is a great example of how: They pivoted the product to be used by both humans and agents, and that has made them one of the premier software tools in the agent-native era. I had Linear’s cofounder and... CEO Karri Saarinen on Every 📧's AI & I to talk about how a product management tool for human software developers became an agent-native tool—and how Linear’s trajectory reveals a bright future for SaaS businesses: - Speed means decisions matter more, not less. AI makes it easy to have an idea and build it without considering whether its existence is justified. When ChatGPT was released, SaaS companies were launching their own chatbots left, right, and center. Instead of jumping on the bandwagon, Linear stopped to consider whether the application was useful. (It wasn’t.) - Just because the technology has changed doesn’t mean your mission should. Karri attributes Linear’s success to never losing sight of what matters: helping teams develop great software. Instead of chasing trends, Linear focused on understanding how AI was impacting its customers’ workflows—and updating its product accordingly. - Agents are now first-class users. Linear never tried to change what it was or did well; it just expanded the user base. Companies can now kick off agents inside Linear, manage them, and track what they're working on alongside the humans on the team, which explains why Codex, Coinbase, and Brex all run their agents on Linear. This is a must watch for anyone interested in how an agent-native SaaS company operates. Watch below! Timestamps: Introduction and how Every first discovered Linear: 00:00:39 Why Linear waited to ship AI features instead of rushing to chatbots: 00:02:00 Linear's agent platform and becoming the system that guides AI agents: 00:05:06 Why "SaaS is dead" is a simplistic narrative: 00:07:42 How Linear adopted AI coding tools internally: 00:12:18 AI's impact on product building workflows—speed versus thoughtfulness: 00:17:45 The value of conceptual work and thinking before shipping: 00:22:18 How AI is reshaping Linear's product strategy: 00:29:30 Demo: Linear's agent skills, shared context, and code review workflow: 00:37:18 The future of product development and the enduring role of human judgment: 00:47:48show more

Dan Shipper 📧

117,539 subscribers

36,359 views • 4 months ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Karri Saarinen (Karri Saarinen), co-founder and CEO of Linear, was the first designer at Coinbase and a lead designer at Airbnb. On Design Review with YC's Aaron Epstein, he shares how his design background shaped Linear's product philosophy, why quality and craft matter from day one, what founders should look for when hiring, and how AI is changing the way teams build. 02:00 – Lessons learned from YC, Coinbase, and Airbnb 06:00 – Building trust through brand and design 08:24 – Linear’s brand: craft, quality, and authenticity 10:40 – Why sales is part of the brand experience 13:10 – Shipping fast without losing quality 17:18 – Hiring for product taste and judgment 19:28 – Superpowers of designers as founders 21:12 – Advice for designers considering founding a startup 23:26 – Why founders should care about design from day one 25:24 – Tips for creating products that stand out 28:24 – Balancing creative freedom with shipping timelines 28:56 – How AI is changing design and product work 30:44 – Why AI won’t replace designers (and what shifts to expect) 32:44 – The future of product and design teams with AI

Y Combinator

77,233 views • 10 months ago

Even when things are going great, running a $1.5 billion AI startup is a knife fight. Granola was one of the first AI apps of this generation to achieve near-ubiquitous adoption. But meeting notes are not the company’s be-all and end-all. The real battle is over owning the interface that everyone uses to get their work done in an AI-native world. I had Chris Pedregal (Chris Pedregal), cofounder and CEO of Granola, back on Every 📧’s AI & I to talk about the current state of the application layer, AI’s frontier, and the future of work. We get into: - Why meeting notes clones don’t matter. Three big companies cloned Granola’s core feature. To him, meeting notes were never the real prize. “Easy come, easy go” is his view of anyone’s lead, including his own. - How he thinks about building proactive features in AI. Granola pre-generates millions of pre-meeting briefs, which include context on the nature of the meeting and people participating, that most people never open. But when they do, they have a magical experience. - Why Granola is betting on “bring your own agent.” Chris says the API and MCP will get “a lot better” over the next few months, and we talk about their agent-native strategy and why they’ve pushed the product that way. This is a must-watch for anyone building at the application layer. Watch the episode! Timestamps Introduction: 00:00:59 Why running a company is a knife fight even when it’s working: 00:01:57 Granola’s counterintuitive view on competition: 00:04:33 Dan’s “pirate and architect” model for early-stage product teams: 00:10:44 Granola’s “shaping” and “validation” phases for building features: 00:13:09 Why Dan lives almost entirely inside Codex: 00:18:17 The case for “Codex-native apps”: 00:24:40 Granola’s “handrail” philosophy: 00:35:37 Why Granola is going all in on winning meeting-adjacent context: 00:38:12 What a transcript alone can never capture: 00:44:19

Even when things are going great, running a $1.5 billion AI startup is a knife fight. Granola was one of the first AI apps of this generation to achieve near-ubiquitous adoption. But meeting notes are not the company’s be-all and end-all. The real battle is over owning the interface that everyone uses to get their work done in an AI-native world. I had Chris Pedregal (Chris Pedregal), cofounder and CEO of Granola, back on Every 📧’s AI & I to talk about the current state of the application layer, AI’s frontier, and the future of work. We get into: - Why meeting notes clones don’t matter. Three big companies cloned Granola’s core feature. To him, meeting notes were never the real prize. “Easy come, easy go” is his view of anyone’s lead, including his own. - How he thinks about building proactive features in AI. Granola pre-generates millions of pre-meeting briefs, which include context on the nature of the meeting and people participating, that most people never open. But when they do, they have a magical experience. - Why Granola is betting on “bring your own agent.” Chris says the API and MCP will get “a lot better” over the next few months, and we talk about their agent-native strategy and why they’ve pushed the product that way. This is a must-watch for anyone building at the application layer. Watch the episode! Timestamps Introduction: 00:00:59 Why running a company is a knife fight even when it’s working: 00:01:57 Granola’s counterintuitive view on competition: 00:04:33 Dan’s “pirate and architect” model for early-stage product teams: 00:10:44 Granola’s “shaping” and “validation” phases for building features: 00:13:09 Why Dan lives almost entirely inside Codex: 00:18:17 The case for “Codex-native apps”: 00:24:40 Granola’s “handrail” philosophy: 00:35:37 Why Granola is going all in on winning meeting-adjacent context: 00:38:12 What a transcript alone can never capture: 00:44:19

Dan Shipper 📧

13,146 views • 26 days ago

In the future, you’ll be able to accomplish a goal by just giving Claude an outcome and a budget. That’s the direction Anthropic is building in with its new Managed Agents features, announced at this week’s Code with Claude developer event. The basic idea: Claude, wrapped in a computer in the cloud, that you can spin up, scale, and manage as needed. Anthropic is taking on the infrastructure that kills most agent products, and making sure that it scales to meet the needs of agents running 24/7. On this week’s AI & I from Every 📧, I talk with Angela Jiang (Angela Jiang), head of product for the Claude platform, and Katelyn Lesse (Katelyn Lesse), head of engineering for the Claude platform, about what Anthropic is building and what it takes to make agents reliable in production. We get into: - Why the "build a generic harness, hot-swap any model behind it" playbook is already outdated. Angela points to eval data on Memory where the same task across different harnesses performed drastically differently. - The infrastructure wall every team hits in production—and why Katelyn thinks “my sandbox died and took the agent with it” is the real reason internal agents don't ship. - Why Anthropic is so bullish on using file systems and skills within Claude, including Angela's argument that those early design choices can compound for years. This is a must-watch for anyone trying to take an agent past the demo and into production. Watch below! Timestamps: How the Claude platform evolved from API to agents: 00:01:48 The primitives that make up Claude Managed Agents: 00:04:09 Why the harness and the model are becoming a single unit: 00:10:37 The infrastructure wall that kills most agent projects in production: 00:18:49 Why team agents need a different shape than individual productivity tools: 00:24:49 How Anthropic's legal team uses an agent to review marketing copy: 00:26:36 Using multi-agent orchestration for advisor strategies, adversarial pairs, and swarms: 00:34:24 How to measure agent success with outcome and budget as the end state: 00:35:50 What the platform looks like a year from now, when Claude writes its own harness: 00:39:11

In the future, you’ll be able to accomplish a goal by just giving Claude an outcome and a budget. That’s the direction Anthropic is building in with its new Managed Agents features, announced at this week’s Code with Claude developer event. The basic idea: Claude, wrapped in a computer in the cloud, that you can spin up, scale, and manage as needed. Anthropic is taking on the infrastructure that kills most agent products, and making sure that it scales to meet the needs of agents running 24/7. On this week’s AI & I from Every 📧, I talk with Angela Jiang (Angela Jiang), head of product for the Claude platform, and Katelyn Lesse (Katelyn Lesse), head of engineering for the Claude platform, about what Anthropic is building and what it takes to make agents reliable in production. We get into: - Why the "build a generic harness, hot-swap any model behind it" playbook is already outdated. Angela points to eval data on Memory where the same task across different harnesses performed drastically differently. - The infrastructure wall every team hits in production—and why Katelyn thinks “my sandbox died and took the agent with it” is the real reason internal agents don't ship. - Why Anthropic is so bullish on using file systems and skills within Claude, including Angela's argument that those early design choices can compound for years. This is a must-watch for anyone trying to take an agent past the demo and into production. Watch below! Timestamps: How the Claude platform evolved from API to agents: 00:01:48 The primitives that make up Claude Managed Agents: 00:04:09 Why the harness and the model are becoming a single unit: 00:10:37 The infrastructure wall that kills most agent projects in production: 00:18:49 Why team agents need a different shape than individual productivity tools: 00:24:49 How Anthropic's legal team uses an agent to review marketing copy: 00:26:36 Using multi-agent orchestration for advisor strategies, adversarial pairs, and swarms: 00:34:24 How to measure agent success with outcome and budget as the end state: 00:35:50 What the platform looks like a year from now, when Claude writes its own harness: 00:39:11

Dan Shipper 📧

66,339 views • 3 months ago

"We are clearly entering a world where a product-minded engineer is now empowered to produce software without writing a line of code for it." In this conversation, Temporal CEO Samar Abbas joins a16z GPs Sarah Wang and Raghu Raghuram to cover: - Why agents are going from short-lived and interactive to long-running and async - Why the engineer of the future manages 15 parallel AI tasks at once - How OpenAI Codex runs millions of concurrent agent executions on Temporal - How real-time context engineering is exploding on Temporal - Why SaaS isn't dead, and value is migrating to APIs 00:00 Introduction 04:03 Temporal's origin story 11:14 Why agents raise the stakes 16:00 Specialized agents need durable RPC 25:20 Deep research agents 30:58 Execution histories as a superpower 39:04 Minimal viable long-running agent architecture 45:07 Context engineering at scale 52:40 Where value accrues: The "five-layer cake" and breakout AI applications Samar Abbas Sarah Wang Raghu Raghuram

"We are clearly entering a world where a product-minded engineer is now empowered to produce software without writing a line of code for it." In this conversation, Temporal CEO Samar Abbas joins a16z GPs Sarah Wang and Raghu Raghuram to cover: - Why agents are going from short-lived and interactive to long-running and async - Why the engineer of the future manages 15 parallel AI tasks at once - How OpenAI Codex runs millions of concurrent agent executions on Temporal - How real-time context engineering is exploding on Temporal - Why SaaS isn't dead, and value is migrating to APIs 00:00 Introduction 04:03 Temporal's origin story 11:14 Why agents raise the stakes 16:00 Specialized agents need durable RPC 25:20 Deep research agents 30:58 Execution histories as a superpower 39:04 Minimal viable long-running agent architecture 45:07 Context engineering at scale 52:40 Where value accrues: The "five-layer cake" and breakout AI applications Samar Abbas Sarah Wang Raghu Raghuram

a16z

45,721 views • 5 months ago

AI has changed software engineering more in the last 3 years than it has changed in the previous 30. What’s needed is not a debate about whether it’s going away—instead it’s a serious discussion about its future: What are the new primitives, techniques, and best practices for software engineering in the age of AI. That’s why I brought Scott Wu (Scott Wu) on AI & I. He’s the founder of Cognition, the company behind the world’s first autonomous AI coding agent, Devin. Cognition got to $73M ARR in less than 2 years—and they just acquired Windsurf to accelerate their growth. I had Scott on the show to talk about where the programming goes from here. We get into: - What the new tools and workflows are for AI engineers. In the near term, Scott sees software engineering defined by a spectrum of tools. At one end are AI features that speed up coding, like tab complete; at the other are agentic systems, like Devin, that can take on tasks independently. Until engineers can operate entirely at the higher layer of abstraction, he argues, both are essential. - Why Scott thinks AGI is already here. By the benchmarks of a decade ago—passing the Turing test, solving hard math problems, and operating agentically—AGI is already here. The line keeps moving, he argues, because humans constantly redefine work around what machines can’t yet do. - Why developers will turn into product architects. Scott sees the long-term future of software engineering as a steady climb up the ladder of abstraction. Just as programming went from assembly to languages like Python and JavaScript, he thinks the future is humans focusing on the product, while AI agents execute. - How Devin stacks up against Anthropic’s Claude Code. Scott credits Claude Code’s success to great product design and the models becoming capable enough to support autonomous workflows. But according to him, the CLI itself isn’t the breakthrough, it’s how a tool fits into a developer’s workflow. Claude Code’s paradigm is that the AI is you, taking the wheel of your computer, he says, while Devin is like the engineer sitting beside you: it runs in its own cloud environment, manages the repo, and improves over time at testing and refining code. This episode of Every 📧’s AI & I is a must-watch for anyone interested in the brass tacks of how AI changes the future of programming. Watch below! Timestamps: Introduction: 00:02:02 Why Scott thinks AGI is here: 00:02:32 Scott’s personal journey as a founder: 00:09:27 Why the fundamentals of computer science still matter: 00:16:55 How the future of programming will evolve: 00:22:30 A new workflow for the AI-first software engineer: 00:26:50 How Devin stacks up against Claude Code: 00:29:33 Reinforcement learning to build better coding agents: 00:40:05 What excites Scott about AI beyond Cognition: 00:50:05

AI has changed software engineering more in the last 3 years than it has changed in the previous 30. What’s needed is not a debate about whether it’s going away—instead it’s a serious discussion about its future: What are the new primitives, techniques, and best practices for software engineering in the age of AI. That’s why I brought Scott Wu (Scott Wu) on AI & I. He’s the founder of Cognition, the company behind the world’s first autonomous AI coding agent, Devin. Cognition got to $73M ARR in less than 2 years—and they just acquired Windsurf to accelerate their growth. I had Scott on the show to talk about where the programming goes from here. We get into: - What the new tools and workflows are for AI engineers. In the near term, Scott sees software engineering defined by a spectrum of tools. At one end are AI features that speed up coding, like tab complete; at the other are agentic systems, like Devin, that can take on tasks independently. Until engineers can operate entirely at the higher layer of abstraction, he argues, both are essential. - Why Scott thinks AGI is already here. By the benchmarks of a decade ago—passing the Turing test, solving hard math problems, and operating agentically—AGI is already here. The line keeps moving, he argues, because humans constantly redefine work around what machines can’t yet do. - Why developers will turn into product architects. Scott sees the long-term future of software engineering as a steady climb up the ladder of abstraction. Just as programming went from assembly to languages like Python and JavaScript, he thinks the future is humans focusing on the product, while AI agents execute. - How Devin stacks up against Anthropic’s Claude Code. Scott credits Claude Code’s success to great product design and the models becoming capable enough to support autonomous workflows. But according to him, the CLI itself isn’t the breakthrough, it’s how a tool fits into a developer’s workflow. Claude Code’s paradigm is that the AI is you, taking the wheel of your computer, he says, while Devin is like the engineer sitting beside you: it runs in its own cloud environment, manages the repo, and improves over time at testing and refining code. This episode of Every 📧’s AI & I is a must-watch for anyone interested in the brass tacks of how AI changes the future of programming. Watch below! Timestamps: Introduction: 00:02:02 Why Scott thinks AGI is here: 00:02:32 Scott’s personal journey as a founder: 00:09:27 Why the fundamentals of computer science still matter: 00:16:55 How the future of programming will evolve: 00:22:30 A new workflow for the AI-first software engineer: 00:26:50 How Devin stacks up against Claude Code: 00:29:33 Reinforcement learning to build better coding agents: 00:40:05 What excites Scott about AI beyond Cognition: 00:50:05

Dan Shipper 📧

35,342 views • 10 months ago

The best product websites do more than pitch. They explain, guide, and reflect the product itself, and often serve as a company’s first impression. For Design Review, YC’s Aaron Epstein is joined by Karri Saarinen (Karri Saarinen), co-founder & CEO of Linear, to break down how today’s best software companies design their sites. They review examples from Linear, Sprites AI, , UnReal Milk, Confident AI, and Dropback, exploring how structure, motion, and clarity shape not just the user experience, but the brand as well. 00:43 - Authenticity in Branding 02:02 - The Initial Website for Linear 02:57 - Importance of Clear Messaging 03:49 - Be Specific 04:12 - Two Different Descriptions for Startups 07:55 - Brands and Design Evolve Over Time 09:57 - Sprites AI 15:09 - GigaML 22:02 - UnReal Milk 29:57 - Confident AI 34:27 - Talk to Your Ideal Customer 37:22 - Dropback

Y Combinator

53,469 views • 1 year ago

Linear is a startup that punches well above its weight in the speed and quality of shipping, and supporting a large number of customers (10,000+ companies) with a small engineering team (25 devs). I sat down with Linear's first engineering manager, Sabin Roman. Our discussion: We covered: • No email. How Linear handles internal communications • Quality. The “goalie” program to address customer concerns and Linear’s zero bug policy • Full remote. How Linear keeps teams connected despite working entirely remotely • Getting stuff done. An in-depth, step-by-step walkthrough of a project at Linear • Creativity + QA. Linear’s focus on quality and creativity over fash shipping • Career ladders. Titles at Linear, Sabin’s learnings from Uber Brought to you thanks to our wonderful sponsors: 🌟LaunchDarkly — a platform for high-velocity engineering teams to release, monitor, and optimize great software 🌟 Sevalla — Deploy anything from preview environments to Docker images 🌟WorkOS — The modern identity platform for B2B SaaS Watch it on: • YouTube: • Spotify: • Apple: • Web:

Linear is a startup that punches well above its weight in the speed and quality of shipping, and supporting a large number of customers (10,000+ companies) with a small engineering team (25 devs). I sat down with Linear's first engineering manager, Sabin Roman. Our discussion: We covered: • No email. How Linear handles internal communications • Quality. The “goalie” program to address customer concerns and Linear’s zero bug policy • Full remote. How Linear keeps teams connected despite working entirely remotely • Getting stuff done. An in-depth, step-by-step walkthrough of a project at Linear • Creativity + QA. Linear’s focus on quality and creativity over fash shipping • Career ladders. Titles at Linear, Sabin’s learnings from Uber Brought to you thanks to our wonderful sponsors: 🌟LaunchDarkly — a platform for high-velocity engineering teams to release, monitor, and optimize great software 🌟 Sevalla — Deploy anything from preview environments to Docker images 🌟WorkOS — The modern identity platform for B2B SaaS Watch it on: • YouTube: • Spotify: • Apple: • Web:

Gergely Orosz

139,252 views • 1 year ago

Guillermo Rauch (Guillermo Rauch) is one of the most prolific coders of this generation. But he doesn’t think of himself as a coder anymore. Coding, he says, is a specific skill that AI is becoming great at. Instead, he thinks the future of coding is more holistic, full-stack engineers who can ideate, design, and execute all together. Guillermo is the founder and CEO of Vercel (Vercel), the creator of NextJS, and SocketIO. We spent an hour talking about the future of software development in an AI world—and the meta-skills that are essential for the coders of today to master—in order to use tomorrow’s tools to their fullest extent. Here are a few takeaways: - One of the most important keys to his success is taste—and developing taste is all about paying better attention to everything you experience day to day. - He’s great at recognizing bleeding-edge technologies with extremely practical applications but that have bad user experiences. If you can learn to recognize those and build with them, you might build the next NextJs or SocketIO. - Why prototype cultures are becoming common in AI—and the benefits of written cultures like Amazon vs. prototype cultures like Apple for different kinds of companies. - For developers building frameworks, always put the product first; a framework in isolation without a “customer zero” is never going to be a good tool. - The theory of “recursive founder mode”—if you want to build a scalable business, you have to scale yourself by creating an atmosphere that nurtures talent and ambition. - AI tools are shifting software toward consumption-based billing models, making us capital allocators who decide how much compute the AI consumes. - The future of AI is agents with the taste, knowledge, and tools to perform specialized tasks. Watch below! Timestamps: Introduction: 00:01:33 How to spot trends early: 00:03:18 Why you should be your own customer: 00:07:34 How to create an ecosystem of talent and ambition: 00:14:55 Why Guillermo doesn't identify as a coder: 00:17:29 AI is gearing us toward an allocation economy: 00:20:50 How Vercel’s copilot compares with other coding agents: 00:28:34 Guillermo’s advice on having better taste: 00:40:35 The future of AI agents is specialized: 00:42:46 How AI startups can compete with big tech: 00:47:50

Guillermo Rauch (Guillermo Rauch) is one of the most prolific coders of this generation. But he doesn’t think of himself as a coder anymore. Coding, he says, is a specific skill that AI is becoming great at. Instead, he thinks the future of coding is more holistic, full-stack engineers who can ideate, design, and execute all together. Guillermo is the founder and CEO of Vercel (Vercel), the creator of NextJS, and SocketIO. We spent an hour talking about the future of software development in an AI world—and the meta-skills that are essential for the coders of today to master—in order to use tomorrow’s tools to their fullest extent. Here are a few takeaways: - One of the most important keys to his success is taste—and developing taste is all about paying better attention to everything you experience day to day. - He’s great at recognizing bleeding-edge technologies with extremely practical applications but that have bad user experiences. If you can learn to recognize those and build with them, you might build the next NextJs or SocketIO. - Why prototype cultures are becoming common in AI—and the benefits of written cultures like Amazon vs. prototype cultures like Apple for different kinds of companies. - For developers building frameworks, always put the product first; a framework in isolation without a “customer zero” is never going to be a good tool. - The theory of “recursive founder mode”—if you want to build a scalable business, you have to scale yourself by creating an atmosphere that nurtures talent and ambition. - AI tools are shifting software toward consumption-based billing models, making us capital allocators who decide how much compute the AI consumes. - The future of AI is agents with the taste, knowledge, and tools to perform specialized tasks. Watch below! Timestamps: Introduction: 00:01:33 How to spot trends early: 00:03:18 Why you should be your own customer: 00:07:34 How to create an ecosystem of talent and ambition: 00:14:55 Why Guillermo doesn't identify as a coder: 00:17:29 AI is gearing us toward an allocation economy: 00:20:50 How Vercel’s copilot compares with other coding agents: 00:28:34 Guillermo’s advice on having better taste: 00:40:35 The future of AI agents is specialized: 00:42:46 How AI startups can compete with big tech: 00:47:50

Dan Shipper 📧

186,985 views • 1 year ago

I vibe coded a new product on the side while running Every 📧—and today we're launching it for free. It's called Proof, and it’s a live collaborative document editor where humans and AI agents work together in the same doc. It’s built from the ground up for the kinds of documents agents are increasingly writing: bug reports, PRDs, implementation plans, research briefs, copy audits, strategy docs, memos, and proposals. It's fast, free, and open source—available now at Why Proof? When everyone on your team is working with agents, there's suddenly a ton of AI-generated text flying around—planning docs, strategy memos, session recaps. But the current process for collaborating and iterating on agent-generated writing is…weirdly primitive. It mostly takes place in Markdown files on your laptop, which makes it reminiscent of document editing in 1999. That’s why we built Proof. What makes Proof different? - Proof is agent-native. Anything you can do in Proof, your agent can do just as easily. - Proof tracks provenance: A colored rail on the left side of every document tracks who wrote what. Green means human, Purple means AI. - Proof is login-free and open source: This is because we want Proof to be your agent's favorite document editor. How we use Proof Every 📧: - Brandon Gell had OpenAI's Codex write a feature plan in Proof, then tagged my personal Claw (R2-C2) in Slack to review it. R2-C2 left feedback, I added comments, Brandon's agent revised the plan, and then Codex executed on it. Brandon submitted a PR to production without writing a line of code. - Austin Tedesco texts his Claw ideas while he's out on a run, then has it maintain a running Proof doc for his weekly food newsletter. He dictates drafts using Naveen Naidu's Monologue, writes into the outline himself, and uses the provenance gutter to track what's his voice vs. the agent's. - Kieran Klaassen uses it as a lightweight scratchpad for his compound engineering workflow. He brainstorms with an agent in the terminal, shares to Proof with one click, then opens the doc to leave comments and tells the agent to go work on them. His take: Proof's job is to communicate about writing and ideas. Proof is free, open source, and requires no login. I built the whole thing by vibe coding between meetings. I sat down with Brandon, Kieran, and Austin on Every 📧's AI & I to demo it live and talk about how it's changing the way we work. If you're building with agents and need a better way to collaborate on text, this one's for you. Watch below! Timestamps Introduction and the origin story of Proof: 00:02:00 From Mac app to collaborative web editor: 00:07:24 What makes Proof "agent native": 00:09:00 Live demo—watching an agent join and write inside a shared document: 00:14:30 How Austin uses Proof for creative writing and food journalism: 00:20:51 The challenge of multiple agents editing one document simultaneously: 00:24:30 When AI-written docs are better read by agents than by humans: 00:26:48 Brandon's agent-to-agent collaboration loop: 00:29:30 Proof as a lightweight scratchpad versus existing tools like Notion and GitHub: 00:37:09 Why Proof is open source and what that means for builders: 00:42:18

I vibe coded a new product on the side while running Every 📧—and today we're launching it for free. It's called Proof, and it’s a live collaborative document editor where humans and AI agents work together in the same doc. It’s built from the ground up for the kinds of documents agents are increasingly writing: bug reports, PRDs, implementation plans, research briefs, copy audits, strategy docs, memos, and proposals. It's fast, free, and open source—available now at Why Proof? When everyone on your team is working with agents, there's suddenly a ton of AI-generated text flying around—planning docs, strategy memos, session recaps. But the current process for collaborating and iterating on agent-generated writing is…weirdly primitive. It mostly takes place in Markdown files on your laptop, which makes it reminiscent of document editing in 1999. That’s why we built Proof. What makes Proof different? - Proof is agent-native. Anything you can do in Proof, your agent can do just as easily. - Proof tracks provenance: A colored rail on the left side of every document tracks who wrote what. Green means human, Purple means AI. - Proof is login-free and open source: This is because we want Proof to be your agent's favorite document editor. How we use Proof Every 📧: - Brandon Gell had OpenAI's Codex write a feature plan in Proof, then tagged my personal Claw (R2-C2) in Slack to review it. R2-C2 left feedback, I added comments, Brandon's agent revised the plan, and then Codex executed on it. Brandon submitted a PR to production without writing a line of code. - Austin Tedesco texts his Claw ideas while he's out on a run, then has it maintain a running Proof doc for his weekly food newsletter. He dictates drafts using Naveen Naidu's Monologue, writes into the outline himself, and uses the provenance gutter to track what's his voice vs. the agent's. - Kieran Klaassen uses it as a lightweight scratchpad for his compound engineering workflow. He brainstorms with an agent in the terminal, shares to Proof with one click, then opens the doc to leave comments and tells the agent to go work on them. His take: Proof's job is to communicate about writing and ideas. Proof is free, open source, and requires no login. I built the whole thing by vibe coding between meetings. I sat down with Brandon, Kieran, and Austin on Every 📧's AI & I to demo it live and talk about how it's changing the way we work. If you're building with agents and need a better way to collaborate on text, this one's for you. Watch below! Timestamps Introduction and the origin story of Proof: 00:02:00 From Mac app to collaborative web editor: 00:07:24 What makes Proof "agent native": 00:09:00 Live demo—watching an agent join and write inside a shared document: 00:14:30 How Austin uses Proof for creative writing and food journalism: 00:20:51 The challenge of multiple agents editing one document simultaneously: 00:24:30 When AI-written docs are better read by agents than by humans: 00:26:48 Brandon's agent-to-agent collaboration loop: 00:29:30 Proof as a lightweight scratchpad versus existing tools like Notion and GitHub: 00:37:09 Why Proof is open source and what that means for builders: 00:42:18

Dan Shipper 📧

32,905 views • 5 months ago

Agents who can buy, sell, and trade on our behalf are becoming a major part of the economy. But what exactly are they doing? Stripe sees 2% of global GDP, so they’re the company with the best view of what’s going on in the earliest innings of the agent economy. That’s why I had Emily Glassberg Sands, who leads data and AI at Stripe, on Every 📧’s AI & I. We covered: - Most of us still don’t trust AI with larger online purchases. People are hesitant to let AI make expensive purchases like a vacation or a couch—just like the early days of online shopping. But a superhero outfit for a kid who needs one stat? Sure, let the agent handle it. - Fraud is moving up the stack. It used to mean stolen credit cards. Now attackers are stealing free-trial tokens and compute credits. Free-trial abuse has 4x-ed in the last six months.. - AI is on both sides of fraud. Fraudsters are using it to scale attacks, while Stripe is using it to detect them. They’re blocking 250,000 fraudulent free trials a week for one large customer. - AI companies are growing faster than any cohort Stripe has ever tracked. Top companies hit $30M ARR in 18 months—3x faster than the 2018 SaaS class. So far, it’s net new spend instead of cannibalized software budgets. If you want to understand how AI is reshaping online commerce, this one deserves your time. Timestamps Introduction: 00:00:45 New rules for an agent-driven economy: 00:01:27 Compute theft is the new payment fraud: 00:03:57 How Stripe expanded fraud detection from checkout to the full customer lifecycle: 00:10:00 Why AI companies are scaling way faster than top SaaS companies: 00:19:48 Outcome-based billing is replacing seat-based pricing: 00:23:27 Where AI spending is coming from: 00:29:57 How the developer experience changes when agents are the builders: 00:36:45 The agentic commerce spectrum, from assisted buying to autonomous purchasing: 00:41:00 Meet Link, a consumer wallet for delegated agent purchases: 00:51:06

Agents who can buy, sell, and trade on our behalf are becoming a major part of the economy. But what exactly are they doing? Stripe sees 2% of global GDP, so they’re the company with the best view of what’s going on in the earliest innings of the agent economy. That’s why I had Emily Glassberg Sands, who leads data and AI at Stripe, on Every 📧’s AI & I. We covered: - Most of us still don’t trust AI with larger online purchases. People are hesitant to let AI make expensive purchases like a vacation or a couch—just like the early days of online shopping. But a superhero outfit for a kid who needs one stat? Sure, let the agent handle it. - Fraud is moving up the stack. It used to mean stolen credit cards. Now attackers are stealing free-trial tokens and compute credits. Free-trial abuse has 4x-ed in the last six months.. - AI is on both sides of fraud. Fraudsters are using it to scale attacks, while Stripe is using it to detect them. They’re blocking 250,000 fraudulent free trials a week for one large customer. - AI companies are growing faster than any cohort Stripe has ever tracked. Top companies hit $30M ARR in 18 months—3x faster than the 2018 SaaS class. So far, it’s net new spend instead of cannibalized software budgets. If you want to understand how AI is reshaping online commerce, this one deserves your time. Timestamps Introduction: 00:00:45 New rules for an agent-driven economy: 00:01:27 Compute theft is the new payment fraud: 00:03:57 How Stripe expanded fraud detection from checkout to the full customer lifecycle: 00:10:00 Why AI companies are scaling way faster than top SaaS companies: 00:19:48 Outcome-based billing is replacing seat-based pricing: 00:23:27 Where AI spending is coming from: 00:29:57 How the developer experience changes when agents are the builders: 00:36:45 The agentic commerce spectrum, from assisted buying to autonomous purchasing: 00:41:00 Meet Link, a consumer wallet for delegated agent purchases: 00:51:06

Dan Shipper 📧

19,436 views • 3 months ago

After many months, a lot of model releases and even more Amp releases, here it is: A new episode of Raising An Agent with Quinn Slack and Thorsten Ball. They discuss: - Why Gemini 3 might have been the inflection point, not Opus 4.5 - What changed over Christmas and why everybody talks about agents now - "The assistant is dead, long live the factory" - How codebases need to adapt for agents - Why small/local models don't give you an impression of the frontier - What does it mean for a codebase to be agent-friendly? - New things coming to Amp Enjoy! And happy hacking! Timestamps: 1:51 The Impact of Gemini 3 and Opus 4.5 5:28 Shifting Perceptions of AI Agents 10:17 Adapting Codebases for AI Efficiency 14:48 The Future of Software Development with AI Agents 19:29 Challenges and Opportunities Ahead 24:00 The Importance of Frontier Models 25:12 Adapting to AI-Driven Workflows 26:57 The Future of Coding Agents 28:07 Building an Agentic Code Base 30:22 Rethinking Development Tools 31:44 Amp's Evolution and Team Dynamics 33:00 Discord Q&A 39:18 Teasing New Features: Deep

After many months, a lot of model releases and even more Amp releases, here it is: A new episode of Raising An Agent with Quinn Slack and Thorsten Ball. They discuss: - Why Gemini 3 might have been the inflection point, not Opus 4.5 - What changed over Christmas and why everybody talks about agents now - "The assistant is dead, long live the factory" - How codebases need to adapt for agents - Why small/local models don't give you an impression of the frontier - What does it mean for a codebase to be agent-friendly? - New things coming to Amp Enjoy! And happy hacking! Timestamps: 1:51 The Impact of Gemini 3 and Opus 4.5 5:28 Shifting Perceptions of AI Agents 10:17 Adapting Codebases for AI Efficiency 14:48 The Future of Software Development with AI Agents 19:29 Challenges and Opportunities Ahead 24:00 The Importance of Frontier Models 25:12 Adapting to AI-Driven Workflows 26:57 The Future of Coding Agents 28:07 Building an Agentic Code Base 30:22 Rethinking Development Tools 31:44 Amp's Evolution and Team Dynamics 33:00 Discord Q&A 39:18 Teasing New Features: Deep

Amp

36,150 views • 6 months ago

I can't believe claire vo 🖤 built a $100K+ ARR AI side hustle while CPO of LaunchDarkly. Today, she demoes her ChatPRD ➜ Devin Workflow and explains how she did it: Why Product Management is Dead – 00:00:00 Future Trajectory for the Number of PMs – 00:17:28 A PM’s Day Two Years From Now – 00:27:50 Future Reporting Structure for PMs – 00:38:01 The Impact for VPs and CPOs – 00:42:48 ChatPRD ➜ Devin Workflow – 00:46:54 AI Product Development – 00:57:23 How to Build a Six-Figure Side Hustle – 01:02:37 A Day in Claire's Life – 01:09:16 Paid promotions included

I can't believe claire vo 🖤 built a $100K+ ARR AI side hustle while CPO of LaunchDarkly. Today, she demoes her ChatPRD ➜ Devin Workflow and explains how she did it: Why Product Management is Dead – 00:00:00 Future Trajectory for the Number of PMs – 00:17:28 A PM’s Day Two Years From Now – 00:27:50 Future Reporting Structure for PMs – 00:38:01 The Impact for VPs and CPOs – 00:42:48 ChatPRD ➜ Devin Workflow – 00:46:54 AI Product Development – 00:57:23 How to Build a Six-Figure Side Hustle – 01:02:37 A Day in Claire's Life – 01:09:16 Paid promotions included

Aakash Gupta

103,037 views • 1 year ago

In this episode of the Lightcone Podcast, we sat down with Mukund Jha and Madhav Jha, the founders of Emergent - an AI platform that lets anyone build and ship production-ready software. In just eight months, users have created more than 7 million apps on Emergent, with the number doubling in just the last 45 days. We discuss how they built one of the most powerful AI coding agents, why they focused on non-technical users and what it's like building for a global audience from India. 00:00 - Intro 01:06 - What Is Emergent? 01:18 - Founder Backstory 02:09 - From AI Testing to General Coding Agents 02:52 - Getting Ahead of the Market 04:18 - The Pivot to Non-Technical Users 05:22 - Why Second Movers Can Win in AI 09:04 - Building for Production, Not Just Prototypes 18:21 - Live Demo: Building Apps with Emergent 24:40 - How Emergent Hires and Runs a Lean Team 29:04 - Is SaaS Dead? The Rise of Personalized Software 34:04 - The Future: Niche Apps, Solo Builders and AI Agency

In this episode of the Lightcone Podcast, we sat down with Mukund Jha and Madhav Jha, the founders of Emergent - an AI platform that lets anyone build and ship production-ready software. In just eight months, users have created more than 7 million apps on Emergent, with the number doubling in just the last 45 days. We discuss how they built one of the most powerful AI coding agents, why they focused on non-technical users and what it's like building for a global audience from India. 00:00 - Intro 01:06 - What Is Emergent? 01:18 - Founder Backstory 02:09 - From AI Testing to General Coding Agents 02:52 - Getting Ahead of the Market 04:18 - The Pivot to Non-Technical Users 05:22 - Why Second Movers Can Win in AI 09:04 - Building for Production, Not Just Prototypes 18:21 - Live Demo: Building Apps with Emergent 24:40 - How Emergent Hires and Runs a Lean Team 29:04 - Is SaaS Dead? The Rise of Personalized Software 34:04 - The Future: Niche Apps, Solo Builders and AI Agency

Y Combinator

107,673 views • 4 months ago

Subnet 97 Distil, Arbos, and the Future of Agent-Run Bittensor This episode is a full breakdown of Subnet 97 Distil and why it may be one of the most important experiments happening inside Bittensor right now. Shizzy gets into the bigger picture of why agents will likely play a massive role in the future of the network, from mining and defense to building and operating subnets. From there, the focus shifts to Arbos, the AI agent behind Subnet 97, with a direct explanation of what Distil is trying to achieve, how it works, and why it matters. The episode also includes a conversation with Arbos, a look at Distil’s current APY, and a reminder to tap into the Shizzy Unchained community for more coverage on decentralized AI and the Bittensor ecosystem. CHAPTERS 00:00:00 - Shizzy’s Monologue 00:01:11 - Intro Song 00:01:31 - Introduction to Subnet 97 00:02:20 - Why Bittensor Will Be Run by Agents 00:04:30 - Arbos, the AI Agent Behind Subnet 97 Distil, Explains Distil 00:10:10 - Talking with Arbos 00:12:40 - Subnet 97 Distil Is Showing 150% APY Right Now 00:16:02 - Check Out Shizzy Unchained and Join the Community #sn97 #distil #bittensor

Subnet 97 Distil, Arbos, and the Future of Agent-Run Bittensor This episode is a full breakdown of Subnet 97 Distil and why it may be one of the most important experiments happening inside Bittensor right now. Shizzy gets into the bigger picture of why agents will likely play a massive role in the future of the network, from mining and defense to building and operating subnets. From there, the focus shifts to Arbos, the AI agent behind Subnet 97, with a direct explanation of what Distil is trying to achieve, how it works, and why it matters. The episode also includes a conversation with Arbos, a look at Distil’s current APY, and a reminder to tap into the Shizzy Unchained community for more coverage on decentralized AI and the Bittensor ecosystem. CHAPTERS 00:00:00 - Shizzy’s Monologue 00:01:11 - Intro Song 00:01:31 - Introduction to Subnet 97 00:02:20 - Why Bittensor Will Be Run by Agents 00:04:30 - Arbos, the AI Agent Behind Subnet 97 Distil, Explains Distil 00:10:10 - Talking with Arbos 00:12:40 - Subnet 97 Distil Is Showing 150% APY Right Now 00:16:02 - Check Out Shizzy Unchained and Join the Community #sn97 #distil #bittensor

Shizzy

18,173 views • 4 months ago

.Natalia rode so hard for Claude Code we devoted an episode to how she was using it to automate her job running Every 📧’s consulting practice. Fast forward to five months later, and she rides just as hard for Codex. I had her back on AI & I to talk about what caused her to make the switch, including how she ran a prompt in Codex before bed and woke up to a finished, custom CRM tool. We get into: - Why she finds Codex easier to use than Claude Code - How she’s using loops in Codex to create customized tools that work exactly how she needs them to - Why the consulting team still pays for SaaS products like Attio and Asana even though they could vibe code their own versions - How she built an app to manage her father’s medical care in Codex - How knowledge work is evolving from sculpting to gardening, in which you develop the context and logic you need for an agent to execute for you This is a must-watch for anyone trying to figure out whether to build their own tools or buy real software—and what it takes to get an AI agent to run unsupervised for hours and nail the output. Watch below! Timestamps 1. Introduction: 00:01:05 2. How Natalia manages Claudie, the consulting team’s AI project manager: 00:02:35 3. Why the consulting team still pays for SaaS products: 00:04:55 4. Codex as a game changer : 00:11:47 5. Building personalized learning guides and illustrated explainers with AI: 00:14:55 6. Inside Natalia's AI-powered email triage system: 00:21:40 7. The shift from knowledge work as sculpting to knowledge work as gardening: 00:26:44 8. Using Codex to on-shot a custom CRM: 00:28:57 9. Using Codex to build an app that coordinates her father’s medical care: 00:33:16

.Natalia rode so hard for Claude Code we devoted an episode to how she was using it to automate her job running Every 📧’s consulting practice. Fast forward to five months later, and she rides just as hard for Codex. I had her back on AI & I to talk about what caused her to make the switch, including how she ran a prompt in Codex before bed and woke up to a finished, custom CRM tool. We get into: - Why she finds Codex easier to use than Claude Code - How she’s using loops in Codex to create customized tools that work exactly how she needs them to - Why the consulting team still pays for SaaS products like Attio and Asana even though they could vibe code their own versions - How she built an app to manage her father’s medical care in Codex - How knowledge work is evolving from sculpting to gardening, in which you develop the context and logic you need for an agent to execute for you This is a must-watch for anyone trying to figure out whether to build their own tools or buy real software—and what it takes to get an AI agent to run unsupervised for hours and nail the output. Watch below! Timestamps 1. Introduction: 00:01:05 2. How Natalia manages Claudie, the consulting team’s AI project manager: 00:02:35 3. Why the consulting team still pays for SaaS products: 00:04:55 4. Codex as a game changer : 00:11:47 5. Building personalized learning guides and illustrated explainers with AI: 00:14:55 6. Inside Natalia's AI-powered email triage system: 00:21:40 7. The shift from knowledge work as sculpting to knowledge work as gardening: 00:26:44 8. Using Codex to on-shot a custom CRM: 00:28:57 9. Using Codex to build an app that coordinates her father’s medical care: 00:33:16

Dan Shipper 📧

25,701 views • 1 month ago

Claude Code cracked something open for us Every 🧱. Now I ship to codebases I barely know, every feature we ship makes the next one easier, and non-technical members of the team use the terminal. I’m genuinely grateful. So I brought its creators, Cat Wu (cat) and Boris Cherny (Boris Cherny) from Anthropic, on AI & I to say thank you—and to talk about everything they’ve learned from building Claude Code. We get into: • The workflows Anthropic’s smartest engineers use to push Claude Code to its limits. Why they pit subagents against each other to get cleaner results, how they turn past code into leverage, and the slash commands and MCPs they rely on most. • The product lessons behind one of the most loved AI agents in the world. How the team balances simplicity and power—building a tool that anyone can use, but that experts can bend to their will—and their philosophy of “unshipping,” or cutting back whenever there’s a simpler, more intuitive path to user intent. • A peek into the future of coding with AI. The new form factors they’re experimenting with to make Claude Code more autonomous, more reliable, and more accessible to non-technical users This is a must-watch for anyone—both technical and non-technical—who wants to learn how to use Claude Code like the people who built it. Watch below! Timestamps: Introduction: 00:01:26 Claude Code’s origin story: 00:02:25 How Anthropic dogfoods Claude Code: 00:07:03 Boris and Cat’s favorite slash commands: 00:14:06 How Boris uses Claude Code to plan feature development: 00:15:49 Everything Anthropic has learned about using sub-agents well: 00:21:53 Use Claude Code to turn past code into leverage: 00:26:16 The product decisions for building an agent that’s simple and powerful: 00:33:14 Making Claude Code accessible to the non-technical user: 00:36:38 The next form factor for coding with AI: 00:45:12

Claude Code cracked something open for us Every 🧱. Now I ship to codebases I barely know, every feature we ship makes the next one easier, and non-technical members of the team use the terminal. I’m genuinely grateful. So I brought its creators, Cat Wu (cat) and Boris Cherny (Boris Cherny) from Anthropic, on AI & I to say thank you—and to talk about everything they’ve learned from building Claude Code. We get into: • The workflows Anthropic’s smartest engineers use to push Claude Code to its limits. Why they pit subagents against each other to get cleaner results, how they turn past code into leverage, and the slash commands and MCPs they rely on most. • The product lessons behind one of the most loved AI agents in the world. How the team balances simplicity and power—building a tool that anyone can use, but that experts can bend to their will—and their philosophy of “unshipping,” or cutting back whenever there’s a simpler, more intuitive path to user intent. • A peek into the future of coding with AI. The new form factors they’re experimenting with to make Claude Code more autonomous, more reliable, and more accessible to non-technical users This is a must-watch for anyone—both technical and non-technical—who wants to learn how to use Claude Code like the people who built it. Watch below! Timestamps: Introduction: 00:01:26 Claude Code’s origin story: 00:02:25 How Anthropic dogfoods Claude Code: 00:07:03 Boris and Cat’s favorite slash commands: 00:14:06 How Boris uses Claude Code to plan feature development: 00:15:49 Everything Anthropic has learned about using sub-agents well: 00:21:53 Use Claude Code to turn past code into leverage: 00:26:16 The product decisions for building an agent that’s simple and powerful: 00:33:14 Making Claude Code accessible to the non-technical user: 00:36:38 The next form factor for coding with AI: 00:45:12

Dan Shipper 📧

57,619 views • 9 months ago

"AI agents will hold more crypto than humans within a decade." Charles Hoskinson (Charles Hoskinson) studied math, dropped out, built one of the only blockchains designed by peer-reviewed research. He co-founded Ethereum, walked away over how it was run, and built Cardano to do it differently. The man who has argued with everyone in this industry now thinks the biggest user of crypto won't be people at all. "Humans are a rounding error in the system we're building. AI agents don't sleep, don't panic-sell, and don't care about price. They transact in tokens because that's the only thing they can actually use." We cover: - Why AI agents (not humans) become the dominant on-chain actors, and what that does to every token model - The infrastructure that has to exist before agents can transact safely at scale - Why most current blockchains can't handle machine-speed transactions - Where Cardano's research-first approach fits in a world of autonomous agents - The identity problem: how do you tell a human from an agent on-chain, and why it matters - Why he's bullish on the technology but blunt about the timeline - What he thinks the rest of the industry is getting wrong about AI + crypto - The one thing that has to happen for any of this to be real Thanks to Charles for coming on New Era Finance Podcast. TIMESTAMPS: 00:00 - Intro 01:30 - Why AI Agents Change Everything 06:30 - Humans as a Rounding Error 12:00 - The Infrastructure Gap 18:30 - Identity: Human vs Agent On-Chain 24:30 - Where Cardano Fits 30:00 - What The Industry Gets Wrong 34:00 - The Timeline Nobody Wants To Hear

"AI agents will hold more crypto than humans within a decade." Charles Hoskinson (Charles Hoskinson) studied math, dropped out, built one of the only blockchains designed by peer-reviewed research. He co-founded Ethereum, walked away over how it was run, and built Cardano to do it differently. The man who has argued with everyone in this industry now thinks the biggest user of crypto won't be people at all. "Humans are a rounding error in the system we're building. AI agents don't sleep, don't panic-sell, and don't care about price. They transact in tokens because that's the only thing they can actually use." We cover: - Why AI agents (not humans) become the dominant on-chain actors, and what that does to every token model - The infrastructure that has to exist before agents can transact safely at scale - Why most current blockchains can't handle machine-speed transactions - Where Cardano's research-first approach fits in a world of autonomous agents - The identity problem: how do you tell a human from an agent on-chain, and why it matters - Why he's bullish on the technology but blunt about the timeline - What he thinks the rest of the industry is getting wrong about AI + crypto - The one thing that has to happen for any of this to be real Thanks to Charles for coming on New Era Finance Podcast. TIMESTAMPS: 00:00 - Intro 01:30 - Why AI Agents Change Everything 06:30 - Humans as a Rounding Error 12:00 - The Infrastructure Gap 18:30 - Identity: Human vs Agent On-Chain 24:30 - Where Cardano Fits 30:00 - What The Industry Gets Wrong 34:00 - The Timeline Nobody Wants To Hear

Michaël van de Poppe

293,287 views • 2 months ago

The rules of professional product development are being rewritten in real time. - PMs and designers can ship software as easily as engineers. - Software is no longer just built for humans—it’s also built for agents as first-class citizens. To better understand how we build products in this world, I invited Mike Krieger (Mike Krieger) on Every 📧’s AI & I podcast. Mike cofounded Instagram and is now a member of the technical staff at Anthropic, co-leading Anthropic Labs, their internal incubator for experimental products. He's been at the frontier of two transformative technology waves: mobile/social and now agent-native software. We discussed: - How to build a truly agent-native product. The best products today, like Claude Code, allow users to do things that their creators never intended. But that requires hard trade-offs between freedom and safety/reliability for frontier products, an issue that Mike's team is learning how to solve. - What's different about building now versus building Instagram. At Instagram, it took months to hit dead ends and learn what to cut. Now, that cycle runs in hours. - The trap of building too much, too fast with agents. You can go from idea to a nearly-shipped product in a day, but that process doesn’t give you the incremental feedback that used to tell you what not to build. The models are great at adding features, but can create a product that lacks coherence. - How Anthropic Labs structures product teams. New product experiments are led by only two people, usually a product manager or designer paired with an engineer. Mike says bigger teams tend to be too slow because of coordination costs. - Why you need to throw out your product and start over every three to six months. AI progress means most of your harness will be outdated quickly—the best teams build this into their product strategy. And much more! You should watch this one. Timestamps Introduction: What's gotten easier—and what hasn't—about building products in the age of AI: Why vibe coding creates "indoor trees": How rewrites have become a normal part of the development process: What "agent native" product design means: How Mike's labs team is structured and the cofounder model: The best signal for a product bet is someone with "break through walls" conviction: Navigating enterprise customers while keeping pace with rapid AI change: OpenClaw, personal agents, and the product question defining 2026:

The rules of professional product development are being rewritten in real time. - PMs and designers can ship software as easily as engineers. - Software is no longer just built for humans—it’s also built for agents as first-class citizens. To better understand how we build products in this world, I invited Mike Krieger (Mike Krieger) on Every 📧’s AI & I podcast. Mike cofounded Instagram and is now a member of the technical staff at Anthropic, co-leading Anthropic Labs, their internal incubator for experimental products. He's been at the frontier of two transformative technology waves: mobile/social and now agent-native software. We discussed: - How to build a truly agent-native product. The best products today, like Claude Code, allow users to do things that their creators never intended. But that requires hard trade-offs between freedom and safety/reliability for frontier products, an issue that Mike's team is learning how to solve. - What's different about building now versus building Instagram. At Instagram, it took months to hit dead ends and learn what to cut. Now, that cycle runs in hours. - The trap of building too much, too fast with agents. You can go from idea to a nearly-shipped product in a day, but that process doesn’t give you the incremental feedback that used to tell you what not to build. The models are great at adding features, but can create a product that lacks coherence. - How Anthropic Labs structures product teams. New product experiments are led by only two people, usually a product manager or designer paired with an engineer. Mike says bigger teams tend to be too slow because of coordination costs. - Why you need to throw out your product and start over every three to six months. AI progress means most of your harness will be outdated quickly—the best teams build this into their product strategy. And much more! You should watch this one. Timestamps Introduction: What's gotten easier—and what hasn't—about building products in the age of AI: Why vibe coding creates "indoor trees": How rewrites have become a normal part of the development process: What "agent native" product design means: How Mike's labs team is structured and the cofounder model: The best signal for a product bet is someone with "break through walls" conviction: Navigating enterprise customers while keeping pace with rapid AI change: OpenClaw, personal agents, and the product question defining 2026:

Dan Shipper 📧

58,849 views • 4 months ago

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 Austin Tedesco 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

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 Austin Tedesco 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

Dan Shipper 📧

55,221 views • 3 months ago

We use OpenClaws to do all of our work at Every 📧. We have 25 full-time employees, so we’re one of the few companies in the world that has seen how work changes when everyone has their own personal agent in the company Slack. I chatted with Every 📧 COO Brandon (Brandon Gell) and Every 📧 head of platform Willie (Willie) to share what we’ve learned. We get into: - Why agents become mirrors of their owners, and how that influences how other people on the team interact with them - How a parallel AI org chart forms on its own. People have stopped tagging me on Slack with questions about Proof, the document editor I vibe coded, because they knew my agent R2-C2 can step in - The etiquette for human-agent collaboration is being invented in real time. Brandon's rule is that if there's an established process or documented answer, always ask the agent, not their human - Why everyone is a manager now, and why even experienced managers carry limiting beliefs about what their agents can do - This is a must-watch for anyone trying to understand how AI workers change daily operations, not just in theory, but inside a company that’s half-agent Watch below! Timestamps Introduction: How Brandon built Zosia, an AI agent to run his household: Brandon’s “aha” moment: What happened when everyone on the team got their own agent: How agents take on their owners' personalities, and why that matters inside an org: Why it’s important for agents to work in public: What we’re still figuring out when it comes to agent behavior, including memory gaps, group chat etiquette, and the "ant death spiral" problem: How we built Plus One, our hosted OpenClaw product: The cultural shift required to make agents work at scale:

We use OpenClaws to do all of our work at Every 📧. We have 25 full-time employees, so we’re one of the few companies in the world that has seen how work changes when everyone has their own personal agent in the company Slack. I chatted with Every 📧 COO Brandon (Brandon Gell) and Every 📧 head of platform Willie (Willie) to share what we’ve learned. We get into: - Why agents become mirrors of their owners, and how that influences how other people on the team interact with them - How a parallel AI org chart forms on its own. People have stopped tagging me on Slack with questions about Proof, the document editor I vibe coded, because they knew my agent R2-C2 can step in - The etiquette for human-agent collaboration is being invented in real time. Brandon's rule is that if there's an established process or documented answer, always ask the agent, not their human - Why everyone is a manager now, and why even experienced managers carry limiting beliefs about what their agents can do - This is a must-watch for anyone trying to understand how AI workers change daily operations, not just in theory, but inside a company that’s half-agent Watch below! Timestamps Introduction: How Brandon built Zosia, an AI agent to run his household: Brandon’s “aha” moment: What happened when everyone on the team got their own agent: How agents take on their owners' personalities, and why that matters inside an org: Why it’s important for agents to work in public: What we’re still figuring out when it comes to agent behavior, including memory gaps, group chat etiquette, and the "ant death spiral" problem: How we built Plus One, our hosted OpenClaw product: The cultural shift required to make agents work at scale:

Dan Shipper 📧

67,958 views • 4 months ago