1. What data is processed
- Editor activity metadata such as workspace name, folder paths, active language, and file-save events.
- Code change counts (line additions/removals) and timing used for productivity timeline correlation.
- AI tooling usage signals, including Copilot focus duration and inline completion estimates when detectable.
- Optional model-level metadata in Precision Mode, when the VS Code runtime API surface allows it.
- Claude transcript change events from local JSONL files under
~/.claude/projects/....
2. Where data is stored
The extension stores operational state in VS Code extension storage and sends selected
events to your local WorqLog application for timeline merging. Core bridge transport is
local only and uses the Unix socket path ~/Library/Application Support/WorqLog/bridge.sock.
3. Transport model
- Primary transport is local machine communication to the WorqLog app.
- The extension is designed to avoid intentional transmission of full file contents over the bridge protocol.
- Terminal command payloads are truncated before transmission.
- If the app is not running, the extension remains active and retries connection automatically.
- No WorqLog cloud account is required for core local telemetry flow.
- Any third-party transfer depends on optional user-enabled integrations.
4. User controls
- You can disable or uninstall the extension at any time.
- You can clear extension storage through VS Code and app-level reset tools.
- You can opt out of optional precision telemetry modes by disabling
worqlog.precisionMode. - You can tune local file polling behavior with
worqlog.claudeWatchInterval. - You can inspect extension events using the command
WorqLog: Show Activity Log.
5. Requirements and compatibility
- Supported operating system: macOS.
- Requires WorqLog macOS app installed and running.
- Requires VS Code version 1.107.0 or newer.