Copilot Free enabled, but Copilot CLI reports no subscription and returns HTTP 403

[bihzatturk-maker]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Copilot in GitHub

Body

Hello,

My GitHub account (bihzatturk-maker) shows GitHub Copilot Free, and Copilot CLI is enabled in my settings. However, the CLI reports that I don't currently have a Copilot subscription.

Trying to activate Copilot Free through the CLI fails with HTTP 403 Forbidden. I have successfully signed in again and updated Copilot CLI to version 1.0.98, but the problem persists. The built-in GitHub MCP server also returns HTTP 403, and the model catalog request times out.

I have no organization membership and confirmed that the CLI and browser use the same GitHub account.

Could a GitHub staff member clarify whether this is an account entitlement issue or a known Copilot CLI problem?

Thank you.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[slyyr]

Since you've already signed in again and updated the CLI, I'd focus on distinguishing a local authentication problem from an account-entitlement issue.

First, verify which GitHub account the CLI is authenticated as. Then check the CLI's authentication status and confirm that Copilot CLI access is enabled for that account.

If authentication is correct but the CLI still returns HTTP 403, record the CLI version, the exact error, and whether the failure also affects the built-in MCP server.

Because both services are failing with 403 responses, this may require GitHub to investigate the account's entitlement or service-side access. Reinstalling the CLI repeatedly is unlikely to resolve a server-side permission issue.

Avoid sharing access tokens or other credentials in the discussion.

If this helps resolve the issue, please mark this reply as the answer. It will help other developers encountering the same error find the troubleshooting steps more easily!

[bihzatturk-maker]

Thank you. I've already verified that the browser and CLI use the same GitHub account, signed in again successfully, and updated Copilot CLI to version 1.0.98.

Copilot Free and Copilot CLI are enabled in my account settings, but activating Free access still returns HTTP 403 Forbidden. The built-in GitHub MCP server also returns HTTP 403, and the model catalog request times out.

Since these checks are already complete, could a GitHub staff member advise how a Free user can request an account-entitlement review for this issue?

I have not shared any credentials or access tokens.