Settings
Open Settings near the bottom of the sidebar. Settings on this page save as you change them. This differs from Devices, which requires Save changes, and the flow editor, which has its own Save action.
General
- Check for updates on startup enables update checks for the installed Windows release.
- Release track chooses Stable (recommended) or Beta (bleeding edge). Moving to Stable may install an older version.
- Restart now restarts the app and applies a pending update. Save your work first; the restart interrupts running flows and device sessions. Flows marked running may start again after launch.
Appearance
Appearance chooses System, Light, or Dark. System follows the operating system. Accent colour changes primary actions and selection; status colors remain separate. Reset beside the accent choices restores the default accent, not the rest of the app's settings.
Theme files
- Click Export current to create a JSON theme in the themes folder.
- Edit a copy of that file to customize colors and corner radius. Use the exported structure as your starting point; themes do not change fonts or spacing.
- Place theme JSON files in
themes/. Reopen the Appearance tab to refresh the list. - Select a file under Theme files to apply it, or choose Built-in to return to the built-in theme.
The app can adjust invalid or unreadable colors and lists the affected tokens under This theme was adjusted to stay readable. A missing or invalid file does not justify resetting all app data; select Built-in first.
SDK components use the host theme. A plugin's custom CSS may need its own changes to support both light and dark modes; see shared UI.
Flow editor
- Snap to grid aligns nodes, groups, and connection pins while dragging and during automatic layout.
- Route connections along the grid draws right-angle wires instead of curves. Double-click a connection to pin it through a point.
These preferences apply to every flow. See the editor guide for shortcuts, groups, templates, and saving.
Logging
- Write logs to disk enables file logging.
- Separate plugin logs routes plugin-category messages to their own file.
- Detail level controls how much is recorded. Start with Information; use Debug or Verbose for a short reproduction when more detail is needed.
- Files to keep and Maximum file size control retention and file rolling.
- Open folder opens the current log directory while file logging is enabled.
Logging changes take effect after a restart. Reproduce the problem after restarting, then keep the files from that run. Logs can contain account names, device identifiers, and plugin-provided data; review them before sharing. See collecting logs.
Privacy
Send anonymous usage data and crash reports controls the host's usage analytics and crash reporting. Changes take effect immediately. Builds compiled without telemetry endpoints show a notice and disable this control.
This setting does not turn off local log files, required PiShock connections, or network requests made by third-party plugins.
Advanced
Backup and restore provides Export configuration, Import configuration,
and Reset to defaults. Configuration exports contain sign-in credentials and
exclude flow files, plugin-configs/, and plugin-owned files. Use the backup guide
before importing or resetting.
Debug & diagnostics → Open shows live app and plugin state. You can also find Debug with Ctrl+K. Use it to inspect connection state, loaded-shocker and serial-device counts, performance, and plugin errors; see troubleshooting.
