Unable to grant repository access to third-party app

[starskipper]

Select Topic Area

Question

Body

I'm trying to use Google Jules and can't get it to to see my repo. I've gone through their setup documentation meticulously, troubleshooted, and retried from scratch multiple times, and have come to the conclusion that the problem is on the GitHub side of my setup, not the Jules side.

In my Settings page, under Integrations->Applications, it says:

• Developer Settings
  Google Labs Jules
• Permissions
  [Green check mark] Read access to metadata
  [Green check mark] Read and write access to actions, code, issues, pull requests, and workflows
• Repository access
  [Radio option selected] All repositories
  [Radio option unselected] Only select repositories

Despite the above, when Jules attempts to list the repos in my account it gets an empty list.

I've also tried selecting "Only select repositories" rather than "All repositories" then selecting my repo explicitly, but the result is the same.

The repository in question is private, but my understanding is that should be OK. Neither my account nor the repo are part of an organization. Most online resources I've found about similar issues suggest revoking and re-granting access; I've already tried that multiple times.

Is there any other setting or step I may be missing? Should the setting above be sufficient on its own, or is there something else I need to do to make my account and/or repo visible to other apps?

[TylerChen1200]

Might sound a bit odd, but sometimes the simplest things can be the issue. If its installed on the right level then ignore this lol.

If your repo is under a personal account, the app should be installed on your personal account.

If it's under an organization, the app needs to be installed on that organization, at least based on the context provided in the post.

[Hariswar8018]

Sometimes, after switching between "All" and "Selected Repositories," OAuth permissions don’t refresh immediately. Try:

Going to https://github.com/settings/applications

Find Google Labs Jules

Click "Re-authorize" (not just "Revoke")

Wait a few minutes, then retry from the Jules interface

[starskipper]

Sorry I should have specified, but it actually installs itself under "GitHub Apps" and not under "OAuth Apps". So there's no "Re-authorize" button.

[nvmaxim]

Hey! Try this: 1) Completely revoke Jules' access in GitHub Settings - Applications, 2) Log out and back into both GitHub and Jules, 3) Reconnect through Jules' official setup (not manually). If it still doesn't work, test with a new public test repo - if Jules sees that one, your private repo might have special security settings blocking access.

[starskipper]

Thanks for the reply. I tried the complete-revoke loop again, and with a new public test repo, but the Jules UI still doesn't show any repos.

[AmanRai8]

Here’s what to check and try to fix the issue with Google Jules not seeing your private repo:

1. Check App Installation:
   Ensure Google Jules is installed as a GitHub App on your user account (not just OAuth). Go to Settings > Applications > Installed GitHub Apps and confirm it has access to your repo.

2. Verify Permissions:
   The app must have repo (full control) permissions to access private repositories. Your current settings seem fine, but double-check that the authorization token includes these scopes.

3. Try Personal Access Token (PAT):
   If Google Jules supports it, generate a PAT with repo and workflow scopes and configure the app to use it. This often fixes permission issues.

4. Reinstall the App:
   Revoke the current authorization, uninstall Google Jules, then reinstall it, selecting All repositories access during setup.

5. Check Repository Status:
   Make sure the repo isn’t archived or has restrictions that could block access.

6. Contact Support if Needed:
   If you still get an empty list, reach out to Google Jules support—they might have app-specific fixes.

[starskipper]

Thanks for the thorough reply!

1. In the Settings > Applications page it is listed under "Installed GitHub Apps" and "Authorized GitHub Apps", and not listed under "Authorized OAuth Apps".
2. There's no mention of authorization tokens in their docs, and I'm not sure how to check that. Is the fact that it's listed under "Authorized GitHub Apps" sufficient confirmation? Or is there a step missing to also authorize it with a token?
3. I just looked into it, and it doesn't look like they support PAT.
4. Done. Same behavior. :-/
5. Double-checked. The repo is in active use. I also created a brand new public repo in my account, and it can't see that one either.
6. Yup, it looks like that's the only way, maybe it is on their end after all, not mine.

[SruthiProfessionalDev]

If Google Jules isn’t seeing your repo, try removing it from your GitHub settings and connecting it again. Make sure it has access to all your repos or that your specific repo is selected and saved properly. also check that the repo isn’t archived and that you still have full access. If you're using a personal access token, it needs the right permissions like repo and permissions like repo a workflow. If it still doesn’t work, try with a public repo to see if the issue is related to it being private.

[haseebnk]

Hi @starskipper 👋

You're right to expect that the “All repositories” permission should allow Jules (or any authorized app) to access your repos — including private ones — as long as the app has the necessary scopes granted.

Here are a few things to double-check:

✅ 1. Ensure the app is OAuth-based and not GitHub App only
OAuth apps use your personal access token and scopes.

GitHub Apps (like Jules) require explicit permission per repo.

So even with "All repositories" selected, GitHub Apps might still not show private repos unless the app has been configured correctly from the developer's side too.

✅ 2. Token scope mismatch
Even though it looks correct in Settings → Applications, go to:

Settings → Developer Settings → Personal Access Tokens (Classic or Fine-grained)

Make sure the token you're using (if any) has:

repo (full access to private repos)

read:org (if repo is under an org)

workflow, admin:repo_hook, etc., depending on what Jules needs.

✅ 3. Jules might use GitHub App authorization flow
If Jules is using the GitHub App model, try:

Going to Settings → Applications → GitHub Apps → Authorized GitHub Apps

Click on Google Labs Jules

Confirm it has access to your specific private repo

Sometimes the permissions page doesn’t immediately reflect the required repo scope until explicitly selected again — even after revoking and re-authorizing.

🛠️ 4. Repo visibility and permissions
Make sure:

The repo has not been archived

You're logged into the correct GitHub account when authorizing

There is no 2FA or SSO blocking repo access (not common for personal accounts, but worth checking)

🔁 Last Resort: Revoke → Re-authenticate cleanly
Revoke Jules from both OAuth and GitHub Apps

Log out from Jules

Log back in, reauthorize Jules carefully, choosing "Only select repositories", and manually pick the target repo

Refresh Jules or retry connecting

Let me know if this helps — if it still fails, the issue may be on Jules’ end or how their app handles GitHub App scopes.

Hope this gets you unblocked!

[schneiderlo]

I have the same issue as described. When looking at the applications on github, I see it on "Installed GitHub Apps" and "Authorized GitHub Apps" but not in the OAuth Apps. I am not sure if I am supposed to do something to get it put in the OAuth part.
Revoking / uninstalling Jules does not help.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[niklasedren]

I'm having the exact same issue.
Did anyone find a solution yet?
Any answer from Jules or GitHub support/dev/engineering teams?