ultraplan remote session executes against wrong repo

Summary

Approved an /ultraplan remote session from inside one repo (JonFermin/vibecoding, on branch master) and the resulting PR was opened against a completely different private repo on my account

Repro

1. cd into repo A (vibecoding) — confirmed via git remote -v that origin points to github.com:JonFermin/vibecoding.git.
2. Run /ultraplan plan - explore the updates to claude code, opus 4.7 capabilites, etc. to improve this repo.
3. Remote session link is produced: https://claude.ai/code/session_01DirK6JmueWpSDQzdp7SAZ1.
4. Approve the plan in the web UI.
5. Remote session runs, opens a PR — but the PR lands on private repo, not on vibecoding.

The task prompt explicitly said "improve this repo," and the session was initiated from within vibecoding, so the target should unambiguously have been vibecoding.

Expected

Remote /ultraplan session should execute against and open the PR on the same repo the session was initiated from (the CWD's git origin).

Actual

PR opened against an unrelated repo on the same GitHub account. No issue was filed, no warning, no indication the target was different from the initiating repo.

Environment

• Claude Code CLI on Windows 10 (bash)
• Model: Opus 4.7 (1M context) — claude-opus-4-7[1m]
• Initiated from: C:\Users\honsf\DEVELOP\vibecoding
• Session: session_01DirK6JmueWpSDQzdp7SAZ1

Impact

Silently operating on the wrong repo is a significant trust issue for remote/autonomous sessions, if I hadn't noticed, the unrelated repo would have been polluted with an off-topic PR, and on a less obvious mismatch it could overwrite real work.