Locate and read timestamped process logs from Code OSS dev builds.
npx skills add https://github.com/Niiihuel/openide --skill code-oss-logs-niiihuel
Please help me install this Agent Skill. Skill: code-oss-logs Source: https://github.com/Niiihuel/openide/tree/main/vscode/.github/skills/code-oss-logs Command: npx skills add https://github.com/Niiihuel/openide --skill code-oss-logs-niiihuel
--user-data-dir. - File-to-Problem Mapping: Maps investigation targets (startup crashes, extension issues, agent host, MCP servers, terminals, network) 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 dev build, use this Skill to locate the latest session folder and read window1/renderer.log and main.log for the error. ## Quick Start Find the most recent Code OSS dev run logs and show me any errors in the renderer log.High-intent search queries and answers about installing and using this skill.
Code OSS dev logs live under $HOME/.vscode-oss-dev/logs/, organized into timestamped folders like 20260330T163430. If the app was launched with --user-data-dir, look in <dir>/logs/ instead, and pick the most recent folder by modification time.
Extension host errors appear in window1/exthost/exthost.log, with per-extension logs under window1/exthost/<publisher.extension>/. For Copilot or agent issues, also check agenthost.log and the GitHub.copilot-chat extension folder.
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.
A new output_<timestamp>/ folder is created each time the window reloads within the same session. The most recent output_ folder holds logs for the current reload, while earlier ones contain logs from prior reloads in that session.
Use ripgrep across the timestamped session folder, for example rg -n "MY_PROBE|error" <timestamp>, to search every log file at once. You can also run find <timestamp> -type f -size +0 to list only non-empty logs.
microsoftLocate and read timestamped process logs from Code OSS and Agents app dev builds.
StiensGate928Diagnose failing commands, patch root causes, and verify with narrow rechecks.
TyrizxAnalyze Agent Host debug log bundles to diagnose Copilot session failures.
SethyPagnaAttach interactive debuggers to Python processes for breakpoint-driven tracing.