GitHub Copilot CLI 0.0.365 stuck at starting [Solved by disabling kwallet]

[lyh543]

Select Topic Area

Bug

Copilot Feature Area

Copilot Coding Agent

Body

Version Info:

copilot --version
0.0.365
Commit: 76d0881

I'm running Copilot CLI on my server, it stucks for about 8mins+ and no output.

I try to get some logs with copilot --log-dir . --log-level debug, however no log files are created either.

---

Then I downgrade Copilot CLI to 0.0.354 (Commit: 076bd172b), it works normally and I get some logs like:

tail -f /var/log/github-copilot-cli/session-xxxx.log
2025-12-01T11:58:00.209Z [DEBUG] Fetched Copilot URL for xxx from https://api.github.com/graphql: 200 https://api.business.githubcopilot.com
2025-12-01T11:58:00.209Z [LOG] Starting remote MCP client for github-mcp-server with url: https://api.business.githubcopilot.com/mcp/readonly
2025-12-01T11:58:00.209Z [LOG] Creating MCP client for github-mcp-server...
2025-12-01T11:58:00.213Z [LOG] Connecting MCP client for github-mcp-server...
2025-12-01T11:58:00.687Z [DEBUG] Fetched Copilot URL for xxx from https://api.github.com/graphql: 200 https://api.business.githubcopilot.com
2025-12-01T11:58:00.688Z [DEBUG] Creating copilot-client for integration ID copilot-developer-cli with token authentication. User-agent: copilot/0.0.354 (linux v25.1.0) OpenAI/5.20.1
2025-12-01T11:58:01.715Z [LOG] MCP client for github-mcp-server connected, took 1502ms
2025-12-01T11:58:01.715Z [LOG] Started MCP client for remote server github-mcp-server
2025-12-01T11:58:01.715Z [LOG] GitHub MCP server configured after authentication
2025-12-01T11:58:03.625Z [DEBUG] Successfully listed 25 models

---

I try to curl https://api.github.com/graphql, and get output:

curl https://api.github.com/graphql
{"message":"API rate limit exceeded for xxx.xxx.xxx.xxx. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)","documentation_url":"https://docs.github.com/rest/overview/resources-in-the-rest-api#rate-limiting"

I wonder whether the first request to https://api.github.com/graphql is unauthenticated, and therefore block Copilot CLI to start?

[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. ⭐

[AyanSaha-CSE-72]

GitHub Copilot CLI version 0.0.365 gets stuck at "starting" due to GitHub API rate limits tied to your IP address, which restrict requests (e.g., 60/hour unauthenticated or higher for authenticated). This commonly affects CLI tools during heavy usage, even with Copilot Pro, as overall service health limits apply separately from premium requests.

[lyh543]

In this case, is there a way to login to GitHub to bypass the restrictions?

[lyh543]

I find the root cause is that my server OS is Manjaro with GUI, with KDE Wallet installed. When I start copilot in an SSH terminal:

1. GitHub Copilot CLI try to access keychain from KDE Wallet
2. KDE Wallet require my password to unlock the keychain by a popup window in GUI!!!
3. Of course I don't know what happened behind a SSH terminal, so copilot just stuck here.

Finally I log in to server GUI and disable the KDE Wallet in system settings, and everything works fine.