VSCodium activity attributed to VS Code

[poli0iq]

This is a server-side user-agent parsing bug, same as #483 (Cursor attributed to VS Code). The client behaves correctly.

Observed behavior

All activity from VSCodium shows up on the dashboard as VS Code.

GET /api/v1/users/current/user_agents on my account shows:

{
  "ai_agent": null,
  "ai_agent_complexity": null,
  "ai_agent_version": null,
  "cli_version": "2.15.0",
  "created_at": "2026-07-20T15:20:01Z",
  "editor": "VS Code",
  "go_version": "1.26.4",
  "id": "d37bec04-0a26-47a0-a4e9-1654e7886714",
  "is_browser_extension": false,
  "is_desktop_app": false,
  "last_seen_at": "2026-07-21T12:18:23Z",
  "os": "Linux",
  "value": "wakatime/2.15.0 (linux-7.1.4-unknown) go1.26.4 vscodium/1.126.0 vscode-wakatime/30.2.1",
  "version": "30.2.1"
},

The extension itself is correct: the user agent above contains vscodium. The backend appears to derive the editor from the plugin token (vscode-wakatime -> VS Code) instead of the editor product token.

Expected behavior

Heartbeats with a vscodium/x.y.z product token attributed to VSCodium, with the editor token taking priority over the name derived from the plugin token.

Environment

• VSCodium 1.126.0, Linux
• vscode-wakatime 30.2.1
• wakatime-cli 2.15.0