Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Claude Code CLI v2.1.107 exits silently after brief idle — new regression, macOS [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#48069•Fetched 2026-04-15 06:34:08
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
landongwlandongw
Participants
github-actions[bot]github-actions[bot]landongwlandongw
Timeline (top)
labeled ×5commented ×1

Error Message

  1. No error message, no stack trace
RAW_BUFFERClick to expand / collapse

Bug Description

Claude Code CLI (v2.1.108, macOS Darwin 25.3.0) silently exits mid-session. This is a NEW regression — started around April 13-14, 2026 and was not happening before.

Key symptom: It happens while actively typing. This is NOT an idle timeout and NOT a permission prompt issue. The session drops to shell with a resume link while the user is in the middle of typing a response.

It also happens:

  • While reading Claude's output
  • While a permission prompt is waiting
  • While background agents/tool calls are running
  • After 30-60 seconds of not typing

Approximately 10+ crashes in a single hour-long session, making productive work impossible.

Environment

  • Claude Code version: 2.1.108 (auto-updates aggressively, cannot be pinned to older version)
  • OS: macOS Darwin 25.3.0
  • Shell: zsh
  • Terminal: macOS Terminal.app
  • Model: Opus 4.6 (1M context)
  • MCP servers configured: Atlassian, Slack, Gmail, Notion

Auto-Update Prevents Version Pinning

Attempted to rollback to v2.1.104 by:

  1. ln -sf .../2.1.104 .../claude — auto-updater reverts the symlink
  2. Deleting 2.1.108 binary — auto-updater re-downloads it
  3. Renaming to .disabled — auto-updater ignores it and re-downloads

There is no way to pin to an older version to test if this is a regression in .107/.108 vs .104.

Reproduction

  1. Run claude in terminal
  2. Start any conversation
  3. Session will exit within 1-5 minutes, often while actively typing
  4. Output: Resume this session with: claude --resume <id>
  5. No error message, no stack trace

Expected Behavior

Session should remain active indefinitely during interactive use.

Impact

Severe. 10+ crashes per hour. Multi-step work is impossible. Each crash requires resume, context recovery, and re-establishing state. An hour of work produces 10 minutes of actual progress.

Related Issues

  • #23092 — Desktop app 300s idle timeout
  • #24997 — Silent session exits with resume link
  • #6691 — Unexpected terminal exit
  • #33010 — Unexpected exit on Windows ARM

extent analysis

TL;DR

The most likely fix or workaround is to investigate and potentially disable the auto-update feature to pin the version to a previous stable release, such as v2.1.104, to mitigate the silent session exits.

Guidance

  • Investigate the auto-update mechanism to understand how it can be temporarily disabled or configured to use a specific version, allowing for testing of previous versions like v2.1.104 to confirm if the issue is a regression.
  • Attempt to reproduce the issue with different models or configurations to see if the problem is specific to the Opus 4.6 model or the MCP servers configured.
  • Review related issues (#23092, #24997, #6691, #33010) to see if any of them provide insights or workarounds that could apply to this situation.
  • Consider reaching out to the development team or support for assistance in disabling auto-updates or gaining access to a version that can be pinned for testing.

Example

No specific code snippet can be provided without more details on the internal workings of the Claude Code CLI or its configuration files. However, understanding how to manage or bypass the auto-update feature could involve modifying configuration files or environment variables, if such options exist.

Notes

The inability to pin a version due to aggressive auto-updates complicates troubleshooting and potential mitigation strategies. The fact that this is a new regression starting around April 13-14, 2026, suggests a recent change in the application or its environment could be the cause.

Recommendation

Apply a workaround by attempting to disable or manage the auto-update feature to test previous versions, as upgrading to a fixed version is not currently an option due to the auto-update mechanism. This approach is chosen because it directly addresses the potential regression introduced in versions after v2.1.104 and may provide a temporary solution until a fixed version is released.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#embedding generation#cache error#pipeline error#runtime error#prompt issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Claude Code CLI v2.1.107 exits silently after brief idle — new regression, macOS [1 comments, 2 participants]