Use distinct buckets for VS Code-compatible editors

[johnyoonh]

Summary

Adds runtime detection for VS Code-compatible editors so their ActivityWatch heartbeats use distinct client and bucket names instead of all writing to aw-watcher-vscode_<hostname>.

Known mappings:

• VS Code: aw-watcher-vscode
• VSCodium: aw-watcher-vscodium
• Cursor: aw-watcher-cursor
• Antigravity: aw-watcher-antigravity

Why

VS Code-compatible editors can run this extension, but when multiple compatible editors are installed on the same machine, their project/file activity currently shares the same bucket. That mixes separate editor activity streams and makes ActivityWatch timelines harder to interpret.

Default VS Code behavior is preserved via the fallback to aw-watcher-vscode.

Validation

• npm run compile
• npm run test:mocha (completed; current test target reports 0 tests)

[Copilot]

Pull request overview

Adds runtime detection of VS Code-compatible editors so ActivityWatch heartbeats are written under distinct clientName/bucket IDs per editor, preventing activity streams from overlapping on the same machine.

Changes:

• Introduces activityWatchClientName() based on vscode.env.appName and uses it for both AWClient and bucket naming.
• Documents the per-editor client/bucket naming behavior in the README.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/extension.ts	Derives a per-editor ActivityWatch client name and applies it to bucket ID and AWClient initialization.
README.md	Documents distinct client/bucket names for known VS Code-compatible editors.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.