Troubleshooting

Resolve backend setup, connection, session, skill, navigation, and review-submission problems.

Backend unavailable

1. Check the selected host. A CLI installed locally may be missing remotely.
2. Open Settings → Backends and read the setup status and diagnostic.
3. Confirm the CLI can run and is authenticated under the account used by that host.
4. Use the displayed install or repair controls, then refresh or reconnect as appropriate.
5. Start a small conversation before returning to a larger task.

Keep the exact error message when reporting a problem. “Installed but unavailable” is a different situation from “not installed,” and the diagnostic helps identify the next step.

Host disconnected or reconnecting

Open Settings → Hosts and inspect the connection state. Confirm that the machine is reachable and that SSH works for the configured destination. If you use a custom remote command, check that it is valid on the remote machine.

A reconnecting state does not prove the agent has stopped. Reconnect and inspect the existing agent before starting a duplicate task. If the server itself restarted or stopped, check the restored session and current process state before continuing.

History or agents seem missing

Select the original host and check filters in the Agents or History view. If the agent is still running remotely, reconnect to it. If you want an earlier saved conversation, resume it from History.

Check the project and backend details before reopening a similarly named conversation. When resuming old work, ask the agent to inspect current files before relying on its earlier assumptions.

A skill is not available

1. Confirm the skill file is on the host where the agent runs, under ~/.tyde/skills/<name>/SKILL.md.
2. Open Skills settings on that host and choose Refresh.
3. Confirm the skill appears in the list.
4. Check that the custom agent definition includes the skill.
5. Start a new conversation with the intended definition to evaluate the updated configuration.

Code navigation is missing

Check that the file is Rust or Python and belongs to a recognized project. Open code-intelligence settings on the host and inspect language-server availability. Verify the configured executable path if one is set.

Opening a file and highlighting its syntax can work even when the language server is unavailable. Report the provider diagnostic, file type, and project marker when asking for help.

A review will not submit

Check whether the review is still a draft, whether it contains comments, and whether AI suggestions still need a decision. Accept or reject pending suggestions, choose the feedback target, and inspect any error shown when you submit.

Confirm you are looking at the intended source: working changes and a historical commit are different review contexts.

Report a useful issue

Open an issue in the Tyde repository. Include the Tyde version, operating system, backend and CLI version, whether the host is local or remote, the steps you took, and what you expected to happen.

Add a screenshot or exact error when it helps explain the problem. Remove credentials, private code, and personal paths from anything you publish.