Use desktop Settings to inspect and change the configuration exposed by your installed build. The source currently constructs General, Hotkeys, Theme, Writer, References, MCP and Verification areas; a particular build can expose fewer controls or show them differently.
Find the right area
| Area in the source | Use it for | |---|---| | General | Application-wide preferences exposed by the current build | | Hotkeys | Inspect or change shortcut bindings | | Theme | Desktop appearance and theme controls | | Writer | Writer-specific configuration | | References | Citation and reference-related options | | MCP | Experimental integration and transport settings, when available | | Verification | Verification-related options, when available |
The table describes source organization, not a promise that each area is enabled in a particular executable.
Inspect appearance
The desktop candidate checked on 2026-10-21 used the title-bar Settings control, then Themes, to select Dark, Black, Light, and Dark in sequence. In the observed Russian locale, the submenu listed Светлая, Тёмная (активная), Чёрная, Пользовательский, Фоновая анимация (холст), and Темы провайдера (Light, Dark (active), Black, Custom, Background animation (canvas), and Provider themes). The maximized workspace showed the selected appearance across the title bar, toolbar, sidebar, main workspace, Help panel, and status bar. Text and controls remained readable at the tested size. After a normal close and relaunch with the same isolated profile, Dark remained selected and rendered. This verifies built-in theme selection and same-profile persistence for the tested local candidate; Custom and provider themes remain unverified. Several Russian sidebar action labels were ellipsized at their displayed widths, so this run does not establish label fit in other locales or layouts.
Change a setting carefully
- Open Settings from the desktop workspace.
- Choose the visible area matching your task.
- Read the current value and any network, credential, local-tool or policy note.
- Change one value at a time and check the related feature.
- If persistence matters, close the app normally and verify the same value after restarting.
Settings labels and defaults can vary by desktop build. Read the text next to the visible control, change one option at a time, and check after a normal restart if persistence matters.
Network, credentials and permissions
Provider, AI backend and MCP settings can affect which services receive requests and which operations are available. A configured API key or enabled integration does not grant permission to share every paper or document. Check the backend and action context before sending content.
MCP is an experimental surface. Confirm the visible transport, listener and token settings for your build before starting a headless or network service. This guide does not authorize starting one.
Local indexing after PDF import
When retrieval indexing is enabled, importing a PDF can start local indexing. If your build shows the AI Model Settings option Off (disable RAG), it controls that retrieval-indexing path; it does not disable every separately started AI action. Check the visible operation status after import.
If you want to avoid local embedding work while importing a PDF, use the visible option only if it is present in your build, and check the application log for the expected disabled state. Do not change model or vector settings in a profile used by another person.
For desktop appearance, see Workspace Customization. For AI backend boundaries, see AI Features. For local data handling, see Backup, Restore & Data Locations.
If a setting is absent or does not persist
Check the app build and explanatory text next to the control. Record its exact label, value, restart sequence and visible result. Preserve the current value and avoid a full settings reset until you have a backup and understand which local state it can change.