Set your preferences

The Preferences dialog holds the settings of the whole application. Open it with Edit › Preferences or Ctrl+P (⌘P or ⌘, on macOS).

Change a setting

1. Open Edit › Preferences.
2. Pick a page in the list on the left, or type in the search field at the top: the list keeps only the pages holding a matching setting (for example “proxy” or “page size”).
3. Change the setting.
4. Click Apply to apply it and keep the dialog open, OK to apply and close, or Cancel to drop your changes.

Values are checked before anything is saved: an out-of-range page size or port is reported on the page, and nothing is written until it is fixed.

Pages

The Background operations page is listed but not available yet.

Move your settings to another computer

1. On the old computer, open Edit › Preferences › General › Move to another computer and click Export settings…. Choose a .json file. Every preference file and the saved MongoDB connections are written, without any password.
2. On the new computer, click Import settings… and choose the file.
3. Read the confirmation: it lists every sensitive change first (program paths, proxies, AI Helper, runner or MCP endpoints, confirmations and other security settings). Confirm to import.
4. Restart the application, then enter the connections’ passwords again.

Each replaced preference file keeps a .bak copy. A file written by a newer version that this version does not know is refused rather than half imported. A connection whose folder name cannot be used here (a dot-folder, a name with : or ?) goes to the top level, and one whose folder differs only in letter case from yours goes into yours; the import lists each of them.

Preset preferences for every user (administrators)

An administrator can deploy a policy file that every user of the machine gets. The first of these that exists is read:

• the path in the OXYSDB_POLICY_FILE environment variable;
• policy.json next to the executable;
• /etc/oxysdb/policy.json on Linux, %ProgramData%\oxysdb\policy.json on Windows, /Library/Application Support/oxysdb/policy.json on macOS.

{
  "disableUpdates": true,
  "defaults": { "theme": "dark", "initialPageSize": 100, "confirmTaskRun": true },
  "branding": { "organization": "Acme Ltd", "supportUrl": "https://support.example.com" }
}

A policy file that exists but cannot be read or parsed fails closed: updates stay off, and the reason names the file. On Windows, Group Policy can set the same values in the registry under Software\Policies\Oxys\OxysDBStudio (computer or user); it wins over the file.

Where your settings are

Edit › Preferences › General › Where your files are and Help › About Oxys DB Studio show the folders. By default, settings and connections are in the system’s per-user configuration folder (~/.config/oxysdb on Linux), data and history in the per-user data folder (~/.local/share/oxysdb on Linux), and logs in ~/.oxysdb.

Portable mode: a folder named oxysdb-data next to the executable holds the settings, connections, data and logs instead, so the application and its settings can move together (on a USB drive, for example). The environment variables above take precedence over it.

Tips

• Every preference is also a command (prefs.get, prefs.set, prefs.reset), usable from the command line.
• Commands kept for problem reports: (General page, commandJournalSize; default 200, 0 to 10,000) sets how many commands the in-memory journal of bug reports keeps; 0 turns it off.
• The theme changes as soon as you click Apply or OK.

Troubleshooting