RepoGo Logo
Documentation

Getting Started

What is RepoGo?

RepoGo is a real development environment that lives on your phone.

Not a chat wrapper, not a remote desktop — a mobile client built from the ground up for agent orchestration, with the parts of a true dev workflow that actually matter when you're away from your desk: real files, a real terminal, real environments, and agents that can ship code.

Run agents anywhere#

Point RepoGo at your own Mac or at a cloud sandbox and run the same coding agents either way. Pair your Mac once and your agents work directly against your real machine — your filesystem, your shell, your running apps — from anywhere you have your phone. No Mac nearby? Spin up a cloud sandbox against any GitHub repo and keep moving.

You're not locked into one model, either. Run Claude, Cursor, Copilot, or Codex, pick the model, and switch per chat.

A real environment, not just a prompt#

The difference between a toy and a workflow is everything around the agent. RepoGo brings it:

  • Clone, create, and worktree any repo on any environment — Mac or cloud — so multiple branches and agents run side by side without stepping on each other.
  • Auto-start services. Drop an environment.json in your repo and your dev servers, watchers, and long-running commands boot automatically every time the environment wakes — each in its own terminal you can watch, stop, and restart.
  • Environment management. Keep secrets where they belong: point a name at a .env file on your Mac and reference it from any repo. RepoGo fetches it on demand, with your approval, and never writes it to the cloud.
  • Port forwarding. Services come up with public URLs, so a dev server running on your Mac or in a sandbox is reachable right from your phone.

Orchestrate by voice#

Running one agent is easy. Running several is where RepoGo earns its keep. Drive the whole fleet hands-free with the voice agent — dispatch work across multiple chats, check on progress, and answer approvals out loud while your agents grind in the background. Talk to your codebase like it's a team.

Where to go next#