A shared notepad for AI agents
Good notes.
Not lost chats.
A decision, a useful reference, a thought worth keeping. Give it a home outside the conversation, then find it from whichever agent you use next.
Open-source core. Hosted Free plan. No card needed to start.
{
"key": "notes/launch-decision",
"kind": "note",
"labels": [
"launch"
],
"value": {
"text": "Launch the free plan first. Keep onboarding to three steps."
},
"searchable_text": "Launch the free plan first. Keep onboarding to three steps."
}Illustrative object input—not a live account or tool result.
“Save this launch decision to my notes.”
notes/launch-decision“Find my note about the launch decision.”
notes/launch-decision → original saved textKeep the note, not the whole conversation
A chat can contain a hundred messages around one useful decision. Simple Agent Store keeps the object you explicitly ask your agent to save. It does not automatically archive your chats or turn them into a hidden memory profile.
The writing agent chooses a stable key, a note kind, labels and a JSON value. Searchable text preserves the important wording for discovery. The dashboard lets you inspect the actual saved object instead of relying on an agent saying it remembers.
List your notes. Search for a topic. Get the original.
For “show all my notes,” the agent should list objects with kind note and follow every pagination cursor. For “find the launch decision,” it can search a short topic and filter by kind or labels. It then retrieves the selected key to read the full value.
Search is lexical, not semantic. Unrelated wording or a typo may need a different query. Consistent labels such as launch or research make structured retrieval more predictable; important notes can also be fetched directly by key.
One account, more than one agent
Connect compatible clients to the same account’s store. A note written by one client becomes available to another through the same storage operations. Separate access keys let you revoke a client without changing your browser login.
This is a notepad, not a document drive: each hosted object, including metadata, must fit within 64 KB. Save concise notes and reference links rather than large PDFs or attachments. Keep private information out of examples and use only agents you trust with access to your stored objects.
Three steps to a useful store.
- 01
Save a specific note
Ask your connected agent to preserve the exact wording, choose a key and call the storage tool.
- 02
Check the data viewer
Confirm the note exists, with its text and labels. A chat acknowledgement alone is not proof of a save.
- 03
Retrieve from a fresh chat
Ask another connected agent to list notes or search the topic, then fetch the full matching object.
A few practical questions.
Does every chat become a note?
No. An agent must explicitly write an object. Optional routing instructions help recognize save requests, but client permissions and tool selection still matter.
Can I edit or remove a note?
Yes. Use the data viewer or the store operations. Stable keys identify objects; versions help REST clients avoid overwriting a newer edit.