Review and Resolve Agent Notes

Agent notes are a lightweight ticketing system built into your site: trackable work items that you and your agent both use — to report bugs, capture tasks, plan follow-ups, and discuss them. This guide covers reviewing, discussing, and resolving them.

An agent note is a trackable work item. Think of it as a ticket on a shared board: it has a status you move it through, a priority, a category, and a comment thread for discussion. Notes outlive any single conversation, so a thing raised today is still there next week, for you or for a different agent. (See The Notes System for how agent notes sit alongside operator notes and knowledge.)

Either side can create them. An agent raises notes as it works — flagging a bug it hit, an inefficiency worth improving, or a suggestion — either on its own judgment or because you’ve given it a standing instruction to (via an operator note, e.g. “log an optimization note whenever you hit a slow step”). And you can ask the agent to open one anytime, for anything you want tracked:

“Open an agent note to follow up on the checkout page slowness next week.”

So agent notes aren’t only “the agent reporting to you” — they’re a general task and issue tracker the two of you share.

Reviewing what’s on the board

Ask your agent what’s open:

“Show me any open agent notes.”

You’ll get each note’s title, kind (bug, optimization, task, suggestion), priority, and status. To dig into one, ask the agent to open it in full:

“Open note 62 and show me the details and comments.”

Comments: the discussion on a note

Each note carries a comment thread — the running record of context, findings, decisions, and back-and-forth about that item. Comments are how a note becomes more than a title and a status: they’re where the why and the what-happened live.

• Read them to understand a note’s history: “What are the comments on note 61?” Opening a note shows its most recent comments; for a long thread you can ask the agent to pull the rest.
• Add them to record something for later — a decision, a test result, an instruction, your reasoning: “Add a comment to note 62: deferring this until after the holiday sale.”

Comments are append-only — they form a permanent log that can’t be edited or rewritten, so the thread is a trustworthy account of how a note progressed. Both you and your agents can post them.

The lifecycle: from raised to resolved

A note moves through a defined set of statuses, so a tracked item gets worked and confirmed rather than just noted and forgotten:

The important part is the loop between verify and fix. When the work is made, the note moves to verify — “this looks done, confirm it.” If confirmation shows it’s genuinely solved, it becomes resolved; if it fell short, it goes to fix and round again. A note doesn’t jump straight to resolved — it earns it by being verified. That’s what stops things being marked done when they aren’t.

Working a note through, in practice

You drive this in conversation; the agent does the legwork:

1. Review — “Show me open agent notes.”
2. Pick one up — “Acknowledge note 62 and let’s work on it.” The agent marks it acknowledged and starts.
3. Do the work — the agent makes the change and moves the note to verify, often leaving a comment on what it did.
4. Confirm — you or the agent check it. Genuinely fixed? “Confirmed, mark it resolved.” Not yet? “Send it back to fix,” and it loops — ideally with a comment saying what’s still wrong.

Not every note runs the full cycle. A suggestion you won’t pursue, or an issue that no longer applies, should be archived — kept in the record without being resolved.

Notes you route rather than resolve

Many notes an agent raises are technical — a bug in how an ability behaves, a suggested plugin improvement. You won’t fix those yourself; route them instead. Assign a note to the right person so it’s clearly theirs:

“Assign note 61 to <user> — it’s a developer issue.”

Genuine plugin bugs are also worth passing to Maxi’s makers, so they’re fixed at the source rather than only worked around on your site.

In summary: agent notes are a shared ticketing system — both you and your agents create them, to report bugs, capture tasks, or plan follow-ups. Review what’s open by asking your agent; use the comment thread to read and record context, decisions, and results (comments are permanent and can’t be edited). Move each note through its lifecycle — acknowledged, verify, resolved — using the verify-and-fix loop to confirm something is truly done before closing it. Archive what you won’t action, and assign technical issues to a developer.