What problem does it solve? Agent Host debug log exports contain many heterogeneous files (events.jsonl, AHP JSONL transport logs, agenthost.log, copilot-logs, renderer logs) with no obvious starting point, making it hard to trace a reported symptom across the client, transport, host, and SDK layers. ## Core Features & Use Cases - Safe bundle extraction: Unpack ah-logs zip archives with a hardened Python extractor that validates entry counts, sizes, paths, symlinks, and Windows portability before writing to a temporary directory. - Layer-oriented triage: Map each file in the bundle to its role in the Window/client <-> AHP <-> Agent Host <-> Copilot SDK flow so analysis starts at the file closest to the symptom. - Cross-layer correlation: Follow session IDs, turnId, interactionId, JSON-RPC request IDs, and AHP serverSeq values across files to reconstruct a failing operation. - Use Case: A user reports a stuck agent turn. Extract the bundle, locate the turn in events.jsonl, then follow its turnId into the AHP JSONL traffic and agenthost.log to find the missing completion or failed response. ## Quick Start Ask the assistant to analyze the exported Agent Host debug logs zip and explain why the reported session or turn failed.