Claude Code 2.1.243 Segfaults on Linux? Roll Back Safely

If Claude Code 2.1.242 or 2.1.243 exits with Segmentation fault (core dumped) before it can even print --version on an Arch-based Linux system with glibc 2.44, stop reinstalling the latest channel. Preserve your Claude Code state, confirm the narrow crash signature, and use Anthropic's official installer to move to the stable channel.

This is a moving release incident, not a permanent installation rule. The evidence below was verified on August 24, 2026. Check the canonical issue and official changelog first. If Anthropic has shipped a fixed newer build that passes the same checks, prefer that build; use the stable-channel recovery only while the exact classifier still matches.

curl -fsSL https://claude.ai/install.sh | bash -s stable

Then verify the recovered binary before reopening a project:

claude --version
claude doctor

Do not delete ~/.claude, project files, transcripts, or settings for this incident. The reported crash occurs during process startup, before Claude Code can load a session.

Confirm This Is the Same Crash

Run these checks from a normal shell:

command -v claude
claude --version
printf 'exit=%s\n' "$?"
uname -m
ldd --version | head -n 1

The current incident has a specific fingerprint:

• claude --version itself crashes;

• the shell reports a segmentation fault and usually exit code 139;

• affected reports name native Linux x64 builds 2.1.242 or 2.1.243;

• detailed reproductions use Arch Linux, EndeavourOS, or CachyOS with glibc 2.44; and

• several core dumps stop in free() called from glibc's __newlocale() before normal CLI startup.

If Claude Code prints its version and crashes only after opening a session, this classifier does not fit. If you are on macOS, Windows, musl, ARM64, or an older glibc, do not assume the same cause from the words "segmentation fault" alone.

Why Reinstalling Latest Repeats the Failure

The strongest issue report compared working build 2.1.241 with failing build 2.1.242. The newer binary exported allocator symbols such as malloc, calloc, realloc, and free, while the older binary did not. Its first free(NULL) path then crashed inside the bundled allocator during locale initialization.

Other reporters reproduced the same instruction address and backtrace on separate Arch and CachyOS machines. One canonical issue reached 28 comments and 16 reactions within hours. A current Reddit report independently described the same Linux startup core dump and advised waiting for the next fixed release.

This evidence supports a release regression, not a damaged project. It also explains why these common attempts do not address the failure:

• launching from a different repository;

• wiping Claude Code session state;

• forcing LC_ALL=C or another valid locale;

• disabling the JavaScriptCore JIT; or

• running the default installer again with no channel or version argument.

The default native installer follows latest. If latest still resolves to the affected build, a clean reinstall simply downloads the same failing executable.

Recover Through the Official Stable Channel

Anthropic documents stable as a delayed channel that is typically about a week behind and skips releases with major regressions. The version or channel passed to the native installer also becomes the default auto-update channel.

Run:

curl -fsSL https://claude.ai/install.sh | bash -s stable

Expected result: the installer completes, and claude --version prints a version instead of exiting 139. Reports identify 2.1.241 as a working predecessor on the same affected systems, but let the official stable channel choose the supported recovery build rather than hand-editing the launcher's symlink.

Now run the read-only installation check:

claude doctor

Only after both commands succeed should you reopen the original project and resume a session. The native installer manages the launcher under ~/.local/bin/claude; you do not need to delete project state or rewrite that symlink manually.

Keep the Recovery From Reverting

Do not run claude update immediately after recovery. The update command follows the configured release channel, and the incident may still be active when you read this.

Check the current channel and version from a healthy session or your settings. Anthropic documents this stable-channel setting:

{
  "autoUpdatesChannel": "stable"
}

If your organization manages Claude Code settings, follow that policy instead of overriding it locally. Do not disable updates permanently. A short stable-channel hold is safer than freezing on an old build after a fix or security release ships.

Know When to Return to Latest

Return to latest only after at least one of these checks is true:

1. Anthropic publishes a newer release that addresses the startup crash.

2. The canonical issue closes with a released fix.

3. The newer binary passes claude --version and claude doctor on the same Linux and glibc combination.

Then install the latest channel through the documented path:

curl -fsSL https://claude.ai/install.sh | bash -s latest
claude --version
claude doctor

Keep the test bounded. Do not validate a runtime fix by opening a sensitive repository first.

Monitor the Fix From Codex Without GitHub Writes

Aident Loadout can let Codex read the canonical GitHub issue through a connected account without pasting a token into the repository. Start with account and Vault checks:

aident account auth status
aident vault vault --action status

Discover and inspect the current read-only issue Action instead of hard-coding a stale catalog name:

aident capabilities search \
  --query "GitHub read issue by owner repository issue number" \
  --targetEnv staging

On August 24, 2026, staging returned composio:github_tools:github_get_an_issue. Its input required owner, repo, and issue_number; a read for issue 89360 preflighted at zero Aident credits and returned its state, comments, labels, reactions, update time, and URL.

Inspect the exact Action returned by search, then preflight the bounded read:

aident capabilities get \
  --name "composio:github_tools:github_get_an_issue"

aident capabilities preflight \
  --name "composio:github_tools:github_get_an_issue" \
  --input '{"owner":"anthropics","repo":"claude-code","issue_number":89360}'

Execute only after the input, connected account, risk, and price match the read you intended:

aident capabilities execute \
  --name "composio:github_tools:github_get_an_issue" \
  --input '{"owner":"anthropics","repo":"claude-code","issue_number":89360}'

Expected result: current issue state and evidence with no GitHub mutation. Search again if the catalog name changes.

Reusable Codex Prompt

Follow https://aident.ai/SETUP.md. Confirm Aident account authentication and Vault status. Search staging for the current read-only GitHub Action that retrieves one issue by owner, repository, and issue number. Inspect its exact schema and connected account, then preflight issue 89360 in anthropics/claude-code. If the input is valid, the Action is read-only, and no unexpected approval is required, execute once. Return only the issue state, title, comments, reactions, labels, updated time, and URL. Do not comment, label, close, reopen, assign, or otherwise mutate GitHub.

Once your CLI is healthy, see Claude Code and Codex: Real-World Integrations for connected workflows. For the full discovery and preflight loop, use Aident Loadout: Your First Task in 10 Minutes.

Set up Aident Loadout and monitor the Claude Code fix from Codex.

Sources

• Anthropic: Advanced setup and release channels

• Anthropic: Claude Code CLI reference

• Anthropic: Claude Code changelog

• GitHub issue 89360: Claude Code 2.1.243 segmentation fault

• GitHub issue 89334: allocator interposition and free(NULL) reproduction

• GitHub issue 89366: deterministic newlocale startup crash

• GitHub issue 89377: CachyOS 2.1.243 crash signature

• GitHub issue 89389: exported allocator symbol comparison

• Reddit: Claude Code 2.1.243 may core dump on Linux

• Aident Loadout setup

Refresh this guide when Anthropic releases a fixed build, changes the stable or latest channel behavior, closes the canonical issue, or the reported crash signature changes.