You're the copy/paste layer.

Copy. Alt-tab. Paste. Wait. Copy. Alt-tab. Paste.

The window that wrote it

> brief for the cohort work Implement cohort infrastructure. Do NOT change existing badge logic. Acceptance: denominator visible on all 14 states…

you

The window that built it

> Implement cohort infrastructure. Do NOT change existing badge logic. Acceptance: denominator visible on all 14 states… working…

91%of our tasks began with a brief we didn't write

246copies, word for word, both halves in one file

6,105messages measured across two years

We did this every day.

So we measured two years of it.

It was worse than we thought.

Now measure yours.

What comes back

Four numbers. Yours.

91%

Briefs you carried, not wrote

Opened with text an AI wrote and you moved.

54%

Messages that were pure relay

Pasted from elsewhere. Nothing of yours added.

34%

Turns spent on setup, not decisions

Env vars. Tokens. Dashboards.

9

Longest unresolved loop, in turns

One problem. Nine round trips. One afternoon.

Before you ask

Your file never leaves this page.

No upload. It's parsed in your browser.
No server. No account, no email.
No memory. Close the tab and it's gone.
No reading. We count shapes, not words.

Your export holds two years of your life. We know. That's why it stays on your machine.

No export yet? ChatGPT → Settings → Data controls → Export. See a sample report first

If this is you

We're building the fix.

Rebase sits between you and your coding agents. It holds the brief, so nothing moves by hand. It handles the env vars, the tokens, the dashboards. It checks that work actually landed instead of taking an agent's word for it. And it only asks you the questions you're the right person to answer.

Measure first. If your number is low, you don't need us.

15 connections, every one of them through you