Switching from WakaTime without losing a day

Switching from WakaTime takes three steps, and none of them loses anything: your history comes with you, every editor keeps a plugin, and you can run both trackers side by side until you trust the numbers.

1. Bring your history

Open Import from WakaTime (also in Settings → Data) and paste your WakaTime secret API key. Inlinr asks WakaTime for your heartbeats export, waits for it to be ready, and shows a preview: each WakaTime project, how many beats it holds, and the Inlinr project it will join. You can also upload the export file yourself.

Each import can be rolled back on its own, without touching what your editors sent. Projects are matched by name, so a repository you already track with the Inlinr extension gets the imported time rather than a second project.

2. Choose how each editor sends

For each editor, pick one of two ways:

• The Inlinr plugin, for VS Code and its forks (Cursor, Windsurf) and for Claude Code. It sends the git remote, so projects are keyed by repository, and it records which assistant wrote the code.
• Your WakaTime plugin, pointed at Inlinr, for every other editor. Create a WakaTime key in Settings → Editors (it starts with waka_) and change two lines of ~/.wakatime.cfg:

[settings]
api_url = https://inlinr.com/api/compat/wakatime/v1
api_key = waka_…

That file is shared by every WakaTime plugin on the machine, so all of them switch at once. Setup for each editor is on the WakaTime integration page.

3. Compare for a week

wakatime-cli sends to one server, so a WakaTime plugin cannot report to both at once. To compare, keep WakaTime's plugin pointed at WakaTime and install the Inlinr plugin next to it in the same editor: each sends to its own server, and after a week you can lay the two dashboards side by side. Once you are satisfied, uninstall the WakaTime plugin, or point it at Inlinr for the editors Inlinr has no plugin for.

What keeps working

Inlinr answers the parts of WakaTime's API that plugins and the tools around them read, with the same waka_ key:

• the editor's status bar (statusbar/today)
• summaries, by start and end or a named range such as Last 7 Days, with an optional project
• stats/last_7_days, last_30_days, last_6_months, last_year and all_time
• all_time_since_today

curl -u waka_…: \
  "https://inlinr.com/api/compat/wakatime/v1/users/current/summaries?range=Last%207%20Days"

A script or a stats card that reads these keeps working once its base URL is Inlinr's. Operating systems, machines and dependencies come back as empty lists: Inlinr does not collect them.

What will read differently

• Slightly less time. A gap between two heartbeats longer than your keystroke timeout counts for nothing; it is not capped at the timeout. The guide to how time is counted explains why, and the timeout is yours to set in Settings.
• Projects by repository. The Inlinr plugin names a project after its git remote. A WakaTime plugin only sends a folder name, so the same repository under two folder names is two projects until you merge them from the project's Settings.
• AI attribution only where it is measured. The Inlinr plugins say which assistant wrote a change. WakaTime's editor plugins do not, so their time carries no assistant, except wakatime-cli's own AI transcript sync.

Inlinr is not affiliated with or endorsed by WakaTime.