skills.rest
jimeh
jimehCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

code-oss-logs

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

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

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 user data dir or a custom --user-data-dir. - File-to-Issue Mapping: Maps investigation targets (startup crashes, extension issues, Copilot/agent problems, MCP servers, terminals, network, sync) 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 reproducing a renderer crash in a Code OSS dev run, ask the assistant to pull the latest window1/renderer.log entries and search the run for error markers. ## Quick Start Ask the assistant to find the most recent Code OSS log folder and show the last 50 lines of the renderer log for the current dev run.

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, organized into timestamped folders per run. If you launched with --user-data-dir, look in <dir>/logs/ instead and pick the most recent folder by modification time.

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?▼

Agent-related activity is recorded in agenthost.log at the session root and in window1/exthost/GitHub.copilot-chat/ for the extension side. In the Agents app, IPC traffic appears in window1/output_<timestamp>/agenthost.*.log when tracing is enabled.

Why does my console.log not appear in Code OSS log files?▼

By default, console.log output only goes to DevTools or stdout, not the log files. You must temporarily enable dev console forwarding in src/vs/platform/log/common/log.ts, or use ILogService for probes that must persist.

Why are some Code OSS log files empty?▼

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

Related Skills

Explore More Software Engineering Skills→
posit-devposit-dev
4.2k

code-oss-logs

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

Official
Intermediate
MaaAssistantArknightsMaaAssistantArknights
22.4k

maa-issue-log-analysis

Analyze MaaAssistantArknights GitHub issue logs to diagnose root causes.

Official
Advanced
az0512124155azz-sysaz0512124155azz-sys

agent-host-logs

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

Community
Intermediate
chkp-ronizchkp-roniz
4

debugger

Diagnose Python bugs via MCPDebug breakpoints and runtime state inspection in VS Code.

Community
Advanced