tydeSettings reference
Find host and session settings, backend setup, code intelligence, keyboard shortcuts, and mobile pairing.
Check the scope first
Host-scoped settings apply to the machine selected in the settings host selector. This includes Backends, Custom Agents, MCP Servers, and Skills. When managing more than one server, check the host label before saving.
Session settings apply to the conversation’s backend. Choose a backend before the first message and inspect the options shown for it. A host default affects new conversations; it does not turn an existing conversation into a different harness.
Updates and agent restoration
In Settings → Updates, update channel and automatic update checks apply to this device. Under Agent restoration, choose the host and toggle Resume previous agents. This is enabled by default. Turn it off to prevent that host from automatically reopening its previous agents after an update or restart. Running agents are not stopped, and saved conversations remain in History for manual resume. The preference takes effect on the next host restart.
Backend setup and compatibility
The current desktop interface includes Claude, Codex, OpenCode, Grok, Antigravity, Hermes, and Kiro integrations. Use Settings → Backends on the target host to see availability and diagnostics. An integration appearing in the interface does not mean its CLI is installed or authenticated on every machine.
| Tyde provides | The harness still determines |
|---|---|
| Conversation and workspace UI | Available models and provider authentication |
| Agent organization and session access | Native context limits and supported session operations |
| Shared agent and skill configuration | Native tools and how instructions are applied |
| Tyde delegation and launch preferences | Provider capacity, cost, and capability limits |
Use launch profiles when you need repeatable backend choices for delegated work. Review the ordered delegation preferences and cost profiles rather than assuming every child will use the parent’s configuration.
Codex defaults and behavior
Open Settings → Codex to edit Codex’s user configuration on the selected host. These settings also apply when you use Codex outside Tyde. Project and explicit session settings can override the defaults.
- Defaults: model, reasoning effort, and supported speed tiers for new chats.
- Subagents: enable Codex’s native subagents, set their maximum concurrency, and choose their default model and reasoning effort. The limit excludes the main agent. Tyde’s own subagent controls remain separate.
- Responses: communication style, verbosity, and reasoning summaries.
- Memory: enable memory, generate or use memories, and exclude external-context conversations from memory generation.
- Advanced: web search, automatic compaction threshold, tool-output token limit, and login shells.
Changes leave running sessions alone. New chats inherit the defaults; process-level behavior takes effect the next time Codex starts, including when reopening a session. Use CLI default removes the user override. Unrelated Codex configuration is preserved, and conflicting external edits require reviewing refreshed values before saving again.
Code intelligence
Tyde has language-server integrations for Rust through rust-analyzer and Python through Pyright. They provide source navigation, hover information, references, and diagnostics when the language server and project are available.
Settings → Code Intelligence → Enable code intelligence controls all projects on the selected host. Turning it off stops language servers and their child processes without closing files or stopping agents. The setting persists across restarts. Rust analysis runs Cargo checks and build scripts, which can compete with your builds.
Open the code-intelligence settings on the project’s host. If automatic discovery cannot find the server, set its executable path and follow the displayed diagnostics. Python support detects .py and .pyi files with project markers such as pyproject.toml or requirements.txt. Rust projects use Cargo.toml.
Other file types can still be browsed. Syntax highlighting by itself does not imply language-server navigation support.
Commands and keyboard access
The command palette lists available actions and their platform-specific shortcuts. Use it to find New Chat, settings, the Agent Monitor, and workspace navigation without memorizing every control.
| Action | macOS | Other desktop platforms |
|---|---|---|
| New Chat | ⌘ N | Ctrl N |
| Toggle Settings | ⌘ , | Ctrl , |
| Focus primary pane | ⌘ 1 | Ctrl 1 |
| Focus secondary pane | ⌘ 2 | Ctrl 2 |
Mobile access
Open Settings → Mobile on desktop to enable mobile connections, pair a phone, manage paired devices, or configure direct hosting. Mobile access connects the phone to the same agents running on the selected host.
See Use Tyde on your phone for cloud and direct pairing, conversations, sessions, notifications, and recovery steps. Mobile pairing is separate from adding a desktop SSH host.
Review agents
Use Review to enable reviews and define review aspects with their own instructions, choose Lite or Heavy as the default mode, and configure independent reviewer lists with their own backend/model/settings choices. Both lists initially contain one reviewer inheriting the host default. Edit aspects in a dialog or ask the Tyde Operator to manage them. Agents await requested reviews and read findings through tools; manual reviews keep the existing submit flow. See review aspects.
Other settings
Settings also include steering instructions, voice options, and agent activity features. Configure these for your workflow after the basic backend and project setup works. For any provider-backed feature, review its required credentials and usage implications on the selected host.
Integrations
Settings → Integrations contains Tychat and ChatGPT Dots. Both apply to the selected host. Tychat retains its existing bot-pairing and agent settings.
Enable ChatGPT Dots to let your dot manage this host's projects and agents. Tyde creates and maintains an outbound connection automatically, without OpenAI Platform keys or inbound firewall ports. On first use, follow the displayed steps to add the MCP server in ChatGPT Plugins with OAuth authentication, then enter the one-time code in the Tyde authorization page. Do not put the pairing code in a chat.
Pairing grants access to this host's agent controls; agents may modify files and use your existing provider credentials. Tool inputs and results pass through the Tyde connection service and OpenAI over TLS, not end-to-end encryption. ChatGPT account and workspace permissions still apply.
Turning the toggle off blocks new remote commands but does not stop existing agents. Turning it back on reconnects the paired host. Disconnect ChatGPT revokes the host's connection and invalidates its OAuth grants. Connection and authorization failures are shown explicitly; use Retry to reconnect or regenerate an expired pairing code.