Engineering
Grok Bot plans, Codex opens the PR, you only merge
Coding on Grok Bot burns tokens; the real bottleneck is reading PRs anyway.
What hurt
@SergioNavarroAI runs side projects with a split: Grok Bot agents know the server and write a change prompt (what / where / done-looks-like); he pastes that into Codex to write code and open the GitHub PR; he is the only human in the loop on purpose — review and merge. Deploys go live minutes after merge with zero rollbacks so far. Tip only. Not affiliated with xAI.
What to install or create
Bot drafts the change prompt → Codex builds + PR → you review/merge → bot deploys.
Bots
No new bot. Follow the first-run steps.
Plugins
GitHub
Required
Routines
None on the first run. Watch one manual pass first.
The prompt
This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.
First run
- 1Read the thread starting at https://x.com/SergioNavarroAI/status/2116308462292566479 (credit @SergioNavarroAI).
- 2Give one Grok Bot agent enough server/repo context to draft change prompts.
- 3For each change, require what / where / done-looks-like in the prompt before any coding.
- 4Paste that prompt into Codex (or similar) so the PR is opened outside your Grok Bot token budget.
- 5Stay the only merge approver; let deploy run only after your review.
Approval fence
Merge and production deploys wait for your review; no silent pushes.
What to tweak
Steal plan-on-Grok / build-on-Codex / human-only-on-PR-review.
Source
Sergio Navarro @SergioNavarroAI · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Pro pack
Want the full setup, not just the idea?
Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.