[BUG] Claude Code on the Web: Git LFS not supported — proxy rejects LFS batch API with "invalid git path"
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 claiming it was fixed, but it was not: https://github.com/anthropics/claude-code/issues/57687
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.
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
- Create a repository that uses Git LFS (e.g. tracking .pdf or .pkl files via .gitattributes)
- Start a Claude Code web session on that repository
- Run git lfs install && git lfs pull
- Observe: 502 error with "invalid git path"
- The LFS-tracked files remain as ~130-byte text pointer stubs instead of actual binary content
Claude Model
None
Is this a regression?
No, this never worked
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
@omid-ant here's a new bug for tracking since you closed the other one.
cc @aunitt @JJC1138 @mikewirth @cvdub @ezheidtmann @hakon-j-d-johnsen
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗