code-oss-logs

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

Updated Aug 30, 2026
One-click install
npx skills add https://github.com/Tyrizx/Tyrizx --skill code-oss-logs-tyrizx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-oss-logs
Source: https://github.com/Tyrizx/Tyrizx/tree/main/.github/skills/code-oss-logs
Command: npx skills add https://github.com/Tyrizx/Tyrizx --skill code-oss-logs-tyrizx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When debugging Code OSS or the Agents app dev builds, logs are scattered across timestamped folders with many process-specific files, making it hard to know where to look. This Skill maps the log directory structure and tells you exactly which file to read for the problem you are investigating. ## Core Features & Use Cases - Log Discovery: Finds the most recent timestamped log folder under the default or custom user data directory. - File-to-Problem Mapping: Matches investigation targets (startup crashes, extension issues, Copilot agent problems, MCP servers, terminals, network) to the correct log files such as main.log, renderer.log, exthost.log, and agenthost.log. - Console Forwarding Workflow: Documents how to temporarily enable dev console forwarding so console.log probes persist into normal log files, with a reminder to revert before check-in. - Use Case: A developer reproduces a renderer crash in a Code OSS dev build and uses this Skill to locate the latest session folder and read window1/renderer.log for the stack trace. ## Quick Start Find the most recent Code OSS dev run logs and show me any errors in the renderer log.

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 dev build logs?▼

Code OSS dev logs live under $HOME/.vscode-oss-dev/logs/ by default, or <dir>/logs/ when launched with --user-data-dir. Each run creates a timestamped folder; list them with ls -lt and pick the most recent one.

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>/. Output channel logs from extensions are in the output_logging_<timestamp> folder inside exthost/.

Where are Copilot agent logs in Code OSS?▼

Copilot and agent issues are logged in agenthost.log at the session root and in window1/exthost/GitHub.copilot-chat/. In the Agents app, agent host IPC traffic appears in window1/output_<timestamp>/agenthost.*.log when tracing is enabled.

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

Console output only reaches log files when dev console forwarding is enabled via isDevConsoleLogForwardingEnabled in src/vs/platform/log/common/log.ts. Otherwise use ILogService for probes that must persist, since console.log may only appear in DevTools or stdout.

Why are some Code OSS log files empty?▼

Many log files are created empty and only populated when that subsystem produces output during the session. Use find with -size +0 to list only non-empty logs in a run before reading them.