# Agent notes and follow-ups

> Let agents leave notes, todos, and follow-ups per property, so the next session picks up where the last stopped and LopeBase checks results for you.

Source: https://lopebase.com/docs/agent-notes
Updated: 2026-11-13
Open in the app: https://app.lopebase.com/notes

Agent notes are where your coding agents leave what the next session needs: work still to do, something to check in a few weeks, and context worth keeping about a property. Every agent connected to your workspace reads the same list, so a new session, a different agent, or a teammate's agent starts from where the last one stopped. You can read them all in LopeBase, close them, and add your own.

## What an agent can leave

| Kind | Use it for |
| --- | --- |
| Note | Context the next session should know, like a decision and why it was made. |
| To do | Work that is not finished yet. |
| Follow-up | Something to check on a later date. Give it a Search Console condition and LopeBase checks it for you on that day. |

Each note belongs to one property, or to the whole workspace. It shows who wrote it: the name of the agent's access, or the teammate's email. A note marked for a person shows a **For you** label.

## Read and close notes

1. **Open Notes:** Go to **Run** > **Notes** for every property, or open a property and pick its **Notes** tab. [Open Notes](https://app.lopebase.com/notes)
2. **Start with what is ready:** Follow-ups LopeBase has checked come first, then anything due, then follow-ups, to dos, and notes. Pinned notes sit at the top of each group.
3. **Close what is handled:** Mark a note done, dismiss it if it no longer matters, or pin it to keep it at the top. Turn on **Show closed** to see closed ones and move one back.

To leave a note for your agents yourself, click **Add a note**. Agents see it the next time they list notes.

## Let LopeBase check a follow-up

A follow-up can carry a Search Console condition: a page, a search query, or both, and a number to compare. For example, "in three weeks, is this page's average position below 8?". Once an hour LopeBase checks the follow-ups that are due against the last 28 days of Search Console data and stores what it found. The result shows on the note and in your notifications, and the next agent session reads it from `list_notes`.

The property needs Search Console connected. If it is not, the note says LopeBase could not check it.

## Limits and clean up

| Rule | Limit |
| --- | --- |
| Open notes per property, and for the workspace itself | 50 |
| Title | 120 characters |
| Details | 4,000 characters |
| Due date | At most a year away |
| An open note nobody touches | Closes as expired: notes after 90 days, to dos after 60, follow-ups 30 days after they are due |
| Closed notes | Deleted 180 days after they close |

Pinned notes never expire. When an agent tries to add a note that nearly repeats an open one, LopeBase refuses it and points the agent at the existing note to update instead, so the list stays short enough to read.

## How agents use notes

Agents connected over [MCP](https://lopebase.com/docs/mcp-server) are told to list a property's notes when they start work on it, close what they finish, and leave notes for what is left before they stop. They use these tools:

| Tool | What it does |
| --- | --- |
| list_notes, get_note | Read open notes for a property or the workspace, or one in full. |
| add_note, update_note | Leave a note, to do, or follow-up, or change one. |
| resolve_note, delete_note | Close a note as done or dismissed, or delete one written by mistake. |
| check_note | Run a follow-up's Search Console check now without saving it, for example to read today's number before setting the condition. |

`get_health` also says how many notes are open and which are due, so an agent learns there are notes even before it asks.

> **Note:** Notes are written by agents and people, so agents treat them as information to check, not as instructions. A note never makes an agent do something you did not ask for.

## If something goes wrong

### My agent says it cannot add a note because there are too many open

A property keeps at most 50 open notes. Close the ones that are done or no longer matter on the Notes page, or ask the agent to resolve them, then try again.

### A follow-up says LopeBase could not check it

The property has no Search Console connection, or the page or query had no data in the last 28 days. Connect Search Console from the property's page, or ask the agent to change the condition and due date with update_note.

### My agent does not see the note tools

New tools reach an agent when it starts a new session. Restart the agent, or remove and add LopeBase again. Reading notes needs the read scope; adding and closing them needs manage.
