Automatic time tracker for developers: branch, files and browser, matched to the issue

Planim is an automatic time tracker for developers: it reads the git branch, file edits, terminal and browser, and matches time to the issue on your machine.

Contents
  1. What an automatic time tracker for developers reads
  2. Matching code time to the issue
  3. The cases developers ask about
  4. Review from the keyboard
  5. Your activity stays on your laptop
  6. Next to WakaTime, Timing and Tempo

Planim is an automatic time tracker for developers. It reads the signals a coding day already produces, the git branch, file edits, the terminal window, pull request tabs, and uses them to match each stretch of work to the right issue in Jira, GitHub, Linear, Asana or Trello. The record and the matching models stay on your machine, and nothing is logged until you confirm it.

I make Planim, and I built it around my own days: an editor, a terminal, forty browser tabs, and a timesheet due on Friday.

What an automatic time tracker for developers reads

SignalWhat it says
Git branchPAY-212-refunds names the issue for everything edited on it
File editsWhich repository and which files, with paths the app learns
Editor and terminal window titlesProject, file, often the running command
Browser tabs (URL and title on macOS, title on Windows)The pull request, the issue, the docs page, the CI run
Idle and lockWhere the work stopped
WSL agent, optionalActivity inside a Linux distribution on Windows

No editor plugin is needed. Planim reads the focused window, file edits and the git branch, so the editor you use does not matter.

Matching code time to the issue

Ten channels vote on an issue for every block of work. The ones that carry most of a coding day:

  • An issue key in the branch, the window title or the URL.
  • Links the app recognizes: a GitHub pull request, a Jira issue, a Figma file, a Notion or Google Docs page.
  • File paths you have confirmed before.
  • Two small language models on your CPU that compare the words on screen with the summaries of your open issues.
  • Your past verdicts, and which issues tend to show up together.

The votes are merged by rank, with direct evidence counted three times, and the inspector shows each one with the text it saw.

The cases developers ask about

Review time. Reading someone else's pull request leaves no commit. The tab URL names the repository and the PR, and the PR title or branch usually carries the key.

Research. Forty minutes of MDN and a forum thread have no key anywhere. The language models place it next to the issue whose summary it matches, and the block sitting between two edits on PAY-212-refunds gets the same proposal from the history channels.

The wrong branch. You forgot to switch and spent the morning on another issue in the browser. The branch is one vote; when the other channels agree on a different issue, the proposal follows them and the inspector shows that the branch disagreed.

An incident across four tickets. Each episode gets its own proposal, and R reassigns any that landed on the wrong ticket.

Slack and mail. A shared window gets the issue of the work next to it, from the channel that tracks what appears together.

Why automatic time trackers pick the wrong task goes through all six failure modes and the numbers behind the matcher: reciprocal rank fusion, an embedding model with a reranker, isotonic calibration.

Review from the keyboard

Enter confirms. R reassigns. I marks a block as not work. N jumps to the next proposal under 80 percent confidence, and J and K move along the day. Single keys pause while you type in a field.

Push worklog sends the confirmed drafts: worklogs to Jira, time entries or comments to Asana, comments to Trello. GitHub and Linear issues are matched against like the rest. Several instances of one tracker can be connected at once, which covers a contractor with two Jira sites.

Your activity stays on your laptop

A developer's window titles include client repository names, file paths and internal hostnames. Planim keeps them in a SQLite file on your disk, runs both models locally and has no account. Denylists drop chosen apps and domains at capture. Your manager gets the worklogs in Jira and nothing else. The full network list is in local AI time tracker.

Next to WakaTime, Timing and Tempo

ToolWhat it seesAssigns time to the issueActivity record lives
PlanimEvery app, browser tabs, files, git branchOn-device AI proposes, you confirmYour machine only
WakaTimeEditors and IDEs through plugins, plus desktop appsReports by project, branch and languageWakaTime's servers
TimingApps, documents and websites on a MacYour rules, plus AI grouping on higher plansYour Mac, optional sync
Tempo TimesheetsCalendar, Jira activity, VS Code and JetBrains extensionsYou pick, from suggestionsTempo's cloud

WakaTime sends heartbeats from editor plugins, with file path, project, branch and language, to its servers; file contents are not sent. It measures coding time by project and language. Planim covers the browser, the terminal and everything else on the same timeline and assigns the time to issues.

Timing records the whole Mac and keeps the data local unless you turn on sync. Assignment is by rules, with AI grouping and summaries on the Expert and Connect plans, and there is no Windows version.

Tempo works inside Jira and suggests entries from your calendar, Jira activity and its editor extensions (Planim vs Tempo Timesheets). Planim writes ordinary Jira worklogs, so a team on Tempo sees the hours in the same reports.

WakaTime and Timing were checked on their own pages in November 2026, Tempo in October 2026.

Planim is in development for macOS 14 and Windows 10/11. Leave an address below and you will hear when the automatic time tracker ships.