Follow-up to AIGOV-193.
The current "Create Support Bundle" command shells out to coder support bundle, which only collects server-side diagnostics. It would be useful to also include VS Code-side logs so support has the full picture.
Logs to include
When the user is connected to the workspace:
- Remote SSH extension logs - path discovered by
SshProcessMonitor (only available while connected)
- SSH proxy logs - tracked via
proxyLogDir in PathResolver
- Coder extension output channel logs - the extension's own log output
When not connected, the bundle contains only the CLI-collected data (current behavior). The VS Code logs are appended as a best-effort addition.
These would go under a vscode-logs/ folder inside the existing zip.
Scrubbing
The extension already redacts sensitive headers (Coder-Session-Token, Proxy-Authorization) in formatters.ts before writing to the output channel, so the logs should be safe to include.
The Coder CLI's own docs note that support bundles may still contain info deemed sensitive by your organization. The same caveat applies here.
Approach options
A) Only include SSH proxy logs. These are generated by the Coder CLI proxy itself, lowest risk. Simple to implement since proxyLogDir is already tracked.
B) Include all three log sources. More useful for support but requires accessing the Remote SSH log path (only available while connected) and the extension's log file on disk.
C) Skip for now. Defer until there's a clear need from support cases.
Files to change
src/commands.ts - post-process the zip after CLI produces itpackage.json - add zip manipulation dependency if needed
Part of AIGOV-193.
Follow-up to AIGOV-193.
The current "Create Support Bundle" command shells out to
coder support bundle, which only collects server-side diagnostics. It would be useful to also include VS Code-side logs so support has the full picture.Logs to include
When the user is connected to the workspace:
SshProcessMonitor(only available while connected)proxyLogDirinPathResolverWhen not connected, the bundle contains only the CLI-collected data (current behavior). The VS Code logs are appended as a best-effort addition.
These would go under a
vscode-logs/folder inside the existing zip.Scrubbing
The extension already redacts sensitive headers (
Coder-Session-Token,Proxy-Authorization) informatters.tsbefore writing to the output channel, so the logs should be safe to include.The Coder CLI's own docs note that support bundles may still contain info deemed sensitive by your organization. The same caveat applies here.
Approach options
A) Only include SSH proxy logs. These are generated by the Coder CLI proxy itself, lowest risk. Simple to implement since
proxyLogDiris already tracked.B) Include all three log sources. More useful for support but requires accessing the Remote SSH log path (only available while connected) and the extension's log file on disk.
C) Skip for now. Defer until there's a clear need from support cases.
Files to change
src/commands.ts- post-process the zip after CLI produces itpackage.json- add zip manipulation dependency if neededPart of AIGOV-193.