Open-source public beta

Ask Grok once. Collaborate with your Grok Bots.

Connect Codex to named Bots already running inside Grok Bot. Codex can send a task, wait, read bounded updates, and continue the work. One isolated Grok CLI call is available too.

Install the beta View on npm
  • MIT licensed
  • macOS verified
  • Node.js 20.19.2+
  • Core and relay CI coverage

grok_ask uses xAI allowance. Persistent Bot collaboration is experimental, and sends are never retried automatically.

TWO WAYS TO USE IT

One-off answers or persistent Bot collaboration.

Ask Grok once for a clean second opinion. Connect persistent Bots when you need continuity and delegation.

01 Available

Ask Grok from Codex

Send one bounded prompt to the authenticated Grok CLI without mounting Grok sessions, memory, plugins, logs, or Bot data into the child process.

grok_ask grok_bridge_status
  • One isolated turn
  • Supported model per call
  • Web search disabled
02 Experimental

Collaborate with Grok Bots

Connect Codex to named Bots already running inside Grok Bot. List them, inspect status, send a task to one exact Bot, wait, and read its latest bounded messages.

grok_list_bots grok_read_bot grok_wait_for_bot grok_send_bot_message
  • Persistent Bot conversations
  • Exact Bot targeting
  • Foreground companion today

THE ROUTE, NOT THE MAGIC

Every boundary stays visible.

The one-off CLI path stays separate from the persistent Bot collaboration path.

YOUR MACHINE
01 Codex
02 Local MCP server credentials stay out of tool input
DEFAULT bounded second opinion
03A Isolated Grok CLI one turn → xAI
OPT-IN persistent collaboration
03B Encrypted relay opaque application frames
04 VM companion local gateway → named Bot
The relay can see connection metadata, a random channel, and client roles, but not Bot names, IDs, messages, or the Grok gateway token.
Explore the interactive architecture

SECURITY IS PRODUCT BEHAVIOR

Useful access, narrow authority.

Failures stop visibly. External writes stay explicit. Sensitive state stays out of normal prompts.

⌁

Credentials stay put

One-off calls use your signed-in Grok CLI. Paired gateway credentials stay inside the Grok Bot VM.

◇

Encrypted, exact-target access

AES-256-GCM protects paired frames. Exact Bot IDs and roster fingerprints make target changes visible.

↯

No optimistic retries

An uncertain send stays uncertain. The bridge will not silently duplicate an external write.

Read the complete security model

THREE STEPS TO FIRST USE

Install once. Start a fresh task.

Requires macOS, Node.js 20.19.2+, Codex, and an installed, signed-in Grok CLI.

Read the full setup guide
  1. 01 · Add the immutable marketplace release 
    codex plugin marketplace add Fato07/codex-grok-mcp --ref v0.2.0-beta.8
  2. 02 · Install the plugin 
    codex plugin add codex-grok-mcp@codex-grok
  3. 03 · Start a new Codex task and ask
    Ask Grok to challenge this architecture and return the three strongest objections.