[BUG] ralph-wiggum stop hook triggered in separate session

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?

Two CC agents were working concurrently in two completely separate terminals (no Tmux or similar). Ralph-wiggum plugin working in one (first time running it), second agent was running in another area of code, unrelated task.

When the second agent stopped working, ralph-wiggum stop hook triggered, feeding command and taking over session. /Feedback sent in CC, also frantic Reddit thread created here, with text snippet.

What Should Happen?

There's no stop hook setup in settings.json or settings.local.json, seems like ralph-wiggum permissions are too broad?

Error Messages/Logs

Steps to Reproduce

1. Two agents running concurrently.
2. Set one to loop with ralph-wiggum (better give it a light task)
3. Wait for evidence - I couldn't reproduce it; early iterations didn't consistently takeover the other session.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Version: 2.0.75

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Running WSL Debian, both agents in WSL.