grok bridge
Your coding tools.
One Grok Bot bridge.
Pass a scoped task between Grok Bot and Codex, Claude Code, Cursor, or Antigravity. Read the result. Continue your work.
One shared CLI. Native logins. No runtime npm dependencies.
8 configured directions.
3 have live exchange evidence.
Start with one task.
Node.js 22 or newer, plus the destination CLI and its own working login. The runtime installs from GitHub.
Release & downloadnpm install -g github:niharnm/grok-bridge#v0.1.0-alpha.1
Then run grok-bridge doctor to check installed
executables.
Grok Bot access also requires the community
grok-bot-cli@0.2.3. Its private gateway is
experimental.
Prefer one shared skill? Use the Skills CLI setup or install the skills.sh pack for Codex, Claude Code, Cursor, or Antigravity.
What’s verified today.
The alpha includes all eight routes. These are the observed live results as of September 13, 2026.
Live exchange verified
- Codex → Grok Bot
- Grok Bot → Codex
- Grok Bot → Antigravity
Native Codex and Antigravity fixture reads and scoped edits also passed, with the outputs checked independently.
Access still required
- Claude Code: provider access is disabled in the test account.
- Cursor: standalone CLI login is required.
- Antigravity → Grok Bot: native command permission was denied.
Host plugin discovery, saved Bot skills, and Windows acceptance remain unverified.
Keep the task explicit.
Choose the computer.
A Bot’s cloud terminal and your laptop are separate. Reverse handoffs need approved execution where the repository and authenticated CLI exist.
Check the result.
A submission receipt means submitted. Waiting requires a correlated final response. A timeout stops local waiting, without cancelling the cloud Bot.
Read the permissions.
Native policies differ. Cursor work uses force within its sandbox; Antigravity review is plan guidance. Review the destination’s controls before allowing edits.