Repo ops overnight
One repo. One PR. A human still merges.
shared by @gippp69 ↗
How it's set up
Grok Bot plus Kimi repo ops: 2 to 3 repos by hand vs up to 300 sub-agents, a $0 PR agent, and it kills the 2am CI check, they posted. We have the tweet. We did not sit the night. $0 PR agent is what they posted, not a bill we saw. No public install.
- 01Point it at a repo you already own. Not 300 on day one.
- 02Let it watch CI and draft a PR note. You still merge.
- 032am CI check is their pain. Cap the run so it does not loop all night.
- 04$0 PR agent is their claim. You still read the diff.
- 05Write hours from your clock. Do not paste 300 as yours.
Prompt
We cannot write an honest starter prompt from what was published. Use the steps above.
How the money works
Hours you get back on CI and PRs can be hours you bill. 2 to 3 by hand vs up to 300 sub-agents and a $0 PR agent are what they posted, not a run we sat. First proof is one PR a human still merged — not 300 sub-agents copied from the tweet.
What to try first
This week: one repo you own, one CI watch or PR note, and a merge a human still does.
Watch out
- Tokens: 300 sub-agents can burn the week. Cap the run.
- Time: one checked PR beats a 2am claim you cannot show.
- Claim: Grok Bot plus Kimi repo ops, 2 to 3 repos by hand vs up to 300 sub-agents, a $0 PR agent, and killing the 2am CI check is what they posted. Not a night we sat. Not a public install.