Troubleshooting
What to do when something goes wrong: Claude Code that can’t be found or is too old, a sign-in that won’t finish, a tab that won’t start or seems stuck, a program Claude can’t find, features missing on Linux, and Claude itself having a bad day. The last pages cover the logs and diagnostics to look at, what to include when you report a problem, and what to do with a settings file that won’t load.
Start with the page that matches what you see. If none does, Diagnostics and logs says where to look next, and Reporting an issue says how to tell us. To ask a question instead, ask on dotBunny’s Discord.
In this chapter
- Claude Code missing or too oldClaudette runs your installed Claude Code, so without one it can't start a tab.
- Signing inSigning in describes the sign-in screen.
- A tab that won't startA tab that can't start, or whose Claude Code stops, shows an error icon in the sidebar.
- A tab that seems stuckA turn can run a long time without being stuck: a test run or a build may take many minutes.
- Claude can't find a programOn macOS and Linux, you may see Claude fail to run node, dotnet, brew or another program in a Claudette tab, while the same command works in a terminal with claude.
- Something missing on LinuxA few features rely on programs a Linux desktop may not have. Without one, the feature is off, and Claudette says why.
- Claude is having problemsWhen Claude itself has trouble, tabs fail in ways that look like Claudette's fault or yours: retries, overloaded errors, a sign-in that won't finish.
- Diagnostics and logsWhen something looks wrong, Claudette has a page of diagnostics and two kinds of logs to look at.
- Reporting an issueQuestions go to dotBunny's Discord, and problems with Claudette to its GitHub issues.
- Settings back to their defaultsClaudette keeps its settings in a file, and its tabs and other state in another.