hook bug

[Owen0225]

Description

There is a severe session cross-talk / context bleeding issue when running multiple instances of Claude Code and Codex simultaneously.

Even though the instances are running in entirely separate projects and distinct terminal sessions, the text from Claude's plan or execution context bleeds into Codex instances. Additionally, this cross-talk also occurs between multiple independent Claude sessions (e.g., Session A's plan/output appearing unexpectedly in Session B's terminal context).

Steps to Reproduce

1. Open two or more entirely separate projects in different terminal windows.
2. Initialize and run a Claude Code session in Project A, and generate a plan or execute a complex prompt.
3. Simultaneously or sequentially, start a Codex session or another Claude Code session in Project B.
4. Observe that the plan content, terminal context, or pending actions from Project A cross over and display/execute within the session of Project B.

Expected vs Actual Behavior

• Expected: Complete isolation between separate project directories and independent CLI sessions. What happens in Project A should remain strictly hidden from Project B.
• Actual: Context and plan contents bleed back and forth between different active sessions, resulting in corrupted states and incorrect tool execution in the wrong projects.

Environment

• OS: macOS / Linux
• Claude Code version: latest
• Pilot version: latest
• Tier: Solo

Error Output

[No explicit crash logs, but the terminal UI cross-populates data from concurrent sessions]
Example:

Project B (Codex/Claude) output unexpectedly prints plan steps or files belonging to Project A's directory tree.

Checklist

• I am using the latest version of Pilot Shell
• I have searched existing issues to avoid duplicates
• I can reproduce this consistently with the steps above

[maxritter]

@Owen0225 Again many thanks for your observation and this should be fixed now in version 9.2.0. Please reload your shell after the update. Best, Max