Skip to content
Download

When something goes wrong ​

Starting, stopping and versions ​

What is seenWhyWhat to do
"The insensical server cannot be reached"No daemon is running and none could be started: isc isn't beside the application or on PATH, or the socket's directory isn't privatePut isc beside insensical; check the directory's permissions
"insensical was updated, and the server still running is from before", at launchA new version was installed under a running daemonPress Enter to restart it. Everything keeps running; if the daemon is too old to make way, programs end and the layout comes back. Or press Escape to leave it
isc: protocol N does not match the running daemon's MThe same, from the command lineRun isc restart-server
"The server has stopped" in the windowThe daemon was stopped or crashedPress Enter to start it; the layout comes back
"The server did not move to the new version" in the window, or isc: the daemon was not movedThe installed isc is missing from where the daemon was started, or can't take over what it runsNothing was lost. Press Enter to go back to it. Reinstall; or run isc kill-server and start again, which ends what's running
daemon: running, but it does not say what it is, from isc versionThe daemon is from before the requests that every version answers, or it's stuckRun isc restart-server
a daemon is already runningisc daemon was run twiceNothing; or run isc kill-server first
path must be shorter than SUN_LENThe socket's path is too longSet a shorter INSENSICAL_SOCKET
The update notice appears though nothing was updatedThe binaries were rebuilt or reinstalledRestart when convenient

Settings and appearance ​

What is seenWhyWhat to do
A red message in the top barA setting couldn't be used; the message names the file and lineFix the line; it applies within a second
All settings seem ignoredOne unreadable line voids the whole fileAs above
Icons are boxes or missingThe font isn't a Nerd FontSet font-family to a Nerd Font
Text smaller or larger than expectedfont-size is in points12 points is 16 pixels on Linux
Text thinner than in another terminalThere's no font weight settingNothing; the regular face is always used
theme = "ghostty" is reported as an errorGhostty isn't installedUse a built-in theme or a theme file
The window has a generic iconIt was run without installing, or the icon cache is oldRun just install or just install-local; restart the launcher or panel

Panes and shells ​

What is seenWhyWhat to do
A different shell, prompt or completion style than in another terminalPanes run $SHELL; the other terminal was set to run something elseSet shell = "…"
Commands not found in panes that exist in other terminalsThe daemon was started from a launcher with a short PATHSet PATH in the shell's start-up files, or stop the daemon with isc kill-server and start it from a terminal
A new variable in a shell profile is missing in panesThe daemon keeps the environment it was started withThe same
Programs over ssh complain about an unknown terminalThe other machine has no xterm-ghostty descriptionSet TERM there, or install the description
A pane shows the generic terminal iconIt has printed nothing and been sent nothing, or its program isn't in the listNothing
A pasted block waits at the foot of the paneIt has several lines and the program didn't ask for marked pastesPress Enter to paste it, or Escape to drop it
Accents typed as two keys, or an input method, do not workNot supportedNothing
Search misses text that is on screenThe text wraps across two rowsSearch for a part that's on one row
A pane does not fit its windowAnother window or isc attach resized itUse one window; leave the attach
Ctrl+` does not reach a programThat key brings up the scratch paneSet the key to none in [keys]

States, agents and notifications ​

What is seenWhyWhat to do
A pane never shows doneThe command ran for under 30 seconds and reported nothingUse isc status from a hook, or a program that reports progress
A failed command shows doneThe shell doesn't mark its commandsUse fish 4, or the isc shell-integration line for bash or zsh
A pane stuck in a stateA hook reported it and nothing has reported sinceisc status explain, isc status idle
A Gemini CLI pane stays running after a failed or cancelled turnGemini CLI has no event for eitherThe next prompt clears it; or run isc status idle
Hooks stopped reportingisc moved since integrateRun isc integrate for that agent again
Codex reports nothingIts hooks aren't trustedRun /hooks in Codex
The bell marks a pane but no notification arrivesThe bell never notifiesNothing
A clicked notification selects the pane but the window stays behindWayland; see Desktop notificationsBring the window forward yourself
Notifications have no application name or iconThe desktop entry isn't installedInstall
The leader does nothingThe desktop took Ctrl+SpacePick another leader