Connect Your Coding Agents

Before a CLI agent can write code for you, it must be installed and signed in on the machine where the project runs. Connecting an account in RepoGo saves credentials for managed cloud sandboxes; it does not install an agent, unlock it for an on-device project, or change the login on your paired Mac.

First, check where your project runs#

This is why Codex can show as Connected under Integrations but not appear in a chat: if that chat uses an on-device project, there is no Codex CLI host to run it. Choose a paired Mac or cloud sandbox and open the project there.

Vercel AI Gateway is not Codex#

The Vercel AI Gateway integration supplies model access to the first-party RepoGo agent. It does not connect the Codex CLI, and it does not create a Vercel cloud sandbox.

To connect it:

1. Open Vercel's AI Gateway API Keys page and create a key.
2. In RepoGo, open Integrations → Vercel AI Gateway.
3. Paste the new key into API Key and tap Connect.
4. Return to your on-device project and choose the RepoGo agent.

If the key is rejected, confirm that it came from AI Gateway → API Keys, not Vercel's account token page. The account token belongs in the separate Vercel integration under Sandbox Providers.

To run Codex instead, connect Codex and use a project on a paired Mac or managed cloud sandbox.

Two ways to connect a cloud agent#

You can save either one — or both — per agent for managed cloud sandboxes. RepoGo defaults to CLI auth because most people already have a subscription and it avoids surprise API charges.

The golden rule: a login on the machine wins. If an agent is logged in on the host where it runs, that login is used even if an API key is also available. To use an API key instead, sign out of that agent on the host.

Where to connect#

Open Integrations:

• In the app — open the left drawer, tap your profile icon, choose Integrations, and tap the agent (Claude, Codex, or Cursor).
• On the web — go to repogo.app/dashboard/integrations and pick the agent.

Each agent's page has two tabs — CLI auth and API key.

Connect with CLI auth#

This reuses the subscription login you already have. On the CLI auth tab you have three ways to do it, easiest first:

1. Load from a paired Mac — if you're already signed into the agent on your Mac (you ran claude or codex and logged in), tap Load from paired Mac to copy that login into your RepoGo account for future managed cloud sandboxes. One tap, nothing to copy manually. (Only Macs that are paired and online appear here, and nothing is loaded until you tap.)
2. Run a command and paste — RepoGo shows a one-line command (for example cat ~/.codex/auth.json). Run it on the computer where the agent is logged in, copy the output, and paste it into the box.
3. Paste the login JSON directly, if you already have it.

Tap Save and the agent shows as connected via CLI.

Don't have a login yet? Install the agent's CLI on your Mac and sign in once (for example, run claude and follow the login prompt, or run codex login). The agent can then run on that Mac. Use Load from paired Mac only if you also want to copy that login to your RepoGo account for cloud sandboxes.

Sign in from the in-app terminal (the easy way)#

Working in a Cloud Sandbox? You can skip the Integrations screen entirely:

1. Open the in-app Terminal in your sandbox.
2. Start the agent's login — for example type claude and follow the prompt, or run codex login — and finish signing in.

That's it. RepoGo notices the new login automatically, encrypts it, and saves it to your account. Every future sandbox then starts already signed in — you only ever do this once.

This automatic save happens for logins you perform inside a cloud sandbox or cloud host, where RepoGo watches for the new credential. A login in your paired Mac's terminal stays on your Mac — use Load from paired Mac to copy that one into your account.

Connect with an API key#

On the API key tab, paste your provider key and tap Connect. Get a key here:

• Claude — platform.claude.com/settings/keys
• Codex (OpenAI) — platform.openai.com/api-keys
• Cursor — cursor.com/dashboard/api

This is the fallback when CLI auth isn't available. Remember the golden rule — if the host is also logged in, the login is used instead of the key.

How saved credentials are used#

Saved integrations apply differently depending on the host:

• Provision a managed cloud sandbox and your credentials are restored into it automatically. Your agents are signed in and ready when the sandbox comes online.
• Sign in inside a sandbox and that login is saved back to your account, so your next sandbox already has it.
• On your paired Mac, RepoGo uses the login already on that Mac. RepoGo never pushes a saved cloud credential onto your computer.
• For an on-device project, CLI-agent credentials do not apply. Use the RepoGo agent with a Vercel AI Gateway key.

Which agents support what#

See Supported Agents, Models & Voices for the full list of models each agent can run.

View historical coding-agent usage#

In the iPhone app, open Environments, select a connected host, then tap Token Usage. You can report today, yesterday, the last 7, 30, or 90 calendar days, or choose a custom inclusive date range of up to 366 days.

RepoGo reads the Claude Code and Codex transcript metadata already stored on that host. It sends only aggregated usage and bounded scan diagnostics to the iPhone; prompts, responses, transcript paths, and session identifiers stay on the host. The report covers all locally stored Claude Code and Codex sessions on that machine, including sessions started outside RepoGo. Cursor, Copilot, and other agents are not included yet.

The dollar total is labeled Raw token cost — if billed at full API rate. It is an API-equivalent estimate based on public model prices, not your actual bill. If you use a Claude or ChatGPT subscription, your incremental charge may still be $0. This history also does not show the provider's current five-hour or weekly quota window; it reports usage during the selected calendar days.

Your credentials are kept safe#

• Logins and keys are encrypted at rest and never shown back to you after saving — the form only ever displays status, not the secret.
• Credentials are pulled from your Mac only when you tap — RepoGo never auto-harvests a login, and never pushes one to a Mac on its own.
• You can Disconnect an agent at any time from its Integrations page.

Troubleshooting#

• Codex is connected but I cannot choose it in chat. Check the project location. Codex is unavailable for on-device projects. Open a project on a paired Mac with Codex installed and signed in, or on a managed cloud sandbox.
• I connected Vercel AI Gateway but Codex is still missing. Vercel AI Gateway unlocks models for the RepoGo agent; it does not unlock Codex. Connect Codex separately and use a Mac or cloud sandbox.
• I saved an API key but the agent still uses my subscription. That's expected — your login wins. If you want API billing, sign out of the agent on that host first.
• "Load from paired Mac" isn't showing. It only appears when you have a Mac that's paired and online and signed into that agent. Check the Mac is connected and that you've logged the agent in there.
• The agent says it isn't logged in. Connect an API key, or log in to the agent on a connected host (your Mac, or inside the sandbox) and try again.
• Do I have to reconnect for each sandbox? No. Connect once; every sandbox picks it up automatically.

Next, spin up a Cloud Sandbox and put your newly connected agent to work — or read Getting Started if you haven't paired your Mac yet.