Notes (working memory)

Notes are Blenau’s working-memory tier: quick, disposable things you want off your mind — shopping lists, reminders, to-dos, a fleeting idea for the next video. You capture one by just telling your agent, and you recall a list complete and exact whenever you need it.

New here? Which one do I use? compares Notes, Knowledge and Collections side by side.

Notes are deliberately not Knowledge. Knowledge (your documents) is curated understanding that earned its place because it made you better, and it lives indefinitely — you recall it to think. A note is the opposite: it costs nothing to capture, it lives only until it’s acted on, and success is the list going toward empty. It’s the agentic version of a shopping list or a calendar — it frees your head from holding the thing, it doesn’t make you wiser.

The one line that matters

Notes never appear in search_knowledge, and Knowledge never appears in recall.

Asking your brain “what do I know about pricing?” can never return “buy toothpaste”. The two tiers have separate stores and separate retrieval paths on purpose — that separation is the whole promise.

Using it through your agent

You don’t open an app. You’re already talking to Claude (or any agent connected to Blenau), so you just say it:

"add toothpaste to my shopping list"
      → remember(note="toothpaste", list="groceries")

"what's on my shopping list?"
      → recall(list="groceries")
      → returns EVERY item, exact — then the agent can group it by aisle,
        add estimated prices, or send it to someone, because it has tools

"got the milk"      → mark_note_done(note_id=…)
"idea: video on why Odoo webhooks lie"  → remember(note=…, list="video-ideas")

Because your agent has other tools connected, a recalled list is an input, not a dead artifact: “group my shopping list by category and add prices”, “send my list to Teresa on WhatsApp” all work — Blenau supplies the list, complete and correct, and the agent does the rest.

Why “complete and exact” is the point

A native agent-memory blob reconstructs a plausible list and may quietly drop the 11th item — you find out at home, without toothpaste. Blenau’s recall is an exhaustive query of the list, not a fuzzy top-k. This is the guarantee a general-purpose memory can’t make, and it’s why Notes lives in Blenau.

Lists

A list is just a named bucket, created the first time you use it (groceries, video-ideas, work). Names are normalized (lowercased, trimmed) so “Groceries” and “groceries” are the same bucket and your list never silently splits in two. A note with no list lands in inbox.

Tools

Tool	Purpose
remember(note, list?)	Capture a note / list item / reminder
recall(list?, query?, status?)	Get a list — complete, in build order
note_lists()	See your lists with open/done counts
mark_note_done(note_id)	Complete an item (the list shrinks toward empty)
update_note(note_id, note?, list?)	Edit the text or move it to another list
forget(note_id)	Delete a note outright

recall defaults to status="open" so a list reads as its remaining work; pass "done", "archived" or "all". query is an optional plain-text filter (“did I jot something about milk?”) — it narrows by words in the note, it is not a semantic search.

What Notes is not

• Not Knowledge. If you’ve understood something and want to keep it, that’s ingest_document, not remember. A note is for offloading a task or an item, not for recording what you learned.
• Not a database. No schema, no fields, no filters beyond list and status — a note is one line of text. For structured business records (products, customers) synced from a system, use Collections.
• Not permanent. Notes are meant to be completed and cleared. There’s no provenance, no versioning, and no brain-health scoring — they’d only add noise.

Dashboard

The Notes section of your dashboard shows every list, its open items, and lets you check things off or delete them — because a note you can’t see is a note you don’t trust. But the fast path is always your agent: capture in a sentence while you work, recall when you need it.