Skip to main content

You read. It writes.

Stet is a native macOS app for a world where 100% of code is written by AI — a code viewer and direction surface, not an editor.

Read the docsThe PR/FAQ
The Stet canvas — a Scheduler.swift diff with a guided Tour stop and an anchored margin comment asking a question about the change.

The canvas: read the diff, follow the AI’s Tour, and mark it up in the margin. Submitting compiles your marks into one brief.

A viewer, not an editor

Read AI-written code and prose. Comment, react, suggest, and vote. The keyboard is for opinions, not code.

Local, sandboxed agents

Submit feedback and a sandboxed agent runs on your Mac — Apple containers or Docker — and opens a pull request.

Bring your own model

Any OpenAI-compatible endpoint. Pluggable harnesses: OpenHands, Crush, Pi. Cloud or a local model.

The project learns

Every dispatch is a versioned trajectory. Distillation turns feedback into reusable skills, committed back to the repo.

Social by design

Comments and reactions ride the forge; a Dolt store versions the rest. Humans and agents vote — humans decide.

A config ecosystem

Agents, Skills, and Verbs versioned across a .stet topology — importable, signed, and governed like software.

The Stet inbox — a kanban of pull requests and files awaiting your stet, grouped Needs review / In progress / Done.
The inbox

An inbox, not a file tree

Stet opens to what is waiting for your stet — PRs and files grouped by where they are in the loop. Read what an agent wrote, not a directory of everything that exists.

A Stet trajectory replay — six numbered steps, a secret-scan-passed badge, a redacted forge token, and per-hunk human and agent votes.
Dispatch

Watch the agent work, then keep the receipt

Submitting a review dispatches a sandboxed local agent that pushes commits to your PR. Every run is captured as a reviewable trajectory — commands, redactions, and cost — committed in-repo like any other artifact.

The Stet provenance view — a vertical lineage tracing a line of code from human markup through brief, dispatch, and commit.
Provenance

Trace any line back to the feedback that made it

Markup → brief → dispatch → commit, with the skills and votes that weighed in branching off the spine. In a world where the code is written for you, provenance is how you trust it.

The Stet first-run window — "You read. It writes." with Sign in with GitHub and Connect a Gitea instance.
Your repo, your Mac, your model

Read-only until you say otherwise

Sign in to GitHub or a Gitea instance, point Stet at your model, and it stays read-only until you dispatch. The wedge is local, sandboxed agents — nothing leaves your machine unless you send it.