Single repository

The common case — one git repo as one Kalauz project.

Most projects are a single git repository. Add its root folder and you're set: every workspace cuts a branch and worktree from that repo.

Setup

Add the repo's root folder as a project. Kalauz detects the environment from the root — package.json, *.csproj, go.mod, and so on — and pre-fills setup and run commands you can adjust later. See the full table in Testing.

Where worktrees live

Worktrees are created outside the repo, under the active profile's worktrees root, grouped by repository:

~/.kalauz/worktrees/<repo>/<slug>

Keeping them outside your main checkout means your primary working copy is never disturbed, no matter how many workspaces you open.

When this is the right choice

• A standalone app, library, or service.
• Any repo where the setup and run commands at the root apply to the whole tree.

If your repo holds several independently-built packages, see Monorepos instead.

What's next?

• Monorepos — many packages in one repo.
• Multiple repositories — several repos at once.