agent-host-logs

Analyze Agent Host debug log export bundles to diagnose session, transport, and provider issues.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/jimeh/hucode --skill agent-host-logs-jimeh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-host-logs
Source: https://github.com/jimeh/hucode/tree/main/.github/skills/agent-host-logs
Command: npx skills add https://github.com/jimeh/hucode --skill agent-host-logs-jimeh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

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.

Frequently Asked Questions about agent-host-logs

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

FAQPage Schema
How do I analyze Agent Host debug log exports?▼

Extract the ah-logs zip with the bundled extract.py script, list the files, then start from the file closest to the symptom: events.jsonl for turn behavior, ahp/*.jsonl for client-server ordering, agenthost.log for host failures, or copilot-logs for SDK behavior.

How do I safely extract an ah-logs zip archive?▼

Run python3 scripts/extract.py with the archive path. The script validates entry counts, sizes, paths, symlinks, and encryption before extracting to a temporary directory, and prints the extraction path on the final line.

What is the difference between events.jsonl and ahp JSONL logs?▼

events.jsonl contains persisted Copilot SDK events for a session such as turns, tools, and permissions over a long period. AHP JSONL files are connection-scoped wire logs with c2s/s2c direction and wire timestamps, showing requests, responses, and notifications.

Why are some files missing from the debug log bundle?▼

Missing files are normal because export collection is best-effort. Files like usage.jsonl and customizations.json only appear when agent-host debug logging was enabled, and remote logs depend on availability.

How do I correlate a failing turn across multiple log files?▼

Search by the known time or ID in the file closest to the symptom, then follow correlation fields such as session ID, turnId, interactionId, JSON-RPC request id, or AHP serverSeq into the adjacent layer. Note that plain .log files may use local time while JSONL logs use UTC.