chore: release v1.17.0

Bump package.json to 1.17.0 and cut the changelog's Unreleased section as
v1.17.0. Merge the two Fixed sections into one, and add the missing
entries for session app names (#1136), SSH tuning per provider (#1146),
and Windows include escaping (#1131).

Author: EhabY

CHANGELOG.md

@@ -5,7 +5,7 @@
      from published versions since it shows up in the VS Code extension changelog
      tab and is confusing to users. Add it back between releases if needed. -->
 
-## Unreleased
+## [v1.17.0](https://github.com/coder/vscode-coder/releases/tag/v1.17.0) 2026-10-13
 
 ### Added
 
@@ -18,6 +18,12 @@
   the socket never reaches a terminal failure. The extension keeps retrying until
   the server is reachable again.
 
+### Changed
+
+- Report the editor you connect from, such as Cursor or Windsurf, to Coder
+  for workspace session tracking. Requires Coder and the Coder CLI 2.38.0 or
+  later; older versions keep reporting `vscode`.
+
 ### Fixed
 
 - OAuth sign-in now works on deployments that enforce token scopes. Sessions
@@ -38,9 +44,6 @@
 - CLI commands and SSH connections that the extension starts ignore
   `CODER_SESSION_TOKEN` from the environment, so they no longer fail or run as a
   different user inside a Coder workspace.
-
-### Fixed
-
 - Run workspace app commands as arguments to `coder ssh` instead of typing them
   into a local terminal. This requires Coder CLI v2.23.0 or later.
 - Validate workspace, owner, and agent names from the deployment before using
@@ -61,6 +64,14 @@
   send them with `coder.headerCommand`.
 - Keep the stored URL of a deployment you are signed in to when a link names
   the same origin with a different path.
+- Apply the SSH connection settings in Devin Desktop (formerly Windsurf), which
+  reads them from `remote.devinSSH.*`, or `remote.windsurfSSH.*` on Windsurf
+  2.0 to 2.3, instead of `remote.SSH.*`. Each editor now gets only the
+  settings its Remote SSH extension reads, both on connect and in **Coder:
+  Apply Recommended SSH Settings**.
+- Escape glob characters in the SSH config `Include` path in a way OpenSSH for
+  Windows understands, so a config directory whose path contains `*`, `?`, or
+  `[` is included correctly on Windows.
 
 ## [v1.16.4](https://github.com/coder/vscode-coder/releases/tag/v1.16.4) 2026-09-23
 

package.json

@@ -1,7 +1,7 @@
 {
 	"name": "coder-remote",
 	"displayName": "Coder",
-	"version": "1.16.4",
+	"version": "1.17.0",
 	"description": "Open any workspace with a single click.",
 	"categories": [
 		"Other"