[BUG] Session context leaks between projects when running multiple WSL terminals with 'claude -c'

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 running Claude Code in multiple WSL terminals simultaneously, the session context
from Project A appears when executing claude -c in Project B's directory.

## Steps to Reproduce

1. Open WSL Terminal 1, navigate to Project A directory
2. Run claude and have a conversation about Project A
3. Open WSL Terminal 2, navigate to Project B directory
4. Run claude -c (continue session)
5. Unexpected: Project A's context/conversation appears instead of Project B's

## Expected Behavior

Each project directory should have isolated session context. Running claude -c should
only continue the session relevant to the current working directory.

## Environment

• OS: WSL2 (Ubuntu on Windows)
• Claude Code: Latest version
• Multiple terminals: Yes, running concurrently

## Possible Cause

Session state stored in ~/.claude/ may not properly isolate sessions by working
directory when multiple terminals are active simultaneously.

## Workaround

Use claude (new session) instead of claude -c (continue) when switching between
projects, or avoid running Claude Code in multiple terminals concurrently.

What Should Happen?

Debug

Error Messages/Logs

Steps to Reproduce

1. Open WSL Terminal 1, navigate to Project A directory
2. Run claude and have a conversation about Project A
3. Open WSL Terminal 2, navigate to Project B directory
4. Run claude -c (continue session)
5. Unexpected: Project A's context/conversation appears instead of Project B's

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.17

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

WSL (Windows Subsystem for Linux)

Additional Information

_No response_