What is code-oss-logs?

A guide for finding and reading timestamped logs from Code OSS development builds and the Agents app. Logs are text records of what a program and its parts did while running.

Use it to inspect recent startup, runtime, or extension-related events in files such as main.log, renderer.log, extension host logs, and agenthost.log. It also explains where logs are stored when the app uses a custom data directory.

It removes the need to search through several dated folders and guess which log belongs to the latest run. It helps focus on the main process, renderer, extension host, or agent host involved in a problem.

How microsoft/vscode configures Claude Code and Codex

About the project

Visual Studio Code is a code editor that supports editing, navigating, understanding, debugging, and extending software projects. Developers use it for the edit-build-debug cycle, and the catalogue add-ons provide skills, instructions, and agents for working within the editor.

microsoft/vscode · 193,657 stars · on GitHub · code.visualstudio.com

Reuse

Borrowing it

Nothing to install: this file belongs to microsoft/vscode. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/microsoft/vscode/main/.github/skills/code-oss-logs/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/microsoft/vscode

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/microsoft/vscode/code-oss-logs/github.svg)](https://agentmods.dev/skills/microsoft/vscode/code-oss-logs)

Your own site

<a href="https://agentmods.dev/skills/microsoft/vscode/code-oss-logs"><img src="https://agentmods.dev/badge/skills/microsoft/vscode/code-oss-logs/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/microsoft/vscode/code-oss-logs"><img src="https://agentmods.dev/badge/skills/microsoft/vscode/code-oss-logs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,954 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

Snyk pass 6 Sept 2026
NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00051	$0.01954
Opus 5.5	$0.00020	$0.00782
Sonnet 5.5	$0.00010	$0.00391
Haiku 4.5	$0.00005	$0.00195

Measured 13d ago against content hash 956a891b7b8b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

code-oss-logs scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/skills/code-oss-logs/SKILL.md · 137 lines

How it starts

The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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

Identify which app the user is asking about: Code OSS or Agents app. If unclear, check both.

Find the most recent log folder:

ls -lt "$HOME/.vscode-oss-dev/logs" | head -5
# or for a custom user data dir:
ls -lt "<user-data-dir>/logs" | head -5

Navigate into the most recent folder and list contents.
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:

<timestamp>/
├── main.log                    # Electron main process (app lifecycle, window management)
├── agenthost.log               # Agent host process (Copilot agent, model listing, agent sessions)
├── mcpGateway.log              # MCP gateway/server coordination
├── sharedprocess.log           # Shared process (extensions gallery, global services)
├── telemetry.log               # Telemetry events
├── terminal.log                # Terminal/pty activity
├── ptyhost.log                 # Pty host process
├── network-shared.log          # Shared network activity
├── editSessions.log            # Edit sessions / cloud changes
├── userDataSync.log            # Settings sync
├── remoteTunnelService.log     # Remote tunnel service
│
└── window1/                    # Per-window logs (window1, window2, etc.)
    ├── renderer.log            # Renderer process (workbench UI, services, startup)
    ├── network.log             # Per-window network activity
    ├── views.log               # View/panel activity
    ├── notebook.rendering.log  # Notebook rendering
    ├── customizationsDebug.log # Agent customizations debug info (Agents app)
    ├── mcpServer.*.log         # Per-MCP-server logs (one file per configured server)
    │
    ├── exthost/                # Extension host logs
    │   ├── exthost.log         # Extension host main log (activation, errors)
    │   ├── extHostTelemetry.log
    │   ├── <publisher.extension>/  # Per-extension log folders
    │   │   └── <extension>.log
    │   └── output_logging_<timestamp>/  # Extension output channels
    │
    └── output_<timestamp>/     # Output channel logs (workbench side)
        ├── tasks.log           # Tasks output
        ├── agentSessionsOutput.log  # Agent sessions output (Agents app)
        └── agenthost.<clientId>.log  # Agent host IPC traffic when tracing is enabled

Read the full file on GitHub · 137 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

13d ago Changed · +6 lines 956a891b7b8b
1mo ago First seen · 131 lines · 51 tokens per session scan A 277bebda0d9f

Subscribe to this mod's changes

code-oss-logs is a skill published in the GitHub repository microsoft/vscode (193,657 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 1,954 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Debugging TypeScript editor electron microsoft visual-studio-code

vscode: Skill for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Code OSS Logs

Log Root Directories

Procedure

Directory Layout

What this file has done since we first saw it

Other skills, from other repositories

javascript-sandbox

Debug

investigate

repro-admin

repro-public

verify