Overnight PR merging with Grok Bot and Opus 5.5
A field guide built from Lauren Tan's pstack shows how a one-line bedtime prompt lets Grok Bot agents write code and merge PRs overnight while Opus 5.5 makes judgment calls.
this is f*cking unreal… SpaceXAI engineer Lauren Tan (ex-Meta) types one line before bed: "/poteto-mode i'm going to bed. land the stack even if ci flakes. i want everything merged by morning." then she goes to sleep - her agents don't 11 PM: picks the playbook, writes one brief, fans out the workers 1 AM: stacks narrow PRs, one writer per chain so nobody undoes anyone 4 AM: CI flakes. one fresh build, never a retry loop. same failure twice? it reads the logs 5 AM: runs the change like a real user would, lands bottom-up, one PR at a time 7 AM: /ketchup. what landed, what's parked and why, what needs her call grok writes the code. opus 5.5 makes the judgment calls. only 4 things can wake her up: force-push, deploys, data deletion, customer messages. that's Lauren Tan (poteto). React core team, millions of lines of code at Meta, Netflix and Cursor. i went through her entire open-source pstack and turned the overnight run into one field guide + the exact prompts to paste before bed. send it to Grok Bot, Cursor or Claude Code tonight and wake up to merged PRs.
This post quotes another post: x.com/0xcarnagee/status/2090102148344262659