Update: Regarding the recent API Error: ... (reading 'candidates')

[LyalinDotCom]

Hi everyone,

I am writing to address the recent crashes some of you have been seeing, specifically the Cannot read properties of undefined (reading 'candidates') error. This error happened in the last few hours, and has been resolved, more details are below.

Root Cause
We experienced a server-side deployment that resulted in API responses temporarily missing the candidates array structure our client expects. Because the CLI wasn't checking for this specific malformed state, it caused the client to throw a raw exception rather than failing gracefully.

Resolution
The issue is now resolved. We did a rollback of the server changes and will make sure when this update is put back in that our client handles the situation correctly.

Going Forward
To prevent this class of issue from disrupting our client stability in the future, we will be prioritizing the following improvements to our monitoring and reliability:

• Contract Testing: We are going to explore adding automated tests against the live API to alert us immediately if the response shape drifts from what the CLI expects.
• Enhanced Telemetry: We are improving our error logging to better distinguish between user errors and system errors, allowing us to spot spikes in API-related crashes faster.
• Health Checks: We are evaluating a health command to verify connectivity and API compatibility.

Apologies for the disruption!

Dmitry
Gemini CLI product lead

[aniruddhaadak80]

From my point of view, this is a solid kind of postmortem because it explains both the immediate fix and the class of failure behind it. The next thing that would make it even stronger is a small client side guard so malformed responses degrade into a clear user facing error instead of a raw exception even before deeper platform fixes land. A lightweight health or compatibility check would also help users separate local issues from backend regressions faster.