Mover

Claude Code process exited with code 1: what to check

By
Updated . 9 min read.

Claude Code process exited with code 1 is a message printed by the program that launched Claude Code, such as VS Code or an SDK app, and the Anthropic error reference lists it under Wrapper and IDE errors. Error reference Troubleshooting page

The first command to run is claude doctor from your shell. Anthropic gives it for a claude that will not start at all, and gives /doctor inside Claude Code for a session that does start. Troubleshooting page The steps below follow that order and then cover the other cases the two pages describe.

The copy of the error reference that we read on 6 October 2026 ended inside its find-your-error table, before the text of the Wrapper and IDE errors section. The pages as read therefore do not say what exit code 1 specifically means, and they give no fix written for that one message. What they do give is a set of checks for a Claude Code that will not start, for a session that misbehaves, and for reporting a problem. Error reference

What does exit code 1 mean?

The error reference describes itself as a list of runtime errors that Claude Code displays, and it makes one exception. Wrapper and IDE errors are printed by the launching program rather than by Claude Code itself. Error reference The text on your screen therefore comes from VS Code, from an app built on the SDK, or from whatever program starts Claude Code for you.

On 6 October 2026 the error reference listed three messages under its Wrapper and IDE errors heading, and Claude Code process exited with code N was one of them. Error reference

The other two entries in that group are "Could not locate the Claude CLI on PATH" and "The connection to Claude Code ended before this message completed". If your launcher shows one of those, you have a different message with its own entry. Error reference The docs write N where the number goes, so code 1 is the same entry with the number filled in.

The troubleshooting page names the code 1 case directly. In its list of where to go for each symptom, "Claude Code process exited with code 1 in VS Code or an SDK app" points to the Error reference. Troubleshooting page

One more detail from the error reference bears on how to read it. Apart from the Wrapper and IDE group, the page says its errors and recovery commands apply across the CLI, the Desktop app and cloud sessions, because all three wrap the same Claude Code CLI. Error reference The page's wording places the launcher-printed group outside that statement, so a recovery command listed for another error is not promised to apply here.

What should you run first?

Anthropic's troubleshooting page gives a short order of checks for a Claude Code that is not behaving. These are the steps it supports, in the order to try them. Troubleshooting page

  1. Open a shell and run claude doctor. The page gives this command for the case where claude will not start at all. Troubleshooting page
  2. If Claude Code does start, run /doctor inside it. The page describes it as an automated check of your installation, settings, extensions and context usage, and says it proposes fixes that it can apply after you confirm. Troubleshooting page
  3. Run /mcp to check MCP server status. Troubleshooting page
  4. Read what the checks report before changing anything, and match each finding to the symptom list in the next section.

The page says to pick a command by whether Claude Code starts. If the shell cannot find claude or the install itself fails, you are not in the territory of a runtime check. The troubleshooting page lists command not found, install failures, PATH issues, EACCES and TLS errors under a separate page, Troubleshoot installation and login. Troubleshooting page

A message that mentions a failed download is another case. The page sends an update or install download that fails with "The connection dropped while downloading the update", or that is aborted, to the Error reference, and the error reference's own index has entries for "Installation was killed before it could finish" and "The connection dropped while downloading the update". Error reference

Is it a VS Code or SDK problem?

The troubleshooting page keeps three IDE-related rows apart, and the difference tells you which page to open. Troubleshooting page

  • A VS Code extension that is not connecting or not detecting Claude goes to the VS Code integration page.
  • The message Claude Code process exited with code 1 in VS Code or an SDK app goes to the Error reference.
  • A JetBrains plugin or IDE that is not detected goes to the JetBrains integration page.

To tell the first two apart, look at what is on screen. A launcher that shows the words "Claude Code process exited with code" followed by a number matches the second row. An extension that simply fails to find or connect to Claude, with no such message, matches the first. The page does not draw this line in words, so this reading comes from how it separates the rows. Troubleshooting page

The SDK case is wider than an editor. The page names "an SDK app" without saying which, so the same entry covers any program you or a vendor built on the SDK that starts Claude Code as a process. The error reference confirms that for this group the launching program prints the message. Error reference If you wrote that program, its own logging is where its message originates.

Which page covers your symptom?

If the message you have is not the exit code at all, the troubleshooting page's symptom list is the quickest way to the right page. Each line below is one row of that list, with the page it points to. Troubleshooting page

  • Command not found, install fails, PATH issues, EACCES, TLS errors: Troubleshoot installation and login.
  • Update or install download fails with "The connection dropped while downloading the update", or aborted: Error reference.
  • Login loops, OAuth errors, 403 Forbidden, "organization disabled", and Amazon Bedrock, Google Cloud or Microsoft Foundry credentials: Troubleshoot installation and login.
  • Settings not applying, hooks not firing, MCP servers not loading: Debug your configuration.
  • API Error 5xx, 529 Overloaded, 429, and request validation errors: Error reference.
  • A model not found, or you may not have access to it: Error reference.
  • A command Claude runs fails with a disk quota or full-disk message, or command output was lost: Error reference.
  • VS Code extension not connecting or detecting Claude: the VS Code integration page.
  • Claude Code process exited with code 1 in VS Code or an SDK app: Error reference.
  • JetBrains plugin or IDE not detected: the JetBrains integration page.
  • High CPU or memory, slow responses, hangs, search not finding files: Performance and stability, on the troubleshooting page itself.

The list ends with a fallback. If you are not sure which row applies, run /doctor inside Claude Code, or claude doctor from your shell if claude will not start. Troubleshooting page

The error reference has its own lookup, a find-your-error table that maps the exact message text to a section. It opens by saying to match the message you see to a section. Error reference Copy the message exactly as your launcher prints it, since the entries are keyed on that wording.

Could a hook or plugin cause it?

The pages do not say that a plugin, MCP server or hook causes this exit. They do give a way to rule customizations in or out. In the performance section, the troubleshooting page says to restart with claude --safe-mode to check whether a plugin, MCP server or hook is the source of a resource problem. It disables all customizations for the session, and if usage drops the page points you to Debug your configuration to find which one it is. Troubleshooting page

That advice is written for high CPU or memory, so it applies to a launcher exit only as an isolation step. If the session starts and stays up under claude --safe-mode when it did not before, that points at something you have configured. If it still ends, the customizations are less likely to be involved. That comparison is the publisher's reading of the flag's description, and neither page promises it.

Separate symptoms have their own row. Settings that do not apply, hooks that do not fire, and MCP servers that do not load all go to the Debug your configuration page. Troubleshooting page If you want background on what hooks are before you look for one that misbehaves, Claude Code hooks explained covers them.

How do you keep your session?

A restart does not cost you the conversation. The troubleshooting page says restarting does not lose it, and that running claude --resume in the same directory picks the session back up. Troubleshooting page The same-directory part matters, so change to the project folder before you run it.

A second command appears in the memory section. After a critical memory warning, the page says to restart Claude Code and run claude --continue to resume the conversation in a fresh process. Troubleshooting page The page presents it for that memory case, and it does not say which of the two to prefer after a launcher exit.

If resuming itself fails, the error reference has entries for it. Its index lists "Failed to resume the conversation" and "No conversation found with the session ID" under its command-line errors. Error reference A message with that wording means you have moved on to a different entry, so look it up by its text.

What a resumed session remembers is its own topic. Claude Code memory: what carries over between sessions sets out what persists.

What if the session is heavy?

The pages do not tie memory use to this exit code. They do describe what happens when a session grows large, and a heavy session is a reasonable thing to rule out. On the troubleshooting page, a session whose heap memory passes 2.5GB shows a critical memory usage warning. To free the memory, restart Claude Code and run claude --continue. Outside fullscreen rendering, running /compact frees memory too, and the warning disappears once memory use drops below 2.5GB. Troubleshooting page

If memory stays high after those steps, /heapdump writes two files to ~/Desktop. They are a JavaScript heap snapshot named <session-id>.heapsnapshot and a memory breakdown named <session-id>-diagnostics.json. On Linux without a Desktop folder they go to your home directory. The command is hidden from the command menu, so type it in full. Troubleshooting page

A related symptom is the message Autocompact is thrashing. The page says it means automatic compaction succeeded but a file or tool output refilled the context window several times in a row, so Claude Code stops retrying. Its recovery options, in the order given, are these. Troubleshooting page

  1. Ask Claude to read the oversized file in smaller chunks, such as a line range or one function.
  2. Run /compact with a focus that drops the large output, for example /compact keep only the plan and the diff.
  3. Move the large-file work to a subagent so it runs in a separate context window.
  4. Run /clear if the earlier conversation is no longer needed.

If the thrashing error returns after /clear, the page says to run /context and compare the Messages row with the rows above it. A Messages row that is the largest means a file or tool output in the new conversation is refilling the window. Other rows that together are larger mean what loads at session start leaves too little room. Troubleshooting page What compaction does to a plan you wrote earlier in the session is covered in Why Claude Code forgets the plan after compaction.

How do you report it safely?

If the checks above do not settle it, the troubleshooting page lists where to go next. Run /doctor for a setup checkup and /mcp to check MCP server status, use the /feedback command inside Claude Code to report problems directly to Anthropic, or check the GitHub repository for known issues. It adds that Claude has built-in access to its own documentation, so you can ask it directly about its capabilities and features. Troubleshooting page

Take care with what you attach. The .heapsnapshot file contains every string in the process, including your full conversation and credentials, and the page says not to attach it to a public issue or share it. For a GitHub issue, it says to attach only the -diagnostics.json file, which carries the statistics behind the printed summary and no conversation content or credentials. Troubleshooting page

Account, billing and subscription problems go elsewhere. The page says to contact Anthropic support by signing in at claude.ai, or platform.claude.com for Console users, clicking your initials in the lower left, and selecting Get help. Troubleshooting page

When you report the exit, include the exact wording your launcher printed and the program that printed it, since the error reference says that group of messages comes from the launching program and not from Claude Code. Error reference

Common questions

Does Claude Code itself print this message?

No. The error reference says Wrapper and IDE errors are printed by the launching program rather than by Claude Code, and it lists this message in that group. Error reference

What is the first command to run?

Run claude doctor from your shell if claude will not start, or /doctor inside Claude Code if it does. The troubleshooting page describes /doctor as checking installation, settings, extensions and context usage. Troubleshooting page

Do you lose the conversation after the process exits?

The troubleshooting page says restarting does not lose your conversation, and that claude --resume in the same directory picks the session back up. It says this in its section on a frozen command, and the pages do not describe the launcher exit case separately. Troubleshooting page

Is exit code 1 the only code the docs mention?

The error reference writes the entry as "Claude Code process exited with code N", with N standing for the number, and the troubleshooting page names code 1 specifically. Error reference Troubleshooting page

How we checked

This page is a reading of two Anthropic pages on 6 October 2026, the error reference and the troubleshooting page. No command was run, tried or tested by the publisher, and every step comes from those pages.

The copy of the error reference that was read ended inside its find-your-error table, so the entries for the Wrapper and IDE errors group were seen as index lines only. No count or test of the publisher's own is reported.

Last verified 6 October 2026. Checked against the Anthropic error reference and troubleshooting pages on 6 October 2026.

Sources

  1. Anthropic, error reference checked 6 October 2026
  2. Anthropic, troubleshooting checked 6 October 2026

From the publisher

Mover (our product)

Run claude doctor from your shell, then look up the exact message your launcher printed in the find-your-error table of the Anthropic error reference.

Mover is a $49 one-time planning tool that runs inside Claude Code or Codex, keeps your plan in plain files on your own computer, and says so when your work drifts from it. It is the wrong choice if you want something that keeps running while your computer is off.

Get Mover, $49 once

One payment. 30-day money-back guarantee.