We've raised a $22m Series A →Skip to docs content
Conductor

How-to Guides

Work in monorepos

Control which directories agents can see in a monorepo workspace

Conductor supports monorepos out of the box.

Adding a monorepo

Adding a monorepo to Conductor is the same as adding any other repository.

When you add a monorepo to Conductor, workspaces are created at the repository's root level. That means agents have access to all packages and services in your monorepo by default.

Working with specific directories

Frequently, you might want your agents to only work on a few directories in your monorepo. If you have multiple directories with similar file names, agents can get confused when grep'ing or glob'ing.

When you create a workspace for your monorepo, you can select which working directories will be visible in the workspace.

Dialog for choosing which monorepo directories are visible in a Conductor workspace

Any directories not selected will be hidden in the workspace using git sparse checkout (Git sparse checkout docs).

You can also add or remove directories from the workspace at any time by clicking "Select working directories" in the git panel.

Running microservices at once

To run microservices at once in a workspace, create a run script that launches all of the services you need.

Using Git Submodules

If your monorepo uses git submodules, we recommend putting git submodule update --init --recursive in your setup script. This will automatically initialize and clone all submodules on workspace creation.

On this page