> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anonalabs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Think out loud, keep the thought

> Say it into your phone on the walk home. It arrives as memory you can question later.

[← All use cases](/use-cases/overview)

<div className="uc-examples"><a href="https://github.com/anonalabs/Anona-Memory-SDK/blob/main/examples/document_qa.py">document\_qa.py</a></div>

## The scenario

The good thinking happens away from the keyboard — walking, driving, in the
shower, twenty minutes after the meeting ended. By the time you are somewhere
you could type it, it has flattened into one sentence, or gone.

People already solve half of this with voice notes. The unsolved half is that a
folder of 200 voice notes is write-only. Nobody has ever scrubbed back through
them to find the one where they worked out the pricing model.

**What this recipe shows that no other does:** getting memory in through a
channel that isn't text at all.

## Step 1 — Record it however you already do

Any voice memo app. MP3 or WAV.

## Step 2 — Hand the file over

The assistant can upload it for you over MCP, or you can do it in one call:

```python theme={null}
client.upload_file(space_id="thinking", file="walk-home-2026-09-15.m4a")
```

It comes back transcribed and extracted into ordinary memory — the same pile as
everything you typed. That is the important part: it is not "your voice notes",
searchable separately. It is just memory now, and it composes with the rest.

## Step 3 — Ask, weeks later

> *"What was I thinking about pricing before the offsite?"*

You do not have to remember that the thought was spoken rather than written, or
which file it was in, or roughly when. Those are exactly the things you have
forgotten, and they are the only things a folder of recordings can be searched by.

## Evals

1. Record three voice notes on different days, one containing a specific
   decision you can check.
2. Ask a question that only that note answers. Check it comes back.
3. Ask using words you did **not** say out loud — describe the idea differently.
   Matching on meaning rather than transcript is the whole point; if it fails
   here, the transcription probably garbled the key term.
4. Check one transcript by hand against the audio. Names and jargon are where
   transcription degrades, and they are usually the words that matter most.

## Guardrails

<Warning>
  **A transcript is not a recording.** It is good enough to find the thought and
  point you back at the moment; it is not evidence and it will get proper nouns
  wrong. Keep the original file if the exact words could ever matter.
</Warning>

* **Audio limits apply**: 25 MB per file. A long walk needs splitting.
* **Do not narrate other people without telling them.** A voice note recorded
  in company is a recording of everyone in earshot.
* **Half-formed thoughts get stored as confidently as conclusions.** If you
  talked yourself out of something, say so out loud — otherwise the abandoned
  idea is recalled later with the same weight as the one you kept, and
  [correcting it](/use-cases/correct-a-memory) is the fix.

## Where to go next

Same mechanism, pointed at a meeting rather than a walk:
[Turn a meeting recording into memory](/use-cases/meeting-recording-to-memory).
