/ultraplan reuses stale remote session from a different project, mixing unrelated context

Bug

/ultraplan opens a previous remote session from a completely different project instead of creating a new one.

Steps to reproduce

1. Use /ultraplan in Project A (e.g., a work project)
2. Archive/close that session
3. Switch to Project B (e.g., a personal project in a different directory)
4. Run /ultraplan <prompt> for Project B
5. The remote session that opens is the old Project A session, not a new one

Expected behavior

Each /ultraplan invocation should create a fresh remote session scoped to the current working directory/project.

Actual behavior

• The old session from a different project is reopened
• Project A's context (files, conversation history) bleeds into Project B
• The plan generated references the wrong codebase

Impact

• Data/context leakage between projects — work project context appeared in a personal project session
• Makes /ultraplan unreliable for multi-project workflows
• Users may unknowingly generate plans based on wrong project context

Environment

• Claude Code CLI
• macOS