This guide covers the two most common local setups:
- Fathom -> Strata
- local export files -> filesystem destinations
- Kujo available locally
- a checked-out copy of this repository
- Strata running locally if you plan to write to the
stratadestination - a Fathom API key if you plan to use the live
fathomprovider path
cp .totalrecall.local.example .totalrecall.local
chmod 600 .totalrecall.localFATHOM_API_KEY=your-fathom-api-key
STRATA_API_BASE_URL=http://127.0.0.1:3939./scripts/totalrecall config validateYou want to see:
- config file resolved
- config permissions acceptable
- required settings present
- sync state readable
- destination ready
./scripts/totalrecall fathom pull --dry-run --limit 5 --verbose./scripts/totalrecall fathom pull --limit 5./scripts/totalrecall fathom pull --limit 5If a note mapping exists but the corresponding Strata note has been deleted, --force now recreates the missing note and repairs sync state automatically.
./scripts/totalrecall fathom pull --limit 5 --forceTOTALRECALL_PROVIDER=chat-export
TOTALRECALL_CHAT_EXPORT_PATH=/path/to/chat-export.json
TOTALRECALL_DESTINATION=markdown-folder
TOTALRECALL_MARKDOWN_OUTPUT_DIR=/path/to/output-notes./scripts/totalrecall chat-export import --dry-run
./scripts/totalrecall chat-export importTOTALRECALL_PROVIDER=slack
TOTALRECALL_SLACK_EXPORT_PATH=/path/to/slack-export.json
TOTALRECALL_DESTINATION=local-index
TOTALRECALL_LOCAL_INDEX_DIR=/path/to/output-index./scripts/totalrecall slack import --dry-run
./scripts/totalrecall slack import./scripts/totalrecall --helpprints usage text../scripts/totalrecall --versionprints the installed TotalRecall version and exits0.
chmod 600 .totalrecall.localThis usually means one of the following:
- the Fathom API key does not have access to recent meetings
- the account has no meetings in the requested range
- the provider is configured correctly, but the source system returned an empty result set
Try:
./scripts/totalrecall fathom pull --dry-run --limit 20 --verbose
./scripts/totalrecall fathom pull --dry-run --since 2026-01-01 --limit 20 --verboseThat stale-reference path should now self-heal by creating a replacement note and updating sync state. If it does not, inspect the sync state and rerun with verbose output:
./scripts/totalrecall state inspect --limit 10
./scripts/totalrecall fathom pull --limit 1 --force --verbose