Settings

Settings control how the app connects to Runtime, how clients connect to the gateway, and how local runtime behavior is managed.

Open Settings for Runtime and Gateway, Network Access, Client Tokens, Runtime Data, Local AI Performance, Start at Login, Gauge, Notifications, and Diagnostics.

Runtime and Gateway

This section shows the app's current Runtime connection and gateway URL.

Use it to:

• Confirm Runtime version and health.
• Copy the OpenAI-compatible URL.
• Copy a model or preset value when one is available.
• Repair the local app connection.
• Restart Msty Nexus Runtime when needed.
• Toggle Always on Top from the app controls when you want a window to stay visible.

If the app cannot authenticate, repair the local connection before changing provider, model, or network settings.

Client tokens

Client tokens let apps and scripts call Nexus.

Recommended practice:

• Create one token per client.
• Use descriptive token names such as Desktop Client, Raycast, or Internal Dashboard.
• Store the plaintext token immediately; it is shown once.
• Rename tokens when ownership changes.
• Revoke unused tokens.

Use the client token as the API key for OpenAI-compatible and Anthropic-compatible clients.

Network Access

Network settings cover the Runtime listener and browser origin access.

Controls include:

• Local-only versus network-exposed access mode
• Current bind address and port
• Pending bind changes
• CORS allowed origins

Changing network exposure requires a Runtime restart. CORS changes apply immediately and do not change the bind address.

Runtime Data

Runtime data settings show safe storage posture:

• Managed runtime root configured
• Model cache configured
• Models directory
• Known local model storage
• Retained managed runtime versions
• Install policy
• Publisher download posture
• PATH install posture

Storage roots stay server-side. The public settings view avoids raw database paths, runtime roots, credential references, and generated artifact paths.

Local AI Performance

Runtime performance settings affect local runtime behavior. Examples include:

• Ollama context length
• Ollama parallel requests
• Ollama max loaded models
• Ollama queue size
• Ollama keep-ready duration
• llama.cpp context length
• llama.cpp parallel requests
• llama.cpp CPU threads
• llama.cpp batch and micro-batch size
• Acceleration engine selection where supported

Higher values can use more memory. Restart the affected runtime after saving when the app indicates a restart is required.

Start at Login

Start at Login launches Msty Nexus automatically after OS sign-in.

Security and ownership rules:

• Nexus manages only its own startup registration.
• Nexus refuses to replace unmanaged OS startup entries.
• Auto-start launches the tray/menu surface, not a foreground setup window.
• Development mode disables and removes managed auto-start registration.
• The control may be unavailable in builds or operating systems where Nexus cannot manage startup safely.

Use this when Nexus should be ready for connected local apps without manually opening it first.

Gauge

Gauge settings control the optional Gauge feature and retention.

Gauge is off by default. Enable it only when you want Nexus to collect local and external usage/capacity signals from configured sources. Each external account source remains opt-in after Gauge itself is enabled.

Notifications

Notifications alert you when background tasks complete while the app menu is closed.

Only tasks started while the app is open can trigger alerts. If OS permission is denied, allow notifications for Msty Nexus in system settings and return to the app.

Diagnostics

Diagnostics produces a support-safe snapshot. It can summarize:

• Runtime version and platform
• Recent task counts
• Runtime service status
• Installed/running/installable service counts
• Gateway request logging state
• Network and CORS posture

Diagnostics does not include provider keys, token values, local paths, prompt text, response text, raw request bodies, or raw provider output.