Suggestion: Support branching conversation history for structured feature and bug development

[shreekrishnaacharya]

Select Topic Area

Product Feedback

Copilot Feature Area

Copilot Coding Agent

Body

Problem

When working on complex features, conversations often interleave feature development and bug fixes, making it difficult to maintain clear context. For example, if developing Feature A with subtasks A.1, A.2, and A.3, encountering a bug while working on A.2 typically results in bug-related discussion mixed with feature implementation. This pollutes the main feature conversation with unrelated debugging steps, making it harder to track progress and maintain clarity.

Proposed Solution

Introduce the ability to branch conversation history, allowing users to create sub-conversations (branches) at any point, especially when handling bugs or alternative implementations. Once the branch (e.g., for a bugfix) is resolved, it can be merged back to the main conversation. This keeps the main feature context focused, while detailed bug discussions remain isolated. When resuming the main feature development (e.g., continuing to A.3), the conversation is not cluttered by debugging context.

Benefits

• Maintains a clean, focused context for feature development.
• Allows AI/assistants to track feature progress without being overwhelmed by unrelated debugging context.
• Improves clarity, organization, and the overall developer experience.
• Enables a flowchart-like history for features, bugs, and enhancements, supporting structured and complete feature delivery.

Example

• Start with Feature A
  • Subtask A.1
  • Subtask A.2 (encounter error)
    • Create branch for "Bugfix for A.2"
      • Fix bug
      • Merge bugfix branch
  • Resume with Subtask A.3

Label

feature, enhancement

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[lopuhin]

Would be super useful indeed.

This sounds really similar to subagents available in Claude Code: https://docs.claude.com/en/docs/claude-code/sub-agents

Also I've seen a mention of this in Copilot CLI docs (hidden at the bottom): https://github.com/features/copilot/cli

Does Copilot CLI support subagents or multi-agent workflows?
Subagents are not available in the current Public Preview release, but they are part of our planned roadmap for future releases.