Back to Signal Feed
CodeTracked since May 18, 2026

Suppress Windows Git Bash hook stderr noise in claude-mem path resolver

The patch adds `2>/dev/null` to the producer block in claude-mem’s plugin-path resolver shell snippets used by hook launchers, preventing stderr from the broken-pipe write path from surfacing as false hook failures while keeping resolver fallback order, early-break behavior, and exit semantics unchanged.

claude-memWindows MSYS Git Bashplugin-path resolverplugin/hooks/hooks.json

What Happened

  • The patch adds `2>/dev/null` to the producer block in claude-mem’s plugin-path resolver shell snippets used by hook launchers, preventing stderr from the broken-pipe write path from surfacing as false hook failures while keeping resolver fallback order, early-break behavior, and exit semantics unchanged.
  • The patch adds `2>/dev/null` to the producer block in claude-mem’s plugin-path resolver shell snippets used by hook launchers, preventing stderr from the broken-pipe write path from surfacing as false hook failures while keeping resolver fallback order, early-break behavior, and exit semantics unchanged.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Introduced a minimal, behavior-preserving shell fix in the hook resolver command pipeline so that producer stderr is swallowed at source, stopping environment-specific pipe-write errors from leaking into Claude Code’s hook runner output.

Why Track This

Why It Matters

Windows users of claude-mem now get clean hook execution in sessions (especially Stop hooks) instead of noisy `printf: write error` messages and misleading non-blocking hook-failure alerts, so operators are less likely to treat a healthy session as broken. The change is a low-risk stderr-suppression fix for the existing `while ... read ...; do ... break` resolver pattern; follow up should watch for any newly added resolver snippets that still emit post-break stderr under the same shell behavior, which could reintroduce false failure signals.

Impact

Windows users of claude-mem now get clean hook execution in sessions (especially Stop hooks) instead of noisy `printf: write error` messages and misleading non-blocking hook-failure alerts, so operators are less likely to treat a healthy session as broken. The change is a low-risk stderr-suppression fix for the existing `while ... read ...; do ... break` resolver pattern; follow up should watch for any newly added resolver snippets that still emit post-break stderr under the same shell behavior, which could reintroduce false failure signals.

What To Watch Next

  • Watch whether claude-mem becomes a repeated pattern.
  • Track follow-up changes around Model Context Protocol.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: windows_git_bash_shell_version_regression, new_resolver_snippets_without_stderr_guard.
Open Topic TimelineOpen Technical EventOpen Original Sourcewindows_git_bash_shell_version_regression / new_resolver_snippets_without_stderr_guard / false_positive_hook_failure_regression

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

thedotmack/claude-mem PR #2526: fix(hooks): silence Windows Git Bash EPIPE/EACCES on plugin-path resolver

A cross-platform plugin-path resolver in hook scripts now redirects block-level stderr to `/dev/null`, eliminating `printf: write error: Permission denied` on Windows MSYS/Git Bash when the loop consumer exits early.