Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] ultraplan sent to wrong codebase [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#47916•Fetched 2026-04-15 06:38:43
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
oeuvrefilmoeuvrefilm
Participants
github-actions[bot]github-actions[bot]oeuvrefilmoeuvrefilm
Timeline (top)
labeled ×3commented ×1

Error Message

Error Messages/Logs

Root Cause

The debug log is empty — logging was just enabled, so there's no historical data to trace the root cause.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

What happened: You launched Claude Code from /Users/andrew/Play Lit on your Mac, but this remote session was provisioned with /home/user/repo as its working directory — which contains your Oeuvre project, not Play Lit. The remote environment doesn't have access to your local Mac filesystem, so it worked with the only repo it could find.

Why: This is a remote session workspace resolution issue. When Claude Code on the web spins up a remote container, it appears to have cloned/mounted the wrong repository. The git config at /home/user/repo/.git/config shows no remote URL, so it's unclear how the repo was provisioned, but it's definitely the Oeuvre project (package.json says "name": "oeuvre"), not Play Lit.

The debug log is empty — logging was just enabled, so there's no historical data to trace the root cause.

To report this bug to Anthropic:

Go to https://github.com/anthropics/claude-code/issues File a new issue with: Title: "Remote session clones wrong repository — workspace mismatch" Body: You launched Claude Code from /Users/andrew/Play Lit but the remote session was provisioned with the Oeuvre project (/home/user/repo) instead. The session's primary working directory was set to /home/user and the repo at /home/user/repo is the wrong project entirely. No git remote was configured on the cloned repo. Session ID: b467099d-5b7f-4d7a-aaff-166e506d269e. To get unblocked now: Run Claude Code locally in your terminal from the /Users/andrew/Play Lit directory — that will use the correct project directly from your filesystem.

1 step

What Should Happen?

Claude should use the directory that Claude Code CLI is running in

Error Messages/Logs

Steps to Reproduce

?

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.105

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Cursor

Additional Information

No response

extent analysis

TL;DR

Run Claude Code locally in the terminal from the correct project directory to use the intended project.

Guidance

  • To resolve the issue immediately, run Claude Code locally from the /Users/andrew/Play Lit directory as suggested.
  • Verify that the local run uses the correct project by checking the working directory and project files.
  • When running Claude Code locally, ensure you are in the correct directory before launching to avoid workspace resolution issues.
  • Consider configuring the remote session to use the correct repository or investigating why the wrong repository is being cloned.

Example

No code snippet is provided as the issue does not require a code-level fix but rather a change in how Claude Code is launched.

Notes

The provided debug log is empty, which limits the ability to trace the root cause. Enabling logging before the issue occurs may help in diagnosing similar problems in the future.

Recommendation

Apply the workaround by running Claude Code locally from the correct project directory, as this allows for immediate use of the intended project without waiting for a potential fix for the remote session workspace resolution issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#environment setup#docker error#permission error#memory optimization

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING