Multiple repositories

Keep several separate repos side by side in one Kalauz window.

When your work spans separate repositories — say a frontend, an API, and an infra repo — add each one as its own project. They sit side by side in the sidebar, each with its own workspaces.

Add each repo

Use Add project once per repository. Each becomes a top-level entry in the sidebar with its own icon, its own detected setup and run scripts, and its own worktrees root under ~/.kalauz/worktrees/<repo>/.

Working across repos at once

This is where parallel agents shine: open a workspace in the API repo and another in the web repo, brief them on the two halves of the same feature, and let them run at the same time. Each is sealed in its own worktree on its own branch, so they never collide. See Parallel agents.

Per-project settings

Each project keeps its own setup, run, and archive scripts, run-script concurrency mode, and files-to-copy patterns. Tune them independently — a Node frontend and a .NET service want very different commands. See Testing.

Shipping coordinated changes

Each repo's workspace produces its own PR. Open them together, and merge in dependency order — typically the API before the client that calls it.

What's next?

• Parallel agents — running the whole yard at once.
• Single repository — the simpler case.