Settings window map
This page answers “where is this configured?” for the complete program. Use the search field above the left navigation, then open the relevant page. The window has no final global “Save all” step: some controls apply on change, while profile editors and service operations have their own buttons.
General
| Page | What it contains | Related guide |
|---|---|---|
| Account | Browser device flow, confirmation code, username/email, API/callback status, sign-in, refresh and sign-out. Minute usage is hidden in the current desktop widget; aggregate balance is available in the web profile. | Account and online services |
| General Settings | Development Platform switches mode immediately; theme and language are persisted and applied to the running application. Version, channel, repository and maintenance-tool availability are display-only here. The only update toggle controls startup checks: turning it off cancels a delayed check that has not started, while enabling it after startup was skipped takes effect on the next launch. The manager button starts a separate confirmation and safe-shutdown flow; it does not edit the repository. | Program modes · Updates → |
| Dependencies | Runtime source, probe, local install, detected global runtime, custom path, repair/remove and signed packs. | Dependencies and updates |
| Tray Settings | Close the application when the window closes is read when the main window closes. The autostart, directory and capture-hotkey fields are persisted but not consumed by the current tray: sign-in startup is not registered, a separate runtime directory is used and startup capture remains fixed at Ctrl+Alt+S. | Windows and permissions |
| Support | Shown when the account/support module is available. A visible widget fetches the thread immediately and repeats the GET about every 20 seconds; entered text and selected attachments are uploaded only by the send action. | Online operations |
AI / Models
| Page | Primary tasks |
|---|---|
| LLM Settings | Direct BYOK/self-host or advanced LiteLLM Proxy profiles, save-and-probe access checks, task models, role assignment, usage/limits, CV generation parameters and a test window. The first profile auto-assigns empty CV/test/semantic roles but not assistant; the verified catalogue is process-local and does not prove CV capability, while the usage JSONL has no automatic retention. Details → |
| CV Settings | Preview/apply behavior, parameter history, overlay/metrics, VLM auto-tuning, OCR runtime and prompts. Geometry policy has three exact modes: prompt asks for commit/rollback and refresh targets, mark_stale commits geometry without recomputation, and refresh_current commits and refreshes connected CV contexts; heavy methods are not started silently. Separate SAM Models and OmniParser tabs manage their local assets. Geometry workflow → · CV GUI → · Models → |
| YOLO Models | Active segment/detect/pose consumers, ML runtime status, download/removal, SHA verification and custom .pt import. The bundled registry currently contains segment/pose entries; a custom registry entry does not survive restart. Models and weights → |
| Element Selection | Selection, Semantics, Assistant, Interface and Files & Formats tabs. Selection geometry and semantic/Assistant settings are connected to runtime, but some legacy UI/file controls are only persisted. The exact application boundaries are listed below. Semantics also accepts an external JSON rules catalog and reports errors instead of silently falling back. Markup and project → · Extension → |
What the Selector tabs actually apply
Every change on the embedded Element Selection page is written to the settings JSON immediately, but a successful write does not mean that the current runtime consumes that key. The table below records the behavior of the current implementation.
| Group | When it takes effect | Current boundary |
|---|---|---|
| Startup and geometry | Launch Screen selectors is read on the next desktop-app start. Minimum sizes, handles, hit width, snapping, lasso, parent assignment and auto-pan are read by Selector during the relevant operations. | Link W×H only controls the two editor fields. The dimming value is persisted, but no runtime consumer was found. |
| Style and relations | Border styling applies immediately only when the dialog is opened from an active Selector. The duplicate-relation policy loads when the canvas is created and can also be applied from that active dialog. | Changing style on the main window's embedded page only persists values: a new Selector does not currently restore them automatically. For relations changed in the main window, reopen Selector. |
| Interface and magnifier | The magnifier enabled flag restores its visibility when Selector is next created. | ui.highlight_color, border width, autosave path, directory memory, and this legacy tab's magnifier size/zoom/grid values are persisted but do not control the current inspection magnifier or writers. |
| Files & Formats | The visible timestamp, date-subdirectory, PNG/JPG and JPEG-quality fields are written to JSON. | Current project/Capture writers do not read those fields. Configure the project in Save Settings and Capture export in Capture. A separate hidden files.png_compression key is consumed by Selector PNG artifacts, but it is not editable on this tab. |
| Semantics and Assistant | Settings are persisted; an active Selector dialog invokes reload/apply for the semantic router and Assistant integration. By default, voice annotation uses the “Fast skip ordinary annotations” policy, and a confident rule may apply automatically. | The external rules catalog is validated fail-closed. “Require confirmation for LLM decisions” acts on an intent already marked requires_review; it does not send every LLM result to review automatically. A Selector already open while changes are made only in the main window may need to be reopened. |
Automation
| Page | Primary tasks |
|---|---|
| Input Emulation | Selection and checks for Arduino HID, legacy serial or FakerInput Virtual HID; Arduino also exposes monitor mapping and firmware flow. Input backends → |
| IDE Interaction | Sending selections to an IDE, Codex VS Code/Trae, Screph Code/Pro Agent paths and autostart, plus additional integrations and tests. Screph Code → |
| Speech Recognition | Provider settings, recognition testing and, when its optional binding is available, service-usage controls. Local/BYOK providers and account-bound server speech have different contracts. Simply activating a configured OpenAI/LiteLLM tab already checks its model list or transcription endpoint; this is not limited to the Check button. Voice providers → · Server speech → |
Developer, Assistant and help
- Logging: The root level, module-prefix filters and main file handler apply immediately to the current desktop process;
Apply automaticallystarts enabled whenever the page is opened but is not itself persisted. Crash reporting, faulthandler, all-thread capture, session logging and retention take full effect only after restart. Disabling main file logging does not remove the separatesession.logwhen it is already enabled for the current crash session. The preview shows a manifest, not file contents; the startup prompt does not show the manifest. Diagnostics and recovery → - AI Assistant: activation and proactive controls have live consumers; context and action policy are cached by the runtime, so restarting is safest after editing the standalone Settings page. Workspace presentation, competence toggles, internal LLM routing/default-role mappings and CV extras are currently persisted-only. The retention field affects action history when the runtime is created, but session cleanup effectively remains at 180 days; the mirror toggle does not stop all generic workspace mirrors. Assistant runtime matrix →
- Documentation: shown when the embedded docs module is available. The current desktop cache contains a bundled snapshot of six core pages: contents, getting started, modes, Capture, Selector and CV; the complete guide set remains on the website. Links to pages outside the snapshot open the website. On startup, the entire local set may refresh through a separate network request without a user-facing toggle.
Where settings are stored
Most controls write ordinary JSON to ScrephData/settings_modules/settings.json. It is not encrypted and may contain local paths, provider endpoints, model/profile metadata and role mappings. API keys and account tokens are not written there; they use Windows Credential Manager. If the system keyring is unavailable, saving a secret must fail rather than fall back to plaintext.
A key's presence in this file proves persistence only. Runtime effect requires a separate consumer, which is why persisted-only Selector and tray fields are called out explicitly on this page.
Resetting a page changes the settings it owns but is not a complete deletion of models, logs, caches, projects or Assistant mirrors. See the local data and cleanup map.
Selector quick controls
You do not need to return to Settings every time. The Selector header contains the Program mode list and AI toggle. The list contains selectable modes only; Development Platform remains the complete source for status, maturity and blocking reasons.