[BUG] /ultraplan always routes to wrong workspace, plan agent gets no context

Resolved 💬 2 comments Opened Apr 7, 2026 by shikyo13 Closed Apr 7, 2026

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 /ultraplan from the project root in CLI, the remote plan agent consistently resolves to the wrong workspace. The plan files and project context never reach the agent, so it operates blind.

What Should Happen?

Plan agent should inherit the current project workspace and have access to all plan files and context. Or require a github repo creation and provide that to the remote agent.

This is especially frustrating since Claude Code itself recommends /ultraplan as a workflow. Shouldn't require manual workarounds for a suggested feature.

Error Messages/Logs

Steps to Reproduce

  • Launch Claude Code CLI in a project root (where .claude/ exists)
  • Run /ultraplan
  • Plan agent spawns but has no access to plan files or project context
  • Always routes to the same incorrect workspace (deterministic, not intermittent)

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.92

Platform

Other

Operating System

macOS

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗