Try Pro free

Lightcone · 3 min · Nov 14, 2026

Slack can carry a feature from request to shipped code

Lauren Tan and colleagues used a Slack thread with a bot to prototype and ship a feature without opening Cursor.

In this episode

Full analysis
  1. 16:09Bots should earn broader access as people learn to trust them7 min
  2. 40:06Agents improve when they can run and check their own code3 min
  3. 52:17Product direction becomes the bottleneck as execution gets cheap4 min
  4. 43:54Agent review can overfit without product context6 min
  5. 22:26Slack can carry a feature from request to shipped code3 min
  6. 35:18Cheap execution shifts the bottleneck to defining goals5 min
  7. 6:26Bot roles work best when each owns a focused problem4 min
  8. 3:35Marketing teams can connect bots to operational workflows3 min
“I didn't even look at cursor for this project. I just, we did it all in the Slack thread.”
Lauren Tanat 25:04 · Lightcone
25:04

Takeaways

  1. The bot spawned a cloud agent to prototype the feature.
  2. Screenshots and video let teammates give feedback in the thread.
  3. Lauren says the feature was built end to end there.

About this segment

Lauren Tan and colleagues used a Slack thread with a bot to prototype and ship a feature without opening Cursor. Sharing screenshots and feedback in the thread shortened iteration.

Lauren Tan

Principal engineer, SpaceXAI

Created pstack and co-authored React Compiler 1.0; now builds Grok Bot's agent workflows and runs 20+ agents.

  • Garry Tan, Host · President & CEO, Y Combinator

    Co-founded Posterous and Initialized Capital, an early Coinbase backer.

  • Harj Taggar, Host · Managing partner, Y Combinator

    Co-founded Auctomatic with the Collison brothers and later Triplebyte.

  • Diana Hu, Host · Managing partner, Y Combinator

    CTO of Escher Reality; after Niantic bought it, ran AR for Pokémon GO.

  • Jared Friedman, Host · Managing partner, Y Combinator

    Co-founded Scribd, which YC funded in 2006; has advised 20+ YC unicorns.

From “The Rise Of AI Coworkers”, Nov 14, 2026. Watch the full episode

Answers “Are AI agents ready for real work?” See all 157 answers

Transcript

Transcribed by machine (Whisper) from the episode’s audio, so a word may be off here and there.

  1. 22:32

    really necessary for these companies to build trust i'm curious what is the for you lauren what is your your loop from requests in slack to pr i think when you did the presentation that had over 4 million views on your dev process you were pushing about 2 000 plus prs per month and now you're like over 4,000? Yeah. Wow, doubling is wild. So what do you do? I can show some like examples. My loop is kind of interesting now where I actually find myself talking to my Grockbots mostly on Slack and of course X as well when I'm helping like a customer or you know a Grockbot user debug something or you know give them some ideas on how to solve a problem. Here on my screen I have an example of me collaborating with my colleague, Samantha, on building out a feature together with my bot, Pateo. And, you know, basically, I kind of started with saying,

  2. 23:30

    I gave it a link to some like a video or something that I found on X. And I asked my bot, you know, what would it take for us to support a feature like this? And it went off and spawned a Cursor Cloud Agent. A Cursor Cloud Agent, you know, has its own virtual machine as well as its own computer. So you can actually run the GrokBot app on its computer and prototype and come back with videos and screenshots. And then it actually did. So This is quite powerful because now, you know, the conversation's happening in public, right?

  3. 24:04

    It's a public channel. It's a thread that anyone who's interested in this topic can join in and give feedback. The process of iterating on a feature together with someone is so much shortened by having these conversations together, you know, in like a multiplayer setting versus, you know, if it was just me going off and building it. And I could certainly come up with something, but maybe the feedback process is it comes later in the process and the loop is sort of like lengthened rather than shortened.

  4. 24:37

    And here I felt like with this particular example, the loop for us to collaborate was just so much shorter. You know, we could see the screenshots, we could see the videos right away. How often would you jump back into Cursor and like sort of complete a PR? Occasionally, I think. So not that often. I mean, you basically can stay in CropBot, like stay up here, tell it what you need, you know, sort of give it direction.

  5. 24:59

    And like as an actual employee, it's like, it's just going. Yeah, I think for us, so the reason we can sort of do this, you know, workflow. To ship the whole feature just like that. Yeah, we literally just like, I didn't even look at cursor for this project. I just, we did it all in the Slack thread. It's got 200 messages. So it was quite a long, a lot of back and forth. But we came up with something that, you know, me, Samantha, and another PM were really, like, happy with the result.

  6. 25:27

    We should ship this feature a lot faster than, you know, a longer process. And so the whole feature is built end-to-end in that one Slack thread with you and Samantha and Potato building it. I mean, basically, like, this is the gold standard for how to do it.