> ## Documentation Index
> Fetch the complete documentation index at: https://dshtauri.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# 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](https://dshtauri.mintlify.site/en/guides/appearance.md) for colors, interface scale, terminal mode, and transparency.

![Desktop Configuration dialog open on Debug](https://mintcdn.com/dshtauri/ulk6UnbnlYmrJhh5/images/desktop-settings.png?fit=max\&auto=format\&n=ulk6UnbnlYmrJhh5\&q=85\&s=a67f66e6b0a087e5be5088e0af752af5)

## 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](https://dshtauri.mintlify.site/en/guides/mobile-remote-access.md) for steps and authorization boundaries, or [CLI integration](https://dshtauri.mintlify.site/en/guides/cli-integration.md) 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.

> [!WARNING]
>
> 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](https://dshtauri.mintlify.site/en/guides/data-management.md) for steps. See [Profiles and cores](https://dshtauri.mintlify.site/en/guides/profiles-and-cores.md) 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](https://dshtauri.mintlify.site/en/guides/profiles-and-cores.md) for version and profile details or [Data, privacy, and security](https://dshtauri.mintlify.site/en/help/data-and-privacy.md) for storage locations.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.