Engineering
Agency flow: context in Grok Bot, code in Cursor, review in PR
Mixing client context and code edits in one chat muddies both.
What hurt
Caribedevs (@cristianmock) agency agent flow: (1) Grok Bot holds client + task context; (2) Cursor agent gets only a scoped prompt + repo; (3) review happens in the PR, not in chat. Context in one place, code in another. Not affiliated with xAI.
What to install or create
Bot = context brain. Cursor = scoped code. PR = review surface.
Bots
Client context desk
Holds client/task context; hands scoped briefs to Cursor.
Plugins
GitHub
Optional
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 https://x.com/cristianmock/status/2110145621667844593 (credit @cristianmock).
- 2Keep durable client/task notes in a Grok Bot (not in the coding chat).
- 3When coding starts, hand Cursor only: scope, repo, acceptance checks.
- 4Open a PR for every change; review there, not in chat.
- 5Merge only after you approve the PR.
Approval fence
No merge without your PR review. Bot does not push production alone.
What to tweak
Steal context/code/PR split. Don't review in chat.
Source
Caribedevs @cristianmock · 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.