skills.rest
az0512124155azz-sys
az0512124155azz-sysCOMMUNITY
Explore all skills by this author →
GitHub

code-oss-logs

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

Updated Sep 3, 2026
Search Tags:#vscode#debugging#troubleshooting#logging#log analysis#code oss#dev build
One-click install
npx skills add https://github.com/az0512124155azz-sys/CodeForge --skill code-oss-logs-az0512124155azz-sys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-oss-logs
Source: https://github.com/az0512124155azz-sys/CodeForge/tree/main/.github/skills/code-oss-logs
Command: npx skills add https://github.com/az0512124155azz-sys/CodeForge --skill code-oss-logs-az0512124155azz-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When debugging Code OSS or Agents app dev builds, logs are scattered across timestamped folders with many process-specific files, making it hard to find the right log for the issue 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-Issue Mapping: Maps investigation targets (startup crashes, extension issues, MCP servers, terminals, agent host) to the exact log files to read. - Console Forwarding Workflow: Documents how to temporarily enable dev console forwarding so console.log probes persist into normal log files. - Use Case: After a failed Code OSS launch, ask the assistant to inspect the latest run; it locates the newest timestamped folder and reads main.log and window1/renderer.log to surface the error. ## Quick Start Find the most recent Code OSS dev run logs and show me any errors in the renderer and main process 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 dev build logs?▼

Code OSS dev logs live under $HOME/.vscode-oss-dev/logs/, with each run creating a timestamped folder like 20260330T163430. If you launched with --user-data-dir, look in <dir>/logs/ instead, and sort by modification time to find the latest run.

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>/. Extension output channels are captured in the output_logging_<timestamp> folder inside exthost/.

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

Native console.log only appears in DevTools or stdout unless dev console forwarding is enabled. Enable isDevConsoleLogForwardingEnabled in src/vs/platform/log/common/log.ts, or use ILogService for probes that must persist in log files.

Does Code OSS create separate logs for each window?▼

Yes, each window gets its own folder such as window1/ and window2/ containing renderer.log, network.log, and exthost logs. Session-level files like main.log and sharedprocess.log sit at the root of the timestamped run folder.

What are the limitations of reading Code OSS log files?▼

Many log files are created empty and only populated when that subsystem produces output. Window reloads also create new output_<timestamp> folders, so older reload logs may be split across multiple directories within one session.

Related Skills

Explore More Software Engineering Skills→
microsoftmicrosoft
190.1k

code-oss-logs

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

Official
Intermediate
vobbilisvobbilis
1

nexus-db-debugging

Reproduce nexus-db errors from logs and verify X-Scope-OrgID headers.

Community
Advanced
microsoftmicrosoft
190.1k

agent-host-logs

Analyze Agent Host debug log bundles for VS Code sessions.

Official
Advanced
SethyPagnaSethyPagna

python-debugpy

Attach interactive debuggers to Python processes for breakpoint-driven tracing.

Community
Advanced