← Back to catalog

The way I work it is that I do all my discussion, thinking, planning, PRD design everything in Grok bot but he does not code anything.

Use Grok Bot for discussion, email and PRDs only, then have a manager bot pick the right machine and hand the full PRD to your coding agent so coding never burns Grok Bot usage.

For

You want Grok Bot for planning and email, and a separate coding agent for the build.

When you're done

PRDs planned in Grok Bot, coding handed to Larry on the right machine without losing context.

How

  1. 01

    Use Grok Bot for discussion, thinking, email and PRD design only.

  2. 02

    Forbid the bot from writing code.

  3. 03

    Create a manager bot (or rules) that picks where the build should run.

  4. 04

    Have it start the coding agent with the full PRD pasted in.

  5. 05

    Keep iterating the PRD in Grok Bot and re-handing off when the plan changes.

Notes

What's good: hard split—Grok Bot never codes—so usage stays on planning and routines. The catch: the author's Larry/server map is personal; you need your own coding agent and handoff path.

Related plays

Write-ups follow public posts and official docs. No likes, views, or dashboard numbers. Open the source to check the original. About