Review every agent edit with tracked changes

Shannon’s agent now edits your document directly, and every change it makes lands as a tracked edit you give one of four answers: accept, reject, rewrite, or branch. You review the agent’s work the way you review a teammate’s marked-up draft. Reviewing is a skill you already have; describing edits to a machine never was.

This is the pillar Shannon stands on: Transparency builds trust. If you can’t see what an agent did, you can’t trust it with your documents. I built the review interface because today’s tools make you work the other way around: you describe the change you want in words, get a fresh copy back, and re-read the whole thing to find out what else moved.

Give every edit one of four answers

You type what you need once, in plain words: “Update the competitive analysis with Q1 data.” No back-and-forth, no learning to phrase things just right. The agent reads the other files in your workspace, opens the document, and makes its edits there. A side panel streams its progress step by step, so you can watch it think or ignore it until it’s done. Either way, the result isn’t a message about a document. It’s the document, edited, with every change flagged the way a coworker’s tracked changes are.

Then you walk through the edits and answer each one. Accept locks a change in. Reject removes it. The other two answers are for the edits that are almost right.

Rewrite an edit and your wording becomes what the agent works from

When an edit is close but not quite, don’t explain what’s wrong with it. Rewrite it yourself, and your wording becomes the version the agent works from. There’s no round trip where you translate “this paragraph, shorter” into careful instructions and then check whether the agent translated it back the way you meant. You just write the sentence you wanted.

Branch a section for a different take

When one part deserves another attempt, select the section, say what you’re after (“more concise”), and the agent drafts an alternative for that part alone. A branch touches only what you pointed at. There’s no third rewrite where the agent reworks the parts you’d already made peace with.

Under the hood

Each answer applies surgically. Reject deletes exactly one tracked change, and nothing regenerates: no second agent pass, no reworked paragraphs around it, everything else exactly as you left it. Hovering over accept or reject renders the document that answer would produce, so you see the result before you commit, not an approximation of it. And every version of the document is kept along the way, so no answer is a one-way door.

The feeling I’m after is ordinary on purpose: a competent colleague handed you a draft, marked their changes, and can explain their thinking when you ask. Open shannon.bot and try it without signing in — hand the agent a document, and answer its edits.