Gemini 4 models (gemini-4-carbon, -argon, -neon, -hydrogen) can generate up to 1,048,576 output tokens minus the input, but a single streamGenerateContent request stops at 65,536. Past that, Google expects the client to run a continuation loop: https://ai.google.dev/gemini-api/docs/long-decode?generate-content=true
Set maxOutputTokens above 65,536. It caps thinking and output across all hops.
A hop that hits the per-request cap ends with finishReason: CONTINUATION and a continuationToken.
The next hop re-sends the same request (same contents, same maxOutputTokens) plus the latest continuationToken. Partial output is not appended to contents.
The loop stops on any other finish reason. The parts from all hops are joined into one model turn.
Streaming hops past the first 64K send a checkpoint continuationToken every 5,000 tokens. A dropped stream resumes from the last checkpoint, discarding uncommitted chunks.
A response that ends with MAX_TOKENS also carries a continuationToken and can be resumed with a higher maxOutputTokens.
create_request sends parameters.max_tokens, falling back to the model's reported output limit (65,536 for the Gemini 4 models). With the default, output stops at 64K and the turn ends with the max-tokens notice.
With max_tokens set above 65,536 it is worse: the forked gemini_client_rs (c072e4b) has no Continuation variant in types::FinishReason and no catch-all, so a CONTINUATION finish reason fails to deserialize and the stream errors instead of ending. Candidate also has no continuation_token field, and GenerateContentRequest has no continuationToken.
The existing max-token chaining is not compatible with Google's loop. Anthropic's chain_on_max_tokens appends the partial output and asks the model to continue, whereas Google requires re-sending the original contents unchanged. jp_llm::stream::chain::EventChain merges overlapping text across chained streams; Google's hops continue from the exact stop point without overlap.
Each hop reports its own usageMetadata, and every hop's promptTokenCount includes the output of all earlier hops. Summing them overstates the prompt size: in Google's example, a 1,000-token prompt reports about 397,000 input tokens across four hops. Usage accounting (T-0n0pgw6) must use the first hop's promptTokenCount as the prompt size. That count does not size the next request, which re-sends this turn's full output; the preflight fit check (T-0n0pex2) estimates the request about to be sent instead.
JP does not use background mode or server-side storage. Google's server-run long decode requires background: true and store: true, so it is out of scope on either API.
On the Interactions API, a foreground segment stops at 65,536 tokens with status: requires_continuation and a continuation_token, so a migration under T-1fev134 (store: false) keeps the client-side loop. The request and status shapes differ between the two APIs, so decide T-1fev134 before implementing the loop.
Map CONTINUATION to a finish reason that is not an error.
Run the hop loop in the Google provider, joining hops into one response.
Resume a dropped stream from the last checkpoint token.