Problem
Many real-world tasks span multiple related sessions rather than a
single long conversation.
For example, while working on a project I might have:
- One session implementing a feature
- Another reviewing architecture
- Another researching APIs
- Another writing documentation
- Another generating tests
- A terminal
- GitHub
- Documentation
- A project board
Today these exist as unrelated tabs. They belong to the same higher-level objective, but there is no way to organize them.
As the number of sessions grows, context switching becomes increasingly challenging.
Proposal
Introduce the concept of a Session Bundle (or Workspace).
A bundle is simply a collection of related tabs that can be treated as one logical unit.
The bundle is purely an organizational layer.
Bonus Feature: Include Non-Agent Tabs
An additional improvement would be allowing bundles to contain non-agent tabs alongside agent sessions.
This is similar to how gmux.app treats a workspace as a collection of related resources rather than only terminal sessions.
Instead of organizing only agent sessions, the UI would organize everything relevant to accomplishing a particular objective.
Benefits
- Better organization for long-running projects
- Reduced tab overload
- Easier context switching
- Natural grouping of related work
- Better support for multi-repository and multi-agent workflows
- Encourages thinking in terms of projects rather than isolated
conversations
I suspect many users naturally organize work this way already, so making it a first-class concept could significantly improve usability for larger, ongoing efforts.
Problem
Many real-world tasks span multiple related sessions rather than a
single long conversation.
For example, while working on a project I might have:
Today these exist as unrelated tabs. They belong to the same higher-level objective, but there is no way to organize them.
As the number of sessions grows, context switching becomes increasingly challenging.
Proposal
Introduce the concept of a Session Bundle (or Workspace).
A bundle is simply a collection of related tabs that can be treated as one logical unit.
The bundle is purely an organizational layer.
Bonus Feature: Include Non-Agent Tabs
An additional improvement would be allowing bundles to contain non-agent tabs alongside agent sessions.
This is similar to how gmux.app treats a workspace as a collection of related resources rather than only terminal sessions.
Instead of organizing only agent sessions, the UI would organize everything relevant to accomplishing a particular objective.
Benefits
conversations
I suspect many users naturally organize work this way already, so making it a first-class concept could significantly improve usability for larger, ongoing efforts.