Minglei (@rae1101x) “if you want to automerge thousands of pull requests , this is how she does it (v” — TopicDigg

if you want to automerge thousands of pull requests , this is how she does it (via @poteto). 809 in june. 10,926 in october. merged prs a month that touch the grok bot team's code. i went through her posts and put the setup in one place. every pr still gets an agentic risk review plus bugbot. low- and medium-risk ones automerge. only higher-risk ones get a person. day to day, in her words, it's just grok bot and cursor projects. she used to have more cursor automations and replaced them with slack bots that have routines. she works on many streams in parallel with pstack: perf, bug fixes, agent-friendly refactors, her own skills, features, ui polish, the harness, release and observability. not from sitting in a review inbox. she's said the speed gains come from parallelizing. a single chat can take longer because of verification. she handholds it less, so she can run several large projects at once. the real setup is in the codebase and the checks around it. she treats the codebase as memory. every agent mistake needs to turn into a constraint. her team built their own framework for grok bot so some anti-patterns become hard to write at all. agents have to verify their own work. they run the app, and can sometimes model it in tla+. they produce screenshots or video that are easier to check than the whole pr. formal verification skills and ordinary run-and-debug skills work together. she calls this an inverse pyramid. push as much as you can into determinism (fuzzing, property tests, formal and runtime verification, stricter languages) instead of spinning up more agent swarms. in her oct 6 post, she tells sandcastle, a grok team bot, to cut. it runs a buildkite dry run, dms every pr author (they can object), kicks the build, and watches it. then it starts a fuzz swarm: usually 10+ agents on grok 4.7 xhigh, some directed, some chaos monkey, using their verification skills and feature map. when something is high priority, she tells sandcastle to @ mention poteto, her engineer bot, which then spins up a cursor project to triage and fix. her team ships a new stable version of the client at least once a day. that's a lot of machinery under "just grok bot and cursor projects."