Settings

What Settings is

The Settings section is the central control panel for the whole app. This is where you wire up AI providers, proxies, auth profiles and notification channels; set the master password and auto-lock; configure auto-update and database backups to FTP / Google Drive / S3. Internal modules (Tracker, RSS, Calendar, Health Check, Web Parser, Site Audit, Servers, Email, etc.) reuse the resources you create here.

Settings sections

The UI is split into 12 tabs:

1. General

Interface language — RU, EN, DE, FR, ES, PT, ZH-CN.
System notifications — all / critical only / off.
Launch on OS startup.

2. AI Providers

Manage the AI provider list used by every module. Supported types:

Claude (Anthropic), OpenAI, Gemini, Grok, Qwen, Kimi, DeepSeek, Mistral, Groq, YandexGPT and any OpenAI-compatible Local LLM.

Per-provider fields:

Type — one of 11 types.
API key (stored field-level encrypted).
API URL — custom or default.
Model — e.g. gpt-4o, claude-3-5-sonnet, bge-m3.
Embedding model — for RAG-aware modules.
Extras — Organization ID for OpenAI, Folder ID for YandexGPT, etc.
Proxy — link to a proxy group.
Test connection button.

3. Proxies

Proxy server groups. Parameters:

Name.
IPs — one IP:port per line.
Default port.
Username/password (optional).

Protocol: HTTP. The auto-test button shows the current external IP through the proxy.

4. Auth profiles

Reusable auth bundles for HTTP-driven modules (Web Parser, Site Audit). Each entry:

Method — header (e.g. Authorization: Bearer ...), cookie (e.g. session_id=...) or query_param (e.g. api_key=...).
Key and value.

Stored as a JSON array in auth_profiles.entries.

5. Notifications

Notification channels used by Health Check, Servers and other modules.

Telegram — bot token + chat ID.
Email — SMTP host/port, login/password, from/to, TLS toggle.

The auto-test button checks the connection.

6. Web search

Web-search providers for AI Chat:

DuckDuckGo — no key needed.
Tavily — with API key.
Brave Search — with API key.

Parameters: label, API key, URL, search depth, country code, proxy.

7. Security

Master password — set on first launch; 10+ chars with letters and digits. It's used to derive the encryption key that protects every sensitive field and the local database. The password itself is never stored — without it the database can't be opened.
Field encryption — sensitive values (api_key, password, OAuth tokens, etc.) are encrypted before they touch the database with a key derived from the master password.
Idle auto-lock (pwAutoLockMinutes, default 15) — the app re-asks for the master password.
Lock on screen lock (pwAutoLockOnScreenLock).
Password clipboard clear (pwClipboardClearSeconds, default 15 s).
Hide passwords by default (pwShowPasswordsByDefault).
Reveal rate limit (pwRevealRateLimit, 30 s between reveals).

8. Updates

Check for updates on startup (updateCheckOnStartup, default on).
Check now button.

Auto-update runs on packed builds (not in dev).

9. Database

Three sub-tabs:

Backup destination — FTP, Google Drive (OAuth), S3.
FTP parameters — host, port, username, password, remote path, TLS.
S3 parameters — endpoint, region, bucket, prefix, access key, secret key, force path style.
Owner name — used to label backups.
Frequency — 1 / 6 / 12 / 24 / 168 hours.
Retention — how many recent backups to keep.

Backups

List of remote backups. Restore downloads the chosen backup and replaces the local DB. If the source's master password differs, you'll be asked to enter it.

Tables

Browse every SQLite table, run SQL queries, export data. Useful for debugging and manual export.

10. Changelog

App version history.

11. Usage

Token spend tracking:

Global limit and per-provider limits.
Spend chart for the last 30 days.
Top chats and breakdown by operation.
Old-event cleanup.

12. Permissions

OS-level permissions (microphone, camera, files, etc. — depends on platform).

Where each key lives

AppSettings (settings table) — global flags and defaults (chatDefault*, emailEnabled, serversEnabled, gitAnalyticsPollMinutes, backupFrequencyHours, etc.).
ai_providers — AI providers with encrypted API keys.
proxy_groups — proxies.
auth_profiles — auth profiles (JSON array of entries).
notification_recipients — Telegram/email channels.
master_password — master password hash.
field_encryption_meta — field-encryption key.

First-run workflow

Set a master password — required on first launch.
Wire up an AI provider — without it AI Chat, AI estimates, RAG, AI reviews, etc. won't work.
Configure proxies and auth profiles — if you plan to parse, scan, or hit resources via them.
Set up notifications — Telegram/email are app-wide.
Enable backups — pick a destination and frequency for safety.
Verify updates — updateCheckOnStartup is usually enough.

Next steps

Getting Started — install and first run.
AI Chat — your AI provider setup comes alive here.
Health Check and Servers — they consume the notification channels.
Contexts & RAG — embedding providers have their own registry inside that module.

Help and feedback

Want 2FA, hardware keys, a global log level or new providers? Contact us via the feedback form.