Open Worktree context menu items no-op for Copilot CLI sessions from terminal

[bamurtaugh]

• + a new Copilot CLI session to be used in an integrated terminal
• See the session in the sessions list
  • My session is Implement Theme Toggle
• ❓ Right-clicking to use the worktree context menu options no-ops
• The worktree context menu options work for a CLI session created in the chat panel
  • So in recording below, it works for add a theme toggle that I created via the chat panel

Agent.2-25.2.mp4

[DonJayamanne]

@bamurtaugh I'm unable to repro this,
Perhaps something was fixed in insiders/pre-release (I know about a perf issue that was address), that might in-directly fix this.
Lets see

[bamurtaugh]

I'm still able to repro:

• Start a copilot session in the integrated terminal myself
• Close the terminal
• Session appears in sessions list in chat panel
• ❓ Right-clicking to interact with the worktree options Open Worktree in New Window or Copy Worktree Branch Name will no-op for this session. Open Worktree in Terminal will open a terminal but with no worktree selected
  • I think this makes sense, given there wasn't a worktree used for my session from the terminal
  • Is there anything else we can do here to guide users for these types of sessions, rather than no-op for worktree command interactions?