---
title: "Review Agent Runs"
description: "The shared review queue, what a run's page shows, how Undo and Revert work, and how to fix an agent's instructions."
canonical_url: "https://docs.basicmemory.com/agents/review-runs"
---
# Review Agent Runs

> The shared review queue, what a run's page shows, how Undo and Revert work, and how to fix an agent's instructions.

Agents change your notes as soon as they finish. The **review queue** is where you look at what they did. It's shared with everyone in the workspace: when one person deals with a run, it leaves the queue for everyone.

## The review queue

A run joins the queue when it finishes and:

- **changed notes**: it reads like "Meeting follow-up created 3 notes and edited 1 from Standup", with what changed underneath (`+3 created`, `1 edited`);
- **needs attention**: it failed (for example, it ran out of time), or couldn't run for a reason someone can fix, such as an agent note that isn't valid or a person who lost edit access. These come first, marked red.

Runs that found nothing to do, or found the work already done, never join the queue. The line under the queue counts them and shows who reviewed the latest runs.

A run stays in the queue until someone deals with it. Nothing is accepted automatically. Unreviewed runs leave the queue when runs are cleared after 30 days.

### Deal with a run

- **Keep** (or **Looks good** on the run's page): the changes are right. Your notes don't change; the run is marked kept by you and leaves the queue.
- **Review**: opens the run, with its changes shown so you can read them before you decide.
- **Undo run** (on the run's page): puts the notes back the way they were before the run, then marks the run undone.
- **Dismiss** (for a run that needs attention): you've seen it. **Run again** starts the same agent on the same note.

<note>

**Editing counts as keeping.** If you or a teammate edits a note the run changed, the run is marked kept, for example "kept when Maya edited Standup". You accepted the agent's work by building on it.

</note>

## A run's page

A run's page leads with what came of it, then shows the evidence.

<theme-image alt="A finished Meeting follow-up run: three task notes created, two existing tasks linked, and a summary added to the meeting note" dark="/screenshots/cloud-app/agent-run-details-dark.png" light="/screenshots/cloud-app/agent-run-details-light.png">



</theme-image>

1. **What came of it**: one line, such as "Created 3 notes and edited 1 from Standup" or "Ran out of time on Standup", with **Looks good**, **Undo run**, and **Adjust instructions**. Once someone has reviewed the run, the line says who and when.
2. **What changed**: each note the run created, edited, moved, or deleted.

  - An edited note opens with its changes shown. Bookkeeping the agent adds to a note's frontmatter (such as `updated_by`) folds into one **Properties** line; **Show** brings back the full diff.
  - A created note shows the start of what it says.
  - **Revert** puts one edited note back without undoing the rest of the run, and **Restore** brings back one deleted note.
3. **What the agent said**: its own summary of what it did. **Full log** opens the run's log note, `agents/runs/<agent> run <id>`, which keeps everything the agent said.
4. **How it got there**: each step the agent took, folded away until you want it.

<theme-image alt="The diff of one note a Stale facts run edited, moving the launch date from February 26 to March 12, with Looks good, Undo run, and Revert" dark="/screenshots/cloud-app/agent-change-review-dark.png" light="/screenshots/cloud-app/agent-change-review-light.png">



</theme-image>

### What Undo can and can't put back

Undo is safe: it never overwrites an edit someone made after the agent. If a note changed since the run, Undo leaves it alone and offers its [version history](https://docs.basicmemory.com/cloud/file-history), where you choose what to keep.

- **Edited notes** go back to their text from before the run.
- **Deleted notes** come back at the same path, with their text from before the run. If another note now has that path, Undo leaves both alone and says so; move the other note and try again.
- **Moved notes** go back to the path they had before the run, along with their earlier text if the agent also edited them. If another note now has that path, Undo leaves both alone and says so.
- **Created notes** are deleted, unless someone edited them after the run; an edited one stays, and its version history keeps the agent's text.
- **Notes deleted after the run** are marked **Deleted since**. Their changes can't be shown or reverted from the run's page; a [snapshot](https://docs.basicmemory.com/cloud/cloud-snapshots) may still have them.

## When an agent gets it wrong

Change its instructions and try again on the same note.

1. On the run's page, choose **Undo run** if its changes should go, then **Adjust instructions**.
2. The page shows what the run did, beside the agent's instructions.
3. Change the instructions yourself, or let your own agent help. Under **Fix it with your agent**, say what went wrong ("it made tasks for everyone, not just my items") and choose **Copy for your agent**. Paste it into Claude or another agent connected to Basic Memory: it reads this agent and the run, proposes better instructions, and edits the agent note when you agree. **Copy agent link** copies just the agent note's link.
4. **Starts** and **Folders or patterns** set what starts the agent; **Show frontmatter** has every other setting.
5. Choose **Save and run again** to try the new instructions on the same note, or **Save** to keep them for next time.

A failed run says where the agent got stuck. When failures keep happening (two or more of the last five runs), the run says so: clearer instructions usually fix it.


## Sitemap

See the full [sitemap](https://docs.basicmemory.com/sitemap.md) for all pages.