# Can we configure whether new thread (CMD + N) opens a thread in local vs new work tree?

**URL:** <https://forum.cursor.com/t/can-we-configure-whether-new-thread-cmd-n-opens-a-thread-in-local-vs-new-work-tree/161387>\
**Category:** Feature Requests\
**Tags:** worktrees\
**Created:** [May 23, 2026, 11:07am UTC](https://forum.cursor.com/t/can-we-configure-whether-new-thread-cmd-n-opens-a-thread-in-local-vs-new-work-tree/161387 "2026-05-23T11:07:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sunwrobert](https://avatars.discourse-cdn.com/v4/letter/s/8491ac/32.png) [@sunwrobert](https://forum.cursor.com/u/sunwrobert)\
**Post date:** [May 23, 2026, 11:07am UTC](https://forum.cursor.com/t/can-we-configure-whether-new-thread-cmd-n-opens-a-thread-in-local-vs-new-work-tree/161387/1 "2026-05-23T11:07:08Z")

</div>

I always want to open a new agent in a new work tree (off main), but for some reason it always defaults to Local which is really annoying. Why doesn’t Cursor save that preference?

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [May 24, 2026, 9:45am UTC](https://forum.cursor.com/t/can-we-configure-whether-new-thread-cmd-n-opens-a-thread-in-local-vs-new-work-tree/161387/6 "2026-05-24T09:45:26Z")

</div>

Hey @sunwrobert

It’s not possible today, but we’re tracking feedback for this ([it came up on X the other day](https://x.com/alexch3n/status/2057294580937052270)), and I’ve added your support!