Engineering build desk
Code, review, and audit — you still merge.
6 bots · 30 min to stand up
Open blueprintEngineering
You pay for several AI tools, and switching between them loses context every time.
Mike P (@mikepat711) wrote up how he uses Grok Bot as the one front door for all his AI subscriptions, with three ways to wire them in and a Notion database every AI writes to. Not affiliated with xAI.
Lane A: an always-on Mac mini with Grok Bot open, so the bot can drive Claude Code, Grok Build, or any CLI there. Lane B: no spare computer? Ask the bot to install a coding CLI on its own cloud computer, hand it the API key through the secure key prompt, and run it headless. Lane C: Cursor cloud agents, no setup, billed to your Cursor usage and returning PRs. For continuity, connect Notion to every AI and have them all write to one shared memory database.
Bots
Orchestrator bot
Routes each job to Claude Code, Grok Build, or a Cursor cloud agent and watches it.
Plugins
Notion
Optional
GitHub
Optional
Files
Shared Notion memory database that every AI writes to.
Routines
None on the first run. Watch one manual pass first.
Quoted from @mikepat711 — as published. Do not invent a second system prompt.
Install Claude Code on your computer.
Never paste API keys into chat; use the bot's secure key prompt. Lane A gives the bot your local machine, so keep local execution on ask-first until you trust it.
Pick the lane by where the files live: your machine for local files, the bot's computer for no-hardware, cloud agents for PRs and parallel work.
Mike P @mikepat711 · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Code, review, and audit — you still merge.
6 bots · 30 min to stand up
Open blueprintPro pack
Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.