Editor integrations
Connect the editor you already use. VS Code has a first-party extension; other editors can use their WakaTime-compatible plugin and point its api_url at the hosted API.
First-party integrations
VS Code
The AtoAxis extension buffers editor metadata, sends heartbeats through wakaclock-cli and shows today’s coding time in the status bar.
AI hooks
The setup flow can configure Claude Code, Codex CLI and Gemini CLI hooks without sending prompt or response content.
WakaTime protocol
Neovim, JetBrains, Vim and other editors with a WakaTime plugin can set api_url and api_key. Their plugin controls its own behavior and update cadence.
What that means in practice
- No new extension to install: the plugin you already trust keeps running
- The plugin decides what it sends, so its own feature set is the ceiling, not ours
- Time, project, language, editor and branch arrive the same way they would from our own client
- Fields a plugin never sends, such as AI attribution, simply stay empty rather than being guessed
What reaches the server, whichever client you use
The heartbeat is the contract. Whether it came from our extension, a WakaTime plugin or your own script, the server accepts the same shape and derives the same analytics from it.
- File path, project and Git branch
- Detected language, editor, operating system and machine
- Line, cursor, keystroke and character counts
- Activity category, optional AI attribution fields and the timestamp
Not supported yet
Stated plainly, because discovering a gap after switching is worse than reading about it now.
- Cursor and Copilot: their activity needs a provider-specific adapter before it can be attributed
- Zed: a language-server client exists but there is no installable Zed extension wrapping it yet
- Design and 3D tools: no Figma or Blender client is published
- No desktop or browser client, so work outside a connected editor is not captured at all