[Bug] Stop hook hangs for 1-2 minutes after response completion, blocking subsequent messages

Resolved 💬 3 comments Opened Apr 21, 2026 by osmos-harsh Closed Apr 25, 2026

Stop hook keeps running for 1-2 minutes after response completes, blocking next message

Environment

  • Platform: macOS (darwin)
  • Terminal: VS Code integrated terminal
  • Claude Code Version: 2.1.116
  • Feedback Id: f9d1b007-7e34-4e43-ad62-ae8c91ee9165

---

Bug Description

After Claude Code finishes generating a response, the UI shows "running stop hook" and does not accept the next user message for 1–2 minutes until the hook completes. This blocks the entire interaction flow and appears to be a recent regression.

Steps to Reproduce

  1. Run Claude Code in VS Code terminal on macOS
  2. Send a message and wait for the response to complete
  3. Observe that the input remains blocked with "running stop hook" shown
  4. Wait ~1–2 minutes — input becomes available only after the hook finishes

Expected Behavior

Input should be accepted immediately (or near-immediately) after the response is complete. Stop hooks should not block the UI for extended periods.

Actual Behavior

UI is blocked for 1–2 minutes post-response due to a hanging stop hook.

---

Errors from Logs

[
  {
    "error": "Error: EISDIR: illegal operation on a directory, read '/path/to/project/accountDrawer'",
    "timestamp": "2026-04-21T08:24:02.024Z"
  },
  {
    "error": "Error: Request was aborted.",
    "timestamp": "2026-04-21T09:25:10.884Z"
  },
  {
    "error": "Error: Request was aborted.",
    "timestamp": "2026-04-21T09:40:12.884Z"
  },
  {
    "error": "Error: 429 {\"type\":\"error\",\"error\":{\"type\":\"rate_limit_error\",\"message\":\"This request would exceed your account's rate limit. Please try again later.\"},\"request_id\":\"req_REDACTED\"}",
    "timestamp": "2026-04-21T09:59:18.884Z"
  },
  {
    "error": "AxiosError: timeout of 5000ms exceeded",
    "timestamp": "2026-04-21T10:05:21.884Z"
  }
]

---

Notes

  • The EISDIR error suggests Claude Code may be attempting to read a directory as a file, which could be triggering the hanging hook behavior
  • Rate limit and abort errors may be related to the hook retrying aggressively before timing out
  • Issue appears to have started with a recent version update

View original on GitHub ↗

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