Agent skill · data analytics · microsoft
code-oss-logs
Find and read timestamped process logs from Code OSS dev builds, including main.log, renderer.log, extension host logs, and agenthost.log. For bundles produced by Export Agent Host Debug Logs, use agent-host-logs.
Why this skill is useful
Provides specific commands and procedures for accessing and interpreting logs from Code OSS and Agents app, which the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-07. 188,455 stars on the source repository.
What this skill does
Code OSS Logs Find and display logs from the most recent Code OSS or Agents app dev run. Log Root Directories Launch Default User Data Dir Logs Path ----- ----------------------- ----------- scripts/code.sh code-oss-dev in the platform app-data dir (~/Library/Application Support on macOS, ~/.config on Linux, %APPDATA% on Windows) <dir>/logs/ .vscode/launch.json $HOME/.vscode-oss-dev $HOME/.vscode-oss-dev/logs/ If Code OSS was launched with --user-data-dir=<dir>, use <dir>/logs/ instead of the defaults above. Launch and debugging helpers often create temporary user data dirs under .build/; always prefer the exact user data dir from the launch command when it is known. Each run creates a timestamped folder like 20260330T163430. The most recent folder sorted by modification time is usually the one the user cares about. Procedure 1. Identify which app the user is asking about: Code OSS or Agents app. If unclear, check both. 2. Find the most recent log folder: 3. Navigate into the most recent folder and list contents. 4. Read the relevant log file(s) based on what the user is investigating. Use tail for recent entries or rg to filter. Directory Layout Each timestamped log folder has this structure: Multiple output Folders A new output<timestamp>/ folder and a corresponding outputlogging<timestamp>/ inside exthost/ is created each time the window reloads within the same session. The session-level timestamped folder, such as 20260330T163430/, stays the same, but each reload gets fresh output channel directories. The most recent output folder by timestamp has the logs for the current or latest reload. Earlier folders contain logs from prior reloads in that session. Cloud Sandbox Startup Failures Start with renderer.log. [CloudSandboxApi] connect/reconnect HTTP failures record status, elapsed time, environment/session/client IDs when available, and a validated requestId from X-GitHub-Request-Id. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills microsoft/code-oss-logs