feat(chat): add supportsHandOffs capability to chat session agents

[Copilot]

Adds supportsHandOffs to IChatAgentAttachmentCapabilities, allowing chat session extensions to opt in to showing the suggest-next widget even when locked to a coding agent.

Changes

• chatAgents.ts: Added supportsHandOffs?: boolean to IChatAgentAttachmentCapabilities
• chatWidget.ts: Added supportsHandOffs: true to supportsAllAttachments; updated renderChatSuggestNextWidget to bypass the coding-agent lock when supportsHandOffs is set
• chatSessions.contribution.ts: Registered supportsHandOffs in the extension point JSON schema so extensions can declare it in package.json

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/repos/microsoft/vscode/compare/main...don/agent-picker-sessions
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

[Chronological Review: The conversation began with the user requesting a review of their changes in the file `chatAgents.ts`. The user then requested to commit their changes, specifying that they wanted to commit all unstaged changes in the branch `don/agent-picker-sessions`, which includes files like `chatWidget`, `chatAgent.ts`, and `chatSessions.contributions.ts`. The user provided context about the repository, including the current and default branches.]

[Intent Mapping:

• "Review my changes" - User wants feedback on modifications made in chatAgents.ts.
• "Commit my changes" - User intends to finalize and save their changes to the repository.
• "I have a few changes in this branch, I would like to commit all of these unstaged changes, chatWidget, chatAgent.ts, chatSessions.contributions.ts" - User specifies the files to be included in the commit.]

[Technical Inventory:

• Repository: vscode
• Current branch: don/agent-picker-sessions
• Default branch: main
• Files mentioned: chatAgents.ts, chatWidget, chatSessions.contributions.ts.]

[Code Archaeology:

• File: chatAgents.ts - User is actively working on this file.
• Other files mentioned for commit: chatWidget, chatSessions.contributions.ts.]

[Progress Assessment:

• Completed Tasks: User has made changes to chatAgents.ts and is ready to commit.
• Partially Complete Work: User is in the process of committing changes across multiple files.]

[Context Validation: All necessary context for continuing work is captured, including the specific files and user intentions regarding the commit.]

[Recent Commands Analysis:

• Last Agent Commands: User requested to commit changes and specified files to include in the commit.
• Tool Results Summary: No specific tool results were returned as the commands were user requests.
• Pre-Summary State: The agent was preparing to commit changes in the specified files when the token budget was exceeded.
• Operation Context: The user is focused on finalizing their changes in the current branch before possibly merging or pushing to the main branch.]

1. Conversation Overview: - Primary Objectives: - "Review my changes" - User seeks feedback on modifications. - "Commit my changes" - User intends to finalize changes. - "I have a few changes in this branch, I would like to commit all of these unstaged changes, chatWidget, chatAgent.ts, chatSessions.contributions.ts" - User specifies files for the commit. - Session Context: The user is working on the `chatAgents.ts` file and has made changes that they want to commit along with other files. - User Intent Evolution: The user transitioned from seeking a review of changes to committing those changes.

2. Technical Foundation:

• Repository: vscode
• Current Branch: don/agent-picker-sessions
• Default Branch: main
• Files: chatAgents.ts, chatWidget, chatSessions.contributions.ts.

3. Codebase Status:

• File Name: chatAgents.ts
  • Purpose: Contains chat agent logic for the application.
  • Current State: User has made changes and is ready to commit.
  • Key Code Segments: Not specified in the conversation.
  • Dependencies: Related to chat functionality in the application.

4. Problem Resolution:

• Issues Encountered: No specific issues were mentioned.
• Solutions Implemented: User is preparing to commit changes.
• Debugging Context: No ongoing troubleshooting was noted.
• Lessons Learned: Not applicable at this stage.

5. Progress Tracking:

• Completed Tasks: User has made changes to chatAgents.ts and is ready to commit.
• Partially Complete Work: User is in the process of committing changes across multiple files.
• Validated Outcomes: Not specified.

6. Active Work State:

• Current Focus: Committing changes in chatAgents.ts and other specified files.
• Recent Context: User has requested to commit unstaged changes in multiple files.
• Working Code: User is focused on the changes made in chatAgents.ts.
• Immediate Context: User is preparing to commit changes when the token budget was exceeded.

7. Recent Operations:

• Last Agent Commands: User requested to commit changes and specified files to include.
• Tool Results Summary: No specific results were returned as these were user requests.
• Pre-Summary State: The agent was preparing to commit changes in the specified files.
• Operation Context: User is focused on finalizing changes in the current branch.

8. Continuation Plan:

• Pending Task: Commit changes in chatAgents.ts, chatWidget, and chatSessions.contributions.ts.
• Priority Information: Finalizing the commit is the most urgent task.
• Next Action: Execute the commit command for the specified files.

Created from VS Code.

---

🔒 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.