skyfleetWork from your terminal
Your agent runs in your terminal, and a cloud machine does the heavy lifting.
Run skyfleet in your repoEvery save syncs in a secondBuilds and tests run in the cloud
Set it up
npm i -g @abuaboud/box
skyfleet login
cd ~/your-repo && skyfleetPrefer Codex? Run skyfleet --agent codex. It runs on the agent, and you sign in to Codex there once. Codex agents don't
get MCP yet, and agents started from the dashboard, Linear or webhooks are always Claude.
No terminal handy? Open in Terminal on an agent's page opens it in the browser, for agents started with
--remote, from the dashboard or from an integration.
Edit the files in ~/.box/<environment>/<agent>/repo/ the way you always do. Git and your .env stay on your laptop.
Every day
| Command | What it does |
|---|---|
skyfleet | Opens one of your agents, or starts a new one |
skyfleet new -n <name> | Starts a fresh agent, named <environment>-<name> |
skyfleet ls | Lists your agents |
skyfleet <name> | Takes you back into an agent |
skyfleet rm <name> | Deletes an agent, saving unpushed work to cb/<name> first |
skyfleet code <environment> | Opens that environment's agents on this laptop in one VS Code window |
| Option | What it does |
|---|---|
--remote | Runs Claude on the agent, so it keeps going after you close the terminal |
--agent codex | Uses Codex, always on the agent |
-e <environment> | Picks the environment |
--size small|medium|large | Picks the machine size |
--always-on | Keeps the agent awake |
Once you've run skyfleet on this laptop, ssh <name>.skyfleet works too, and wakes the agent if it's asleep. The full list is in the
CLI reference.