detachbox
PagesProjects and launches

Projects and launches

Every repository you work on is a project: a folder at /work/<project> on your account disk, and a new one costs $0. One click puts Claude Code, Codex or OpenCode to work inside it on the subscription or API key you pick, and several agents run 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, with a home folder of its own that its terminals see at /home/dev. The folder holds your code, its launches and the agent conversations they share. The project folder and its home folder both stay when the terminals that used them end.

A project terminal sees its own project and its own home folder. Logins, git keys, agent settings and caches there belong to that project alone, and nothing one project's code drops into its home runs in another. Each terminal has its own Docker and system packages. A shell terminal can reach all the projects on its Compute and works in a home folder of its own.

Every new project starts with a clean home folder: sign in to git, gh and your other tools once in its terminal. A project made before home folders were split already has your skills, subagents, commands, rules, output styles and plugins copied into its home.

/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 the git sign-in and keys of your Shell's home folder, so private repositories work: sign in once in a shell terminal with gh auth login or glab auth login.
    • Empty: an empty folder. Leave Make it a git repository ticked to start with git init.
    • Folder: a folder inside /home/dev of your shell terminals. 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.

With more than one Compute, the dialog also asks which Compute the project lives on. It stays there: to work on it from another Compute, push it and clone it there.

A clone of a big repository takes a few minutes, and the page shows its progress. If the setup stops, the project page says why: fix the address right there and pick Try again to set up the same project again. Your first project can also start from Terminals right after checkout: Get started shows the three questions.

Find a project

Projects lists every project with the agents of its launches. With 6 or more projects, a search field sits on top: press / and type part of a name, an agent or an account.

Open a project to see Where it lives: the folder (the button beside it copies the cd command), where the code came from and when the project was created.

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 default; the empty Model field names the model the launch gets for that agent and provider. A launch on a subscription or key connected in the dashboard can also turn on rotation and Continue after the limit resets, and then a limit no longer ends the run.

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.

The default launch of api: Claude Code on one of three Claude subscriptions, with a DeepSeek key and a Z.ai key also on offer, an optional model, and rotation across the Claude subscriptions as limits run out.

The first launch on a project becomes its Default launch: the one a single click runs. A project with none shows Set the default launch. Every other combination you run or save waits under Saved launches; New launch adds one there without starting it.

Each launch keeps its own settings and login inside the project, out of git. The agent's conversations belong to the project: every launch finds them with claude --resume, codex resume or opencode --continue, whichever account started them, so switching accounts never loses the conversation. A new terminal starts a new conversation. Restart terminal on this conversation and Continue after the limit resets carry the current one on.

Your skills, subagents, commands, output styles and rules in the project's ~/.claude, and your skills in ~/.codex/skills, reach every launch of the project, whatever account it runs on.

Claude and Codex · API keys · Rotation

Edit a launch

  • Default launch: pick Edit on its row.
  • Saved launch: open its ⋯ menu and pick Edit or Make default.

Change the agent, Runs on, the model, rotation and Continue after the limit resets, then pick Save. The agent and the model reach terminals you open from then on. Rotation reaches the running ones too, at once.

Open a terminal of a project

Pick Launch next to a launch on the project page, or pick New terminal on Terminals and answer Project, Agent and Runs on. A combination you already saved runs as it is; a new one is saved as a project launch for next time. The line under the form says which of the two Launch does.

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. A rotate mark shows 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 conversation stays on the account disk. So does the project's home folder, /home/dev in its terminals.

Docker images, build cache, containers, apt packages and system services belong to that terminal. They stay through a closed browser and a node reboot, and go when you end or restart the terminal. Keep database data and other work in the project or its home folder.

Remove a launch or delete a project

  • Remove a launch: open its ⋯ menu on the project page and pick Remove, then Remove launch. Its terminals end, and its settings and login leave the project. The code and the agent's conversations stay for the project's other launches. Remove the default launch and the oldest saved launch becomes the default.
  • Delete a project: open the project's ⋯ menu, pick Delete project and type its name. Its terminals end, its launches go, and the folder is erased with every file and agent conversation 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>. detachbox makes it for you, and everything that runs in the project shares it. You decide in Sallyport what each project may call; its pass lives in the project's .detachbox folder.