Skip to content

How it works

You open a file, agents work on it, a human signs off.

Agents draft, suggest and comment. People accept, reject and approve. Every save becomes an attributed version you can restore.

Who is in the workspace

Five roles share one document, and each needs something different from it.

Each gets the actions their job needs and no more — a reviewer never has to learn an editor, and no agent can approve anything: sign-off is always a person's.

Five columns describing who shares a DraftMesh document. The author drafts in plain markdown and accepts or rejects suggestions. The reviewer highlights a sentence and types. The approver approves a specific version, often from the phone queue. The guest opens one shared document on a scoped link. Local AI agents use the DraftMesh CLI and skill to read, comment and propose; hosted agents use the cloud connector on synced workspaces. They can never approve, restore or share.
Everyone works on the same plain file, and every mark made on it carries a name.

On the free local app it's you and your agents on your own machine. Guest review links and phone review come with Individual; named teammates with verified identity come with Team.

01

The author

Writes the thing. Drafts in plain .md on their own disk, hands a first pass to an agent, and accepts or rejects every suggestion that comes back.

02

The reviewer

Knows whether it is actually true. Highlights the sentence they doubt and types a comment — no install, and nothing borrowed from developer tooling.

03

The approver

The one whose yes counts. Approves a specific version rather than "the document", usually by clearing a queue on their phone.

04

The guest

Outside counsel, a customer, a subject-matter expert for one week. Opens one shared document — not your workspace — and loses access when the link expires.

05

Your AI agents

Named participants, not a plugin. Each reads, searches, comments and proposes changes under its own name. A person can let an agent accept suggestions, on one document or as themselves; approving, restoring and sharing always stay with people.

One document, end to end

From a file on your disk to a version somebody signed off on.

Five steps, with no hand-off to another tool — it all happens in the one file.

A five-step flow across four swimlanes — author, AI agents, reviewers and guests, and approver. Step one, draft the file in place. Step two, ask an agent, which returns suggestions signed with its own name. Step three, reviewers and guests question and suggest on the rendered text. Step four, a human accepts or rejects and the approver signs off on one version. Step five, the save is kept as a restorable version. Accepting suggestions can be delegated to an agent by a person; approving, restoring and sharing are always human acts.
At no point does the document leave your machine unless you switch sync on for that workspace.
  1. 01

    Draft

    Start from a file in a folder you already have. Point DraftMesh at it and start writing — no import and no upload.
  2. 02

    Ask an agent

    Hand a connected agent the whole document or one heading, with a brief. It comes back as suggestions and comments signed with its own name.
  3. 03

    Review in place

    People highlight the sentence they doubt and comment. Questions become threads on the rendered text; better wording becomes a suggested edit.
  4. 04

    Decide

    A human accepts or rejects each suggestion, and the approver signs off on one specific version — a step no agent can take, however much it has been granted.
  5. 05

    Keep

    Every save becomes a version, credited to its author and searchable. If the answer changes later, restore an earlier one in a click.

The boundary

An agent proposes. Approving stays a human act.

DraftMesh enforces this rule itself instead of trusting an assistant to behave.

A person and an AI agent, each connected by a line to the same draft document, which flows on to a check mark.

An agent can

Read and search · comment and reply · ask and answer questions · suggest an edit · save where it holds edit (on by default on a workspace kept only on your machine) · ask a person to sign off.

Only where a person turns it on

Accept or reject suggestions. Off by default, with three ways in: a document's owner grants it to one agent on one document; you let assistants on your account accept as you; or, on your own machine, a per-workspace switch. Every accept is credited to the agent.

No agent, ever

Approve or sign off a document · restore an earlier version · share a document or invite a guest.

Use them

Both diagrams are yours to reuse.

Plain SVG, so they stay sharp in a deck, a printout, or your own onboarding docs. They are the same two files the in-app user guide uses.

Good work. Woven together.

The local app is free forever — no account, no upload, no card. Your markdown never leaves your machine.

Free forever, local, no account