Work locally

Clone the project, populate its backend environment file, and run its Docker Compose stack on your machine.

Run the project locally

Work locally hands you the managed Auth, model access, and project values your workspaces use, resolved for you, so the full stack runs on your machine without rebuilding its configuration by hand.

Before you start, you need access to the project (a project admin can add you from the project's Users tab with Add member), access to its GitHub repository, and Git and Docker Compose on your machine.

Open Work locally

Open the project in Crucible and select Work locally in the project header. The button appears once project setup completes.

Clone the repository

Copy and run the command under Clone the repository. It checks out the project's configured branch.

Create the backend environment file

Crucible names the file in its second step (Create backend/.env for the Agents template). Create that file, select Copy all, and paste the values into it. Secrets stay masked on screen until you select Reveal secrets, but Copy all always copies the real values.

Start the app

From the repository root, run the Docker Compose command under Start the app.

To hand setup to an agent instead, copy the prompt under Or paste this into a local coding agent. It checks prerequisites, clones and starts the app, and asks you to paste the environment file when it is needed.

Do not commit the backend environment file. It contains live secrets for your project.

Run the project locallyCopy Anchor Link

Under the hood: how Crucible builds the file

On this page

Run the project locally