[BUG] Remote session (ultraplan) receives wrong project context

Preflight Checklist

• [x] Searched existing issues
• [x] Single bug report
• [x] Using latest version

What's Wrong?

When running /ultraplan (which spawns a remote session via RemoteTrigger at claude.ai/code), the remote session receives the wrong project context.

I was working in project A, but the remote session identified the workspace as a completely different project B — a project I had used ultraplan with in a previous session. The remote agent reported:

현재 워크스페이스(/home/user/repo)는 [Project B]로, 말씀하신 프로젝트와는 다른 프로젝트입니다.

The remote sandbox path /home/user/repo appears to have stale or misrouted project context from a prior ultraplan session on a different project.

What Should Happen?

The remote session should receive the correct project context matching the local session's current working directory and project. When I run /ultraplan from project A, the remote agent should understand it's working on project A, not a previously used project B.

Error Messages/Logs

Remote agent incorrectly identified project as "Project B" instead of "Project A"
The local session was correctly registered under Project A's path.

Steps to Reproduce

1. Open Claude Code in project A and run /ultraplan — remote session correctly uses project A context.
2. Close or finish that session.
3. Open Claude Code in project B and run /ultraplan.
4. The remote session may receive project A's context instead of project B's.

Claude Model

Opus

Is this a regression?

I don't know

Claude Code Version

2.1.92 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

• The previous ultraplan session for Project B was stored under the correct project-specific path in ~/.claude/projects/.
• The current local session was also correctly registered under Project A's path in ~/.claude/sessions/.
• The issue suggests RemoteTrigger may be reusing or leaking project context across sessions/projects.

---

Note: This replaces #44637, which was closed because its edit history contained sensitive local paths.