Notes¶
What Notes Are¶
Notes turn individual dictations into a persistent, searchable collection. Each note is a plain folder containing metadata and whichever transcript or audio artifacts the profile is configured to save.
This is different from temporary history:
| Feature | Purpose | Lifetime |
|---|---|---|
| Temporary history | Quickly recall and paste recent finalized results | Up to 10 items in memory; cleared when OpenScreech exits |
| Notes | Browse, search, tag, play, copy, and retain captures | Stored on disk until you delete or move them |
| Saved Outputs | Write selected artifact types into separate flat-file folders | Stored on disk independently of Notes |
When Notes Are Useful¶
- Keep voice ideas that should outlive temporary history.
- Build a searchable collection of project notes or research observations.
- Retain the original transcript beside cleaned or LLM-processed variants.
- Store the capture audio with its text for later review.
- Organize captures by profile, folder, and deterministic tags.
Enable Notes for a Profile¶
- Open
Profilesand select the profile used by your hotkey. - Enable
Save to Notes. - Choose a Notes folder, such as
Inbox,Work/Ideas, orResearch/Interviews. - Select the artifacts to include: audio, original transcript, word-replaced transcript, and LLM transcript.
- Complete a dictation using a hotkey mapped to that profile.
- Open
Notes...from OpenScreech Home or the menu bar.
Notes are also written for HTTP transcription requests when the resolved profile has Save to Notes enabled. Meeting Recording and Transcribe File(s) currently write their own session outputs and do not create Notes.
What a Note Contains¶
A typical note bundle looks like this:
OpenScreech Notes/
tags.json
Inbox/
2026-07-12-142233-K7M2QX/
metadata.json
transcript.txt
transcript.replaced.txt
transcript.llm.txt
audio.wav
Only enabled and available artifacts are written. A note can be created from early capture artifacts and then updated when the selected LLM result and tags become available. For example, transcript.llm.txt is absent if the profile did not produce LLM output.
| Artifact | Meaning |
|---|---|
metadata.json |
Created and updated dates, tags, profile, and note metadata |
transcript.txt |
Original ASR result |
transcript.replaced.txt |
Text after deterministic word replacements |
transcript.llm.txt |
Selected final output from the profile's LLM graph |
audio.* |
Original capture audio in its stored format |
tags.json |
Root-level registry of known tags |
The Notes Window¶
The Notes window lets you:
- Search transcript text, tags, folder names, and profile names.
- Use
tag:nameto filter by tag. - Group notes by date, folder, or profile.
- Switch between available transcript variants.
- Copy transcript text.
- Play capture audio.
- Reveal a note bundle in Finder.
- Edit tags or delete the entire note.
Every free-text term and every tag: filter must match. Tag searches are partial and case-insensitive, so tag:meet matches meetings.
Audio playback is read-only. The progress bar displays playback position but is not a seek control.
How Notes Load¶
Opening Notes first indexes the category and note folders without reading every note's metadata or transcript files.
When a note row becomes visible, OpenScreech:
- Lists that note bundle once to record which transcript variants and
audio.*file exist. - Reads
metadata.json. - Reads one preferred transcript: LLM, then word-replaced, then original, depending on which artifact exists.
- Caches the bundle information, metadata, and transcript for reuse when the note is selected.
Switching to another transcript variant reads and caches only that text artifact. Audio content is not read until playback begins. A slow cloud-backed note can remain loading without holding up other visible notes or a different note you select.
Free-text search intentionally reads transcript artifacts on demand. Profile grouping and tag: filtering load the metadata required for those operations; ordinary date or folder browsing remains lazy.
Notes Root and Folders¶
The default root is:
~/Documents/OpenScreech Notes
Use the folder menu in the Notes window to show the root in Finder, choose another local or synced folder, or restore the default.
For a Notes root stored in iCloud Drive, Control-click the root folder in Finder and choose Keep Downloaded when you want the complete library retained on this Mac. Otherwise macOS may leave older files as cloud placeholders and download an individual metadata or transcript file when OpenScreech first reads it.
Changing the root changes where OpenScreech reads and writes Notes. It does not move existing note bundles. Switch back to the previous root to see them again, or move them separately in Finder while OpenScreech is not writing a note.
A profile's Notes folder is relative to the root. Use / for nesting, such as Clients/Example Project.
Using Auto Tag with Notes¶
Auto Tag scans the final processed text for configured phrases and attaches matching labels to the note. The note may already contain earlier capture artifacts and is updated with these tags; tagging does not alter transcript text.
Auto Tag needs a persistent destination to be useful. Enable Save to Notes on the same profile when you want its computed tags retained.
Tag Library Updates¶
tags.json is the root-level library used for tag suggestions. Creating a note, adding processing results, or editing its tags merges newly encountered tags into this registry. Browsing or opening a note does not rewrite it.
Use the Notes folder menu's Rebuild Tag Library… action when notes were added, removed, or changed outside OpenScreech and you want to reconstruct the library from all metadata.json files. The rebuild shows progress, can be cancelled, and keeps the previous registry unless a complete scan succeeds.
Important Deletion Behavior¶
Deleting a note removes its complete bundle folder, including transcript variants, metadata, and audio. Use Reveal in Finder first if you need to preserve any artifact.
Common Pitfalls¶
| Pitfall | Outcome | Fix |
|---|---|---|
| Notes enabled on the wrong profile | Expected dictations are not saved | Check which profile the hotkey maps to |
| Changing the Notes root | Existing notes appear to disappear | Switch back to the previous root or move the bundles separately |
| iCloud-backed rows take time to appear | macOS is downloading placeholder files on demand | In Finder, Control-click the Notes root and choose Keep Downloaded |
| Expecting every transcript variant | Some files are absent | Enable the artifact and its required processing on the profile |
| Expecting Meeting or File results | No Notes bundle is created | Use those workflows' own output folders |
| Confusing history with Notes | A recent result disappears after quitting | Enable Save to Notes for persistent storage |
Validation Checklist¶
- A hotkey is mapped to the intended profile.
Save to Notesis enabled on that profile.- A completed dictation appears in the Notes window.
- The bundle contains only the selected and available artifacts.
- Search and any
tag:filters return the expected note.
Quick Tips¶
- Changing the Notes root switches libraries; it does not move the previous one. You can return to the old root and see those bundles again.
- Deleting from the Notes window removes the complete bundle, including audio and every transcript variant. Use
Reveal in Finderfirst when any artifact may be worth keeping.