[BUG] /config command causes terminal to freeze/hang when invoked a second time consecutively (v2.1.104)

Resolved 💬 3 comments Opened Apr 14, 2026 by liuziyuan Closed Apr 17, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

When using the /config slash command in Claude Code, invoking it a second consecutive time within the same session causes the entire terminal to become
completely unresponsive. No input is accepted after this point — the session is effectively frozen and must be force-terminated by closing the terminal
window or killing the process externally.

This only occurs on the second (or subsequent) invocation of /config. The first call works normally. There is no error message, no timeout, and no way to
recover without restarting the session.

What Should Happen?

The /config command should open the configuration interface successfully on every invocation, regardless of how many times it has been used in the current
session. After closing the config menu, it should be possible to invoke /config again without any side effects or degraded behavior.

Error Messages/Logs

Steps to Reproduce

<img width="1048" height="962" alt="Image" src="https://github.com/user-attachments/assets/2dfe453a-fea2-44fb-a00f-56edd3a192b6" />

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.104

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗