Troubleshooting
Fix a missing agent, recover chats after a crash, reconnect a moved project or an SSH host, and find Glade's logs when something breaks.
An agent is missing or won’t start
Check these in order:
Run it in a fresh terminal
If claude, codex, cursor-agent, grok or opencode doesn’t run there, fix the install
first.
Check the sign-in
Sign in again with the agent’s own command, listed on its agent page.
Check the version
Settings → Providers shows Update required when the CLI is older than Glade needs.
Check the path
If the CLI isn’t on your PATH, or a custom path in Settings → Providers is wrong, Glade
can’t find it.
Restart Glade
If the agent reports a service or account error, that comes from the provider. Check its status page.
Chats stopped after a crash
When Glade stops unexpectedly, the next launch offers to continue the chats that were running. Continue sends each chosen chat a message saying the run stopped, asking the agent to check what already happened before repeating anything. Dismiss drops the offer. Nothing continues on its own.
A project folder moved
Don’t add the folder as a new project. Right-click the project in the sidebar, choose Change project path… and enter the new location. Chats and history stay attached.
Finish running turns and close terminals in the old folder first. This doesn’t move files or repair Git worktrees.
An SSH host won’t connect
Open Settings → SSH hosts and choose Reconnect in the host’s … menu. It drops the connection, asks any sign-in questions again and reinstalls Glade on the host if needed. See SSH hosts for the requirements.
A device can’t reach Glade
See remote access troubleshooting.
Logs
Glade writes its logs to ~/.glade/userdata/logs. If the app fails to start, the error dialog offers
Open logs. Review and redact logs before attaching them to an issue.
Report a problem
Use /feedback in any chat, or open an issue on
GitHub.