Your team's week,
in four sentences.
Throughline reads what your team's Claude Code sessions already recorded — from their own laptops, no admin key — and writes the brief no standup could: what shipped, what's grinding, who's gone quiet, what the assist cost. With names. Not charts.
The standup your coding agents run for you — the one your engineers never have to attend. Coaching, never monitoring: they read exactly the brief you read.
NO CREDIT CARD · 10 MINUTES TO YOUR FIRST BRIEF
The week Priya unblocked checkout.
A heavy shipping week carried by Priya, whose sessions drove the checkout refactor (ENG‑142) over the line by Thursday. Spend stayed under a third of budget. Watch: Marcus went quiet after Tuesday — likely blocked, worth a check-in before you plan the sprint.
ENG‑142 shipped in two focused days — 15 files, tight turn count. Dev doubled his acceptance rate scaffolding tests with agents.
ENG‑190 (payments timeout): three days, 135 turns, $60, still open. Marcus quiet since Tuesday. Coaching, not blame.
Three steps, then it never asks you again.
Share one install line
No admin key, no procurement thread. Each engineer runs one pinned, checksummed script on their own laptop and their session metadata starts syncing.
Watch last week land
A live readout counts sessions day by day and tells you exactly who matched your roster — "matched 3 of 4" — instead of spinning. Your first brief covers the last full week, on the spot.
Skip the meeting entirely
Your agents already logged the week. Throughline turns it into four sentences in your inbox — nobody blocks time, nobody rehearses an update, nobody gets interrupted. Quiet weeks get a brief too, and it says so.
One install per laptop. No admin key, ever.
Engineers sync from their own machines — counts only, and only what they choose to keep syncing. Every source lands in the same schema, so the brief never cares which tool the data came from.
Claude Code
Session-grain metadata straight from each engineer's machine: turns, duration, model, cost, files-touched counts.
Cursor
Next in line. Cursor sessions join the same brief when the connector lands — same install, nothing new to approve.
GitHub Copilot
On the connector list. Copilot sessions will land in the same schema and read the same way.
Codex
Also queued. We'd rather say "not yet" than fake a logo wall.
How the sync works
One pinned, checksummed script posts session metadata in the background — never prompts, never code, never file paths. Revocable per device.
A brief your engineers would forward themselves.
Every team member reads the same brief the manager reads — no hidden view, no scoreboard, no ranking. People who haven't joined your roster appear only as a count, never by name.
Personal weekly recaps stay private to the engineer, who can delete their own synced data whenever they want.
Session counts, turns, duration, files-touched counts, model and cost. Never a prompt, never a line of your code, never a file path.
Nothing to paste, nothing to escalate. Each laptop gets its own write-only token, stored 0600, revocable per device without touching anyone else's.
Briefs are written on Throughline's own API key, at our cost. Engineers can delete their synced data in one click, and anything older than 180 days purges itself.
The standup your agents run for you.
Not on the list yet? Get the occasional note when a connector ships or the brief gets sharper. Nothing else — we hate newsletters too.