Settings & Config

Settings live under File → Options, in eight groups down the left of the window: General, Editing, Results, Connections, Look & feel, Keybindings, Integrations and License. Each heading below says which group it sits in.

Appearance

Options → Look & feel → Appearance. Nine themes — five dark, four light:

• Dark: Obsidian (blue), Coastline (cyan), Ember (coral), Forest (emerald), Slate (violet)
• Light: Linen (warm), Glacier (blue), Dawn (rose), Kawaii (candy pink — with its own icon set)

Fonts are configurable separately for the UI (Space Grotesk, Sora, IBM Plex Sans) and the editor/monospace surfaces (JetBrains Mono, Fira Code).

Editor

Options → Editing → Editor is for the thing you spend the day in. Every change applies to every open editor at once — the shell, the document window — with no reload:

• Font size for code (10–24), separate from the UI font under Appearance
• Tab size (2, 4 or 8) and whether an indent is spaces or a tab character
• Wrap long lines, line numbers and the minimap
• Suggest as you type, with a delay in milliseconds — off keeps suggestions behind Ctrl+Space
• Close brackets and quotes as you type them

Workspace

Options → Look & feel → Workspace is how the workspace behaves rather than how it looks:

• Save the workspace after — the quiet time before tabs and scripts are written to disk (300 ms by default)
• Open tabs at most — 0 means no limit; at the limit, either be warned or have the oldest tab closed for you, never the one you are on
• List the open tabs in the sidebar — a folding list above the connection tree, off by default; the fold is remembered
• Sidebar on the left or the right
• Zoom from 80 to 150 % in steps of ten — Ctrl+=, Ctrl+- and Ctrl+0 do the same and can be rebound
• Reopen the window where it was — size, place and screen come back, unless that screen is gone

Results

Options → Results → Display is how a result reads, not what it contains:

• Default view, per engine — table when the rows are tabular and JSON otherwise (the default), or always table, JSON or tree. The toolbar switch still works per result.
• Nulls — the word null, the word dimmed, or nothing
• Cut long cells at — 20 to 2 000 characters (80 by default); the full value is a double-click away, and copying never sees the cut
• Dates — ISO in UTC as the server sends them, ISO on your clock with the offset said, or your locale's own format
• Numbers — as sent, or grouped for your locale

Run

Options → Editing → Run.

• Run executes — what the main shortcut runs: the selection else the whole script (the default), the selection else the statement under the cursor, or always the whole script. Run all and Run selection on the toolbar always do what they say.
• Measure a write that nothing narrows, and ask — an UPDATE or DELETE with no WHERE, a deleteMany with an empty filter. The dialog says how many rows it reaches, measured before it runs. On by default.

Query

Options → Editing → Query holds what a statement may cost. Each number applies to the next run without a restart:

• Default row limit — rows a statement returns when it names no limit of its own. 50 by default, 1–10 000; the results toolbar pages past it.
• Statement timeout — seconds before a running statement is stopped, on every engine. Off by default (0), up to an hour.
• Response size limit — megabytes one result may carry to the window. 2 by default, 1–50; a result over it is cut and says which limit cut it.

Keyboard Shortcuts

Options → Keybindings. Run selection, Run all, Run at cursor, Switch tab, View document, Edit document, Delete and the three zoom steps are rebindable — pick the action and press your combination. See Keyboard Shortcuts for the defaults.

How to: rebind a shortcut

1. Open File → Options and pick Keybindings
2. Click the action you want to change
3. Press your preferred key combination; it takes effect immediately

Behavior

Options → General → Behaviour.

• Restore workspaces on launch — tabs, scripts and connections come back as you left them
• Auto-reconnect the last used connection
• Auto-activate the matching connection when you run a query
• Check for updates on launch (a custom update URL is supported for self-managed setups)

Connections

How long a connection waits, how long it stays, and what happens when it drops. The four numbers live in Options → Connections; a single connection can override any of them on its Advanced tab, where an empty field means the global value.

Setting	Default	Range
Connect timeout	8 s	1–120 s
Close after idle	5 min	0–60 min, 0 keeps the pool open
Reconnect attempts	off	0–10
Between attempts	3 s	1–60 s

The connect timeout is the engine's own knob on every engine — the socket timeout on PostgreSQL and SQL Server, server selection on MongoDB, the client timeout on Aerospike, the validating query on ClickHouse, the ping on Elasticsearch — and Test waits as long as Connect will. Closing after idle also brings the SSH tunnel down; a changed value applies at the next idle check, within half a minute, without reconnecting.

Reconnect is deliberately narrow. When a run's first statement fails because the connection itself went away — a reset socket, a terminated backend, a destroyed topology — Sutido drops the dead pool, and if the script only reads it runs it again, as often as allowed, with a notification counting the attempts. A write is never sent twice, a statement that failed after earlier ones ran is never re-run, and Stop ends the wait. Whether or not a retry follows, the next run opens a fresh pool.

The Advanced tab also has Start in database: a new shell on that connection opens there instead of the connection's default.

Confirmations

Every confirmation dialog — delete a snippet, clear the history, the changelog or the error log, revert a document, delete a connection, run a statement that destroys data or a delete larger than the changelog can journal, drop or truncate a collection, drop a function or view — has a Don't ask again box. Ticking it and confirming switches that one dialog off; cancelling never does, and a drop that fails keeps its dialog.

Options → General → Confirmations lists the dialogs you switched off, each with Reset, and Reset all. A reset applies at once, even to a window that is already open.

Language & Formats

Options → Look & feel → Language & formats decides how numbers and dates read across the app — the history, changelog and error log timestamps, the connection manager's dates, count notifications, the MCP approval window's row counts.

• Numbers and dates: System follows your OS; or pick a locale from the list — German gives 1.234,56 and 09.09.2026, 14:05, American 1,234.56 and Sep 9, 2026, 2:05 PM. A preview shows the result as you pick.
• Clock: as the locale has it, or forced to 24-hour or 12-hour.

The interface itself is in English. Grid cells show dates as ISO 8601 and are not affected by this setting.

AI Integration

AI query generation is bring-your-own-key, per provider, each with an enable toggle and an optional custom model override:

Provider	Default model
OpenAI	gpt-4o-mini
Google Gemini	gemini-1.5-flash
Anthropic Claude	claude-3-5-sonnet

API keys are stored encrypted in the local secret store, and requests go directly from your machine to the provider — Sutido runs no proxy in between.

License

Options → License handles activation, deactivation and refresh of your license key. For what's included in each plan, see pricing.

Settings File, and the Way Back

Every group can be written to one JSON file and read back on another machine — or on every seat of a team. Export… and Import… sit under Options → General → Settings file. Import shows which groups the file carries before anything is applied, and a file written by a newer Sutido is refused with a sentence rather than half-applied.

The file holds settings only: appearance, general, editor, query, keybindings, and the AI provider and model. Never a connection, a password, an API key, the licence or the MCP grants.

Every section has a Reset to defaults, and the settings file section has Reset everything for the lot.

Data

Options → General → Data, how long each store keeps what it wrote — with the count beside it and a Clear now per store:

• Query history — every statement you ran. The last 5,000 by default.
• Delete journal — the documents a delete or an edit took, kept so they can be restored. The last 5,000 by default; "restore" reaches exactly as far back as this rule.
• MCP activity — every request a connected agent made. The last 50,000 by default.

Each rule is keep the last N entries, keep the last N days or keep everything, and a changed rule applies at once rather than on the next insert.

Where Your Data Lives

All app data is local, under %APPDATA%/sutido:

• Connections, workspaces, snippets, query history and the delete-recovery changelog in a SQLite database
• Passwords, SSH keys and API keys encrypted with OS-level encryption (safeStorage) — never plaintext
• Error logs, viewable and exportable from the Error Log panel

Getting Help

• Browse the FAQ
• Email support@sutido.com