detachbox
Menu

Features

Browser terminalProjectsTerminals modeNotificationsPhone and voiceLimits boardRotationAgentsDockerPreviews and filesVault

Use cases

Overnight refactorsParallel agentsPR factoryAgencies and freelancersLong-running jobsAgents from your phoneTeam subscription limitsStudents and indie hackersDocker services
DocsSecurityEnterprisePricingLog in
Get my Compute
PagesProjects and launches

Projects and launches

Every repository you work on is a project: a folder at /work/<project> on your account disk. One click launches Claude Code, Codex or OpenCode inside it, each on its own subscription, several side by side.

Projects on shipyard: api, storefront, etl-pipeline and landing, each with the agents that run on it.

What a project is

A project is a folder at /work/<project> on your account disk, next to your home folder /home/dev. It holds your code, its launches and the agent sessions they all share, and it stays when the terminals that used it end.

A project terminal sees its own project and your shared home folder. Each terminal has its own Docker and system packages. A Shell terminal can reach all your projects.

/work/<project> · CLAUDE.md · AGENTS.md · .claude/ · .mcp.json

Create a project

  1. Open Projects and pick New project.
  2. Pick where the code comes from:
    • Clone: paste the address you give git clone, such as git@github.com:you/app.git or https://…. It is cloned with your git keys on your Compute, so private repositories work.
    • Empty: an empty folder. Leave Make it a git repository ticked to start with git init.
    • Folder: a folder inside /home/dev on your Compute. It is copied into the project, and the folder stays where it was.
  3. Check the Name. It follows the repository or the folder until you type your own: up to 40 lowercase latin letters, digits and hyphens. The name becomes the path, /work/<name>.
  4. Pick Create project.

A clone of a big repository takes a few minutes, and the page follows along. Your first project can also start from Terminals right after checkout: Get started shows the three questions.

Launch an agent in a project

A launch is an agent and what it runs on: Claude Code, Codex or OpenCode, on a subscription or an API key. Add a model if you want one other than the agent's default, and, for Claude Code and Codex, rotation and Continue after the limit resets.

Pick the agent first, then an account it can use under Runs on: a Claude subscription for Claude Code, a ChatGPT subscription for Codex, or a compatible API key for any of the three. Agents lists which key works with which agent.

A launch on api: Claude Code running on one of three Claude accounts and two API keys, an optional model, and rotation to the subscription with the most room as limits run out.

The first launch on a project becomes its Default launch: the one a single click runs. Every other combination you run or save waits under Saved launches, where you can run it, edit it, remove it or make it the default.

Each launch keeps its own settings and login inside the project, out of git. The agent's sessions belong to the project: every launch sees them in claude --resume or codex resume, and a new launch picks up the latest one, whichever account started it.

Claude / Codex · API · Rotation

Open a new terminal

Pick New terminal in Terminals and answer three fields: Project, Agent and Runs on. Pick Launch. A combination you already saved runs as it is; a new one is saved as a launch on the project on the way, ready for next time.

New project… in the project list brings in more code, and Shell opens a plain login shell that needs no launch. Every choice starts a fresh environment, so pick a running terminal in the list to get back to it.

New terminal on shipyard: pick the project, the agent and what it runs on, then Launch; or open a plain Shell.

Every terminal in the list shows its project, its agent and the account it runs on, with a rotate mark when the launch rotates subscriptions.

The project api: Claude Code with rotation as its default launch, one click away, and Codex review on its own account among the saved launches.

What stays for your next run

Your project folder with its code, its launches and every agent session in it stays on the account disk, and so does everything in /home/dev.

Docker images, build cache, containers, apt packages and system services belong to that terminal. They keep running after you close the browser and are removed when you end the terminal. Keep database data and work in your project or home folder.

Remove a launch or delete a project

  • Remove a launch: open its ⋯ menu on the project page and pick Remove. Its tabs close, and its settings and login leave the project. The code and the agent's sessions stay for the project's other launches.
  • Delete a project: open the project's ⋯ menu, pick Delete project and type its name. Its tabs close, its launches go, and the folder is erased with every file and agent session in it. Push what you want to keep first.

Projects and service keys

With Vault, every project gets its own Sallyport agent, named detachbox · <project>, made for you and shared by everything that runs in the project. You decide in Sallyport what each project may call, and its pass lives in the project's .detachbox folder.