# Feature Proposal: Multi-Threaded Goal Execution in Cursor

**URL:** <https://forum.cursor.com/t/feature-proposal-multi-threaded-goal-execution-in-cursor/162143>\
**Category:** Feature Requests\
**Tags:** multitask, subagents\
**Created:** [June 1, 2026, 4:15pm UTC](https://forum.cursor.com/t/feature-proposal-multi-threaded-goal-execution-in-cursor/162143 "2026-06-01T16:15:22Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![neverinfamous](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/neverinfamous/32/80409_2.png) [@neverinfamous](https://forum.cursor.com/u/neverinfamous)\
**Post date:** [June 1, 2026, 4:15pm UTC](https://forum.cursor.com/t/feature-proposal-multi-threaded-goal-execution-in-cursor/162143/1 "2026-06-01T16:15:22Z")

</div>

### Feature request for product/service

Cursor IDE

### Describe the request

Hi everyone,

I wanted to propose an enhancement to the goal-based workflows in Cursor: the ability for an agent to spawn new sub-agents in separate threads. While the current /goal command is fantastic for guiding focused tasks, it can get overloaded as a project grows. The context window can get exhausted, and threads can lose clarity, degrading quality or causing crashes.

My proposal is that when a goal is set, if it’s complex or large-scale, the agent could spin off new threads, each tackling a sub-part of the goal. This would let us organize a project as a hierarchy—one master agent overseeing smaller sub-agents, each with its own task, ensuring we keep both clarity and scalability. Even for smaller projects, this would be a game changer, especially when tasks drift or interconnect unexpectedly.

I’d love to hear thoughts—do you think this would fit into the workflow? Thanks!