エンジニアリング

Drive Claude, Grok Build, and other AI subs from Grok Bot: three lanes plus shared Notion memory

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.

ボット

Orchestrator bot
Routes each job to Claude Code, Grok Build, or a Cursor cloud agent and watches it.

プラグイン

Notion
任意
GitHub
任意

ファイル

Shared Notion memory database that every AI writes to.

ルーティン

初回の実行では使いません。まず手動で1回通して確認してください。

プロンプト

Lane B starter line (author-quoted)

Quoted from @mikepat711 — as published. Do not invent a second system prompt.

Install Claude Code on your computer.

初回実行

1Read https://x.com/mikepat711/status/2107651872496533800 (credit @mikepat711).
2Choose a lane: always-on computer (A), the bot's own computer (B), or Cursor cloud agents (C).
3For B, tell the bot “Install Claude Code on your computer” and give the key via the secure prompt.
4For C, just ask the bot to spin up a cloud agent for a task and report back.
5Connect Notion to each AI you use and have them all write to one shared memory database.

承認フェンス

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.