[BUG] Repository cloned with stale capitalized URL despite lowercase name in session

Resolved 💬 1 comment Opened Jun 6, 2026 by Dansan-Dev Closed Jul 13, 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 a GitHub repository has been renamed to lowercase and is added to a Claude Code cloud session using the current lowercase name, the session still clones it using the old capitalized URL format via the direct Anthropic API proxy. The clone succeeds but pulls an outdated version of the repo — in this case, missing many months of commits. Additionally, the proxy URL used fails authentication, making git fetch and git pull unusable for the rest of the session, so there is no way to get up to date without a manual workaround.

A second repo in the same session that was never renamed clones correctly via the local proxy (127.0.0.1:41365) and works fine — so the issue is specific to repos that were previously registered under a different casing.

What Should Happen?

The repo should be cloned via the local git proxy using the current name as shown in the session config, e.g.:
http://local_proxy@127.0.0.1:41365/git/myorg/my-repo

Error Messages/Logs

Steps to Reproduce

Add a GitHub repo to a Claude Code cloud session (e.g. myorg/My-Repo)
Rename the repo on GitHub to lowercase (myorg/my-repo)
Update the session configuration to use the new lowercase name
Start a new cloud session — the repo is cloned with the old capitalized proxy URL and git fetch fails

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.42

Platform

Anthropic API

Operating System

Other

Terminal/Shell

Other

Additional Information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗