You can install Codex, Claude Code, and Pi right inside Grok Bot.

Send a task in the chat. Your agents get to work in the cloud, and the diff and test results come back to you. Put all your other subscription quotas to work.

Grok Bot runs on a Linux cloud machine you can control. Install your usual coding agents there, connect your accounts, and split the work:

→ You still send tasks to Grok Bot
→ Grok Bot uses its own quota to break down tasks, delegate, track progress, and check the results
→ Codex / Claude Code / Pi write code and run tests, using their connected accounts’ quotas
→ Diffs, test results, and outputs come back to your chat

Start with one agent. Send this to Grok Bot:

“Install Codex CLI on your own cloud machine and guide me through signing in to use my existing subscription.

Clone [REPOSITORY URL] into a separate working directory and use Codex to complete [TASK]. The acceptance criteria are [EXPECTED RESULT]. Do not modify [OUT-OF-SCOPE AREAS].

Let Codex handle the implementation. Track its progress, give it the information it needs, and review its changes and test results. Don’t redo the work yourself.

When it’s done, send me the diff and test results, and tell me where to find the outputs. Ask me first if you need additional authorization.”

The agents read the repo, edit code, and run tests on Grok Bot’s own cloud machine.

If you subscribe to Grok Build or Cursor, connect them the same way. When running multiple tasks at once, you can also have Grok Bot use Herdr to manage the sessions.

You keep assigning tasks in one chat, using several subscriptions you’ve already paid for.

The diagram below shows how the work is split. 👇