Feature-Centric Session Trees for GitHub Copilot

### Feature summary

GitHub Copilot sessions are currently organized primarily as a flat structure grouped by repository/project. In real-world development workflows, work is usually feature-centric rather than repo-centric. A single feature may span multiple repositories, PRs, reviews, investigations, and implementation sessions. I would like to see GitHub Copilot support hierarchical session trees where sessions can have parent/child relationships centered around a feature or orchestrator session instead of being grouped primarily by repository. This would allow developers to: organize work around actual features spawn child sessions from orchestrator sessions track blocked/unblocked work collapse and expand large features resume work more effectively across multiple repositories

### What problem are you trying to solve?

The current session model becomes difficult to manage in larger engineering workflows, especially in microservice or multi-repo environments.

My workflow typically starts with one orchestrator session for a feature. From there I spawn many focused implementation sessions:

- debugging
- implementation
- code review handling
- QA/review
- investigations
- release notes
- API compatibility checks

These sessions may touch many repositories but are all logically part of the same feature.

Today Copilot treats them as unrelated flat sessions grouped by repository, which creates several problems:

- the relationship between sessions is lost
- it is difficult to understand which sessions belong to the same feature
- switching between features becomes hard
- blocked work due to PR reviews is difficult to track
- I often lose track of which work is ready to continue

A common workflow looks like this:

1. Work on feature
2. Create PR
3. Wait for review
4. Switch to another feature
5. Lose track of when work becomes unblocked

The current experience feels more like a chat history than an engineering workflow workspace.

### Proposed solution

Introduce feature-centric session trees with parent/child relationships between sessions.

Instead of organizing sessions primarily by repository, sessions should be grouped around a feature or orchestrator session.

Repositories should simply be metadata attached to a session rather than the primary structure.

The tree should support:

- expand/collapse behavior
- automatic child session linking
- blocked/unblocked workflow visibility
- status summaries on collapsed nodes

Suggested workflow states:

🟢 Ready to continue
🟡 Needs attention
🔴 Blocked by review
✅ Review approved
🔁 Changes requested

Collapsed nodes could summarize status:

▸ Flexible cancellation policies 2 blocked • 3 ready
▸ Loyalty points redesign All blocked
▸ Notification delivery tracking Ready to continue

Potential future enhancements:

- feature completion %
- open PR counts
- failing CI visibility
- “Resume feature” actions
- “Continue blocked work” shortcuts
- orchestration-aware workflows

### Workflow impact

This would significantly improve workflows for developers working in:

- microservice architectures
- multi-repo systems
- enterprise environments
- AI-assisted orchestration workflows
- large feature implementations

The biggest improvement would be reducing context switching and making it much easier to answer:

“What can I work on right now?”

Instead of manually checking:

- PRs
- repositories
- review states
- unrelated session histories

Copilot could become an actual engineering workflow dashboard rather than only a conversation list.

This would especially help developers coordinating large cross-repository features where work frequently becomes blocked/unblocked due to code review cycles.

### Installation context

_No response_

### Additional context

_No response_