Agent-native time tracking

Your agent keepsthe record

Steno is an evidence ledger for work. Your coding agent reconstructs what you did from pull requests, threads, and meetings, and files it for your approval. Its own sessions go on the record too: the tokens, the cost, and what they shipped.

Works with Claude CodeCodexCursorany MCP client

Work itemReferral form validationNorthline Health · Patient intake
Human2.5 happroved
Agents3 sessions1 h 23 m
AI cost$7.30of $25 budget
  • Claude Code · CLI46 m$4.42
  • Codex · desktop28 m$2.12
  • Claude Code · CLI9 m$0.76
PR #412 merged Deployed

The review — yours to try

A studio agent filed three client entries. Approve them.

Needs review
2.5 hTUE

Referral form validation repaired and reviewed

† fix: referral form validation #412‡ #patient-intake launch review

1.25 hWED

Driver handoff mapped with operations

† Operations workflow review (45m)

3 hTHU

Lesson notes export fixed and shipped

† fix: lesson notes export #418‡ PDF notes cut off on mobile #415

StenoStatement of workTandem Works · Client portfolio · this week
Approved entries land here.
In sum0 h · $0

New · Agent sessions

Every agent session, accounted for.

Hours tell you what a person spent. Sessions tell you what the agents spent alongside them. Steno links the two to the work item and the outcome, so a week reads as one story: who worked, what it cost, and what shipped.

SessionRepair referral validation Claude Code · CLI · Tue, Jun 9
Complete coverage
Agent time46 m
Tokens2.39M
Cost$6.31

Tokens by bucket

  • Cached input1.48M
  • Input406k
  • Cache write215k
  • Output287k

Allocated to work

  • Referral form validation$4.42
  • Intake QA checklist$1.26
  • Unallocated$0.63
Priced at published API rates, as of Jun 1. Source records collapsed.
Every session, imported.
The reporting skill reads your Codex and Claude logs on a nightly backfill. No hooks, no transcript upload. Each session lands with its model, token buckets, and the published price it was costed at.
Cost lands on the work.
Usage is split across work items by weight. Whatever an agent can't attribute stays on the books as unallocated, never quietly spread around.
Outcomes, not claims.
Work items link the ticket that started them and the pull requests, documents, and deploys they produced. Opened, merged, and deployed are kept apart.
Human time stays human.
Your hours still come from the entries you approve. Session duration is agent time, and it never pads a timesheet.

An illustrative studio week

Each company. Each project. One record.

Picture a product studio with its own systems and several client products moving at once. Steno keeps the company, project, person, and evidence together, so each hour lands in the right place.

The client companies and all project details on this page are fictional examples.

01Tandem WorksStudio systemsInternal tools for research, publishing, and operations.
02Northline HealthPatient intakeA clearer path from referral to first appointment.
03Relay FreightDispatch consoleOne live view of loads, drivers, and delays.
04Juniper LearningTutor workspaceLesson planning, notes, and follow-up in one place.

№ 1 — 3

Three steps, no timers.

  1. Connect your agent.

    Add the MCP server to Claude Code, Codex, or Cursor. It signs in with OAuth, so there are no API keys to copy or leak.

  2. It files the evidence.

    The agent reconstructs your work from PRs, agent threads, Slack, and your calendar. It files pending entries with receipts, plus its own sessions and usage.

  3. You approve. The ledger bills.

    Review in seconds, approve, and export a statement of work your client can actually audit.

Billing for judgment
needs receipts

The case

Timers measure sitting. Steno records work.

When an agent does ten hours of work in two, "how long did you sit there" stops being the question. What got done, and what it's worth, is. Timers can't answer that, and screen surveillance shouldn't have to.

Steno keeps an auditable record instead: each hour traced to the pull request, the thread, or the meeting it came from, approved by you before it counts. Set a rate and the same record prices itself; don't, and it's simply the truest timesheet you've ever kept.

StenoStatement of workTandem Works · Client portfolio · June 1 – 30, 2026
Jun 4Intake form validation3.75 hJun 9Dispatch handoff review2.5 hJun 9Lesson notes export3 h
In sum14.5 h · $1,740
The output is a document, not a dashboard.

Tariff

Free to keep your record.

Keeper

Free

For keeping your own record.

  • One connected agent
  • One space, unlimited projects
  • Full evidence trail & approvals
  • Statements, CSV & Markdown export
Start free

Studio

$29 / user / month · 3-user minimum

For agencies billing across developers and clients.

  • Organization-bound agents & assigned projects
  • Developer review & manager exception audit
  • Confidential member-specific rates
  • Consolidated client statements, PDF & CSV
Set up a studio

Let the agent take it down

Connect once. Review a week of evidenced work, sessions included, in the time it takes to read it.

Create your account