Your AI assistant remembers what it has processed

Your assistant writes one note on each recording it has handled, so its next run takes only what is new.

Plan: Premium

For someone who lets an AI assistant work through their recordings over MCP, for example turning each meeting into a note in their own files. The assistant runs again tomorrow, and should take only what is new.

Every source can carry one note, the same for everyone in the account. The assistant writes it when it is done with a source and reads it next time. Writing the note never reprocesses the source or changes its transcript.

Sketch: a plug seated in a blank wall socket, its cable running out of frame; the plug carries the gradient.

What you need

  • An account on Premium or Enterprise. Testers get Premium while they test: become a tester.
  • An AI assistant connected over MCP: Claude Desktop, claude.ai or Claude Code.

Steps

  1. The assistant reads
  2. It does the work
  3. It writes the note
  4. Next run: only what is new
  1. Step 1: Connect the assistant, with write access

    Connect it as in Connect over MCP. On the consent page, approve kb:write as well as the default scopes. A connection without it can read notes but not write them.

  2. Step 2: Ask it to write a note when it is done

    Tell the assistant that, when it has finished with a recording, it writes the note with set_source_note, for example “processed 2026-10-10, filed as Meetings/Exempelbolaget kickoff”.

  3. Step 3: Next run, start from what has no note

    Ask it to begin with the recordings that have no note: list_sources lists only those. When it reads a recording, the note comes with it.

What happens next

  • A record on each source of what an assistant has done with it.
  • The next run starts where the last one stopped.
  • Everyone in the account who can read the source sees the same note.

Read more

Stuck? E-mail support@deep-thought.cloud.

All use cases