Locate and read timestamped process logs from Code OSS dev builds.
npx skills add https://github.com/basedgod55hjl/vsbrax --skill vsbrax-logs-basedgod55hjl
Please help me install this Agent Skill. Skill: vsbrax-logs Source: https://github.com/basedgod55hjl/vsbrax/tree/main/.github/skills/code-oss-logs Command: npx skills add https://github.com/basedgod55hjl/vsbrax --skill vsbrax-logs-basedgod55hjl
--user-data-dir paths. - 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 goals (startup crashes, extension issues, Copilot/agent problems, terminal or network errors) to the exact log files to read. - Console Forwarding Workflow: Explains how to temporarily enable dev console forwarding so console.log probes persist into normal log files, with a lint-hostile guard against accidental check-in. ## Quick Start Find the most recent Code OSS log folder and show me any errors in the renderer and extension host logs.High-intent search queries and answers about installing and using this skill.
Code OSS logs live under $HOME/.vsvsbrax-dev/logs/ in timestamped folders like 20260330T163430. Run ls -lt on the logs directory to find the most recent folder, or use the custom logs path if the app was launched with --user-data-dir.
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.
Agent-related activity is recorded in agenthost.log at the session folder root and in window1/exthost/GitHub.copilot-chat/. For the Agents app, agent host IPC traffic appears in window1/output_<timestamp>/agenthost.*.log when tracing is enabled.
Console output only reaches log files when dev console forwarding is enabled in src/vs/platform/log/common/log.ts. Without it, use ILogService for probes that must persist, since native console.log may only appear in DevTools or stdout.
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 investigating.
microsoftLocate and read timestamped process logs from Code OSS and Agents app dev builds.
millioncoInstrument code with NDJSON logs to debug issues via hypothesis testing.
posit-devLocate and read timestamped process logs from Code OSS dev builds.
openclawDebug Python code using pdb, breakpoint(), and debugpy remote attach.