You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: collect remote editor logs in support bundles (#1042)
Support bundles now include the remote editor server's logs alongside the
local Remote-SSH and Coder proxy logs. Remote files are passed through the
CLI's repeatable `--workspace-file` flag, gated to Coder 2.36.0+.
- Resolve the server data directory from `remote.SSH.serverInstallPath` for
the workspace's SSH host, falling back to `~/{serverDataFolderName}` from
the editor's `product.json`. No remote connection needed.
- Handle each Remote-SSH fork's convention: parent directory for Microsoft
and Cursor, final data directory for Open Remote SSH (with exact >
wildcard > `*` precedence), home default for Windsurf and Antigravity.
- Collect three known layouts: `data/logs/**/*.log`, `.*.log`, and
`cli/servers/*/log.txt`. Both startup layouts are included rather than
gated on `remote.SSH.useExecServer`, which can change after connection.
- Omit remote logs rather than scan broad paths or pass unresolved
environment variables.
- Pass the selected agent to `coder support bundle`, reconstructing the SSH
authority from workspace metadata when not connected so sidebar, picker,
and palette flows resolve identically.
- Add `raceWithAbort` to keep glob resolution cancellable, since the VS Code
resolution APIs take no signal.
0 commit comments