Skip to content

feat: collect VS Code diagnostics in support bundles#971

Open
EhabY wants to merge 1 commit into
mainfrom
feat/support-bundle-diagnostics
Open

feat: collect VS Code diagnostics in support bundles#971
EhabY wants to merge 1 commit into
mainfrom
feat/support-bundle-diagnostics

Conversation

@EhabY
Copy link
Copy Markdown
Collaborator

@EhabY EhabY commented May 21, 2026

Summary

  • add vscode-logs/settings.json with inspect-style coder.* / remote.* settings and redaction for coder.headerCommand and coder.binarySource
  • store the active Coder SSH proxy log as vscode-logs/proxy/active.log while keeping recent proxy logs under vscode-logs/proxy/
  • collect actual Remote-SSH logs and recent cross-session Coder extension logs under stable session/window paths
  • split support bundle diagnostics into src/supportBundle/ modules for ZIP mutation, log discovery, and settings collection

Follow-up

Tests

  • pnpm format:check
  • pnpm lint
  • pnpm typecheck
  • pnpm test:extension ./test/unit/supportBundle/appendVsCodeLogs.test.ts
  • pnpm test:extension

Closes #955.
Refs #970.

Generated by Coder Agents.

@EhabY EhabY force-pushed the feat/support-bundle-diagnostics branch from 6a3af1c to c3c4c49 Compare May 21, 2026 15:21
@EhabY EhabY self-assigned this May 21, 2026
@EhabY EhabY force-pushed the feat/support-bundle-diagnostics branch 4 times, most recently from 7ee04f1 to 9f7c4e5 Compare May 22, 2026 13:14
@EhabY EhabY force-pushed the feat/support-bundle-diagnostics branch from 9f7c4e5 to 76e7ff2 Compare May 22, 2026 13:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Capture more diagnostic context in support bundle and prompt to create one on Reload Window

1 participant