Repository navigation
UX pass over PR description header area #7379
Description
Activity
We have 3 new buttons here:
- "Open Changes" shows on all PRs
- "View Session" shows on Padawan PRs
- "Cancel Coding Agent" shows on Padawan PRs that Copilot is still working on.
We could put the "Checkout" and "Open Changes" into one arrow button, with "Checkout" being the default, then remember it per workspace.
We could do the same thing for "Copy Link" and "Copy vscode.dev Link"
"Cancel Coding Agent" should still be very discoverable, as it's good to be able to cancel quickly.
We could remove the "View Session" button since it's in the PR timeline below.
Peng Lyu (@rebornix), what do you think of these proposed changes?
I might expect different actions depending on whether this is a PR from Padawan or not. For example, when it's a PR from Padawan, "Open Changes" and "View Session" are more important to me, while "Rename"/"Copy Link"/"Copy vscode.dev link" are less relevant.
We could do the same thing for "Copy Link" and "Copy vscode.dev Link"
As a first step, it makes sense to me to put them into a dropdown, at the same time I wonder if we can remove them. We can right click on the issue number (
#44...) in the title and choose "copy", I'm not sure if we need a "Copy Link" button on the toolbar. For "Copy vscode.dev link" I'm curious how many users are using it.Reacted by Lee Murray and Brigit MurtaughI use both the copy buttons often! Unfortunately, I don't have telemetry for them. Will add!
We can right click on the issue number (#44...) in the title and choose "copy", I'm not sure if we need a "Copy Link" button on the toolbar.
We actually cannot do this. The right-click copy comes from the webview in core, and doesn't copy the link, rather the text.
I might expect different actions depending on whether this is a PR from Padawan or not. For example, when it's a PR from Padawan, "Open Changes" and "View Session" are more important to me, while "Rename"/"Copy Link"/"Copy vscode.dev link" are less relevant.
This is interesting. I would find it surprising to open the same view, over what is essentially the same data, and have different buttons. Instead of trying to special case Padawan, my preference would be that we make improvements that benefit all users.
- changed the title
[-]UI overview of a coding agent has way too many buttons[/-][+]UX pass over PR description header area: UI overview of a coding agent has way too many buttons[/+]on Jul 2, 2025 When using the coding agent today, I also felt like there were a lot of buttons. This felt especially crowded when I had the chat panel open as well, so the PR overview page had less space and the buttons ended up in 3 rows:
We could put the "Checkout" and "Open Changes" into one arrow button, with "Checkout" being the default, then remember it per workspace.
I like this idea! I was wondering if we should we only show
Open Changesif there are actually changes in the PR, but perhaps Alex Ross (@alexr00)'s suggestion here addresses this in a better way.I also like the other suggestions you mention Alex Ross (@alexr00).
Reacted by Lee Murray- changed the title
[-]UX pass over PR description header area: UI overview of a coding agent has way too many buttons[/-][+]UX pass over PR description header area[/+]on Jul 14, 2025 Here is the proposed update:
This includes:
- Split primary button for checkout, open changes, open in vscode.dev actions
- right click on PR number to copy link & copy vscode.dev link
pencilicon button to edit PR title- removal of view session button
- using copilot status avatar to indicate remote agent state
Reacted by Alex Ross and Brigit Murtaughremoval of view session button
One thought - what if
Cancel Coding Agentalso had a dropdown, which allowed users toView Sessionif they wanted? I like the convenience of being able to view my session logs from the top.I like that idea - will mock it up
I really like the updated design Lee Murray (@mrleemurray)!
Last thing to do is make the styling of the dropdown button look like the styling in core.
I mourn the loss of "copy link" 😢
But I can understand
You can right click on the link in the title and "Copy link" from there now. If we keep hearing feedback that the "Copy link" button is missed though, we might add it back.
Testing #253045
I am lost here, whats with all the buttons? Can we do a UX round on this editor?
//cc Lee Murray (@mrleemurray)