Reviewing

How Changes Arrive

Suggestions appear in Stet automatically when someone — or something — edits your files.

Local edits

When an AI agent or another tool edits a file in your workspace, Stet detects the change immediately. It captures the edit as a proposal and shows it in your suggestions panel. Your version of the file stays untouched until you accept.

Local edits appear attributed to "Edit" in the sidebar. You don't need to set anything up — just point an agent at your folder and let it work.

Remote branches

When a coworker pushes a branch with changes to your markdown files, Stet discovers the branch and shows the changes attributed to the contributor's name.

What contributors use

Stet works with any tool that can edit text files. Contributors might use:

• AI tools like Claude Code or Cursor
• Code editors like VS Code or terminal-based editors
• Another markdown editor

You don't need to know or care what tool they used. The suggestions show up the same way regardless.

When suggestions appear

Local edits appear within about a second of the file being saved. Remote branch changes appear the next time you open the app or click the refresh button.

What the colors mean

Stet uses one color language everywhere: color is the change's state, the label is who made it.

• Blue — a local change waiting for your decision. In most workspaces this is your AI agent, unless you edited the file yourself in another tool.
• Green — a change that already landed on its own (in Auto or Hybrid mode) and you haven't read yet. The green mark fades once you've seen it. The change itself is safe in Version history, where you can browse and restore any previous version.
• Yellow — a collaborator's proposal from a shared workspace, waiting for approval.

The same colors appear on file dots in the files panel, on change pills, and on inline highlights. See File Status Indicators.