agent-host-logs

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

1|Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Niiihuel/openide --skill agent-host-logs-niiihuel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-host-logs
Source: https://github.com/Niiihuel/openide/tree/main/vscode/.github/skills/agent-host-logs
Command: npx skills add https://github.com/Niiihuel/openide --skill agent-host-logs-niiihuel

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 root-cause analysis of agent session failures slow and error-prone. ## Core Features & Use Cases - Safe Bundle Extraction: Extract ah-logs zip archives with a hardened Python script that validates entry counts, sizes, paths, symlinks, and Windows portability before writing to a temp folder. - Guided Log Triage: Map each file in the bundle (events.jsonl, usage.jsonl, customizations.json, ahp/.jsonl, agenthost.log, copilot-logs, vscode-logs) to the layer of the Window/AHP/Agent Host/Copilot SDK flow it describes. - Cross-Layer Correlation: Correlate events using session IDs, turnId, interactionId, JSON-RPC request IDs, AHP serverSeq, and event id/parentId to follow one operation across client, transport, host, and SDK. - Use Case: Given an ah-logs zip from a user reporting a stuck agent turn, extract the bundle, locate the turnId in events.jsonl, then trace the same request through ahp/*.jsonl and agenthost.log to find the failed response. ## Quick Start Analyze this Agent Host debug log export zip and find why the agent turn failed around the reported timestamp.

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, or agenthost.log for host failures. Correlate using session IDs, turnId, or request IDs.

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

Run python3 .github/skills/agent-host-logs/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 files are in an Agent Host debug log bundle?▼

A bundle may contain events.jsonl (SDK session events), usage.jsonl (per-call token usage), customizations.json (loaded skills/hooks/MCP servers), ahp/*.jsonl (transport traffic), agenthost*.log (host process logs), copilot-logs/*.log (SDK logs), and vscode-logs window/shared logs. Collection is best-effort, so missing files are normal.

Why is token usage missing from events.jsonl?▼

The SDK's assistant.usage event is ephemeral and never persisted to events.jsonl. Per-call token and credit usage is only recorded in usage.jsonl, which exists only when agent-host debug logging was enabled during the session.

How do I correlate events across AHP and agenthost logs?▼

Use the raw session ID, session/chat URI, turnId, interactionId, tool or request IDs, JSON-RPC request id, AHP serverSeq, and event id/parentId. Note that events.jsonl and AHP timestamps are UTC while plain .log files may use local machine time.

What are the limitations of Agent Host log export analysis?▼

Export collection is best-effort, so bundles may lack key files. AHP logs are connection-scoped and can mix multiple sessions, _ahpLog.truncated means values were omitted, and warning severity alone does not prove causality without a matching failed response.