Who’s building with AI, and wants help? Join me + @simpsoka from OpenAI Codex, product, coding stuff :) Ask us anything! nitter.net/i/spaces/1oKMvRPBjoNGQ

been talking and hearing a bunch of creators talk about agentic coding and the common theme i heard is everyone (including myself) hasn't had this much fun and felt this much joy with it feels like being able to build anything you want without the grind of the boring 90% is opening so many alleys of joy

17 yo asked what makes a good founder. I said being good at building stuff and being sufficiently fierce. That's about it.

Marcus Aurelius wrote this over 1800 years ago: “When you arise in the morning think of what a privilege it is to be alive, to think, to enjoy, to love.”

True dat

We're recording round two of this on Monday! While the calendar says it's only been a year, it feels more like twenty since we've entered the age of agents.

How to make people care about your startup lennysnewsletter.com/p/how-t…

Every startup should have a daily markdown file called "what_the_market_is_telling_us.md" It updates every morning from the places where customer truth already lives: 1. Stripe for who pays, upgrades, downgrades, and churns 2. PostHog for what people actually do in the product 3. Intercom or Plain for support tickets/complaints 4. Granola or Gmeet transcriptions for sales calls/ customer interviews 5. HubSpot or Salesforce for CRM notes/lost deal reasons 6. Linear, Jira, or GitHub Issues for bugs and feature requests etc 7. Ideabrowser MCP for outside market signal: startup ideas, trend reports, social/search demand, AI research reports, and builder prompts that show what people are starting to want before it shows up in your own customer data. Basically, the file should notice what changed in the business this week and not just be this summary of here’s what happened (which I think a lot of people have their agents do). Why this is valuable: 1. Maybe new buyers are using different words than they were a month ago. 2. Maybe trial users are getting stuck in the same place. 3. Maybe upgraded customers all touched one feature right before they paid. 4. Maybe churned customers keep mentioning setup confusion. 5. Maybe sales calls are suddenly losing to a competitor you used to beat. 6. Maybe support tickets are revealing a workflow your product accidentally became responsible for. You get the point. The fastest way to PMF is understanding customers better than anyone else, and the highest signal customer insight is usually a change in behavior. So I’d have the agent update the file every morning with the pattern it found, the receipts behind it, and the product or GTM decision it might affect. For example: “3 customers who churned this week all mentioned setup confusion, and 2 of them never invited a teammate. This looks more like an activation problem than a pricing problem, so I’d look at team invite and onboarding before building another analytics feature.” A little helpful tip for all those out there looking to get more from their LLMs.

Fable 5 is back.

We’re shipping 2 major releases:
 🔘 Nano Banana 2 Lite: our fastest and cheapest Gemini Image model 🔘 Gemini Omni Flash: now available via the Gemini API and in @GoogleAIStudio to help developers generate and edit high-quality videos.

Today we're announcing Live Studio, a brand new livestreaming command center on X X is where everything is happening now. So we're launching the best tools for pro streamers to go live, connect with their followers & manage their streams Check it out on 𝕏.com in Creator Studio

Good marketing is finding different ways to tell the truth.

Startups: what’s your best feature? Share links, curious to see.

RT @levelsio: I think the challenge is that everyone can now build apps But 1) almost nobody has distribution (like an audience), or 2)…

Massive output uptick due to agentic AI. Complete flat adoption.

pitch me your company in 1 word.

Anyone who surfed the early web between 1995-2010. What’s the one website/app you still think about?

Today!

Some tips to help agents understand your codebase: 1. The source code either needs to be the source of truth, or have something legible as a path to the source. For example, if marketing site content is actually stored in a CMS, you need to either delete the CMS and move that content into code, or make the CMS legible through and MCP, CLI, or skill: leerob.com/agents 2. Agents need to be able to verify their work. This includes but is not limited to: using a typed language, having high-quality and fast tests, having a well-configured linter: nitter.net/leerob/status/20263694… 3. You need to have a concise and effective AGENTS.md file, which is included in every message to your agent. Models are quite good now, so some things you can omit as the models know them. You don’t need to say the tests live inside /tests for example. It’s worth asking the models to find things in your codebase and making sure they’re named what the models might expect, otherwise consider refactoring: cursor.com/learn/customizing… 4. Set up automations which give you suggestions for refactoring code, catching security issues which may have slipped through code review, and optionally continuous documentation of the codebase. You can effectively create a self-driving codebase which gets better while you sleep: cursor.com/blog/security-age…

Watch me control my computer with just my voice. This is the future of operating systems. No hands. GPT-Realtime 2.0 is very, very underrated. Demo:

The only thing worse than having the CEO knee-deep in building stuff with AI is not having the CEO knee-deep in building stuff with AI.