code-oss-logs

Locate and read timestamped process logs from Code OSS dev builds.

10|1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/KevinHuangIsLearning/shortestpath-ide --skill code-oss-logs-kevinhuangislearning
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-oss-logs
Source: https://github.com/KevinHuangIsLearning/shortestpath-ide/tree/main/.github/skills/code-oss-logs
Command: npx skills add https://github.com/KevinHuangIsLearning/shortestpath-ide --skill code-oss-logs-kevinhuangislearning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When debugging Code OSS or the Agents app, developers struggle to find the right log files among many timestamped folders and process-specific logs, slowing down diagnosis of startup crashes, extension failures, and agent issues. ## Core Features & Use Cases - Log Discovery: Locates the most recent timestamped log folder under the Code OSS user data directory, including custom --user-data-dir locations. - Structured Log Map: Documents the full directory layout covering main.log, renderer.log, exthost logs, agenthost.log, MCP server logs, and per-window output folders. - Use Case-Driven Lookup: Maps investigation scenarios (startup crashes, extension issues, Copilot agent problems, terminal failures) to the exact log files to read. - Console Forwarding Workflow: Explains how to temporarily enable dev console log forwarding so console.log probes persist into normal log files. ## Quick Start Find the most recent Code OSS log folder and show me any errors in the renderer and extension host logs.

Frequently Asked Questions about code-oss-logs

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

FAQPage Schema
How do I find Code OSS logs from a dev build?▼

Code OSS dev logs live under $HOME/.vscode-oss-dev/logs/, with each run creating a timestamped folder like 20260330T163430. List folders by modification time with ls -lt and open the most recent one to find main.log, renderer.log, and other process logs.

Which log file should I check for extension host errors?▼

Extension host errors appear in window1/exthost/exthost.log, with per-extension logs under window1/exthost/<publisher.extension>/. For Copilot agent issues, also check agenthost.log and the GitHub.copilot-chat extension folder.

Where are logs when Code OSS uses a custom user data dir?▼

When Code OSS launches with --user-data-dir=<dir>, logs are written to <dir>/logs/ instead of the default $HOME/.vscode-oss-dev/logs/. Launch helpers often create temporary user data dirs under .build/, so prefer the exact dir from the launch command.

Why is my console.log output missing from Code OSS log files?▼

By default, console.log only appears in DevTools or stdout, not in log files. Temporarily enable isDevConsoleLogForwardingEnabled in src/vs/platform/log/common/log.ts so console output is written through the process log service, then restore the flag afterward.

What are the multiple output_ folders in a Code OSS log directory?▼

Each window reload within a session creates a new output_<timestamp>/ folder and a matching output_logging_<timestamp>/ inside exthost/. The most recent output folder holds logs for the latest reload, while earlier ones contain prior reload output.