using-jj-workspaces

To isolate parallel development in a jj-managed repository, you can use jj workspaces. This redirects git worktree requests to create sibling workspaces outside the main tree, ensuring concurrent work proceeds safely with a verifiably clean baseline.

Git worktree requests in jj-managed repositories cause interference because multiple agents compete for the same tree. Intercepting these requests and redirecting them to isolated jj workspaces prevents this conflict and provides each agent a clean starting point.

To set up an isolated jj workspace, request its creation in your jj-managed repo. The process intercepts standard worktree commands, translating them to create a clean, sibling workspace outside the main tree for safe parallel feature work.

Yes, you can use git worktrees with jj-managed repositories for sub-agent workflows. Worktree requests are intercepted and translated into jj workspace commands, creating isolated sibling directories that support safe multi-agent parallel development.

The best way to manage multiple isolated baselines in jj is using workspaces. By intercepting git worktree requests, it creates sibling workspaces outside the main repo with clean starting points, avoiding interference during parallel development.

You should avoid standard git worktrees in jj-managed projects when running multi-agent parallel work. Without redirecting to jj workspaces, concurrent worktree requests cause interference and compromise the clean baseline needed for safe development.