Tempo reads the work itself: real Claude Code sessions plus git history. It shows you who ships what, what it costs and whether AI is actually paying off, and it never needs a screenshot to do any of it.
Works with Claude Code today, including the Pro and Max subscription seats that no admin API can see.
4 sessions · 3 in parallel · 2h 18m attended · 1 feature shipped
Release guardrails shippedJ. Park attended from 09:12 to 11:54 for 2 hours 18 minutes. Session S1, Build loop, ran from 09:12 to 10:26. Session S2, Test sweep, ran from 09:38 to 11:17. Session S3, Docs pass, ran from 10:04 to 11:02. Session S4, Release check, ran from 11:18 to 11:54. The maximum concurrency was three sessions from 10:04 to 10:26. All four sessions link to the shipped feature Release guardrails.
When AI does the typing, volume is free. Anyone can push fifty easy pull requests a week. Tempo scores what mattered: the features that landed, on the priorities you declared, and whether they stayed fixed.
Most teams can say they spent seventy grand on models last month. Very few can say what it bought. Tempo attributes spend to people, projects and models, then follows it all the way down to the features that landed.
Tempo ships as an MCP server for any compatible coding agent. Dashboards show you charts. Tempo answers questions, with citations, wherever you already work.
The monitoring industry trained everyone to expect stealth modes and screenshots. We built Tempo so that its privacy claims are architectural facts, the kind your security team can verify in the product itself.
The code to capture a screen was never written, so there is nothing to switch on. The same goes for desktop activity: Tempo does not read window titles, app usage or the accessibility tree. It sees agent sessions and git, and nothing else.
The collector is a visible app the employee installs and can see running. A hidden mode does not exist to be turned on.
Collection is scoped to projects in your company's GitHub organisation, enforced on the device and re-checked on the server. Personal projects never leave the laptop.
Everyone can query everything Tempo holds about them, including an access log of who looked and when.
An employee can remove a session after the fact. It leaves storage and every statistic, numerator and denominator, permanently.
Manager queries are audit-logged, and the log cannot be switched off. Symmetry is the point: this is measurement you would accept being on the other end of.
A small desktop app on each dev machine syncs Claude Code session data, from company repositories only, on a gentle schedule. It never asks for screen access because it never uses any.
A small MCP configuration adds Tempo to any MCP-compatible coding agent, with manager scope for leads and self scope for everyone else. The dashboard covers installs and team timelines.
Run /tempo:assess, /tempo:churn, or just ask in plain language. Declare this quarter's priorities and the scoring follows them.
Tempo works both ways. The engineer being measured gets useful answers from the same data, on the same day, in the same tool.
/tempo:how-am-i-doingYour own trend, your strongest shipped work and concrete tips, computed from your data, visible to you, never comparative.
/tempo:team-visionWhat leadership has declared as this quarter's priorities. The actual weighting, not a guess at what matters.
/tempo:score-taskScore a task against the declared vision before you spend a week on it. Knowing the weighting up front is what makes the system fair.
Coding-agent session data (Claude Code today, other agent CLIs as raw capture) and git metadata, from company-organisation repositories only. That scope is enforced on the device and verified again on the server. It never touches keystrokes, browsing history, window titles, the accessibility tree, email or chat, and there is no screenshot capture of any kind.
It measures the work, and you can check the difference yourself instead of taking our word for it. No screen capture exists in the codebase. There is no stealth mode. Employees see and can delete their own data, and every manager read is audit-logged.
Yes. That is a structural advantage of measuring from the session record rather than from billing APIs. Official admin consoles exclude individual Pro and Max seats entirely, whereas Tempo puts every seat on the same ledger, with costs computed from public per-model pricing.
No. Tempo informs human judgement and never renders verdicts. Every claim carries citations, negative findings run an adversarial refute-first pass before they are shown, and no score is ever displayed without its rubric, its caveats and an explicit list of what the data cannot see.
In your Tempo organisation's isolated store. Manager-scope tokens can query team data, always audit-logged. Self-scope tokens see only your own. Nothing is sold or used to train models, and processing stays with the sub-processors that run the service, all of them listed in your agreement.
We are onboarding early teams directly and pricing with them. Book a demo and we will talk concrete numbers for your team size.
A 30-minute walkthrough with the founders, built around your questions rather than a canned deck.
Book a demo