Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix /config freezes on second invocation in same session [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#46873•Fetched 2026-04-12 13:30:48
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
oavelino39oavelino39
Participants
github-actions[bot]github-actions[bot]oavelino39oavelino39
Timeline (top)
labeled ×3closed ×1commented ×1cross-referenced ×1
RAW_BUFFERClick to expand / collapse

Bug Description

Running /config for the second time in the same session causes the TUI to freeze. The config dialog renders but becomes completely unresponsive — no keyboard input is accepted, and the dialog cannot be dismissed.

Steps to Reproduce

  1. Start Claude Code (claude)
  2. Type /config — the config dialog opens normally
  3. Dismiss the dialog (press Esc or select a setting)
  4. Type /config again — the dialog renders but freezes

Reproduced 5+ times consistently.

Environment

  • Claude Code: v2.1.104
  • macOS: 26.4.1 (Build 25E253), Apple Silicon (arm64)
  • Terminal: Warp v0.2026.04.08.08.36.stable_02
  • Node.js: v24.13.1
  • Shell: zsh

Diagnostic Isolation

Systematically ruled out user-side causes:

EliminatedMethodResult
Custom statusLine commandRemoved from settings.json, restartedStill freezes
Plugins (17 enabled → 0)Set all enabledPlugins to false, restartedStill freezes
Adaptive wrapper scriptBypassed via CC_WRAPPER_DISABLE=1, direct binary invocationStill freezes
Hooks (PreToolUse/PostToolUse)Hooks only fire on tool use, not slash commandsN/A (ruled out by design)

The freeze occurs with a completely default config and direct binary invocation, confirming it is an internal TUI bug.

Expected Behavior

/config should open and dismiss cleanly on every invocation within a session.

Likely Cause

The config dialog's TUI component (likely Ink-based) does not fully release terminal state (raw mode, signal handlers, or React component unmount cleanup) after the first dismissal, causing the second invocation to deadlock on terminal I/O.

Screenshot

The second /config invocation renders the settings list but accepts no input:

<img width="1154" height="732" alt="Image" src="https://github.com/user-attachments/assets/076e349a-c8de-4f71-95b0-9c385bdd6fab" />

(Config dialog visible but unresponsive on second invocation)

extent analysis

TL;DR

The issue can be potentially resolved by ensuring the TUI component properly releases terminal state after the config dialog is dismissed.

Guidance

  • Investigate the Ink-based TUI component's cleanup process to verify that it correctly releases terminal state, including raw mode and signal handlers, after the config dialog is dismissed.
  • Check the React component unmount process to ensure it is properly cleaning up after the first invocation of the config dialog.
  • Review the terminal I/O handling to identify potential deadlocks that may occur during the second invocation of the config dialog.
  • Consider adding logging or debugging statements to the TUI component to track its state and identify where the freeze occurs.

Example

No code example is provided as the issue lacks specific code details.

Notes

The provided information suggests an internal TUI bug, but without access to the codebase, it's challenging to provide a definitive solution. The suggestions above are based on the likely cause described in the issue.

Recommendation

Apply a workaround by modifying the TUI component to ensure proper cleanup after the config dialog is dismissed, as the root cause appears to be related to the component's failure to release terminal state.

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…
#configuration error#environment variable#network issue#logging issue#authentication 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