This is the trickiest part of Conductor. If you’re having trouble, feel free to reach out to us at [email protected].
Under the hood, each workspace in Conductor is a git worktree. This allows Claude to work on an isolated copy and branch of your git repo. But, a new workspace only copies files tracked in Git. You probably have other files in your codebase that are important for your code to run, like .env files and dependencies. This is where the setup scripts come in. A setup script is a bash script that runs every time you create a new workspace.

​
Setup script example

To add a setup script, click the repository name in the sidebar and click Add setup script. Add setup script We’ve included a commented out setup script that you can use as a starting point. You’ll want to add everything you need to run your codebase in a setup script, like installing dependencies, copying .env files, etc. Here’s an example: 
cp "$CONDUCTOR_ROOT_PATH/.env" .env
pnpm install
You have special variables you can use in your setup script, like $CONDUCTOR_ROOT_PATH to reference the root path of the workspace.

​
Advanced setup script

You can go quite far with your setup script. At Conductor, we’re building a desktop app. We use setup scripts to install dependencies, create a unique database, and even a custom app icon. Here’s a link to the setup script we use for Conductor. Feel free to give it to Claude and ask it to build a custom setup script for your codebase. Here’a video walkthrough on how it works: