claude-code - 💡(How to fix) Fix GitHub repository access check fails for CCR routines after re-authorization

Official PRs (…)
ON THIS PAGE

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…
RAW_BUFFERClick to expand / collapse

Bug

When creating a scheduled remote agent (CCR) routine with a GitHub repo source, the routine fails with:

GitHub repository access check failed — re-authorize GitHub in settings reason: github_repo_access_denied

Steps to reproduce

  1. Create a CCR routine with a git_repository source pointing to a valid GitHub repo
  2. Connect GitHub in claude.ai settings (OAuth flow completed successfully)
  3. Attempt to run the routine via API or claude.ai/code/routines

Expected behavior

Routine clones the repo and runs successfully.

Actual behavior

Fails immediately with github_repo_access_denied before the session even starts.

Notes

  • Repo is public (visibility is not the issue)
  • GitHub was re-authorized multiple times
  • Routines without a repo source work fine
  • Account is newly created (May 2026)

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…

FAQ

Expected behavior

Routine clones the repo and runs successfully.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING