|
5 | 5 | from published versions since it shows up in the VS Code extension changelog |
6 | 6 | tab and is confusing to users. Add it back between releases if needed. --> |
7 | 7 |
|
8 | | -## Unreleased |
| 8 | +## [v1.17.0](https://github.com/coder/vscode-coder/releases/tag/v1.17.0) 2026-10-13 |
9 | 9 |
|
10 | 10 | ### Added |
11 | 11 |
|
|
18 | 18 | the socket never reaches a terminal failure. The extension keeps retrying until |
19 | 19 | the server is reachable again. |
20 | 20 |
|
| 21 | +### Changed |
| 22 | + |
| 23 | +- Report the editor you connect from, such as Cursor or Windsurf, to Coder |
| 24 | + for workspace session tracking. Requires Coder 2.38.0 or later; older |
| 25 | + versions keep reporting `vscode`. |
| 26 | + |
21 | 27 | ### Fixed |
22 | 28 |
|
23 | | -- OAuth sign-in now works on deployments that enforce token scopes. Sessions |
24 | | - missing required scopes stop refreshing and require sign-in when they expire. |
| 29 | +- OAuth sign-in is offered only when the deployment enables Coder's OAuth2 |
| 30 | + provider and allows dynamic client registration, which is off by default |
| 31 | + from Coder 2.37; otherwise a notice says sign-in uses a session token. OAuth |
| 32 | + becomes the default sign-in method in a future release, so ask your Coder |
| 33 | + administrator to enable them. For instructions, see |
| 34 | + [OAuth2 provider](https://coder.com/docs/admin/integrations/oauth2-provider). |
| 35 | +- OAuth sign-in now works on deployments that enforce token scopes, and |
| 36 | + requests the permissions needed to refresh workspace external-auth links. |
| 37 | + Sessions missing required scopes stop refreshing and require sign-in when |
| 38 | + they expire. |
| 39 | +- Preserve OAuth refresh credentials when reusing a stored token. |
25 | 40 | - Revoke OAuth tokens on logout and after successful session replacement, even |
26 | 41 | when their scopes are outdated. Failed or canceled sign-ins do not revoke |
27 | 42 | the stored session. |
28 | | -- Preserve OAuth refresh credentials when reusing a stored token, and request |
29 | | - the permissions needed to refresh workspace external-auth links. |
30 | | -- OAuth sign-in is offered only when the deployment allows dynamic client |
31 | | - registration, which is off by default from Coder 2.37; otherwise a notice |
32 | | - says sign-in uses a session token. OAuth becomes the default sign-in method |
33 | | - in a future release, so ask your Coder administrator to enable dynamic client |
34 | | - registration. For instructions, see |
35 | | - [OAuth2 provider](https://coder.com/docs/admin/integrations/oauth2-provider). |
36 | 43 | - Keep session tokens, OAuth tokens, and client secrets out of the Coder output |
37 | 44 | channel and its buffered logs, including from failed requests. |
38 | 45 | - CLI commands and SSH connections that the extension starts ignore |
39 | | - `CODER_SESSION_TOKEN` from the environment, so they no longer fail or run as a |
40 | | - different user inside a Coder workspace. |
41 | | - |
42 | | -### Fixed |
43 | | - |
| 46 | + `CODER_SESSION_TOKEN` from the environment and use your stored session, so |
| 47 | + they no longer fail or run as a different user when that variable is set. |
44 | 48 | - Run workspace app commands as arguments to `coder ssh` instead of typing them |
45 | 49 | into a local terminal. This requires Coder CLI v2.23.0 or later. |
46 | 50 | - Validate workspace, owner, and agent names from the deployment before using |
|
61 | 65 | send them with `coder.headerCommand`. |
62 | 66 | - Keep the stored URL of a deployment you are signed in to when a link names |
63 | 67 | the same origin with a different path. |
| 68 | +- Apply the SSH connection settings in Devin Desktop (formerly Windsurf), which |
| 69 | + reads them from `remote.devinSSH.*`, or `remote.windsurfSSH.*` on Windsurf |
| 70 | + 2.0 to 2.3, instead of `remote.SSH.*`. Each editor now gets only the |
| 71 | + settings its Remote SSH extension reads, both on connect and in **Coder: |
| 72 | + Apply Recommended SSH Settings**. |
| 73 | +- Escape glob characters in the SSH config `Include` path in a way OpenSSH for |
| 74 | + Windows understands, so a config directory whose path contains `*`, `?`, or |
| 75 | + `[` is included correctly on Windows. |
64 | 76 |
|
65 | 77 | ## [v1.16.4](https://github.com/coder/vscode-coder/releases/tag/v1.16.4) 2026-09-23 |
66 | 78 |
|
|
0 commit comments