Skip to content

Stopping, restarting and new versions ​

Keep, tune, script, in under a minute, with sound

Close the window, update insensical or stop the daemon whenever you like. Here's what keeps running and what comes back.

What survives what ​

What happensProgramsScreens and scrollbackLayout, directories, names
The window is closedkeep runningkeptkept
The window is opened again—shown as they are—
The daemon moves to a new version (restart from the window, isc restart-server)keep runningkeptkept
The daemon is stopped (isc kill-server, a logout that stops your user manager, reboot)endkept, as text and colourkept
The daemon dies with no warning (crash, power cut, kill -9)endlostkept

After the daemon has been stopped ​

Your layout is saved whenever it changes: projects, tabs, splits, floats, minimized panes, focus, each pane's directory, and names. When the daemon starts, it rebuilds all of it, zoomed, floating, minimized, muted and sleeping things included.

Each pane gets a fresh shell in its directory, or in the project's root or your home directory if that's gone. Nothing runs again by itself: a pane that was running nvim or an agent comes back as a shell, and a program's environment isn't kept.

Each pane also shows what it showed before, history included, at the same size. A dim line, "── from before the server stopped ──", separates it from the new prompt.

  • You can scroll, search and copy it, but it's only the printed text.
  • It's written when the daemon is told to stop and when a pane's program ends. A crash or power cut keeps the layout but loses the screens.

Screens are saved in ~/.local/state/insensical/screens, readable only by you. They hold everything a program printed, secrets included. With keep-scrollback = false, nothing is written, and files already there are removed as their panes close.

What ran in a pane is offered, not run

  • A pane started with a command, as in isc run -- npm start, comes back as a shell with that command typed at the prompt. Press Enter to run it, or edit it first. Commands you typed in the shell aren't offered.
  • With the Claude Code hooks installed, a pane where Claude was still working when the daemon stopped gets claude --resume <session> at the prompt, once. If you quit Claude yourself, or don't run it, it isn't offered again. Codex, opencode and pi are offered their own resume commands (Agents). Gemini CLI isn't.

A layout file that can't be read

The daemon sets it aside as state.json.unreadable, beside the original, and starts empty. That means a file from a version this one can't read, or a damaged one. To go back to it, run isc kill-server, mend the file, and put it back as state.json.

A new version installed underneath ​

The daemon asks GitHub for a new release a minute after it starts and then about every 24 hours, and tells every window and isc version what it found. The request names only your version and platform. If you're offline, it says nothing. To turn the daily look off, switch off Check for updates automatically on Settings > General, or set check-for-updates = false. Then insensical asks only when you press Check Now or run an update yourself.

When a new release is out, the window's notice says "insensical 0.6.0 is out", with three buttons. It's never a desktop notification.

  • What's New opens the release notes in your browser.
  • Update installs it, as isc upgrade does, and then the notice says to restart. If a package or Homebrew installed insensical, the button says How to Update and shows the command to run, with a copy button. A copy no release ships, such as a Linux window on arm64 or an Intel Mac, was built from source: How to Update says "This copy was built from source. Build the new version the same way."
  • Skip hides that version in every window. You're told again when a newer one is out.

Settings > General says the same in its Updates row: the version you run, then when the daemon last checked, or the version that's out with What's New. Check Now looks at once, even with the daily look off. Update or How to Update works as in the notice. If a check or an update fails, the row says why in red.

isc version prints one more line when a newer release is out, such as insensical 0.6.0 is available, with what's new, and the command that updates it if a package or Homebrew installed insensical (or, for a copy built from source, that it's built again the same way). No other isc command prints this. You can also watch the releases' Atom feed on GitHub.

isc upgrade fetches the latest release and installs it over the copy you're running, after checking the download against the release's signed record. If they differ, it replaces nothing. If a package or Homebrew installed insensical, it prints the command that updates it instead. isc upgrade --check only says what there is. It never restarts the daemon.

Installing replaces files and nothing else. Your daemon and window keep working. The top bar says "insensical was updated. Restart to use the new version." isc version and isc ls say the same.

To move to the new version, do any of these:

  • press the notice;
  • press Ctrl+Alt+Shift+R (leader U);
  • choose "Restart insensical" in the palette;
  • close the application and open it again;
  • run isc restart-server in a terminal.

Each one asks first. Press Enter to restart, or Escape to leave everything as it is. With no terminal to ask on, isc restart-server does nothing unless you pass --yes.

Restarting ends nothing. The daemon becomes the installed version in place, with the same terminals, programs, screens and scrollback. The first move to a version that can do this still ends everything, and the prompt says so.

Good to know

  • If you open the application while the old daemon is still running, the window says so. Press Enter to restart the daemon, or Escape to leave it and close the window.
  • If the server is newer than the window ("The server is already the new version, and this window is from before it"), the server is left alone whatever you press. The new application opens by itself or on Enter. Otherwise, close the window and open the insensical you installed.
  • If the daemon can't make way, nothing is stopped. The window says "The server did not move to the new version" and why. Press Enter to go back. isc restart-server prints the reason and exits with status 1.
  • Across a move, windows reconnect by themselves. isc attach, isc events and isc wait end, and you run them again.
  • With a different terminal engine, screens are redrawn: text, colours, history and cursor are kept, a redefined colour isn't.
  • Restarting won't give you a fresh daemon, for instance after it started with the wrong environment. For that, run isc kill-server, which ends every program, then run any command or open the window.

Remote hosts run exactly your version. When hosts you're connected to run an older one, the notice says so, such as "2 remote hosts run 0.5.0", with Update Them (Update It for one) and Not Now.

  • Update Them updates each host in turn to this computer's version, never the latest. The notice shows progress, such as "Updating agents, 1 of 2", and then how it went. If a host's server would need a restart, its card asks you first.
  • A host where a package or Homebrew installed insensical isn't touched. The notice gives the command to run there, with Copy.
  • Not Now hides the notice until this computer has a new version.

This computer's own update or restart notice comes first.

When the daemon goes away under an open window ​

The window looks for a daemon once a second and carries on when one appears. Press Enter to start one yourself.

  • "The server has stopped": the layout comes back when it starts.
  • "The server is moving to a new version": the window finds it again by itself.
  • "This window fell behind the server and was cut off. It has connected again.": the daemon cut the window off after it left 8 MiB unread.
  • "This window was disconnected": you ended its connection from another client. Press Enter.
  • If the new daemon is a different version from the window, the window starts the installed application in its place, or tells you to close and reopen.

Different versions of isc, window and daemon ​

  • They work together when they share a protocol and terminal engine, whatever their version numbers. A mismatch is refused with a message that names isc restart-server.
  • With --host, the other machine's isc has to match too.
  • These always work: isc version, isc status, isc notify, the agents' hooks, isc kill-server, isc restart-server.