How capture works

From on-screen text to a memory you can ask questions about.

Goldfish runs a small background process that reads the text of the foreground window every few seconds through the operating system’s accessibility layer. Text only: no screenshots, no screen recordings, no keylogging.

From screen to memory

1. Capture: the text of the window you are working in, with the app name and, in browsers, the domain.
2. Deduplicate: the same content is never stored twice. Rereading a page updates one record instead of piling up copies, so the database stays small.
3. Mask: card numbers, CVVs, social security numbers, and IBANs are masked before anything is written to disk.
4. Store: everything lands in a local database on your device.
5. Summarize: Goldfish rolls activity up into hourly and daily summaries (the chronicle) and keeps wiki pages on the people, projects, and topics it encounters.

What retrieval looks like

When you ask something, Goldfish layers its answer from four levels: who you are (identity), what you are doing right now (working memory), what you did over time (the chronicle), and a deep search across everything captured. The result: “what did I do yesterday” and “where did I read about X” are both one question away.

Staying in control

Capture is yours to steer: pause it any time, blacklist apps and domains, or delete everything. The Privacy page lists every control.