[FEATURE] Give CC Web access to whitelisted private repositories

[virtualritz]

Preflight Checklist

• I have searched existing requests and this feature hasn't been requested yet
• This is a single feature request (not multiple features)

Problem Statement

TLDR; I use CC Web to work on private repo foo and this in term depends on private repo bar (which may depend on baz, etc., etc.). All three, foo, bar & baz are whitelisted for CC Web.

I am on the CC Web preview. I have private GH repos I like CC Web to work on. This is Rust code. They in term have private repo. dependencies. I gave all CC Web access to all of them. Dep. resolution via cargo fails with 401: access denied.

CC, when asked, has this to say:

Ah, you've identified a key limitation! The GitHub App authentication that Claude Code uses for repository operations (reading files, making commits, pushing) is separate from the git credentials that cargo uses when fetching dependencies.

Here's what's happening:

The Problem

• Claude Code's GitHub App can access your private foo repository ✅
• When cargo tries to fetch dependencies, it uses the system's git credentials ❌
• The system doesn't have access to barbecause it's private and there are no credentials configured

Cross-Repo Dependencies Don't Work This Way
Unfortunately, cargo's git dependency fetching doesn't inherit Claude Code's authentication. It's a separate process that needs its own credentials.

Proposed Solution

Make all privat repos that have been whitelisted accessible from CC Web sessions.

Alternative Solutions

The only solution I see is cloning repos into the repo in questions. But when these have deps themselves that are private repos, this become infeasible very quicly.
Terragonlabs suffered the same issue -- they fixed it within a day after I reported it.

Priority

Critical - Blocking my work

Feature Category

Other

Use Case Example

No response

Additional Context

No response

[github-actions]

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

[zflamig]

+1 this, would be a great future to have!

[leith-bartrich]

This is still an issue. A private repo as a submod of another private repo cannot be checked out even though it's on the allow list. Nor does Claude Code on the web seem to think it could use any tools or creds to authenticate to work around.

[github-actions]

Closing for now — inactive for too long. Please open a new issue if this is still relevant.