Run Claude Code or Codex on your Bot's computer with your ow

How this helps you

Your Bots use your existing plan for coding and your own skills, not a fresh setup.

✦ Try it

On your desktop, open the terminal and install [Claude Code or Codex]. When it needs me to sign in, stop and tell me so I can take over. Then clone [repo URL] and run a quick check that you can work in it.

Fill in: [Claude Code or Codex] is the CLI you pay for. [repo URL] is the repo with your project or skills.

What they did

Nate Herk shows a Bot running Claude Code in his repo on his own team plan. Every Bot has its own screen but they share one file system, and there is a terminal, so a Bot can install Claude Code, Codex or other CLIs. He told the Bot to open the terminal on its desktop and install it; it then prompted him to sign in, so he took over, signed in and clicked authorize. Next he had it clone his repos, which carry his skills and agent file, and copy over the one file of keys he relies on, so the Bot can do what he does on his own desktop. He suggests a Bot named after the tool ("Claude Code" or "Codex") so it is always on in your pocket.

Who it's for: People who already pay for a coding CLI and want it running in the cloud from their phone.

Before you start

A paid Claude Code or Codex plan of your own.
A repo with your skills or project files.
Comfort taking over the Bot's screen to sign in.

How to try it

Pick or create a Bot for coding work.
Ask it to open the terminal on its desktop and install the CLI.
When it asks you to sign in, take over, sign in and authorize.
Ask it to clone your repo.
Move over the files your setup needs, keeping secrets out of chat (see the 1Password tip).
Give it a first small task in that repo.

What to expect

A terminal on the Bot's screen running the CLI on your plan, with your repo cloned and ready.

Common mistakes

Pasting API keys or passwords into the chat. Use a password manager or the sign-in screen.
Forgetting all Bots share the file system, so other Bots can see that repo.

Related tips

Watch coding work live and get recordings back: With Cursor connected, your Bot links you to the cloud agent live and sends screenshots and screen recordings.
Use your 1Password with Grok Bot: Connect 1Password, approve each login in the 1Password app, and it fills the sign-in without the Bot seeing the password.
Open your Bot's screen to watch or help: Each Bot works on a real desktop you can open, watch, sign in on, and take over.
Move an old AI agent folder into Grok Bot: Tom moved 59 local agents into about two dozen Bots by going through them one role at a time: keep, merge, instructions or shared skill.
Run nightly code audits that leave PRs for the morning: Engineer Bots clean up the codebase overnight; you review a fresh set of pull requests with breakfast.
Keep a restore skill for when your Bot's computer is updated: Files and logins survive a computer update; installed tools don't. A restore skill puts them back in one message.
Make your Bot the manager, not the coder: one rule and locked doors: Let your Bot plan and check the work while coding agents write the code. Start with one rule, and remember every Bot shares one computer and its logins.