Your first workspace
Add a repo, open a workspace, hand it to an agent, and ship the diff.
A workspace is the one move you'll make over and over in Kalauz. This page runs through it end to end.
Add a repository
Click Add project and pick a folder. Kalauz checks whether it's a git repo,
detects an icon for the sidebar, and pre-fills a setup command from what it finds
(for example pnpm install when it sees a pnpm-lock.yaml). The project is
saved and shows up in the left sidebar.
Open a workspace
With a project selected, choose New workspace (or press ⌘N).
Kalauz cuts a fresh branch — kalauz/<slug> — and creates a dedicated git
worktree for it, sealed off from your other branches. New workspaces are named
after railway stations, so you get something like Budapest Keleti rather
than branch-3.
Any environment files matching the project's copy patterns (.env* by default)
are copied into the worktree, and the setup script runs automatically in the
Setup console.
Hand it to an agent
Type your task in the chat input and send it. Pick the model and reasoning effort, and toggle Plan or Fast mode if you want — see Agent modes. Kalauz launches the agent (Claude Code or Codex) in the worktree, reusing the login already on your machine, and streams its work into the transcript.
Open more workspaces and run them in parallel; nothing one agent does can touch another's ground.
Review and ship
When the agent settles, switch to the detail panel on the right:
- All files — the full worktree tree.
- Changes — just what the agent touched.
- Diff — the change set against your base branch, where you can leave inline comments.
Run your Run script to try it, then Create PR to push the branch and open the pull request. Walk through it in detail in Review and merge a workspace.
What's next?
- Isolated workspaces — the model behind the seal.
- Workflow — the full loop in one place.