### Preflight Checklist - [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) 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 tool finishes its work, it can't execute the stop function. Logs provided. Started to happen right after upgrading. ### What Should Happen? It shou

[BUG] Tool always fail to execute stop hook

Status Fixed / completed

Reported on v2.1.4

Maintainer reply None cached

Activity 8 comments · opened Jan 13, 2026 · closed Feb 2, 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 tool finishes its work, it can't execute the stop function. Logs provided. Started to happen right after upgrading.

What Should Happen?

It should stop fluently after work's done.

Error Messages/Logs

● Ran 1 stop hook
  ⎿  command: "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" claude-judge-continuation.sh
  ⎿  Stop hook error: Failed with non-blocking status code: No stderr output

Steps to Reproduce

Ran claude prompt
Claude handles the work
When work's done it should stop but I wait for a few seconds (nearly 1 min) and it doesn't stop, displaying error message.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.4

Claude Code Version

2.1.5

Platform

Google Vertex AI

Operating System

Other Linux

Terminal/Shell

Other

Additional Information

Using Cachyos, installed with bun package manager

View original on GitHub ↗

8 Comments

dnsliu · 7 months ago

+1 here

lukasmalkmus · 7 months ago

Yes, +1. Even on 2.1.12.

wang-silas · 7 months ago

Mine error is a little bit different:

Ran 1 stop hook
  ⎿  Stop hook error: Failed with non-blocking status code: <3>WSL (26110 - Relay) ERROR:
  CreateProcessCommon:798: execvpe(/bin/bash) failed: No such file or directory

zk020106 · 7 months ago

Mine error is a little bit different:

● Ran 1 stop hook

⎿ Stop hook error: Failed with non-blocking status code: No stderr output

wenbo97 · 7 months ago

Same, mark this issue here.

Ray0907 · 7 months ago

@rzgrozt
The error message shows run-hook.cmd claude-judge-continuation.sh - do you
have the double-shot-latte plugin installed?

If so, I encountered the same issue. The run-hook.cmd polyglot wrapper can't
be executed directly on Linux/macOS since there's no shebang line.

Uninstall to fix:
``bash claude /plugin uninstall double-shot-latte@superpowers-marketplace``
I've submitted a fix: https://github.com/obra/double-shot-latte/pull/11

EmanuelFaria · 7 months ago

+1 Experiencing this on v2.1.29 (macOS Darwin 25.3.0, Homebrew Cask install)

Error:

Ran 6 stop hooks
  ⎿  Stop hook error: Failed with non-blocking status code: No stderr output

Investigation findings:

All 6 stop hooks return exit code 0 when tested individually
All hooks output valid JSON ({} or {"continue": true})
No stderr output (which is correct behavior)
Error persists across fresh sessions
Hooks work correctly - the error is purely cosmetic

Tested conditions:

# All pass with exit 0 and valid JSON
echo '{"stop_reason":"end_turn"}' | ./hook.sh  # Exit 0, outputs {}
echo '' | ./hook.sh                             # Exit 0, outputs {}
./hook.sh                                       # Exit 0, outputs {}

The error message "No stderr output" is misleading - stderr should be empty for successful hooks. The issue appears to be in Claude Code's hook result interpretation, not in the hooks themselves.

This was also reported in the now-closed #10463. A comment there claimed it was fixed in "v2.2.12" but that version doesn't exist - latest release is v2.1.29.

github-actions[bot] · 6 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.