# Working with Worktrees in Cursor

**URL:** <https://forum.cursor.com/t/working-with-worktrees-in-cursor/153472>\
**Category:** Help\
**Tags:** worktrees\
**Created:** [March 3, 2026, 2:53pm UTC](https://forum.cursor.com/t/working-with-worktrees-in-cursor/153472 "2026-03-03T14:53:36Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\
**Post date:** [March 9, 2026, 9:04pm UTC](https://forum.cursor.com/t/working-with-worktrees-in-cursor/153472/3 "2026-03-09T21:04:09Z")

</div>

Hi Ryan,

Worktrees are a powerful part of the Cursor workflow, so I get why the Conductor comparison comes up.

Today, **local worktrees are primarily session-scoped sandboxes for parallel agents**. Each local agent gets its own worktree so it can make changes without conflicting with your working directory or other agents. The usual flow is: agent runs in a worktree → you review → you apply changes back to your branch (or discard). These worktrees are **auto-cleaned** as limits are hit (default ~20) and **aren’t meant to persist across sessions**.

If you’re looking for the “one feature = one branch = one PR” model, **[Cloud Agents](https://cursor.com/docs/cloud-agent)** are the closest match to Conductor. They clone your repo from GitHub/GitLab, work on a separate branch, and can open merge-ready PRs—without touching your local environment. You can launch them from the IDE (Cmd/Ctrl+E), the web, Slack, or Linear, and monitor progress remotely.

If you want **persistent per-feature work locally** , a few workable options:

- **Manual `git worktree` + separate Cursor workspace** : create a worktree (`git worktree add ...`) and open it as its own workspace. Agents will work there normally; Cursor just won’t manage it via the Parallel Agents system.

- **Save plans to `.cursor/plans/`** : persist agent plans so you can resume work in a new session even if the original worktree is gone.

- **Setup scripts via `.cursor/worktrees.json`** : configure per-worktree setup (e.g., `npm install`) to run automatically when a worktree is created.

There aren’t publicly announced plans for persistent per-feature worktrees in local agent mode right now, but we’re actively iterating on this. If this would be valuable for your workflow, a feature request in **[Feature Requests](https://forum.cursor.com/c/feature-requests/5/l/latest?order=votes&solved=no)** is the best way to signal demand.

Best,  
Mohit

---

_[View the full topic](https://forum.cursor.com/t/working-with-worktrees-in-cursor/153472)._