Add slash command to troubleshoot agent info

[pwang347]

No description provided.

[Copilot]

Pull request overview

This PR adds a new /agentInfo slash command to help troubleshoot and diagnose Copilot customization settings. The command provides comprehensive diagnostics information about the user's customization setup in a single, accessible view.

Key Changes

• Adds a new /agentInfo slash command that displays diagnostic information about instructions, skills, agents, and other customization files
• Shows system information, workspace configuration, and active customization files with their paths
• Implements progressive rendering using multiple progress.report calls to provide a responsive user experience

Comments suppressed due to low confidence (2)

src/vs/workbench/contrib/chat/browser/chat.contribution.ts:1273

• The error object is directly concatenated into the markdown string without proper formatting or message extraction. This pattern is repeated throughout the function (lines 1273, 1306, 1342, 1380, 1416) and could expose internal error details to users. Consider using a consistent error formatting approach that extracts error messages safely.

				content += `*Error: ${e}*\n\n`;

src/vs/workbench/contrib/chat/browser/chat.contribution.ts:1202

• The folder name is inserted directly into markdown table cells without escaping special characters. If the folder name contains pipe characters (|) or other markdown special characters, it will break the table formatting. This issue also appears in lines 1284, 1318-1320, 1353-1356, and 1394-1396. Consider escaping these values before inserting them into the markdown table.

				for (const folder of workspace.folders) {
					content += `| ${folder.name} | ${folder.uri.fsPath} |\n`;

[Copilot]

All user-facing strings in the markdown output should be localized using the nls.localize() method. The strings include section headers, table headers, messages, and labels. This is consistent with VS Code's localization requirements where all strings visible to users must be externalized.

[Copilot]

The function call uses CancellationToken.None instead of the token parameter passed to the slash command handler. This is inconsistent with other async calls in the same function that properly use the token parameter (lines 1240, 1261, 1294, 1327, 1403). Using the provided token allows for proper cancellation handling when the user cancels the operation.

Suggested change

	const skills = await promptsService.findAgentSkills(CancellationToken.None);
	const skills = await promptsService.findAgentSkills(token);

[Copilot]

The folder name and file names are inserted directly into markdown table cells without escaping special characters. If these names contain pipe characters (|), backticks (`), or other markdown special characters, they will break the table formatting. Consider escaping these values before inserting them into the markdown table.

This issue also appears in the following locations of the same file:

• line 1201

[Copilot]

Creating a new Set on every iteration of the outer loop is inefficient. The Set should be created once before the loops begin. Move the Set creation outside the nested loops to avoid creating multiple Sets unnecessarily.

Suggested change

	content += '| Source | Path |\n';
	content += '|--------|------|\n';
	for (const folder of workspace.folders) {
	for (const location of [...new Set(agentLocations)]) {
	const uniqueAgentLocations = [...new Set(agentLocations)];
	content += '| Source | Path |\n';
	content += '|--------|------|\n';
	for (const folder of workspace.folders) {
	for (const location of uniqueAgentLocations) {

[Copilot]

The error object is directly concatenated into the markdown string without proper formatting or message extraction. This could expose internal error stack traces or object representations to users. Consider using a more user-friendly error message format, such as extracting the error message with proper checks for Error instances.

This issue also appears in the following locations of the same file:

• line 1273

[Copilot]

The agent name and description are inserted directly into markdown table cells without escaping special characters. If these values contain pipe characters (|), backticks (`), or other markdown special characters, they will break the table formatting. This same issue exists in the skills table (lines 1372-1373) and prompt files table (lines 1407-1409). Consider escaping these values before inserting them into the markdown table.

[Copilot]

This large function (over 240 lines) could be refactored into smaller, focused helper functions. Consider extracting sections like "System Information", "Workspace Information", "Instruction Files", "Custom Agents", "Agent Skills", and "Prompt Files" into separate private methods. This would improve readability, testability, and maintainability.

Suggested change

	try {
	const promptFiles = await promptsService.listPromptFiles(PromptsType.prompt, token);
	if (promptFiles.length > 0) {
	content += '| Name | Storage | Path |\n';
	content += '|------|---------|------|\n';
	for (const file of promptFiles) {
	const label = promptsService.getPromptLocationLabel(file);
	content += `| ${file.uri.path.split('/').pop()} | ${file.storage} | ${label} |\n`;
	}
	content += '\n';
	} else {
	content += '*No prompt files found*\n\n';
	}
	} catch (e) {
	content += `*Error: ${e}*\n\n`;
	}
	progress.report({ content: new MarkdownString(content), kind: 'markdownContent' });
	await timeout(200);
	}));
	}
	content = await this.appendPromptFilesSection(content, promptsService, token);
	progress.report({ content: new MarkdownString(content), kind: 'markdownContent' });
	await timeout(200);
	}));
	}
	private async appendPromptFilesSection(content: string, promptsService: IPromptsService, token: CancellationToken): Promise<string> {
	try {
	const promptFiles = await promptsService.listPromptFiles(PromptsType.prompt, token);
	if (promptFiles.length > 0) {
	content += '| Name | Storage | Path |\n';
	content += '|------|---------|------|\n';
	for (const file of promptFiles) {
	const label = promptsService.getPromptLocationLabel(file);
	content += `| ${file.uri.path.split('/').pop()} | ${file.storage} | ${label} |\n`;
	}
	content += '\n';
	} else {
	content += '*No prompt files found*\n\n';
	}
	} catch (e) {
	content += `*Error: ${e}*\n\n`;
	}
	return content;
	}