Your people and their agents,
on the record.
Engineering now runs on coding agents. Throughline is the one place that knows what your people and their agents actually did, what it cost, and what's stuck — and it doesn't just watch. It steps in while a session loops, hands over the fix a teammate already found, and writes the week for every engineer, team and leader.
Coaching, never monitoring: every level sees exactly what the level below sees about itself. No dashboards, no leaderboards, no boss-only view.
SELF-SERVE IN 10 MINUTES · ENTERPRISE PILOTS ON REQUEST
ENG‑190 unblocked Thursday — one step-in, fixed two turns later from a shared note. A second three-day grind that didn't happen.
One record. Three readers. Same rules for all of them.
The engineer gets help and a mirror. The team gets the story and every fix worth keeping. Leaders get the roll-up — built from the same rows, never a richer copy.
Help while the session is still going, and a mirror nobody else holds.
An agent supervisor
NEWWhen a session loops — the same call failing, a long run with no file changes — it gives the agent context, suggests a new approach, then tells you. Opt-in; never blocks or stops anything.
A private recap
LIVEWhere your time and tokens went: the retry loop worth cutting short, the session that landed clean. Visible only to you.
A standup you never write
LIVEYour week as work items — tickets moved, sessions behind them — ready to paste. Teammates see the same view; there's no manager-only version.
The story of the week, and every fix someone chose to keep.
Team notes
NEWGot unstuck? A three-line note — symptom, what didn't work, what fixed it — drafted for you, private until you share it. The next agent on the same ticket gets it handed over.
The weekly brief
LIVEFour sentences on what shipped, what's grinding, who's gone quiet and what the assist cost — told in work items, Linear titles included.
Answers in Slack
NEXTThe repetitive tagged question, answered from shared notes and the channels you add it to — with citations, as a draft a human approves.
The roll-up, built from the same rows — never a richer copy.
The org readout
ON REQUESTTeam briefs roll up to directors and VPs: AI-assisted work shipped, bugs versus features, adoption and spend — a narrative first, the tree underneath to verify it.
Same view at every altitude
LIVEEach level sees exactly what the level below sees about itself. The rule is in the data model, not the policy page.
Agents as first-class actors
LATERWhen agents open PRs on their own, they join the record next to the people who run them — what they did, what it cost, what's stuck.
One install line. Then it works while you do.
Share one install line
Each engineer runs one pinned, checksummed script. Session metadata starts syncing; the supervisor and team notes are one opt-in command each. No admin key, no procurement thread to start.
It works while you work
When a session loops, the supervisor steps in on the laptop — context, a new approach, then a heads-up. When someone gets unstuck, their fix becomes a draft only they see until they share it.
It writes the record
Every week, the story lands for each altitude: a private recap, a standup nobody had to write, the team brief — and, for enterprise pilots, the roll-up to leadership. Quiet weeks get a record too.
One install per laptop. No admin key, ever.
Engineers sync from their own machines. Every source lands in the same schema, so the record never cares which tool the work came from.
Claude Code
Session-grain metadata straight from each engineer's machine: turns, duration, model, cost, files-touched counts — plus the live supervisor hook.
Cursor
Next in line. Cursor sessions join the same record 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 — counts, never file paths. Content only if you turn on team notes: a redacted excerpt of a stuck stretch, for your private draft. Revocable per device.
Built to pass the security review, not to dodge it.
Everything on the left is running today. Everything on the right we build for a signed pilot — we'd rather say “on request” than check a box we can't back.
Named data is stored only for people who joined a roster; everyone else is a count. Not a display filter — the rows never exist.
Session content moves only through team notes: engineer opt-in, secrets scrubbed on the laptop and again on ingest, private draft, raw excerpt deleted.
Each laptop holds its own token (0600). It can send its own sessions and read only notes your team shared. Revoke one device without touching the rest.
Any vendor key is AES-256-GCM encrypted at rest; every query is scoped to your org.
Append-only audit log of briefs, joins, device mints and shares; session data purges after 180 days; self-serve deletion for every engineer.
Sign-in through your IdP; roster invites pre-filled from your directory — joining stays each engineer's choice.
Admin / manager / viewer, and roll-ups from team to director to VP with the same-view rule intact.
Exportable audit trail; Postgres row-level security; dedicated database or VPC deployment for data-residency needs.
DPA, sub-processor list and a security questionnaire, done with you rather than at you.
A record your engineers would sign off on.
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 recaps, the supervisor's log and draft notes stay private to the engineer — a note reaches the team only when its author shares it, and anyone can delete their own data whenever they want.
Session counts, turns, duration, files-touched counts, model and cost. Session content moves only if an engineer turns on team notes — and then only a redacted excerpt of a stuck stretch, for a draft only they see.
Nothing to paste, nothing to escalate. Each laptop gets its own token, stored 0600: it can send its own sessions and read only the notes your team chose to share. Revocable per device.
Drafts are private. Keys and tokens are scrubbed on your laptop and again on our side, and the raw excerpt is deleted once the draft exists. A note reaches your team only when you press Share — and you can unshare it.
Briefs are written on Throughline's own API key, at our cost. Engineers can delete their synced data and notes in one click; session data older than 180 days purges itself.
Where the record goes from here.
No dates — the teams using it decide the order. What doesn't change: opt-in, private until shared, same view at every level.
A standup that talks back
Needs-attention items become a question to the engineer. Their answer — labeled as theirs, not verified — lands in next week's record instead of a meeting.
Coaching with the dollars attached
Your recap names the habits that burn tokens — retry loops, a big model on small work, context that never caches — with what each cost and what changing it saved. From session shape, never your prompts.
A record that checks itself
Before it writes, the brief verifies its claims against your tickets and past weeks — so "shipped" means shipped.
WHAT WE WON'T BUILD: a dashboard · a leaderboard · a manager-only view · anything that shares your work without your OK
Put your org's agents on the record.
Leave a work email and we'll set up a pilot with you — your security questions, your rollout, your first record, done together. Small team? Start free and read your first brief in ten minutes.