›_ Claude Code Issues
Claude Code Issues / #57687

[BUG] Claude Code on the Web: Git LFS not supported — proxy rejects LFS batch API with "invalid git path"

Status Fixed / completed
Maintainer reply None cached
Activity 13 comments · opened May 9, 2026 · closed May 15, 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?

Git LFS still doesn't work in Claude Code Web. This bug was reported before and closed due to inactivity, but it's not fixed: https://github.com/anthropics/claude-code/issues/25043

Repositories that use Git LFS cannot pull LFS-tracked files
in Claude Code web sessions. The local GitHub proxy
(127.0.0.1) actively rejects the LFS batch API endpoint,
so all LFS-tracked files remain as pointer stubs throughout
the session.

The proxy seems to have a path validation check that
only allows standard git smart HTTP protocol paths. It
rejects the /info/lfs/objects/batch URL pattern with the
error Proxy error: invalid git path.

What Should Happen?
The GitHub proxy should pass through Git LFS batch API
requests (/info/lfs/objects/batch) to GitHub, allowing
git lfs pull to download LFS objects. Repositories using
Git LFS should be fully functional in web sessions.

What Should Happen?

Pulling LFS file should work.

Error Messages/Logs

Steps to Reproduce

$ curl -s -o /dev/null -w "%{http_code}" -X POST
http://127.0.0.1/://.git/info/lfs/objects/batch
502

  1. Create a repository that uses Git LFS (e.g. tracking .pdf or .pkl files via .gitattributes)
  2. Start a Claude Code web session on that repository
  3. Run git lfs install && git lfs pull
  4. Observe: 502 error with "invalid git path"
  5. The LFS-tracked files remain as ~130-byte text pointer stubs instead of actual binary content

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Claude Code Web

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Non-interactive/CI environment

Additional Information

_No response_

View original on GitHub ↗

13 Comments

tomkitewing · 3 months ago

cc @aunitt @JJC1138

tomkitewing · 3 months ago

cc @mikewirth @cvdub @ezheidtmann @hakon-j-d-johnsen

github-actions[bot] · 3 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/25043
  2. https://github.com/anthropics/claude-code/issues/55808
  3. https://github.com/anthropics/claude-code/issues/55803

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

tomkitewing · 3 months ago

Not a duplicate. Those bugs are closed/abandoned and LFS is still unsupported.

aunitt · 3 months ago

Agreed. This does need addressing.

omid-ant · 3 months ago

Fix is going out for this shortly! Let me know if you still see it happening, sorry for the gap here!

tomkitewing · 3 months ago

You're a hero @omid-ant 💪 🎉

JJC1138 · 3 months ago

I just tested and didn't have any success, I'm afraid. Could the feature still be rolling out @omid-ant? Here's what Claude reported:

Here's a useful summary of what I found — feel free to paste this into the issue: ### What's broken 1. git-lfs binary not installed in the container base image. which git-lfs returns nothing on a fresh container. (apt-get install -y git-lfs does succeed, so it's just not preinstalled — and none of the setup scripts (install_powershell.sh, install_dependencies.ps1, init.ps1) reference LFS either.) 2. The local git proxy doesn't handle LFS endpoints. The remote is rewritten to http://local_proxy@127.0.0.1:36901/git/NeverDontPlay/cosmic. After installing git-lfs manually and running git lfs pull, the batch API request fails: `` POST /git/NeverDontPlay/cosmic.git/info/lfs/objects/batch → HTTP 502 Bad Gateway Proxy error: invalid git path ` So even with git-lfs installed, the proxy rejects the /info/lfs/... path. The proxy appears to route only the standard smart-HTTP paths (info/refs, git-upload-pack, etc.) and not the LFS batch / object endpoints. ### Scope of the problem 24 working-tree files are LFS pointers rather than real content: - 13 .png, 7 .blend, 2 .ttf, 1 .otf, 1 .exr - Includes both game assets (props/heart/heart.blend, etc.) and addon assets under addons/gdUnit4/... and addons/dialogue_manager/... ### Environment details that may matter - git version 2.43.0, Ubuntu Noble; git-lfs candidate version 3.4.1-1ubuntu0.3 - Relevant env vars: CCR_TEST_GITPROXY=1, CLAUDE_CODE_PROXY_RESOLVES_HOSTS=true (the second hints the proxy handles host resolution, which may be why direct LFS S3 redirects wouldn't work either) - .gitattributes declares LFS for .blend .png .exr .ttf .psd .otf — config side is fine; it's purely the fetch path that's broken ### Suggested fixes for the engineer - Preinstall git-lfs in the container image (or have it pulled in by the setup scripts). - Teach the local git proxy to forward */info/lfs/objects/batch` and the object download URLs it hands back (or proxy LFS through GitHub's LFS endpoint with the same credentials it's already using for smart-HTTP).
tomkitewing · 3 months ago

I also get 502s when trying to use lfs ☹️

tomkitewing · 3 months ago

@omid-ant any update on this rollout?

tomkitewing · 3 months ago

New bug opened since this was closed without fixing the issue: https://github.com/anthropics/claude-code/issues/60593

tomkitewing · 3 months ago

FYI @omid-ant still hasn't gone out.

<img width="671" height="214" alt="Image" src="https://github.com/user-attachments/assets/2fc4c679-beee-4580-8191-58a19eb702b1" />

github-actions[bot] · 1 month ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.

Related Claude Code issues

Matched on shared title terms, labels, topic and reported release — ranked so issues with real discussion come first.

Browse by topic

This issue appears in the ranked issue list on this topic page, alongside a backlog trend for the whole topic.

Network & proxy errors →

Browse all Claude Code issue topics →