How-to Guides

Work with Cursor and VS Code

Open a workspace's worktree in your editor and work alongside the agent.

A Kalauz workspace is just a real folder on disk — its git worktree. That means you can open it in Cursor, VS Code, or any editor and work side by side with the agent.

Open the worktree

Each workspace has a worktree path (shown in the detail panel header). Point your editor at it:

# VS Code
code ~/.kalauz/worktrees/<repo>/<slug>

# Cursor
cursor ~/.kalauz/worktrees/<repo>/<slug>

Because the worktree is a normal git checkout on the kalauz/<slug> branch, your editor's git tooling, extensions, and terminal all work exactly as they would in any clone.

Working alongside the agent

You and the agent share the worktree, so edits show up on both sides:

  • Files the agent writes appear in your editor immediately.
  • Your saves show up in Kalauz's Changes and Diff tabs (the worktree is watched live).

To avoid stepping on each other, it's cleanest to let the agent finish a turn before you start hand-editing the same files — then review everything together in the Diff tab.

Why a separate folder helps

Since every workspace is its own worktree on its own branch, opening one in your editor never disturbs your primary checkout. You can keep your main repo open on main in one window and a Kalauz workspace open on its feature branch in another.

A one-click Open in editor action is on the roadmap. Until then, copy the worktree path from the header and open it with code or cursor.

What's next?