Press Space to continue
Curated tech Twitter/X posts on AI, startups, and product development—signal without the doomscroll, updated on weekdays.
Press Space to continue
Press Space to continue
SpaceXSI's @mattyp reveals why Grok Bot users keep creating an AI chief of staff to manage their other bots: "What we found is that almost everyone had this usage pattern where they’re creating a chief of staff or a single point bot that would then manage these other bots." "We designed Grok Bot to feel like an AI companion such that you’re creating these little coworkers. But having one bot that serves as an inbox or a catchall is something that most people do, and we’ve started to build it…
FULL INTERVIEW: SpaceXSI's @mattyp says agents now build in an instant what used to take him a whole weekend. He still doesn't think software engineers will ever go away, because the "model doesn't really have empathy for people." @mattyp works on @bot at @spacexai. He joined @theojaffee to break down why chat might replace most apps, how Grok Bot keeps your passwords hidden from the bot itself, and what agents still can't do: 00:56 why have multiple Grok Bots instead of one 03:52 why chat might be the only UI you need 06:31 why chat is just the first form factor for agents 07:43 how Grok Bot handles security 09:22 the Gmail alerts from a VM in Korea 10:27 treat your agent like a new hire 11:23 the cantaloupe problem with AI memory 13:45 why software engineers won't go away 15:07 where models still fall short 17:49 how SpaceXSI uses Grok Bot internally 19:33 working for @elonmusk after Cursor 21:05 what comes after the IDE