Docs: The review loop with your agent
Docs / Using Markloop

The review loop with your agent

How your AI agent pulls review comments, fixes the document, and publishes a new version at the same link.

View as Markdown

The loop in short

  1. You publish a document.
  2. Reviewers leave comments.
  3. Your agent pulls the comments.
  4. Your agent fixes the document on your computer or in your AI tool.
  5. Your agent publishes a new version at the same link.

Markloop never runs an AI model on its server. All reading and editing happens in your AI tool.

Example prompts

Talk to your agent in plain language. For example:

Publish a document

Send this proposal to Markloop, in the Acme project, and give me the link.

Read the feedback

What did Acme say about the proposal? Group the comments by section.

Fix and publish

Address the open comments on the proposal and publish the next version.

Answer a reviewer

Reply to comment 4: weekly reports aren't in phase 1. Ask if monthly works.

Compare versions

What changed between version 2 and version 3 of the spec?

Send a client copy

Send a clean copy of the spec to the Acme client project, without our internal comments.

Address the comments

To address review comments, ask your agent:

After reviewers comment

Address the open comments on the proposal and publish the next version.

The agent then:

  1. Pulls the document and its open comment threads (markloop_pull). A thread includes the first comment and all replies, and the agent reads the replies before it acts, so it doesn't ask a question someone already answered.
  2. Downloads the document and fixes it.
  3. Uploads the fixed file as a new version (markloop_put_version). The new version keeps the same link and the same document ID.
  4. Marks the comments it addressed, which show as addressed in the new version.
  5. Replies to each thread it skipped, with the reason.

If someone else uploaded a version while the agent was working, Markloop rejects the upload. The agent pulls again and retries.

Comment numbers

Each comment thread has a number, and it's the same in the app and in your agent. You can write "fix comment 7" and the agent finds the right thread.

Versions

Markloop keeps every version. A comment belongs to the version it was made on. Open comments from older versions also show on newer versions, with a label saying which version they came from.

If a reviewer has the document open when you publish a new version, a banner shows the version numbers, for example "You're viewing version v2 — a newer version v3 is available". The reviewer clicks See latest.

Compare versions

To see what changed between versions, ask your agent:

Compare versions

What changed between version 2 and version 3 of the spec?

The agent reads both versions (markloop_list_versions, markloop_get_version) and compares them itself. The app doesn't show a visual diff.

Ask your agent to review

Your agent can also act as a reviewer and open a new comment thread on a quoted passage (markloop_create_comment). Use this for questions and objections.

Send a clean copy to a client

You can give a client a copy of a document in another project, even in another workspace. The copy starts as version 1 with no comments, and your internal comments stay in your project.

Ask your agent:

Send a client copy

Send a clean copy of the spec to the Acme client project, without our internal comments.

The agent calls markloop_publish_document. Later, to refresh the client's copy, ask:

Refresh the client copy

Update Acme's copy of the spec with the latest version.

The agent calls markloop_republish_document, which replaces the version the client sees. Most AI apps ask you to confirm before this runs. Comments the client made stay on the client's copy. To address them, run the normal loop on the client's project.

Work with comments in the app

In the viewer, the Comments panel lists the threads on the document. Use the Open, Resolved and All filters to switch between them. Resolved threads are hidden until you pick Resolved or All.

  • Resolve closes a thread, and Reopen opens it again. Anyone who can edit the project can resolve any thread. Invited reviewers can resolve only threads they started.
  • You can edit or delete your own comments. Delete thread removes a thread with all its replies. Project owners and workspace admins can delete any thread.

Organize documents

  • Rename a document: in the viewer, click the title and type a new one. In the project, use Edit title or Rename file in the document's menu.
  • Folders: in a project, click New folder. Use Move in a document's menu to put it in a folder. Folders have the same access as their project.

Limitations

  • The agent marks comments as addressed. Markloop doesn't detect this itself.
  • Your agent needs edit access to a project to publish versions. Reviewers can't publish versions.
  • The app doesn't compare versions visually. Your agent does the comparison.
  • Reviewers see a new version when they click See latest or reload. Markloop doesn't send an email when you publish a new version.

For the full list of tools, see MCP tools.