Guides
Coding time and AI sessions, measured
How to set tracking up, how the numbers are computed, and which ones change a decision. Each guide is written from something Inlinr measures rather than around it, which is why there are 5 of them and not thirty.
Time tracking5 min read
How coding time is counted, and why two trackers disagree
Time is the gaps between heartbeats. Which gaps count is one setting, and getting it subtly wrong adds over an hour a day.
Read the guide
AI usage6 min read
Why your assistant re-reads everything, and what it costs
Most of a Claude Code turn is context you have already paid to send once. Here is how to tell whether you are paying twice.
Read the guide
AI usage5 min read
What “percent written by AI” can and cannot tell you
The number is easy to produce and easy to misuse. What it counts, what it misses, and the questions it genuinely answers.
Read the guide
AI usage4 min read
Reading a token bill without overstating it by 10×
Four numbers, four prices. Adding them up is how people end up off by an order of magnitude.
Read the guide
Put your own numbers next to these
Install the plugin for your editor or Claude Code, and the time, token and line counts these guides describe appear on your dashboard within minutes.
No card to start · no source code leaves your machine