Omniscio

OmniscioGuidesCouldn't restart

Claude Code couldn't restart: your conversation is saved

Last checked against Anthropic's documentation on November 18, 2026. By the Omniscio team. Updated .

What is the exact message?

Claude Code couldn't restart. Your conversation is saved. Start Claude Code again and run /resume to pick it up.

There is a shorter form, used when the restart had no conversation to reopen — for example when /tui was your first input in a new session:

Claude Code couldn't restart. Start Claude Code again.

What does it mean?

Claude Code was restarting itself and could not start the new process, so it exited with status 1. The sentence about your conversation tells you which of the two variants you got, and so whether there is a conversation on disk to reopen.

When it says the conversation is saved, it is on disk and you can pick it up where it stopped.

What causes it

  • A renderer switch. Claude Code restarts itself to switch to or from fullscreen rendering. /tui fullscreen and /tui default are the two switches, and each relaunches the conversation in the new renderer. Anthropic names this as the example.
  • The replacement process would not launch. The message reports the launch, not the conversation, and Claude Code exits with status 1 rather than carrying on.
  • The launch keeps failing. When it happens on every attempt, the operating system's own reason is in the debug log, not in the terminal message.

How do I fix it?

  1. Run claude again in your shell. That is the whole recovery for a one-off restart failure.
  2. Run /resume and select the conversation, if the message said it was saved. It comes back where it stopped.
  3. If it is not in the list, widen the session picker. By default it shows the current worktree. Ctrl+W widens it to every worktree of the repository, and Ctrl+A to every project on the machine.
  4. If restarts keep failing, capture the reason. Start with claude --debug-file claude-debug.log. If a restart from that session fails, the log in the directory you started from records a Failed to relaunch: line with the operating system's error, and that line is what a bug report needs.

How do I know it is fixed?

  • claude starts and stays up, so the shell returns a prompt box rather than the error.
  • The conversation comes back with its earlier messages after you pick it in /resume.
  • Running /tui fullscreen or /tui default switches the renderer without the error, so the restart path itself works.

Where these answers come from

Common questions

Did I lose the conversation?

No, when the message says your conversation is saved. Anthropic's wording is that the conversation is on disk and you can pick it up where it stopped. Run claude again and use /resume.

What made Claude Code restart itself?

Switching to or from fullscreen rendering, which happens after /tui. Claude Code restarts itself for that, could not start the new process, and exited with status 1.

The conversation is not in the /resume list. What now?

Widen the session picker. By default it lists the current worktree; Ctrl+W widens it to every worktree of the repository and Ctrl+A to every project on the machine, so a conversation started elsewhere appears once you widen it.

How do I find out why the restart failed?

Start Claude Code with claude --debug-file claude-debug.log. If a restart from that session fails, the log in the directory you started from records a Failed to relaunch: line with the operating system's error.