troubleshoot

Diagnose unexpected chat agent behavior by analyzing Copilot debug JSONL logs.

Updated Aug 30, 2026
One-click install
npx skills add https://github.com/Tyrizx/Tyrizx --skill troubleshoot-tyrizx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: troubleshoot
Source: https://github.com/Tyrizx/Tyrizx/tree/main/extensions/copilot/assets/prompts/skills/troubleshoot
Command: npx skills add https://github.com/Tyrizx/Tyrizx --skill troubleshoot-tyrizx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a Copilot chat agent behaves unexpectedly—slow requests, skipped tools, missing instructions, or failed tool calls—users have no easy way to find the root cause. This Skill investigates session debug logs to explain exactly what happened and why, based on evidence rather than guesswork. ## Core Features & Use Cases - Log-Based Root Cause Analysis: Parses JSONL debug logs (main.jsonl, subagent logs, system prompt and tool snapshots) to trace conversation flow, tool calls, and model requests. - Latency and Error Detection: Identifies slow events, failed tool calls, and discovery issues using grep, jq, Select-String, or Node.js one-liners across platforms. - Network Diagnostics: Runs the github.copilot.debug.collectDiagnostics command to check authentication, connectivity, and proxy configuration when network issues are suspected. - Use Case: A user asks why their custom skill did not load. The Skill searches the session log, finds a name mismatch between the folder and SKILL.md frontmatter, and explains the fix with concrete steps. ## Quick Start Ask the agent why your last Copilot request was slow or why a specific tool was not called, and it will analyze the session debug logs to explain the cause.

Frequently Asked Questions about troubleshoot

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find out why a Copilot request was slow?▼

Search the session debug log for events with high duration values, for example using jq to filter entries where dur exceeds 5000 milliseconds. Check llm_request entries for time-to-first-token and token counts to identify whether latency came from the model or from tool execution.

Why did my custom skill or instruction file not load in Copilot chat?▼

Check the discovery events in the session debug log, which record which instructions, skills, and agents were resolved or skipped. A common cause is a name mismatch between the folder name and the name field in the file's frontmatter.

Can I search Copilot debug logs with workspace search tools?▼

No, workspace-scoped search tools cannot access debug logs because they live in user storage outside the workspace. Use terminal commands like grep or jq on macOS/Linux, or Select-String and Node.js one-liners on Windows.

How do I diagnose Copilot network or authentication errors?▼

Run the VS Code command github.copilot.debug.collectDiagnostics, which returns a report covering authentication status, network reachability, and proxy configuration. Review the returned diagnostics string before concluding the cause of repeated timeouts or 401/403 errors.

What should I do when log analysis shows no clear root cause?▼

Consult the Copilot Issues wiki on the microsoft/vscode GitHub repository for known issues matching the symptoms. If the wiki has no relevant guidance, report the behavior as a new issue with the session details.