Engineering
Outer loop, inner loop: the bot reads the standup doc and spins up cloud coding agents
Your team improves lessons one at a time on local agents, limited by compute.
What hurt
Kanishk Jain (@kanishksj01) connected his bot to his team's Google Drive and Cursor Cloud Agents, using what Lauren Tan calls the outer loop + inner loop setup. Not affiliated with xAI.
What to install or create
The bot handles the outer world (messaging, bug reports, Drive); cloud agents handle the engineering. He told it to find the daily standup doc and start on the issues noted there. It found the doc and spun up several cloud agents; in a day, hundreds ran in parallel across his physics learning app's lessons.
Bots
Outer-loop bot
Reads team docs and dispatches cloud agents.
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/kanishksj01/status/2108674323762340072 (credit @kanishksj01).
- 2Connect your bot to the team Drive and to cloud coding agents.
- 3Tell it which doc holds the daily standup notes.
- 4Ask it to start agents on the issues listed, with a cap on how many at once.
- 5Review the resulting changes before merging.
Approval fence
Agents open changes; your team reviews before merge. Parallel runs cost usage, so cap how many it starts.
What to tweak
Point the bot at the doc your team already writes, not a new tracker.
Source
Kanishk Jain @kanishksj01 · 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.