Gemini Generate Content API request storage on by default
In brief
New paid-tier Google Gemini API projects now store Generate Content API requests by default. Developers who do not want requests logged must opt out per request or in the dashboard.
How it works
For new paid-tier projects, requests to generateContent, streamGenerateContent, and batchGenerateContent now default to store=true, matching the Interactions API. Existing projects keep their current settings. To opt out, developers can pass store=false on individual requests or turn off Generate Content API logging in the Settings panel of the Logs and Datasets dashboard.
Developers creating new paid-tier projects on the Gemini API.
Availability
Sources
1 merged into this cardMore from Google
Gemini CLI /stats heatmap subcommand
Google added a /stats heatmap subcommand to Gemini CLI v0.69.0 to track daily token usage. It lets developers monitor their token consumption directly from the command line.
Gemini CLI adds standalone theme.json support
Google's gemini-cli v0.69.0 adds support for a standalone theme.json configuration file. Users can now define custom themes in a dedicated file.

Gemini 4 Neon
Google's new Gemini 4 model pairs a 1M-token context window and four thinking levels with lower cost per task. It scores 61 on the AA Intelligence Index and targets complex coding, analysis, and cyber workflows.