Advanced settings
Settings → Advanced handles maintenance tasks: exporting JSON workspace backups, configuring local log retention, capturing local AI polish traces for prompt tuning, and performing a full reset.
For live shortcut status, rolling logs, and interactive hotkey or microphone probes, open Diagnostics settings (Settings → Diagnostics).
Workspace backup
Export your notes, snippets, and (optionally) dictation history into a portable JSON file before making major edits or reinstalling:
- Toggle Include dictation history if you want transcripts included (note this increases file size).
- Click Export workspace JSON.
- If you attach files inside Notes, copy your local
attachmentsfolder inside Kalam's data directory alongside the JSON export.
Logging
Configure how much diagnostic detail Kalam writes to its rolling database (Enable Logging, Log Level from Off to Debug, and Max Records from 500 to 20,000), open the local data folder, or export .log / .csv files.
On pre-release beta builds, debug logging runs automatically so crashes and shortcut bugs stay traceable; Download log and Download CSV remain available at any time.
Polish capture & support export
- LLM polish capture: Toggle Capture sessions on to save local transcripts, prompts, and context payloads strictly on your computer so you can inspect how Improve with AI rewrote a take. Use Reveal folder to inspect files or Clear to delete them.
- Support export: Run Analyze config, Modifier snapshot, (on Windows) DISM health, and Export markdown to produce a single report with environment checks and recent logs (LLM polish capture payloads are never included in support exports).
Danger Zone
Under Danger Zone, Clear All Data → Reset erases local history, notes, snippets, and settings and returns Kalam to the first-run setup wizard. This action cannot be undone from inside the app—export a workspace backup first if you want to keep your notes or snippets. See Reset and setup.