claude-code - 💡(How to fix) Fix Remote agent (Ultraplan) reports repo is empty on recently-transferred private org repo [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#45022Fetched 2026-04-09 08:15:09
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Timeline (top)
labeled ×2commented ×1
RAW_BUFFERClick to expand / collapse

Bug Description

Remote agents (specifically Ultraplan / /ultraplan) consistently report that the repository is empty when attempting to clone and analyze it. The repo is a private repo that was recently transferred to a GitHub organization.

Environment

  • Claude Code CLI (local terminal)
  • Repo: private, hosted under a GitHub Organization
  • Claude GitHub App installed on the org with repository_selection: "all" and contents: write permission
  • App installed ~20 hours before the issue was observed

Steps to Reproduce

  1. Transfer a private repo from a personal GitHub account to a GitHub Organization
  2. Install the Claude GitHub App on the organization (all repos, full permissions)
  3. Confirm the repo is accessible via gh api (commits visible, size > 0, push confirmed)
  4. Run /ultraplan from Claude Code CLI
  5. Remote agent reports the repo is empty

What I Expected

The remote agent should clone the repo and see all files/commits.

What Actually Happened

The remote agent consistently says the repo is empty. Tried multiple times with the same result.

Diagnostics

Verified locally that:

  • git push --dry-run → "Everything up-to-date"
  • gh api /repos/{owner}/{repo} → size: 111837, default_branch: main, recent commits visible
  • gh api /orgs/{org}/installations → Claude app (app_slug: "claude") installed with contents:write, repository_selection: all
  • The repo has 100+ commits and is ~112MB

Possible Cause

The repo was recently transferred from a personal account to a GitHub Organization. The Claude GitHub App was installed on the org shortly after the transfer. Suspect either:

  1. GitHub app token propagation delay after org transfer
  2. The remote agent is caching/using the old pre-transfer repo path
  3. Redirect from old personal account path isn't being followed by the clone mechanism

extent analysis

TL;DR

The issue can likely be resolved by waiting for a longer period to allow GitHub app token propagation or by re-installing the Claude GitHub App on the organization.

Guidance

  • Verify the GitHub app installation and permissions to ensure they are correctly set up for the newly transferred repository.
  • Check the Claude GitHub App's documentation for any specific instructions or recommendations for handling repository transfers within an organization.
  • Attempt to re-install the Claude GitHub App on the organization to potentially reset any cached settings or tokens.
  • Consider waiting for a longer period (e.g., 24-48 hours) to see if the issue resolves itself due to token propagation delays.

Example

No specific code snippet is applicable in this case, as the issue appears to be related to GitHub app configuration and repository permissions.

Notes

The exact cause of the issue is uncertain, but it is likely related to the recent repository transfer and GitHub app installation. The provided diagnostics suggest that the repository is accessible via the GitHub API, but the remote agent is still reporting it as empty.

Recommendation

Apply workaround: Re-install the Claude GitHub App on the organization to potentially resolve any token propagation or caching issues. This is a relatively safe and straightforward step that may help resolve the issue without requiring significant changes or upgrades.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING