agent_ui: Improve draft threads for worktrees#58268
Merged
Merged
Conversation
bennetbo
approved these changes
Jun 2, 2026
TomPlanche
pushed a commit
to TomPlanche/zed
that referenced
this pull request
Jun 8, 2026
Closes AI-351 This PR builds on top of zed-industries#57692 by improving the draft threads UX in the context of worktrees. If you have more than one worktree loaded for a given group, clicking on the plus button will now display a menu allowing you to choose for which worktree you'd like to open a new thread in. This felt particularly relevant in the case of discarding a draft within a worktree when that was the only thread item for that worktree, making it hard to come back to it. Added some extra stuff in here as well with regards to better draft management. Most notably, if you created a new thread and then typed something, this draft thread would show a timestamp that's relative to the creation time of the thread. However, if you moments later deleted the draft content and then typed something up again, the timestamp would be stuck in the creation time. That felt wrong because by erasing the content you effectively reset the draft. So, this branch makes it so, in this context, the timestamp would be reset to now. Release Notes: - Agents: Added improvements for the draft thread UX particularly in the context of worktrees, allowing to choose for which worktree to open a thread in when the group contains more than one.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes AI-351
This PR builds on top of #57692 by improving the draft threads UX in the context of worktrees. If you have more than one worktree loaded for a given group, clicking on the plus button will now display a menu allowing you to choose for which worktree you'd like to open a new thread in. This felt particularly relevant in the case of discarding a draft within a worktree when that was the only thread item for that worktree, making it hard to come back to it.
Added some extra stuff in here as well with regards to better draft management. Most notably, if you created a new thread and then typed something, this draft thread would show a timestamp that's relative to the creation time of the thread. However, if you moments later deleted the draft content and then typed something up again, the timestamp would be stuck in the creation time. That felt wrong because by erasing the content you effectively reset the draft. So, this branch makes it so, in this context, the timestamp would be reset to now.
Release Notes: