Skip to content

Extend the session app registry with JetBrains products and VS Code fork aliases #29928

Description

@EhabY

sessionApps in codersdk/appname.go is missing keys that the IDE clients will start reporting (coder/vscode-coder#1044, coder/jetbrains-coder#599). A name absent from the registry is stored correctly but classified as AppFamilyUnknown, which fragments family aggregates, the family-labeled Prometheus gauge and the legacy session_count_* fields.

Add them up front so the server is ready before either client change, and so a client build can be gated on a release rather than on a registry entry. Independent of both client issues.

JetBrains products (AppFamilyJetBrains)

The keys are what the plugin derives from the JetBrains product code. One key per editor — editions are not distinguished.

App name Display name Product codes
intellij IntelliJ IDEA IU, IC, IE
pycharm PyCharm PY, PC, PE
goland GoLand GO
webstorm WebStorm WS
phpstorm PhpStorm PS
rubymine RubyMine RM
clion CLion CL
rider Rider RD
rustrover RustRover RR
datagrip DataGrip DB
dataspell DataSpell DS
mps MPS MPS
android_studio Android Studio AI

The name identifies the editor, not the licence tier, so there is no intellij_ultimate or pycharm_community. This also avoids a naming trap: from 2025.3 (build 253) JetBrains ships one unified IntelliJ IDEA reporting IU and one unified PyCharm reporting PY, with paid features unlocked by licence rather than by a separate download, so IC and PC are no longer published (SDK docs). Edition-suffixed keys would mislabel users on current builds and fade out unevenly on older ones. Only IDEA and PyCharm ever had an edition split — every other product keeps a distinct product code, so editor identity is preserved.

Aqua (QA) is omitted: JetBrains' docs list it as removed as a target platform.

VS Code forks (AppFamilyVSCode)

The extension reports vscode.env.uriScheme verbatim, with - folded to _ by NormalizeAppName:

App name Display name Source scheme
code_oss Code - OSS code-oss (verified in microsoft/vscode product.json)
vscodium_insiders VSCodium Insiders vscodium-insiders (verified in VSCodium's prepare_vscode.sh)
trae_cn Trae CN trae-cn
devin_next Devin Desktop Next devin-next (verified in the app's product.json)

vscode-exploration is deliberately excluded: it is a Microsoft-internal build, and an unknown row for it costs nothing.

Keep

jetbrains and windsurf stay in the registry. jetbrains is what historical rows and older plugin builds use. windsurf is likewise historical and still live: it is the urlProtocol of pre-rename Windsurf installs, which report it verbatim.

devin needs no mapping — current Devin Desktop builds register it natively ("urlProtocol": "devin"; the old windsurf protocol survives only as oldUrlProtocol, which the extension API does not expose). Keep its display name "Devin Desktop", and keep "Windsurf" on windsurf so the two eras stay legible.

Icons can follow later; an empty icon is already supported.

Done when

  • AppNameFamily returns the right family for every name above
  • A goland session rolls into the JetBrains family in the deployment stats legacy field and the family-labeled metric, and shows "GoLand" in the deployment banner
  • The same holds for code_oss under the VS Code family

Related: coder/vscode-coder#1044, coder/jetbrains-coder#599, #27411.


🤖 Created by Coder Agents on behalf of @EhabY. Updated: JetBrains editions collapsed to one key per editor (intellij, pycharm); devin/devin-next confirmed as native schemes.

Activity

  1. added theissue type on Sep 25, 2026
  2. linear-code commented on Sep 25, 2026

    @linear-code
  3. changed the title [-]Add JetBrains product names to the session app registry[/-] [+]Extend the session app registry with JetBrains products and VS Code fork aliases[/+] on Sep 25, 2026
  4. added a commit that references this issue on Sep 29, 2026
    0285a3c
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions