Desktop settings

Configure the local service, interface scale, CLI integration, profiles, plugins, and core engine.

Open Running in the desktop title bar. Model providers, tools, and agent behavior remain in the embedded Harness Settings. See Appearance for colors, interface scale, terminal mode, and transparency.

Application

Setting or status	Purpose and when it applies
Service address and connection status	View the actual address; local access by default, with preferred port 3080
Port	Restart Harness when prompted after saving; another available port may be used if it is busy
Memory limit	Use automatic management or set Harness’s Node.js heap limit; restart the service after changes
CLI integration	Release builds enable the managed dsh shim by default; open a new terminal after changes
Launch on login and close behavior	Closing the window hides it to the tray by default; you can change this to quit
Versions, data directory, and logs	View running components, open directories, or copy diagnostic information

Share at the top provides LAN and public-tunnel sharing; advanced settings are in Harness Settings → Remote access. See Mobile remote access for steps and authorization boundaries, or CLI integration for PATH and shell configuration changes.

Profiles

First installation uses the tauri profile; web is the built-in fallback profile. Profiles manage configuration, plugins, and patches, not operating system isolation.

1. Create or clone a profile in Profiles, using a short ASCII name.
2. Select it, confirm the switch, and restart the service when prompted.
3. Back up before modifying or deleting it; prefer Restore as New to test recovery.

Resetting, deleting, or restoring over a profile changes its data. Back up first and confirm the recovery scope. Profile backups do not replace workspace or complete session-data backups.

Data directory

Use Data Directory for disk usage, preflight checks, migration, and rollback; see Data management for steps. See Profiles and cores for profile configuration and migration.

Plugins and core engine

Panel	Common actions
Plugins	Inspect sources, versions, and errors; install, upgrade, or remove optional plugins, or mount a local plugin directory and enable hot reload
Core Engine	Download compatible versions, select a source, and switch; the desktop and Harness core update separately

Do not delete a profile or core as the first troubleshooting step. Copy logs first and determine whether the issue concerns dependencies, a plugin, the service, or a model.

See Profiles and cores for version and profile details or Data, privacy, and security for storage locations.