troubleshoot

To diagnose slow Copilot chat turns or blocked tool calls, analyze session debug logs to trace model requests and tool definitions. This process correlates subagent activity and loading events to pinpoint latency sources and identify why specific tool calls were blocked.

Troubleshooting missing instructions or system prompts in Copilot sessions requires examining debug logs for customization loading events. This approach traces session-level behavior changes and verifies whether specific system prompts, agents, or instructions failed to load properly.

The best way to investigate unexpected chat agent behavior is by reading direct debug logs and correlating model requests with subagent activity. This method turns raw session logs into evidence-based explanations for anomalies like skipped skills or slow turns.

Yes, troubleshooting Copilot chat sessions requires direct evidence from debug logs. The diagnosis of system prompts, tool definitions, and session-level behavior changes relies entirely on correlating actual model requests and tool calls rather than speculation.

Yes, you can trace subagent activity and tool definitions during a Copilot chat session by analyzing debug logs. This process correlates subagent activity with model requests to verify tool definitions and explain session-level behavior changes.