← ClaudeAtlas

code-oss-logslisted

Find and read logs from Code OSS dev builds. Use when: finding logs, reading log files, debugging Code OSS, checking renderer logs, extension host logs, agent host logs, main process logs, investigating errors in dev builds.
Pointa-Labs/basehalf · ★ 15 · AI & Automation · score 73
Install: claude install-skill Pointa-Labs/basehalf
# Code OSS Logs Find and display logs from the most recent Code OSS or Agents app dev run. ## Log Root Directories | App | Default User Data Dir | Logs Path | |-----|-----------------------|-----------| | Code OSS | `$HOME/.vscode-oss-dev` | `$HOME/.vscode-oss-dev/logs/` | | Agents app | `$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**: ```bash ls -lt "$HOME/.vscode-oss-dev/logs" | head -5 # or for a custom user data dir: ls -lt "<user-data-dir>/logs" | head -5 ``` 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: ```text <timestamp>/ ├── main.log # Electron main process (app lifecycle, window management) ├── agenthost.log # Agent host pr