GeezerVison

Summary

Connection logs now record how a connection was made (connection_method) separately from which app made it (app_name), as specified in the Completing Scalable IDE Session Tracking RFC. Storage, the HTTP API, search filters, and the UI move to the new fields. Legacy agent reports and the deprecated type field keep working.

What changes

API: GET /api/v2/connectionlog

• connection_method (new): ssh, reconnecting_pty, workspace_app, port_forwarding, or tunnel.
• app_name, app_display_name (new, optional): the self-reported name of the connecting app, such as cursor. Workspace app slugs and ports stay in web_info.slug_or_port.
• type (deprecated): now a plain string, so new methods pass through. The Go SDK's ConnectionLog.Type becomes a string.

{"type": "vscode", "connection_method": "ssh", "app_name": "cursor", "app_display_name": "Cursor"}

Search filters

method: and app: intersect, like the existing owner filters. type: can't be combined with method: or app:. List and count always agree.

UI

• The Type menu becomes a Method menu. Picking a method drops a leftover type: from old links.
• A warning appears when the filter contains the deprecated type:.
• Behavior change: the Active SSH connections preset now uses method:ssh instead of type:ssh, so it also includes SSH sessions from VS Code and JetBrains apps.
• Rows show the app next to the method, for example "Cursor (SSH) session to …".

SDK

• codersdk.ConnectionLogMethod is generated from the database enum by typegen dbenums instead of being maintained by hand.

Docs

• The filter docs cover method: and app:, and include a table for replacing each type: value.

Upgrade impact

Migration 617 rewrites connection_logs under an ACCESS EXCLUSIVE lock.

• vscode and jetbrains rows become ssh rows with app vscode or jetbrains. Other rows keep their method and have no app.
• Rollback folds apps back into the old types, so per-app names are lost. Apps registered after this migration roll back to ssh.

Single runs on indexed PostgreSQL 13 with 2 CPUs and 6 GB, excluding lock waits. Not a deployment guarantee.

Design decisions

• Why keep type:? It has shipped since v2.25.0, the old Type menu wrote it into page URLs, and the old "Active SSH connections" preset used type:ssh. Removing it would break saved links and scripts.
• When does it go away? In a future release, together with the type response field and excluded_app_names. Both follow one rule (db2sdk.ConnectionLogType), so there is no separate invariant to maintain.
• Why excluded_app_names? Only type:ssh needs it. It means SSH outside the VS Code and JetBrains families, including connections with no reported app.
• Why can't type: combine with the new filters? Old clients only send type:, and mixing a legacy alias with its replacements has no useful meaning.
• Why no family: filter? It could never be complete, because new forks can show up before they're in the registry, and several family values would match nothing. A repeatable app: covers the same need.
• Why are app filters limited to SSH and reconnecting PTY? app: matches what the response returns in app_name. Other methods store a destination slug or port in the same column, which belongs in separate workspace_app: and port: filters (follow-up).

Stack

Land #30466 → #30467. #30467 adds explicit agent reporting on top of this PR. The insights stack (#30497 → #29796 → #29906) is independent. Replaces #29674.

Generated with Coder Agents on behalf of @EhabY.