The author reports using a Python script to call gemini-4-carbon through the Gemini API with high thinking, asking it in a single request to review 13 files totaling about 682 KB and 252,465 input tokens. After running for 44 minutes and 54 seconds, the model exhausted its total generation allowance of 262,144 tokens: 262,141 were thinking tokens and only 3 were reply tokens. The saved review was 0 bytes. This is a single personal experience and does not establish whether the behavior is common.
Useful for assessing: The latency, continuation process, and empty output the author observed in one single-request code review with a very large input.
Not suitable for extrapolating to: Smaller code scopes, staged reviews, or other prompts and API configurations. The post did not test these cases and does not indicate the model's quality or stability on other tasks.
Model version tested: The author identifies it as gemini-4-carbon. No model snapshot or version number is given.
Test environment or client: The author used a custom Python script to call the Gemini API through the Google SDK. The SDK version and endpoint are not specified. The author clarified in the comments that this was not a third-party tool.
Thinking level and parameters: High thinking. The maximum output allowance and continuation process are described below. Temperature, the full prompt, and other request parameters are not specified.
The author used one request to review 13 files and perform code review and claim verification. The request text was about 682 KB, with an initial input of 252,465 tokens. The author said continuation was enabled and logged 8 consecutive generation segments of 32,768 tokens each, with the last ending in MAX_TOKENS. The post does not include the code, full prompt, SDK request body, or review scoring criteria, so the request cannot be independently reproduced and it is not possible to determine whether the task itself was achievable by the model.
| Item | Original post record |
|---|---|
| Number of files | 13 |
| Request text | About 682 KB |
| Initial input | 252,465 tokens |
| Runtime | 44 minutes 54 seconds |
| Total generation allowance | 262,144 tokens |
| Cumulative thinking | 262,141 tokens |
| Cumulative reply | 3 tokens |
| Saved review output | 0 bytes |
| Final status | Segment 8 MAX_TOKENS |
The author posted the following per-segment logs. sent is the number of tokens recorded as sent for each segment. The author separately reported a cumulative total of 2,937,224 tokens across the segments.
| Segment | Status | sent | reply | thinking |
|---|---|---|---|---|
| 1 | CONTINUATION | 252,465 | 3 | 32,765 |
| 2 | CONTINUATION | 285,233 | None | 32,768 |
| 3 | CONTINUATION | 318,001 | None | 32,768 |
| 4 | CONTINUATION | 350,769 | None | 32,768 |
| 5 | CONTINUATION | 383,537 | None | 32,768 |
| 6 | CONTINUATION | 416,305 | None | 32,768 |
| 7 | CONTINUATION | 449,073 | None | 32,768 |
| 8 | MAX_TOKENS | 481,841 | None | 32,768 |
The cumulative reply and thinking tokens in the log add up to 262,144, matching the total generation allowance reported by the author. The saved result was still 0 bytes. The author did not specify the content of the 3 reply tokens.
The comments describe individual experiences from other users. One commenter said they had also observed a large number of thinking tokens, mediocre results, and variable runtimes on long-context, in-depth analysis tasks. They said thinking tokens were close to zero at the medium level. Another commenter suggested narrowing the review scope and processing it in segments. The original author replied that they used a custom script and the Google SDK. They also mentioned the empty-text case for MAX_TOKENS described in Google's long-decode documentation, along with suggestions to raise the limit or lower thinking_level. Another commenter said their experience with Carbon high on a code project of about 200k was good, though their use case and measurement method differed. These comments do not reproduce the original request or constitute a controlled comparison.
This case shows that, in the author's single high-level code review with an initial input of 252k tokens, enabling continuation did not prevent the total output allowance from being exhausted. Most of the allowance went to thinking, and the saved result was empty. The case may prompt readers to examine the scope of a single task, thinking level, and output allowance. However, the post did not compare different scopes, levels, or allowances, and the author did not rerun the task. The cause therefore cannot be determined, nor can we tell whether raising the allowance or lowering thinking would produce a usable review.
Experiences in the comments varied: some users reported excessive thinking on long-context tasks, while another reported good results with the high level on their code project. The model, client, task breakdown, and token accounting were not consistent, so the comments cannot be compared with one another or used to draw general conclusions.
An exact reproduction would require the author's 13 files, full prompt, Google SDK and model snapshot, complete generation configuration, and original response and usage records. The post does not provide these materials. Any follow-up test should separately record the initial input, each continuation request, thinking and reply tokens, final status, output file size in bytes, and runtime. A single request containing the entire codebase and a staged review should be treated as different test conditions. These are reproduction suggestions, not tests reported in the original post.
Gemini 4 Carbon