Troubleshooting
Common problems and how to fix them.
Blank/white screen after waking from sleep
macOS can drop the rendering context in the background without telling the app right away, so the editor or terminal comes back blank after standby. Quack watches for this and repairs affected panes automatically on wake — if it still looks wrong after a few seconds, switch tabs and back to force a redraw.
If the screen is blank with a red error overlay, that's a different problem (a build error), not this one — read the overlay instead of waiting.
Something's stuck / high CPU
Open the Task Manager (Ctrl+Alt+U) to see Quack's own process tree with
CPU and memory per process, and kill only the one that's misbehaving.
Closing a terminal tab kills only that terminal; closing a chat kills only
that chat's agent process — so if one thing is stuck, the rest of your open
work is unaffected either way.
Claude Code says you're not signed in
Quack checks your actual credentials rather than trusting a cached state — if it detects the CLI installed but not signed in, you'll see a banner with a Sign In button. Click it and Quack opens a terminal, runs the login flow, and closes it automatically once it detects success. This needs an open workspace, since Claude Code's login runs from a project directory.