Fix worktree context menu items no-op for Copilot CLI sessions created from terminal#4016
Draft
Fix worktree context menu items no-op for Copilot CLI sessions created from terminal#4016
Conversation
Co-authored-by: DonJayamanne <1948812+DonJayamanne@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix worktree context menu options for Copilot CLI sessions
Fix worktree context menu items no-op for Copilot CLI sessions created from terminal
Feb 26, 2026
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.
When a CLI session is created from an integrated terminal, the CLI manages worktree creation independently—
setWorktreePropertiesis never called by the extension, sogetWorktreePath(sessionId)returnsundefinedand all worktree context menu commands silently no-op.Changes
IChatSessionWorktreeService+ChatSessionWorktreeService: AdddetectAndRegisterWorktreeFromPath(sessionId, path)that checks the in-memory store and metadata store first, then falls back togitService.getRepository(path). If the path is a git worktree (kind === 'worktree'), it derivesChatSessionWorktreePropertiesusingworktrees[0]as the parent repo (always first ingit worktree listoutput) and persists them viasetWorktreeProperties.CopilotCLIChatSessionItemProvider._toChatSessionItem: WhengetWorktreePropertiesreturnsundefinedandsession.workingDirectoryis set, calldetectAndRegisterWorktreeFromPath. This runs during sessions-list rendering—before the user can invoke any context menu—so subsequentgetWorktreePathcalls succeed.Tests: 8 new unit tests covering the detection/caching flow and edge cases (non-worktree paths, missing git repo, already-registered properties, metadata store fallback, empty HEAD).
Original prompt
🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.