Open-source tooling for technical work with AI

Put your AI’s plans
through a proper review.

Your AI writes the Markdown. You and your colleagues work through it. Leave comments on the passages that matter, let your AI tool revise, and review the diff before moving on.

Get the source on GitHub

Or self-host the whole tool.

Recorded in RevisedA release plan, before and after feedback
A colleague’s rollback question beside the old and new versions of a technical plan.
See the change and the feedback it answers.Full size ↗
  • Plain Markdown
  • Real Git repositories
  • No registration for reviewers
  • AGPL-3.0

The loop around the work

Plan. Discuss. Revise.
See what changed.

Use the AI tools you already have. Keep the plan, the conversation, and the next version in the same place.

01 / THE PLAN

Give the plan
a place to land.

Connect Claude Code, Codex or any tool that speaks MCP with one line, then sign in and press Allow. It can publish a plan, read your comments, and push revisions on your behalf. You can also drop in Markdown you already have.

A document can hold several pages, diagrams, equations, and references. The defaults are ready to read.

How to connect a tool
A technical plan with several Markdown pages and supporting files, published in Revised.
From Markdown files to a readable plan.Full size ↗

02 / THE FEEDBACK

They get an email.
They open it.
They comment.

No account registration. Your colleagues follow the link in their email and leave feedback beside the right passage. That’s it.

There is no team subscription to arrange and no platform rollout to negotiate. Share one document, with the access each person needs.

ReadCommentCompareEditInvite

Ask for a decision on one version, or just open a discussion. Your AI tool can read the feedback too.

An invited colleague commenting on a particular sentence, without a registration form.
Invite → open the email link → leave a comment.Full size ↗

03 / THE NEXT VERSION

Check what changed.
Keep what works.

Work through the comments yourself, or ask your AI tool to do it. Compare the result with the version your colleagues read: additions, removals, and the original feedback stay in context.

Explore an alternative on a branch. Switch between drafts. Merge a useful change back into the plan. Revised keeps every saved version.

Parallel drafts in the version graph, with a selected branch ready to merge into the document.
Two drafts. One reviewed merge.Full size ↗

Git is the foundation

It’s a repository.
Use it like one.

Clone it. Branch it. Push to it. The browser and your local tools work on the same history. Your AI tool can make a draft with ordinary Git, and you can review and merge it in Revised.

  • Compare versions as rendered prose, rather than hunting through raw Markdown.
  • Work in parallel with separate branches for alternatives or different contributors.
  • Keep your tools with native Git over HTTPS.
  • Take the work with you: git clone it, or Download a copy.

Get your exact clone command in Manage document → Export data. When Git asks for a password, paste a named key from Account.

Your terminal. Your usual Git.
# Clone the document with its history
git clone <your-document-url> release-plan
cd release-plan

# Let a person or an AI tool explore a draft
git switch -c rollback-checks
git add .
git commit -m "Add recovery checks"
git push origin rollback-checks

# Review and merge in the browser,
# or keep working with Git locally.

Plain files and commits. No special Git client.

Useful after the conversation

Find the plan again.

Technical plans can be short-lived. Their reasoning often isn’t. Keep the pages, discussion, drafts, and history together; use tags and search when you need them again.

Saved plans found with live search and organized with tags.
Search the work. Keep its context.Full size ↗

When you need a formal copy

Send a proper PDF.

Typeset the same Markdown, with equations, figures, citations, and a bibliography. Include highlighted comments for feedback or export a clean final. One style file can customize every page.

The same technical plan exported as a typeset PDF.
A PDF from the source you reviewed.Full size ↗

One line, then the same loop

Connect the tool
you already plan with.

Revised doesn’t supply a model. Claude Code, Codex, Claude, ChatGPT, Cursor and any tool that speaks MCP connect with one address, and get the same tools and the same review loop.

  1. 1

    Connect it.

    Claude Code, with the Revised plugin:

    claude plugin install revised --marketplace LiamBindle/revised.md && claude mcp login plugin:revised:revised

    Codex, with the instructions that have it put every plan to you:

    codex mcp add revised --url https://revised.md/mcp && mkdir -p ~/.agents/skills/revised && curl -fsSL https://revised.md/skill.md -o ~/.agents/skills/revised/SKILL.md

    Claude, ChatGPT, Cursor and the rest take the address https://revised.md/mcp. Account → Keys has the steps for each.

  2. 2

    Sign in and press Allow.

    Your browser opens on Revised. Nothing is copied by hand, and Account → Keys lists every tool you connect, with Revoke beside it.

  3. 3

    Review its plans.

    Before it starts work, the tool puts its plan up and asks you to go ahead. Comment on the lines that are wrong: it revises, and you compare the versions.

In Claude Code the plugin can also replace the plan dialog: leaving plan mode puts the plan here and waits for your answer, with a key for plan mode. Git and scripts use a key from Account → Keys. You can also bring in Markdown from ChatGPT or your editor.

A tool I needed for my day job

Open source.

I built Revised to make this part of my own work easier. You can use the source, host it yourself, fork it, and improve it.

Your server

Run your own copy.

Every feature, with no fair-use limits. One Go program, SQLite, and a folder of Git repositories.

git clone https://github.com/LiamBindle/revised.md
cd md
echo '{"owners": ["you@example.com"]}' > revised.json
docker compose up --build -d
docker compose logs revised
Get the source

AGPL-3.0. Needs only Docker with Compose; the image includes Git. One configuration file names who may create documents; the logs print your first sign-in link. The self-hosting guide covers HTTPS, email, and backups.

A few practical details.

Do my colleagues have to register?

No. You invite them by email. They open the link and comment in their browser. There is no registration form, password, or separate subscription. They can start with just one document.

What can I share with someone?

Choose Read, Comment, Compare, Edit, or Invite. Compare includes saved history and diffs. Edit includes changes, drafts, and merging. Invite also lets them bring other people in. Access belongs to the person; removing them leaves their earlier writing in the history.

Can a plan be more than one Markdown file?

Yes. Keep related pages, diagrams, code snippets, references, and supporting files in one document. A SUMMARY.md file sets page order. The file list connects the pages, and PDF export typesets them together.

What can an AI tool do on my behalf?

A named key can read, write, and comment where you can. It can publish a plan, read the discussion, revise files, and ask you to decide something. Its work is attributed to you and the key’s name. It cannot invite people or answer a question meant for you. Revoke a key in Account when it’s no longer needed.

Can I use it without AI?

Yes. Write in the browser or push Markdown with Git. Comment, compare versions, share drafts, and export a PDF in the same way.

Can I change the PDF style?

The default works without setup. Add a root-level style.typ to extend it; references.bib and an optional references.csl provide the bibliography and citation style. Those files apply to every page. Manage document → Export data includes the default PDF style to download. The file reference has examples.

Start with one plan

Give the next revision
a better starting point.

Publish the plan. Read the feedback. Review what changed.

Or start with the source