Restarting the Daemon

The daemon runs the tuios build it started with until it stops. After you update tuios, restart the daemon to move your sessions to the new build. tuios restart-server Unreleased does that in one step. First it shows what stops and what comes back, and asks you. Then it stops the daemon and starts the newest tuios you have installed. It waits until the new daemon answers.

Quickstart

tuios update            # or your package manager
tuios restart-server    # show what stops, ask, then restart

From a shell, the command prints the plan and asks:

Daemon now      0.10.1
After restart   0.11.0   (from ~/.local/bin/tuios)

These stop:
  nvim in "edit" (session work)
  claude in "agent" (session work)
Only shells in notes.

These come back:
  Each session, with its layout, its pane history and new shells.
  claude-code in "agent" (session work) can resume.
The Inbox offers to resume each one.
Restart the daemon? [y/N]

Then it shows each step:

Stopping the daemon...
Starting the daemon 0.11.0...
The daemon restarted on 0.11.0.
These sessions came back: work, notes.

What stops and what comes back

A restart ends every program that runs in a pane: editors, servers, agents, long builds. The plan names each one, by pane and session, so you can finish or save work first.

Each session comes back with its layout, the pane names and the history each pane showed. Every pane gets a new shell, under a divider that says when it was restored. An agent conversation that can resume is listed in the plan. daemon.resume_agents says what the new daemon does with it:

See Resuming after a restart.

Which tuios starts

The new daemon runs the newer of two binaries, by --version:

• The tuios at the path of the command you ran. tuios update replaces this file.
• The tuios on your PATH. An install by Nix, mise, asdf or Linuxbrew moves this one.

When the version does not change, the plan says "This restart starts the same version." The restart still saves and restores each session, so it is also a clean way to apply a change to [daemon] or [hooks].

From the app Unreleased

When the daemon runs a version other than your client, the dock says so, for example "The daemon runs 0.10.1. ctrl+b j restarts it." Click the notice, or press the key it names. Esc puts the notice off until the next start. These open the same dialog:

• The command palette entry "Restart the daemon".
• The row "Restart the daemon" at the top of the Daemon tab in the settings.
• The rail's menu for this machine.

The dialog shows the plan. Press r to restart, or Esc to cancel. The dialog then shows each step: stop the daemon, start the new one, attach again. tuios starts again on the new build, in the same session, and says "The daemon restarted on 0.11.0. Your session is back."

A program can start or stop after you read the plan. Then the restart does not run, and the dialog asks you to read the new plan. If your session did not come back, tuios does not attach to it. The dialog says so and points to tuios resurrect.

The action is restart_daemon. It has no default key. To bind one:

[keybindings.prefix_mode]
restart_daemon = ["alt+r"]

The action is only on a client on the daemon's own machine. Over tuios ssh or tuios-web, run tuios restart-server on the daemon's machine.

Other clients come back by themselves

Before it stops, the daemon tells each attached client why:

While a client waits, the dock says "Waiting for the daemon. Keys are not sent." Keys you type then are dropped. The panes are new after a restart, so a held key could land in a different shell. Sometimes no daemon comes back, or the new daemon does not hold the session. Then the client quits with "The connection to the TUIOS daemon was lost."

Only a client on the same machine waits and reattaches. A client of a daemon older than v0.11.0 gets no reason, so it waits 6 seconds and then quits. Attach again after that.

From a script

tuios restart-server --dry-run          # print the plan, change nothing
tuios restart-server --yes              # restart without a question
tuios restart-server --yes --json       # one JSON object per step
tuios restart-server --last             # the steps of the last restart

• Without a terminal to ask on, the command refuses unless you give --yes. --json needs --yes.
• --json writes one object per line: plan, then stopping, starting and done. done holds restarted, after, back and missing. A failed step sets error and fix, and the command exits 1.
• --expect DIGEST refuses the restart unless the plan has that digest. The app passes the digest of the plan you agreed to.
• When no daemon runs, the command starts one.

The stop and the start run in a process of their own, in a session of its own. So a restart still finishes when you start it from a pane of the daemon it stops. Each step goes to restart.log beside the daemon log. One restart runs at a time. A second one refuses with "Another restart of the daemon is running."

How do I

• Move to a new build after tuios update? Run tuios restart-server, or click the version notice in the app.
• See what a restart would stop, without a restart? Run tuios restart-server --dry-run.
• Restart from a deploy script? Run tuios restart-server --yes --json and read the done line.
• Stop the daemon and keep the clients from waiting? Run tuios kill-server. The clients quit at once.
• Start with no sessions at all? Run tuios kill-server, then tuios daemon --no-restore.

Related