[BUG] Ralph Wiggum plugin sessions bleed across Claude Code sessions

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?

Hi team,

I’m running into session bleed with the Ralph Wiggum plugin.

If I start a long task with Ralph in one Claude Code session, then open another session to work on something else, the second session is often affected by Ralph. It behaves as if Ralph is still tied to the first session and continues working on or referencing that original task.

This makes it hard to work in parallel, since actions and output can show up in the wrong session.

What Should Happen?

Expected behavior is full isolation: Ralph should only act within the session where it was started.

Error Messages/Logs

Steps to Reproduce

1. Open Claude Code Session A
2. Start a long running task using the Ralph Wiggum plugin
3. While that task is still running, open Claude Code Session B
4. Start unrelated work in Session B
5. Notice Ralph appearing active in Session B and continuing or referencing work from Session A

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.2 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

WSL (Windows Subsystem for Linux)

Additional Information

_No response_