Agent notes

Most agents start every chat or run from scratch. Notes give each Profile a notebook: a workspace for working thoughts that are not Sources yet. When an agent learns something reusable — a tool quirk, a fix, a trap to avoid — it leaves a note: the problem, what it tried, what worked, what failed, what to do next time, and the Sources it used. Before similar work, it searches those notes first. Notes are lessons, not a status log: progress and status updates go on the task.

Every key in a Profile reads and writes the same notebook, so Claude, Cursor and a scheduled job all connected as Support work from one place. Other Profiles never see it, unless you switch on Read all notes for one that needs the full picture, like a review bot that reads every notebook once a week. That permission reads only. It never edits or deletes another Profile’s notes. Connect tools through the same Profile when they should work together, and use separate Profiles when their work should stay apart.

Notes are opt-in per Profile. Turn on Leave & curate when creating the Profile — or later in the profile editor — for agents that should keep notes, and add Export drafts only where a draft workflow is wanted. Add Read all notes only to a reviewer that reads across notebooks. Profiles without Notes do not appear in the Notes view.

takibi notes search -q "refund exception"
takibi notes append \
  --project support \
  --problem "Refund replies missed the policy exception" \
  --worked "The current policy lists the exception" \
  --next-time "Check the policy date before replying" \
  --source <document-id> --run-id <run-id>

The API blocks obvious secrets instead of storing them. Keep credentials and private data out of notes anyway. Write the four body fields in Markdown — short lists, code, links, and tables render when the founder reads the note. The title stays plain text. For every field and command, read Agent Notes API.

Open Notes in the app and choose a Profile by its avatar and name. The first view is a short queue of notes worth your attention, not every note. Notes that several keys keep looking up, and notes about problems your Sources may not cover, rise to the top. A tag on each note says why it appeared.

Those tags are signals, not proof that a note is right or that a Source is missing. Select a note title to read the full record before you decide anything. The record renders Markdown in the body fields; the title stays plain text.

All notes shows everything the Profile has, including flagged notes and expired notes. Search there to narrow the list. A flag means another note contradicts this one — both stay visible to you and to agents, so read both sides before deciding anything.

Notes do not become Sources automatically. Review a draft before adding it to your library. You can upload it yourself or authorize an agent whose Profile has Uploads enabled.

1. On each note worth keeping, choose Add to draft.
2. Choose Make draft. Takibi combines the selected notes into one Markdown draft.
3. Read the draft and compare each claim with the documents it cites. Edit anything that needs fixing.
4. Choose Copy or Download, then upload the approved version through Documents.

For the rest of the queue:

Keep

Endorses a useful note and takes it out of the queue; agents can still find it. It does not make the note a Source, settle its conflict flags, or extend its lifetime.

Remove

Stops agents from seeing the note right away. There is no undo, so read the note first.

Every note expires 30 days after it is created. Keeping a note or looking it up again does not reset that clock. Anything worth holding onto longer belongs in a Source.

A note that conflicts with another note carries a flag linking both sides — flagged notes stay in agent search and drafts, so readers can consult both claims. Only removed or expired notes stay out of drafts. If a draft reports a conflict, check both claims against their Sources before deciding what to preserve.