Route Grok Bot tasks to your Claude and ChatGPT subscriptions

What does this setup do?

Install Claude Code and OpenAI Codex CLIs on Grok Bot’s shared cloud computer, sign in with your own Anthropic and OpenAI subscriptions, then set routing rules so writing, coding, and browser-heavy jobs hit the model you already pay for, without pasting the setup into Codex or Claude Code directly.

Who is it for?

Grok Bot users who already pay for Claude and/or ChatGPT and want Bots to delegate coding or drafting to those CLIs instead of defaulting back to Grok every time.

How do you set it up?

Tools

• Grok Bot with Computer access (paid plan)
• Anthropic subscription with Claude Code CLI access (per provider terms)
• OpenAI subscription with Codex CLI access (per provider terms)
• Completed shared-computer security audit (see linked setup below)

Steps

1. Read each provider’s terms for automated or agent use of a consumer or team subscription. You are routing usage through CLIs on a shared cloud machine.
2. Run the Grok Bot shared-computer security audit setup first; every Bot on your account shares that computer, browser sessions, and credential files.
3. Open one Grok Bot chat (any Bot you trust for setup). Paste the prompt below here, not into Claude Code or Codex terminals.
4. When the Bot offers sign-in links or codes for Claude Code or Codex, complete OAuth or device login yourself; do not paste passwords or API keys into chat.
5. After login, have the Bot run a short smoke test in each CLI (one harmless command each) and confirm which subscription usage pool each draw affects.
6. Set default models in each CLI if prompted, then add explicit routing rules to every Bot’s instructions (e.g. “use Codex for repo edits, Claude Code for refactors, Grok for browser research”).
7. Save the same routing block to shared memory or a /workspace file all Bots are told to read so rules persist across chats. Otherwise Bots tend to revert to Grok-only.
8. Re-test after a day: ask a coding task and a writing task and confirm the Bot names which CLI it used.

SUBSCRIPTION CLI ROUTING SETUP (run in this Grok Bot chat only, not inside Claude Code or Codex)

Goal: On my Grok Bot shared cloud computer, install and authenticate Claude Code CLI and OpenAI Codex CLI with MY subscriptions, then document routing rules so my Bots use the right tool per job.

Safety and scope:
- Complete the shared-computer security audit mindset first: one computer per user; all Bots share files and CLI logins. Prefer an isolated host or separate Cursor user if I need hard credential separation.
- I will approve every sign-in link, device code, and OAuth screen myself. Never store tokens in plain text files other Bots can read (no committing .env with secrets to /workspace).
- If a CLI is unavailable, not installed, or a usage limit is hit, say so clearly and do the task yourself in Grok instead of failing silently.
- Ask before changing any other Bot's instructions or shared memory.
- When finished, report which Bots you updated and which CLIs authenticated successfully.

Tasks:
1) Check whether Claude Code CLI and Codex CLI are installed; install per official docs if missing.
2) Guide me through subscription login for each CLI I want (I perform login; you verify with a read-only version or status command).
3) Explain whose rate limits and terms apply for each CLI call (Anthropic vs OpenAI vs Grok usage pool). In plain language, citing what you can see from CLI output only.
4) Draft a ROUTING RULES block I can paste into each Bot's instructions, for example:
   - Long-form writing / editing → [Claude Code or Codex per my preference]
   - Repo coding / tests → [Codex or Claude Code]
   - Browser research, connectors, email → Grok Bot native tools
   - If limit hit → notify me and fall back to Grok with a short note
5) Save the ROUTING RULES to shared memory (or a agreed /workspace path) and confirm how other Bots should load it each session.
6) Run one tiny test task per CLI and show me the command output summary (no secrets).

Do not revoke connectors or delete files unless I explicitly approve after this setup.

Which chat tools work with this prompt?

Paste the prompt into any of these assistants (free or paid tiers).

• Grok Bot
• Claude Code CLI
• OpenAI Codex CLI

What tips make it smoother?

• Name one “routing admin” Bot that may edit instructions; keep other Bots read-only for routing files.
• After marketplace templates, re-run a one-line routing test. Templates often omit CLI rules.
• Pair with Ask-first rules for spend and outbound send; routing does not replace approval fences.

Where do the claims come from?

Summaries use public sources linked below, not independent verification. How setups are picked.

• Read @coreyganim’s write-up (x.com)

  @coreyganim: Pattern for installing subscription CLIs on Grok Bot’s computer and routing work.

• Read @solomonsgrave’s write-up (x.com)

  @solomonsgrave: Where to paste setup: Grok Bot chat vs Codex vs Claude Code.

• Read @SilvaRhys70444’s write-up (x.com)

  @SilvaRhys70444: Need to tell Grok to use Claude/GPT each time or it reverts to Grok.

• Read @chenxi2072332’s write-up (x.com)

  @chenxi2072332: Question on whose rate limits and terms apply.

• Read @sebuzdugan’s write-up (x.com)

  @sebuzdugan: CLI login exposes local credentials; isolate host first.

• Read @vaitkus’s write-up (x.com)

  @vaitkus: Routing also consumes subscription limits.