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

Resolved 💬 3 comments Opened Feb 11, 2026 by aunitt Closed Mar 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?

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:<proxy-port>/<org>/<repo>.git/info/lfs/objects/batch
502

Response body: Proxy error: invalid git path

  1. Create a repository that uses Git LFS (e.g. tracking

*.pdf or *.pkl files via .gitattributes)

  1. Start a Claude Code web session on that repository
  2. Run git lfs install && git lfs pull
  3. Observe: 502 error with "invalid git path"
  4. 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

Other

Terminal/Shell

Other

Additional Information

_No response_

View original on GitHub ↗

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