What is the exact message?
Session failed: spawn error:Anthropic describes it as that prefix followed by an ENOENT message, and the message names the file the launch could not find. Search your line for spawn error and ENOENT together, because the path in the middle is specific to your machine. It appears in the terminal running claude remote-control, which is where the server prints what happened to a session it tried to start.
On current builds a missing folder gets its own wording instead:
Session failed: working folder not found: "<path>"What does it mean?
The Remote Control server could not start a new session because something the launch needed is missing from disk. The session never began, so there is nothing to find in the phone or the browser — the problem is on the machine running the server.
ENOENT is the operating system's "no such file or directory". Anthropic documents two different things it can name, and the fix differs between them.
What causes it
- The program file the server started from is gone. A newer version may have replaced it; new sessions then run that version. When no newer version exists to run, new sessions fail with this message.
- The working folder a session named does not exist. Before v2.1.318 a session that failed this way showed the same
spawn errorwith anENOENT, and the text named a program file rather than the missing folder. Current builds give that case its own message instead. - Claude Code lives on network storage. Anthropic treats a server started from network storage as its own case, because the file behind the running server can move under it.
How do I fix it?
- Check that
clauderuns in your shell. If it does not, install Claude Code again — that is Anthropic's step for this message, and the first thing to rule out. - Stop the server, then run
claude remote-controlagain from a folder that exists. The running server keeps using the program file it started from, so it has to stop before it can move onto a different one. Start a session to confirm one launches. - If Claude Code is installed on network storage, restart the server and follow Anthropic's install-on-network-storage steps. The program file can be replaced or moved under a server that holds it.
- If the
ENOENTnames a folder instead, restore that folder and start the session again. If the server has already exited, runclaude remote-controlfrom a folder that exists.
How do I know it is fixed?
- A new session starts from the phone or browser instead of failing in the server terminal.
- The server terminal prints no further
spawn errorlines when you start one. - After the restart, the warning about the program file being gone stops appearing, which means the server is on the current file.
Where these answers come from
- The message and where it prints, the program-file warning, the missing-folder case before v2.1.318, the stop-and-reinstall steps and the network-storage route: Anthropic's Remote Control troubleshooting, read November 18, 2026.
- The missing-folder message in its current form: the same page, read November 18, 2026.
- Installing on network storage: Anthropic's setup page, read November 18, 2026.
Common questions
Which process prints Session failed: spawn error?
The terminal running claude remote-control. It prints the message when a new session cannot start, so the failure is in the server's ability to launch a session, not in the session itself.
What does ENOENT mean here?
A file or folder the launch named does not exist. Anthropic documents two things it can name: the program file the server started from, and, before v2.1.318, the working folder a session was asked to use.
Will updating Claude Code fix it?
It can. Anthropic documents that before v2.1.318 new sessions failed this way even with a newer version installed, and that the missing-folder case now has its own message. Restart the server after updating.
The server is still running. Do I have to stop it?
Yes, to move the server onto the current program file. Stop it and run claude remote-control again. If Claude Code is installed on network storage, restart the server and follow Anthropic's install-on-network-storage steps.