WorqLog for VS Code

WorqLog for VS Code connects editor activity to the WorqLog macOS app so your coding sessions can be reflected in one timeline.

This extension is designed to work with the WorqLog desktop bridge and sends lightweight activity signals (not full file contents) over a local Unix socket.

Features

• Live connection indicator in the status bar.
• Automatic reconnect to the local WorqLog macOS bridge.
• Workspace metadata sync (workspace name, folders, VS Code version, Copilot availability).
• Passive coding telemetry for AI-assisted sessions, including:
  • Copilot chat focus duration (when detectable through tab/webview state)
  • Inline completion character estimates
  • File save count and line add/remove deltas
  • Optional Copilot model discovery in Precision Mode
• Claude Code transcript tracking from local JSONL files under ~/.claude/projects/....
• Terminal AI tool detection for common tool commands (for example: claude, aider, cursor, continue, sgpt, codeium, tabby).
• Built-in output log channel for diagnostics.

Requirements

• macOS
• WorqLog macOS app installed and running
• VS Code 1.107.0 or newer

The extension sends data to a local socket at:

~/Library/Application Support/WorqLog/bridge.sock

If the macOS app is not running, the extension remains active and keeps retrying automatically.

Getting Started

1. Install the extension from the Marketplace.
2. Start the WorqLog macOS app.
3. Open any folder or workspace in VS Code.
4. Confirm the status bar shows WorqLog as connected.

Click the status bar item to open the WorqLog output channel.

Commands

• WorqLog: Show Activity Log (worqlog.showLog)

Extension Settings

This extension contributes the following settings:

• worqlog.precisionMode (boolean, default: false)
  • Enables additional model-level telemetry via the VS Code Language Model API when available.
• worqlog.claudeWatchInterval (number, default: 5000, min: 1000, max: 30000)
  • Polling interval in milliseconds for Claude transcript file change detection.

Privacy

WorqLog for VS Code is designed for low-footprint activity signaling.

• Sent data includes activity metrics and metadata such as counts, durations, language IDs, model IDs (when available), and workspace folder paths.
• The extension does not intentionally transmit full file contents over the WorqLog bridge protocol.
• Terminal command payloads are truncated before transmission.
• Claude transcript parsing is local and event-based; only aggregated activity details are forwarded.

Review your organization's policy requirements before enabling any telemetry tooling.

Troubleshooting

If WorqLog stays disconnected:

1. Verify the WorqLog macOS app is running.
2. Confirm the socket path exists at ~/Library/Application Support/WorqLog/bridge.sock.
3. Open WorqLog: Show Activity Log and check recent connection events.
4. Reload the VS Code window.

If Claude activity is not detected:

1. Ensure Claude Code is writing transcript files under ~/.claude/projects/....
2. Increase worqlog.claudeWatchInterval if your environment has delayed file change events.

Known Limitations

• Some activity signals are heuristic by design and may vary by VS Code API behavior.
• Copilot model/token visibility depends on API availability and extension/runtime state.
• This extension currently supports the WorqLog local bridge flow on macOS.

License

MIT

Automated Publishing (GitHub Actions)

This repository includes a workflow at .github/workflows/publish-marketplace.yml.

When a GitHub Release is published, the workflow will:

1. Install dependencies
2. Run lint + typecheck
3. Build and package the VSIX
4. Verify release tag matches package.json version
5. Publish to VS Code Marketplace

Required repository secret:

• VSCE_PAT: Personal Access Token with Marketplace publish permissions

Release tag format:

• vX.Y.Z (recommended)
• X.Y.Z (also accepted)

The tag version must match the version in package.json.