Settings

Open Settings from the left sidebar to configure the workbench, execution defaults, saved runs, storage, and connected features.

Settings shown in Desktop depend on the application surface, project type, and account. Native hardware options appear in the installed application, while cloud project controls require a signed-in cloud project.

General settings

The main Settings view includes common controls such as:

• theme;
• showing internal project files;
• placing the Command Window in a tab;
• running automatic AI-assisted root-cause analysis after errors;
• persisting runs;
• enabling GPU acceleration;
• reviewing project storage.

Changes to layout and appearance take effect in the workbench. Runtime-related changes apply to later runs and may require the project session to restart.

Persist runs and notebooks

Persist runs retains supported output, variables, and figures so they remain available in run history and notebooks. Disable it for temporary work that does not need saved results.

Open Advanced settings to configure:

• whether a notebook resumes remaining cells or runs from the beginning after cancellation;
• whether notebook execution stops at the first error;
• automatic notebook workspace restoration;
• automatic workspace and figure clearing before scripts;
• trace and Runtime log persistence;
• the artifact root used for saved run data.

Persistence settings apply to future runs. Existing runs retain the data captured under their original settings.

Workspace and figure clearing

Auto clear workspace before script runs starts each script after clear. Enable it when scripts should be independent of values created by earlier commands.

Auto clear figures before script runs starts each script after close all. Disable it when a workflow intentionally updates existing figure handles across runs.

These settings apply to script runs. The Command Window remains interactive and keeps its state until you clear or restart it.

GPU and native devices

Enable GPU allows supported operations to use the available accelerator. Runtime chooses acceleration for supported work and falls back according to the active Runtime policy.

The installed application can also expose native-device options such as SpaceMouse support when the device and host are available.

For reproducible accelerator choices shared with CLI, CI, or remote workers, use runmat.toml.

Project storage

Open Storage to see how much space the project uses for source, datasets, runs, and other files. The artifact root controls where Desktop stores large saved-run and notebook data within the project.

Review storage before deleting saved runs or artifacts. Removing an artifact can make an earlier variable or figure unavailable.

Cloud projects also show project identity and visibility controls when your role permits changes.

Desktop settings and project configuration

Desktop settings follow the application or user. runmat.toml follows the project and belongs in version control. Put source roots, entrypoints, dependencies, compatibility behavior, and shared Runtime options in the project configuration.