Unable to run prompts within Copilot session

[Conrad2134]

Describe the bug

When attempting to run (any) prompts after starting a Copilot CLI session, I am met with the following error:

Execution failed: Cannot destructure property 'viewer' of 'I.data' as it is undefined.

This seemed to start happening out of nowhere. I was using Copilot CLI this morning and, after starting a new session, I started receiving the error. I did try clearing the npm cache, logs and such in the ~/.copilot folder, and uninstalling/reinstalling the CLI. Included error from the logs in additional context.

Affected version

0.0.354 Commit: 076bd172b

Steps to reproduce the behavior

1. copilot
2. Wait for session to load.
3. Prompt with "hi"

Expected behavior

No response

Additional context

Error from the logs:

2025-11-06T16:18:13.800Z [ERROR] Failed to fetch Copilot URL, using default: TypeError: Cannot destructure property 'viewer' of 'I.data' as it is undefined.

session-d7fd8d27-04d3-44d6-b951-3d19c9f73f83.log

[Conrad2134]

Update - it works now. Nothing changed on my end other than waiting 30 minutes 🤷‍♂️

Potentially related, but I was doing a lot of data fetching with the GitHub APIs and hit primary rate limits. Those reset after I had opened this issue, and so I'm kinda curious if that's what I was running into.

[andyfeller]

@Conrad2134 : First, apologies for the difficulties troubleshooting the underlying issue here and thank you for reporting back. 🙇

I was taking a look at the attached session and would love to try confirming if rate limiting was really the problem here. I see the logs redacted the user you were using with this, so I'm unsure if its the same as the user you're using to report the issue or not.

[Conrad2134]

@andyfeller it was my EMU account, and I figured it best just to redact it.

I did run down my graphql rate limit to 0 and found that I was able to continue using an existing copilot session that was already open, but I was not able to use a new copilot session or one that I had resumed, if that helps! Also happy to provide any other info I can or help in any other ways.

[examon]

This appears to be addressed in current releases. The authentication startup flow was reworked, and the crash that blocked prompts from running during session startup is no longer reproducible. If you're still seeing this on the latest version, please feel free to reopen with version details and any updated logs.