SpaceXAI Engineer Lauren Tan: Scheduling Bots Are More Expensive Than Writing Code

SpaceXAI engineer Lauren Tan stated during a one-hour Grok Bot seminar that she operates over twenty agents simultaneously: one chief, three managers, and more than ten executors. She mentioned that the most valuable bot hardly writes code; it remembers what the other members are doing to avoid duplicating tasks, with the goal of freeing engineers from serial acceptance processes.

Tan previously worked as an engineering manager at Netflix and contributed to the React Compiler at Meta, later joining SpaceXAI through Cursor, where she is responsible for Grok Bot. She uses the open-source skill package pstack to equip agents with validation capabilities: running applications, capturing CPU and heap snapshots, and opening simulators for interaction, rather than just generating patches. The architecture, nicknamed Dune, modifies the repository to be agent-friendly: rules are written as lint and CI, prohibiting easily abused patterns, and failures turn the pipeline red. She reported handling over 3,000 PRs in five months, with over a thousand in a single month, and once woke up to find about twenty PRs merged into the main branch, stating she rarely reads code anymore, focusing instead on evidence.

The live demonstration involved multiple agents monitoring PRs and CI, with a Slack duty bot reproducing defects, and standards being written into reusable skills rather than one-off chats. Grok Bot provides each bot with independent cloud computers, identities, and routine tasks, capable of launching Cursor cloud agents, submitting PRs, recordings, and screenshots upon completion. She likened the agents to forgetful yet teachable newcomers: they rely not on a single long prompt but on rules, skills, tools, and long-term memory. If private and shared memories are not separated, tone drifts, old mistakes recur, and previously fixed defects resurface after a few weeks. She compared the high token costs of early restructuring and constraints to the cost of hiring another person to do the same organization work.

The product is developed by a small team over about four weeks for an internal version, followed by about three weeks for public release, with Grok Bot also heavily used for its own development. During the same period, duty agents appeared to monitor Datadog and PagerDuty, front-end and back-end agents mutually subscribing to interfaces, and QA supplementing end-to-end testing. She noted that most users still treat the bot as a chat window, with only a few using it according to job roles.

In market mechanisms, buyers aim to replace junior engineering teams with agent teams, while sellers provide Grok Bot with cloud computers and skill layers; the driving forces are validation and memory, rather than just adding another chat window. Funding shifts from hiring and duty hours to tokens, cloud hosts, and skill maintenance. Beneficiaries are individual super-productive engineers who can transform architectures to automatically reject bad patches, while those under pressure are agent tools that only sell conversations without memory management and CI hard constraints, as well as mid-level management bandwidth that still expands based on headcount.

Source: Public Information