Configuration

Configure Persyk in its Settings window. Your configuration is still stored in a human-editable JSON5 file. When you save in Settings, Persyk adds a JSON Schema reference for editor autocomplete and validation (a release schema in production, or a local schema in development).

File Location

Settings are stored in the application data directory:

Platform	Path
macOS	~/Library/Application Support/ai.persyk/settings.json5
Windows	%APPDATA%\ai.persyk\settings.json5
Linux	~/.config/ai.persyk/settings.json5

Development builds using tauri.dev.conf.json keep the persyk-dev application data directory.

The release bundle identifier changed from persyk to ai.persyk. Settings are not migrated automatically. Before switching from an older build, quit Persyk and back up its application data directory. To retain configuration, copy only settings.json5 into the new application data directory, reconciling any existing settings rather than overwriting them blindly.

Sessions are file-backed directories containing session.jsonl and assets/. Their default root is ~/Documents/persyk/sessions/ (development: ~/Documents/persyk-dev/sessions/); roots are configurable. Copying an old database does not import a library. Older data remains untouched, and there is no old-data importer.

Note: Persyk has only been tested on macOS. If you encounter issues on Windows or Linux, please open an issue.

Editing Settings

Choose Settings… in the system tray menu, or use CmdOrControl+,, to open the Settings window. The same window opens automatically when setup is incomplete or the configuration is invalid.

• Providers: add, rename, or remove OpenAI-compatible services. API keys are masked by default, with a Show/Hide button to reveal them temporarily. They are stored in the local settings file, not in the macOS Keychain.
• Transcription: enable transcription, choose a provider and model, and adjust clipboard, notification, and audio options.

Fields validate while you edit. An amber status strip highlights unsaved changes; it turns green after a successful save, without opening a popup. Save changes validates the complete configuration before writing; Cancel leaves the file unchanged. The full settings file path is displayed at the bottom of the window. Saving rewrites JSON5 formatting and removes comments, while retaining unrecognized configuration properties.

A schema-valid but incomplete configuration can be saved, but Persyk will direct you back to Settings before recording. Invalid JSON5 is never silently replaced with defaults: use Open settings file to repair it, then Try again.

Applying Changes

Saving in the Settings window refreshes the application’s settings across open windows. Changes apply to subsequent recordings; a recording already in progress keeps its original configuration through post-processing.

You can also edit the JSON5 file directly. After manual file edits, choose Reload Config (CmdOrControl+R) from the tray menu. The Settings window does not detect external file edits or merge them into an open draft; close it before editing the file manually.

Note: If you notice unexpected behavior after changing settings, try restarting the app. If issues persist, please create an issue describing the behavior.

Configuration Reference

For detailed information on all available configuration options, see the Configuration Reference Page (autogenerated from the JSON schema).

Example

{
  "$schema": "./settings.schema.json",
  "providers": {
    "openai": {
      "type": "openai-compatible",
      "baseUrl": "https://api.openai.com/v1",
      "apiKey": "sk-..."
    },
    "local-whisper": {
      "type": "openai-compatible",
      "baseUrl": "http://localhost:8000/v1",
      "apiKey": null
    }
  },
  "transcription": {
    "enabled": true,
    "provider": "openai",
    "model": "whisper-1",
    "copyToClipboard": true,
    "notifications": true,
    "requestOptions": {
      "language": "en",
      "prompt": "Technical discussion about software development",
      "temperature": 0
    }
  }
}