Skip to content

Time tracking for people and their coding agents.

The work gets logged. Nobody has to log it.

Your coding agents record the hours as they work — attributed to the person, sorted into the right project, reviewed before anything counts — or just ask one to start a timer, or log an hour by hand. Then it becomes a report finance trusts, or an invoice a client pays.

Request access

Shyre is in early access and accounts are set up by hand. Tell us what you work on and we'll be in touch.

One Claude Code session, as Shyre measures it

32 min idle — not counted
09:1210:31
The agent working — sampled from its own tool callsWaiting for the person — the agent has answered and the next prompt has not come. Counted, and reported as a number of its own.A gap longer than the idle cap never counts as time — fifteen minutes by default, and each person sets their own in their own shell.

One entry: 47 min — 35 with the agent working, 12 waiting for the person — attributed, categorized

Recorded by the agent's own hooks while you work — a timestamp on your machine for each prompt, tool call and turn — and sent when the session ends. No Shyre process has to be running, and nothing reads the transcript — unless you run the backfill yourself, which reads timestamps and the working directory, nothing else. If Shyre is unreachable, the entry waits on your machine and is delivered by the next session, for up to thirty days.

Two ways people use it

We invoice the work

Proposal, tracked work, invoice, signed sign-off — one record, no retyping.

For consultants and studios

We know what engineering costs

Where the quarter went, per project and per person, with a real cost against it.

For teams inside a business

Seven dollars a person, a month — four while we're in early access. Pricing

Everything that ships

Time

  • Timer, week grid, day and log views
  • Claude Code, the Codex CLI and Cursor log their own hours — one runtime, installed once per agent
  • Tokens by model, recorded where the agent reports them, as an estimate at list price — never on an invoice
  • Entries link to Jira and GitHub tickets
  • Categories, templates, sub-project rollup
  • Harvest and CSV import, undoable in one click

Money

  • Invoices grouped by project, task, person or ticket; month-end drafts for every customer ready to bill, in one run
  • Expenses with reference numbers, split out from services
  • Fixed-bid, NTE, range and time-and-materials
  • Hours, billable share, human-vs-agent lens, agent runtime per project
  • Effective-dated cost rates, owner and admin only
  • Financials open masked; press H to reveal

Documents

  • Proposals priced, sent and e-signed — or started from a previous one
  • Release notes your client signs, per line item
  • A published changelog on its own gated link
  • One client portal link per customer

Team & access

  • Period locks the database enforces
  • Owner, admin, member; rates masked by role
  • Two-factor, recovery codes, step-up re-auth
  • CSV export of time, customers, invoices, expenses

What's next

Everything above ships today. These are next, in no particular order.

  • A pay link on the invoice, so a client pays from the portal and the payment records itself.
  • Statements of account, and reminders that go out on a schedule.
  • Accounting sync, QuickBooks Online first.
  • Retainers with a balance the client can see, and hours a client approves before they bill.
  • Self-serve signup and card billing. Until then accounts are opened by hand and nothing is charged.
  • Internal chargeback: what each project cost a team, per period, for finance to allocate.
Request access

Shyre is in early access and accounts are set up by hand. Tell us what you work on and we'll be in touch.