One change
Error reference
errors
Nearest release: v2.1.250, published under an hour before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
errors Changed · +57 / -2 lines
### Session was stopped while the respawn was in flight ### EACCES when starting a background session ### Background service exited before it became reachable
This page is larger than the 256 KiB this site keeps, so one side of the diff below stops where the stored text does.
from line 173
| `This session has no saved transcript` | [Background session errors](#this-session-has-no-saved-transcript) | | `terminal host process died — press Enter to restart` / `This session's terminal host process died` | [Background session errors](#terminal-host-process-died) | | `Session isn't responding` / `Press enter again to restart this session — it isn't responding` | [Background session errors](#session-isnt-responding) | +| `Session <id> was stopped while the respawn was in flight` | [Background session errors](#session-was-stopped-while-the-respawn-was-in-flight) | | `This session was running agent '<name>', which is no longer available` | [Background session errors](#session-agent-no-longer-available) | | `CLAUDE_CODE_PROCESS_WRAPPER: launcher ...` | [Background session errors](#claude_code_process_wrapper-launcher-errors) | | `EUNKNOWN: unknown error, uv_spawn` | [Background session errors](#eunknown-when-starting-a-background-session) | +| `EACCES: permission denied, posix_spawn` | [Background session errors](#eacces-when-starting-a-background-session) | +| `exited before it became reachable` | [Background session errors](#background-service-exited-before-it-became-reachable) | | `Claude Code process exited with code N` | [Wrapper and IDE errors](#claude-code-process-exited-with-code-n) | | `Could not locate the Claude CLI on PATH` | [Wrapper and IDE errors](#could-not-locate-the-claude-cli-on-path) | | `Restored the code, but skipped N files` | [Rewind warnings](#restored-the-code-but-skipped-files) |
from line 2496
* From the shell, run `claude stop <id>`, then `claude attach <id>` * For a shell-command row, press `Ctrl+X` in agent view or run `claude stop <id>` to stop it; dispatch the command again to rerun it -<h3 id="session-agent-no-longer-available"> - Session agent no longer available -</h3> +### Session was stopped while the respawn was in flight -You resumed a session that was running a [custom agent](/docs/en/sub-agents#invoke-subagents-explicitly), started with `--agent` or the `agent` setting, and Claude Code didn't find an agent by that name. It searches the session's original directory first, when you have [trusted that workspace](/docs/en/permissions#project-allow-rules-and-workspace-trust), then the directory you resume from. The session still resumes, but with the default tools and system prompt, so the agent's tool restrictions no longer apply: +You opened a [background session](/docs/en/agent-view) whose process wasn't running, and while Claude Code was restarting it, another Claude Code process stopped it, for example `claude stop` in another terminal. Claude Code keeps the session stopped: ```text theme={null} -This session was running agent 'code-reviewer', which is no longer available (no agent by that name in /home/you/project). Continuing with the default tools and system prompt — the agent's tool restrictions no longer apply. To restore it, re-create the agent, or resume with an explicit --agent <name>. +Session <id> was stopped while the respawn was in flight ``` -The warning names only the directories Claude Code searched, and it appears in the resumed conversation whether you wake a [background session](/docs/en/agent-view), run `/resume` or `claude --resume`, or resume in [non-interactive mode](/docs/en/headless), where it also goes to stderr. Sessions using `--input-format stream-json` don't show it, because the Agent SDK supplies agents after startup. +Opening a session you just dispatched, while its process is still starting, waits for the process instead. Before v2.1.246, opening it at that moment could stop it and show this message. -Claude Code doesn't save the fallback to the session, so the warning repeats on each resume until you act. The built-in `claude` agent doesn't trigger the warning, since falling back to the default toolset changes nothing for it. Before v2.1.216, Claude Code silently continued as the default agent, and the lookup covered only the directory you resumed from, so a project-scoped agent was lost on any resume from another directory. - **What to do:** -* Re-create the agent file at `.claude/agents/<name>.md` in the session's project, or at `~/.claude/agents/<name>.md` for a personal agent, then resume again -* Or resu +* If you didn't stop the session, open its row again in agent view or run `claude respawn <id>` to restart it +* If you stopped it yourself, nothing remains to do: the session stays stopped + +<h3 id="session-agent-no-longer-available"> + Session agent no longer available +</h3> + +You resumed a session that was running a [custom agent](/docs/en/sub-agents#invoke-subagents-explicitly), started