You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following up on a previous issue closure, I’d like to propose a few usability enhancements and a feature request to make managing/cleaning up conversation threads significantly easier and more intuitive for new users like me.
Note: I'm not asking multiple feature requests for the same thread. For me, these are all related to each other because they came from the same underlying problem (see: issue).
1. Improve Bulk Selection Discoverability in Sidebar (UX)
Current State: Multi-selecting threads requires Cmd/Ctrl + Click or Shift + Click followed by a right-click. Right-clicking a section header (e.g., "Settled") currently does nothing. Problem: There are no visual cues (such as selection checkboxes, a "Select All" option on right-click, or a "Clear/Delete All" action on section headers). Expecting users to guess desktop OS modifier keys without any UI prompt creates high friction. Proposed Solution:
Add a "Select All" and "Delete All Settled" option when right-clicking section headers.
2. Clarify Terminology in Storage Settings (UX)
Current State: Storage options list rules for clearing "worktrees," browser artifacts, and logs. Problem: Terminology like "worktree" is easily confused with "conversation workspace" by users who aren't deeply familiar with Git internal terms or T3Code underlying architecture. I'm new here. This leads to the expectation that "Delete now" will clear old conversation threads. Proposed Solution:
Add explicit helper (?) in Options -> Storage defining what a worktree is.
If thread retention isn't handled here, clearly note where threads are stored or how to manage them.
3. Feature Request: Agent Tool to Manage/Delete Threads (with User Confirmation)
Use Case: When using agents to analyze full thread histories (e.g., auditing past conversations to refine AGENTS.md), it can be tedious to manually select and delete threads after processing.
Proposed Feature: Give AI agents access to a thread management/purge tool.
Safety Guardrail: To prevent accidental data loss, executing a bulk delete tool must require explicit user confirmation in the UI before any threads are wiped.
--
Closing Thought
If a user is clearly confused about something as straightforward as bulk deleting threads, there’s likely a underlying design and discoverability issue here worth revisiting. Just my point of view though, and hopefully this feedback helps refine the experience!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Following up on a previous issue closure, I’d like to propose a few usability enhancements and a feature request to make managing/cleaning up conversation threads significantly easier and more intuitive for new users like me.
Note: I'm not asking multiple feature requests for the same thread. For me, these are all related to each other because they came from the same underlying problem (see: issue).
1. Improve Bulk Selection Discoverability in Sidebar (UX)
Current State: Multi-selecting threads requires
Cmd/Ctrl + ClickorShift + Clickfollowed by a right-click. Right-clicking a section header (e.g., "Settled") currently does nothing.Problem: There are no visual cues (such as selection checkboxes, a "Select All" option on right-click, or a "Clear/Delete All" action on section headers). Expecting users to guess desktop OS modifier keys without any UI prompt creates high friction.
Proposed Solution:
2. Clarify Terminology in Storage Settings (UX)
Current State: Storage options list rules for clearing "worktrees," browser artifacts, and logs.
Problem: Terminology like "worktree" is easily confused with "conversation workspace" by users who aren't deeply familiar with Git internal terms or T3Code underlying architecture. I'm new here. This leads to the expectation that "Delete now" will clear old conversation threads.
Proposed Solution:
3. Feature Request: Agent Tool to Manage/Delete Threads (with User Confirmation)
AGENTS.md), it can be tedious to manually select and delete threads after processing.--
Closing Thought
If a user is clearly confused about something as straightforward as bulk deleting threads, there’s likely a underlying design and discoverability issue here worth revisiting. Just my point of view though, and hopefully this feedback helps refine the experience!
All reactions