Track the work where it happens.
Connect one seat key to VS Code, Claude Code, or Codex. Each tracker reports session metadata such as project, branch, language, timestamps, and duration. QuarryFi does not receive source code, diffs, file contents, keystrokes, or conversation transcripts.
Development trackers are a Core feature. Free accounts can explore QuarryFi before upgrading, but they cannot generate tracker keys or send accepted heartbeats.
VS Code
Current release 0.4.2
Install from the Visual Studio Marketplace, confirm the QuarryFi publisher, then use the command palette to connect a seat-assigned Core key.
Install from VS MarketplaceClaude Code
Current release 1.6.3
Install the maintained QuarryFi tracker from its GitHub repository and connect a seat-assigned Core key. A public Claude marketplace listing is not available yet.
Open GitHub setupCodex
Current release 0.4.7
Install QuarryFi from the official Plugins Directory, review and trust its lifecycle hooks, then run the included status check.
Open Plugins DirectoryOne key, assigned to one person
A QuarryFi owner adds the contributor's email. The contributor claims that seat from a one-time link, creates the seat key during a limited setup session, and connects their own tools. The owner never has to copy or send a code.
Freshness you can verify
During active work, accepted heartbeats should appear on the dashboard in about one minute. The Team page shows each tracker's last contact so a stale or misconfigured client is visible.
Prepare the records behind the tracker data
Tracker metadata can help establish who worked, when, and in which project. Use the Software R&D evidence checklist to pair those records with business-component facts, technical uncertainty, expense support, exclusions, and CPA handoff questions.