Skip to content

When something goes wrong ​

Find what you see, then do what's next to it.

Starting, stopping and versions ​

What you seeWhyWhat to do
"The insensical server cannot be reached"No daemon is running and none could start: 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", at launchA new version was installed under a running daemonPress Enter to restart it. Everything keeps running, unless the daemon is too old to make way. Escape leaves it
"The server is already the new version, and this window is from before it", at launchAn older application was still running when the server moved onPress Enter to open the new application, or close the window and open insensical again. Nothing ends
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
"This window was disconnected", or "Disconnected" in a terminal or browserYou ended that connection from another client, with isc disconnect or DisconnectPress Enter in the window, any key in a terminal, or reload the page
"The server did not move to the new version", or isc: the daemon was not movedThe installed isc is missing from where the daemon started, or can't take overPress Enter to go back. Reinstall, or run isc kill-server and start again (ends what's running)
daemon: running, but it does not say what it is, from isc versionThe daemon is too old to answer, or 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
isc: ssh needs your key or password for buildssh to that machine needs something typed, and a link can't type itisc host answer build shows what it asks. Give the machine a key (ssh-copy-id build), or load yours with ssh-add
isc: ssh hasn't met build beforessh would have asked about the host's keyRun isc host answer build and answer it
isc: build's host key is not the one ssh has for itThe machine's key changedFind out why first. ssh-keygen -R build forgets the old key
isc: build is offA machine of your tailnet that Tailscale says isn't onlineTurn it on, or start Tailscale there
isc: build has no `isc` where a shell finds itinsensical isn't installed there, or is somewhere ssh doesn't lookInstall it there. ~/.local/bin, /usr/local/bin and Homebrew's bin are checked
isc: build has isc X … and this machine has isc Y … which cannot speak to each otherThe two machines have different versionsInstall the same version on both (isc host put build puts this one there), then run isc host restart build
isc: this connection was not given the right to …, which … needs. Its rights are: …The command ran with --rights and left out a right it needsRun it with that right, or without --rights
isc: `isc integrate` asks before it changes an agent's settings, and on another machine there is nobody to askisc --host NAME integrate without --status or --yesRun it in a terminal there, or look with --status and then add --yes
isc: theme is a setting of the interface, read from the file on the machine the interface runs onisc --host NAME config was given a setting that isn't the daemon'sLeave --host out
isc: this daemon was not started as `isc daemon`, so it has no `isc` to do that withAnother program runs the daemon inside itselfRun isc integrate or isc config on that machine
isc: the link to the other machine was lost, or "is out of reach" in the interfaceThe machine stopped answering, or ssh endedRun the command again; the interface retries by itself
The update notice appears though nothing was updatedThe binaries were rebuilt or reinstalledRestart when convenient

Settings and appearance ​

What you seeWhyWhat 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 fileSame
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 used
theme = "ghostty" is 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 oldInstall it from a package, or rebuild the icon cache (see The icon); restart the launcher or panel

Panes and shells ​

What you seeWhyWhat to do
A different shell, prompt or completion than in another terminalPanes run $SHELL; the other terminal runs something elseSet shell = "…"
Commands found in other terminals aren't found in panesThe daemon started from a launcher with a short PATHSet PATH in the shell's start-up files, or run isc kill-server and start it from a terminal
On another machine, the first letters of a line show late and the rest at onceTyping is drawn ahead only once the program has shown two letters you typedNothing: it keeps passwords from being drawn. type-ahead = "off" makes every letter wait alike
On another machine, a letter you typed shows and then goesThe program answered the key with something else, or nothingNothing: what's left is what the program has
A new variable in a shell profile is missing in panesThe daemon keeps the environment it started withSame
Programs over ssh complain about an unknown terminalThe other machine has no xterm-ghostty descriptioninfocmp -x xterm-ghostty | ssh host tic -x -, or term = "xterm-256color"
A pane shows the generic terminal iconIt has printed 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 pastes, or it holds the sequence that ends one. The card says whichRead the card, then press Enter to paste or Escape to drop
Ctrl+click on a path shows it in the file managerIt's a directory, a runnable file, or a kind opening could runOpen it yourself, or set open-files-with to your editor
A path isn't underlined under the pointerPaths are looked up only while Ctrl is heldHold Ctrl
An input method does nothingIt's off by defaultSet input-method = true
On a Mac, Alt+B and Alt+F do nothing in a shell, or type ∫ and ƒOption types the layout's characterSet option-as-alt = true
Search misses text that is on screenThe text wraps across three rows or more; two rows are foundSearch for a part on one or two rows
A pane doesn't fit its window, and its header says "Sized elsewhere"Another window, or isc attach, was used lastClick this window, or press the mark
Ctrl+` doesn't reach a programThat key brings up the scratch paneSet the key to none in [keys]

States, agents and notifications ​

What you seeWhyWhat to do
A pane never shows doneThe command ran under 30 seconds and reported nothingLower long-command, use 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 is stuck in a stateA hook or the program reported it and nothing has reported sinceisc status explain says who. Run isc status clear, or choose "Forget what this pane's program said it was doing" in the palette
isc status changes nothing in a paneThe pane's program reports its own state in its terminal, which winsisc status explain says so. It counts again when the program says it's done or idle, or ends
A pane stays running or waiting after its program was killedThe program reported in its terminal and never took it back, somewhere insensical can't see it end: through ssh, in a pane started with a command, or under a nested shell. See "Programs that report by themselves"Same as above
A program's reports aren't heardIt runs inside tmux or screen, which don't pass them onRun it in the pane itself
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
Nothing reaches your phoneA window, terminal or browser that can type is attached, so you count as there; or the command or address failed; or a notify- setting is mistypedisc notify --sinks says how the last one went. Set notify-command-when or notify-url-when to always
isc notify --test says https can't be done on this processorIt lacks what the built-in https needsUse notify-command with curl
A clicked notification selects the pane but the window stays behindWayland; see NotificationsBring the window forward yourself
Notifications have no application name or iconThe desktop entry isn't installedInstall it
The tray's icon is blankinsensical's icons aren't installedInstall them
There's no icon in the trayThe desktop has no tray for status notifier items, or tray is offOn GNOME, add the AppIndicator extension
The leader does nothingThe desktop took Ctrl+SpacePick another leader