# Move/promote a subagent into its own independent agent chat **URL:** \ **Category:** Feature Requests\ **Tags:** subagents, chat\ **Created:** [July 28, 2026, 10:31pm UTC](https://forum.cursor.com/t/move-promote-a-subagent-into-its-own-independent-agent-chat/166910 "2026-07-28T22:31:48Z")\ **Posts on this page:** 1\ **Showing post:** 4
**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:** [July 31, 2026, 8:41am UTC](https://forum.cursor.com/t/move-promote-a-subagent-into-its-own-independent-agent-chat/166910/4 "2026-07-31T08:41:17Z")
Hey @Tr_n_Minh_Quang The closest thing that exists is resuming. Every subagent execution returns an agent ID, and you can pass that ID back to keep the same subagent going with its context, tools, and model preserved: Resume agent abc123 and analyze the remaining test failures That covers the follow-up-and-iterate part of what you’re describing, including after the subagent has finished. It just still goes through the parent chat rather than living as its own session, which is the piece you’re actually asking for. Details in **[Subagents → Resuming subagents](https://cursor.com/docs/subagents#resuming-subagents)**. We’ll be tracking this post to gauge interest, which helps our product team prioritize. Two open threads are circling the same area if you want to add your voice there too: **[Agent-spawned side sessions](https://forum.cursor.com/t/agent-spawned-side-sessions-parallel-tasks-in-a-new-chat-tab-with-fresh-context-optional-worktree/163000)** (its V3 section proposes promoting subagents to full sessions) and **[Having fork of the main agent as subagent](https://forum.cursor.com/t/having-fork-of-the-main-agent-as-subagent/162694)**. --- _[View the full topic](https://forum.cursor.com/t/move-promote-a-subagent-into-its-own-independent-agent-chat/166910)._