Evidence-backed time tracking

Time tracking watched over by tiny robots.

Stopwatch captures the real shape of interrupt-driven work: active apps and URLs, screenshots, idle gaps, resumption events, tickets, projects, branches, and commits. Robots read the evidence and propose the entries — you review, clean up, and ship defensible time. Pomodoro timers keep the day moving, and a focus soundtrack built from your own music library keeps you in it.

  • macOS Agent
  • Web Review
  • iOS Companion
  • Android Companion
  • Windows Agent
  • Linux Agent

Workflow

Capture the day, then make it billable.

Three passes, and only the last one needs you: the agent records, the robots label, and you approve what leaves the building.

01

Capture context

Screenshots, foreground apps, browser tabs, repos, shell activity, idle, sleep, resume, and task switches are recorded by the desktop agent.

02

Attach the work

Session context — client › project › ticket, plus branches and commits — rides along with every span, so time entries explain themselves.

03

Review and export

Multi-track sessions, manual backfill, and time boxes roll up into day, week, and month reports you can export with confidence warnings and optional evidence.

Capture and intelligence

The robots do the recall. You keep the judgement.

Activity monitoring turns a fragmented day into an ordered ledger. Optional AI reads that ledger and drafts the labels — on your own key, or not at all.

App and activity monitoring

Foreground app, browser tab, repo, and shell activity are sampled continuously on macOS, Windows, and Linux, with idle, sleep, and resume events bracketing every span. The web app breaks the day down by machine. Task switches become the seams you split and merge along.

AI-analysed screenshots

Ask a model to read the captured frames and propose the project, the ticket, and a one-line summary of what the hour actually was. Every suggestion arrives with a confidence score and stays editable.

Bring your own key — optional

Point Stopwatch at your own Anthropic, OpenAI, or self-hosted endpoint and inference runs on your account under your retention terms. Leave the key blank and no frame is ever analysed.

Focus toolkit

Timers, soundtracks, and time that lands on the right work.

Tracking is the core; focus is the point. Stopwatch pairs the ledger with Pomodoro sessions and a soundtrack built from music you already own.

Focus soundtrack

Point Stopwatch at your own music library — volumes, playlists, and ratings included. Star the tracks that work and your stars sync across your machines. Ratings drive Focus Fuel and Deep Work generation, and any playlist exports back out as a volume.

Pomodoro that adapts

Focus and break timers you can retime mid-session, for when the real world disagrees with the plan. Session context — client › project › ticket — keeps focus time landing on the right work, and each page remembers its own tabs.

Time tracking core

Multi-track sessions, manual backfill, and time boxes, reported as day, week, and month breakdowns. Clients, projects, and tickets each carry drill-down reports and project notes.

Platforms

Capture on the desk. Review anywhere.

One ledger, synced. Desktop agents record; phones and the web review, correct, and approve.

macOS

Alpha

The capture agent. Menu-bar timer, retimeable Pomodoro spans, the focus soundtrack from your own library, app, tab, repo, and shell tracking, periodic screenshots, and full local evidence storage.

Web app

Alpha

Day review, timeline correction, day and machine activity analytics, client, project, and ticket reports with drill-downs, exports, and organisation admin.

iOS

In build

Companion review: browse the timeline, resolve idle gaps, add manual entries. No capture, no background timer.

Android

In build

Companion review with the same correction tools as iOS, and the same refusal to capture anything itself.

Windows

Alpha

A full capture agent: foreground app, window title, URL, idle, sleep, and resume, at parity with the Mac.

Linux

Alpha

Wayland and X11 capture agent for developer desktops, with the same evidence and redaction controls.

Integrations

Wired into the rest of The Robot Lives.

Stopwatch is the ledger layer of a larger operational stack, so a tracked hour lands next to the ticket, branch, and plan it belongs to.

  • The Robot Plans

    Push reviewed spans back to the projects, tickets, and OKRs they came from, and pull the current work item list into the capture agent for one-click attachment.

  • Agent-friendly MCP

    An MCP server exposes the ledger to your own agents and to the rest of the stack, so coding assistants can read what was worked on and file time without a browser.

  • Git and ticket context

    Branches, commits, and ticket references collected during capture become the evidence attached to the entry — no second pass through a changelog.

  • Exports that survive review

    CSV and JSON exports carry confidence, evidence links, and the audit trail, so an invoice line can be defended months later.

Privacy

Evidence without invisible surveillance.

Monitoring this detailed is only acceptable if the person being monitored owns the switch. Stopwatch is built for the individual holding the timer. The fine print: Privacy Policy · Terms · Warranty.

Visible capture

Agent state, permissions, screenshot interval, and sync health stay visible.

Local-first screenshots

Screenshot pixels stay on the Mac unless you deliberately export, sync, or send them for analysis.

Redaction controls

Blur private regions, exclude apps and domains, and delete evidence before reporting.

Window titles stay home

Window titles never leave your Mac. Cloud sync is opt-in per device, and ignore lists keep whatever you'd rather not track out of the ledger.

Alpha

Desktop capture, web review, agent-friendly MCP.

Stopwatch is focused on a tight single-user loop today: capture a day, score it with a Pomodoro and your own soundtrack, resolve the messy parts, and turn it into project-ready time entries.

Sign in