Feature Request
When working in a session, side conversations (bug reports, quick questions, feedback) pollute the main context. This makes it harder to continue the primary task because the context window now contains unrelated discussion.
Use Case
User is deep in a feature specification workflow. They notice a UI bug and want to report it. Reporting the bug injects unrelated context into the session, "poisoning" the conversation flow for the primary task.
Proposed Solutions (pick one or combine)
- Multiple chat threads per session — Allow users to open a separate chat thread within the same session for side conversations, keeping the primary thread focused.
- Chat forking — Allow users to fork the current chat at any point, creating a new branch of conversation that doesn't affect the original thread.
Expected Benefit
Users can handle side tasks (feedback, bugs, quick questions) without disrupting the context of their primary workflow.
Filed via Ambient session
Feature Request
When working in a session, side conversations (bug reports, quick questions, feedback) pollute the main context. This makes it harder to continue the primary task because the context window now contains unrelated discussion.
Use Case
User is deep in a feature specification workflow. They notice a UI bug and want to report it. Reporting the bug injects unrelated context into the session, "poisoning" the conversation flow for the primary task.
Proposed Solutions (pick one or combine)
Expected Benefit
Users can handle side tasks (feedback, bugs, quick questions) without disrupting the context of their primary workflow.
Filed via Ambient session