AI-native team monitoring
Chronologue records apps, sites, activity and screenshots like the tools you already know, then writes a daily narrative for every person and team. Ask about anyone’s day and get an answer linked to the evidence.
USD 10 per seat/month billed annually. Seven-day free trial; first charge after seven days.
// what you get
Chronologue covers the same ground as the incumbents, then does the reading for you. Pick a tab, any tab.
Each day becomes a short written account of what was worked on, built from apps, window titles, sites, meetings and commits. Managers get the team view; each person sees their own.
Most of the day went to the checkout redesign. The afternoon moved to the payments retry pull request after the weekly sync.
Each line links to the apps, window titles and screenshots behind it.
Get an answer whose claims link to the underlying activity, so you can check it.
What did Sam get done on Tuesday afternoon?
Timelines, activity levels and idle time for every person, on one scale.
Apps and sites are rated productive or not automatically, and every rating shows why. Correct one for a person, a team or the whole workspace.
Optional screenshots with blur, beside the apps and sites they came from.
Blur on
Tracked time rolls into weekly timesheets, ready to approve.
| Person | Mon | Tue | Wed | Thu | Fri | Total | Status |
|---|---|---|---|---|---|---|---|
| Sam | 7:40 | 8:05 | 7:55 | 8:10 | 6:30 | 38:20 | Approved |
| Priya | 8:00 | 7:30 | 8:15 | 7:45 | 7:10 | 38:40 | Approved |
| Jun | 6:50 | 7:20 | 8:00 | 8:30 | 7:00 | 37:40 | Waiting |
Approved hours become a payroll file your accountant can open.
person,period_start,period_end,hours,rate_usd,amount_usd
Sam,2026-10-12,2026-10-16,38.33,30.00,1150.00
Priya,2026-10-12,2026-10-16,38.67,28.00,1082.67
Jun,2026-10-12,2026-10-16,37.67,32.00,1205.33Billable hours turn into invoice lines without retyping.
Every plan includes the command-line tool, an MCP server and a REST API. More on that further down.
$ chronologue timeline sam --day tuesday 09:05–11:40 Figma · Checkout redesign 11:40–12:10 Google Meet · Weekly sync 13:00–15:25 GitHub · Payments retry pull request $ chronologue payroll export --week 2026-10-12 --csv wrote payroll-2026-10-12.csv
// how it reads a day
Same apps, sites and activity you’d track anyway. Here is what Chronologue does with them.
Each day becomes a short written account of what was worked on, built from apps, window titles, sites, meetings and commits. Managers get the team view; each person sees their own.
Most of the day went to the checkout redesign. The afternoon moved to the payments retry pull request after the weekly sync.
Checkout redesign in Figma, then review comments in Linear
FgLnWeekly sync on Google Meet
GmPull request for the payments retry flow on GitHub
GHEach line links to the apps, window titles and screenshots behind it.
Ask “what did Sam get done on Tuesday afternoon?” and get an answer whose claims link to the underlying activity, so you can check it.
What did Sam get done on Tuesday afternoon?
Apps and sites are rated productive or not automatically, and every rating shows why. Correct one for a person, a team or the whole workspace.
Why: design work on the checkout redesign, which Sam’s team owns.
Why: entertainment, with no link to a project in the window titles.
Correct this rating for
Only Sam’s ratings change.
// before and after
Same ground as the incumbents. Then it does the reading for you.
And still the everyday surface of Time Doctor or Hubstaff:
// for your agents
Every plan includes the command-line tool, an MCP server and a REST API, so your AI agents can read the same timelines, narratives and reports you do.
$ chronologue narrative --team design --day tuesday # Daily narrative · Design team Most of the day went to the checkout redesign. 09:05–11:40 Figma, then Linear 11:40–12:10 Google Meet 13:00–15:25 GitHub # each line links to its evidence
# token created in settings, revocable any time you What did the Design team get done on Tuesday? tool chronologue.narrative(team: "design", day: "tuesday") ai Mostly the checkout redesign, then the payments retry pull request after the sync. ↳ 3 linked lines
GET /narratives?team=design&day=tuesday 200 { "summary": "Most of the day went to the…", "lines": [ "09:05–11:40", "11:40–12:10", "13:00–15:25" ] } # webhook → your own tools
Your afternoon went to the payments retry pull request, then review comments in Linear.
Which keys: never recorded
// visible by design
The same day, from their side of the screen.
The desktop app shows in the menu bar whenever it runs.
Everyone can open their own timeline, narrative and screenshots.
Activity level counts keyboard and mouse events per minute. It never records which keys are pressed.
Seven-day free trial. Enter a card at Checkout; nothing is charged today and the first charge is seven days later.