- Guides
- Setup
Switching from WakaTime without losing a day
Import your WakaTime history from a start date you choose, keep every editor's plugin by pointing it at inlinr, compare both trackers for a week, and know which numbers will read differently and why.
: Its sources, and what the WakaTime plugins say about assistants.

In this guide
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 the WakaTime tab of the Import page (also linked from Settings → Import & export) and paste your WakaTime secret API key. inlinr asks WakaTime for your heartbeats export, waits for it to be ready, and shows a preview. You can also upload the export file yourself. The import runs on the server: you can leave the page and come back to the same step.
To start later than your first day on WakaTime, set Import from: activity before that day stays in WakaTime.
The preview gathers the spellings of one project into one row and shows its repository when WakaTime links one, its folder and its files. It suggests a merge for close names, and each row can go into any inlinr project or into another row, under a client. Agents' scratch folders start unticked.
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. A name you send into a project is kept in its Other names, so the next import and your WakaTime plugins land there too.
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, bystartandendor a namedrangesuch asLast 7 Days, with an optionalprojectstats/last_7_days,last_30_days,last_6_months,last_yearandall_timeall_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.
For the stats on your GitHub profile, inlinr has its own card, with no key to store: the README stats guide sets it up and moves a waka-readme or github-readme-stats block over.
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 with Merge into… in 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 always, so time from them names an assistant only when the plugin sends one.
inlinr is not affiliated with or endorsed by WakaTime.
Sources
- WakaTime API: the endpoints the compatible API answers, and the export your history is imported from. Checked on 29 October 2026.
- wakatime-cli, its README: the
api_urlsetting in~/.wakatime.cfgthat points every WakaTime plugin at one server. Checked on 29 October 2026. - WakaTime FAQ: the keystroke timeout. Checked on 29 October 2026.
What changed
- : Its sources, and what the WakaTime plugins say about assistants.
- : The README stats guide, for the card on your GitHub profile.
- : The new import preview: a start date, one row per project with its spellings, and names kept for the next import.
- : first published.
See it on your own sessions
Import your WakaTime history, then let your editors send here: the years you already tracked stay on the same charts as the time you track from today.
Free for solo use · no source code leaves your machine