$ loading_
帮助开发者定位并读取 Code OSS 开发构建日志，快速排查运行与扩展问题。
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "code-oss-logs" 技能： 1. 下载 https://raw.githubusercontent.com/microsoft/vscode/main/.github/skills/code-oss-logs/SKILL.md 2. 保存为 ~/.claude/skills/code-oss-logs/SKILL.md 3. 装好后重载技能，告诉我可以用了
请帮我查找 Code OSS 开发构建中的 extension host 日志，定位最近一次报错，并总结错误时间、关键信息和可能原因。
返回相关日志位置、最近报错片段，以及对问题原因的简要分析。
读取 Code OSS 开发构建的 renderer logs，查找启动后界面卡顿或报错的线索，并按时间顺序整理出来。
输出按时间排序的关键日志事件，并指出可能导致界面异常的记录。
请检查 Code OSS 开发构建中的 main process、renderer、agent host 日志，找出同一问题在不同进程中的关联线索，并给出排查建议。
生成一份跨日志来源的问题汇总，包含关联证据与下一步排查建议。
Find and display logs from the most recent Code OSS or Agents app dev run.
| 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.
ls -lt "$HOME/.vscode-oss-dev/logs" | head -5
# or for a custom user data dir:
ls -lt "<user-data-dir>/logs" | head -5
tail for recent entries or rg to filter.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
output_ FoldersA new output_<timestamp>/ folder and a corresponding output_logging_<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.
| Investigating... | Check these files |
|---|---|
| App startup / crashes | main.log, window1/renderer.log |
| Extension issues | window1/exthost/exthost.log, window1/exthost/<publisher.ext>/ |
…
帮助开发者验证 Azure DevOps 流水线改动，快速排查构建与 YAML 配置问题。
帮助开发者在 VS Code 仓库中运行并筛选集成测试，区分不同测试类型。