Gemini 4 Argon Arrives, and Agent Infrastructure Opens Up

The headline technical detail is a unified input and output limit of 1 million tokens.

That means the allowance covers the material sent to the model and what it generates, rather than advertising a huge context window while treating the output separately.

Google has also introduced a continuation protocol for work that runs for a long time.

In practical terms, the model is being offered for jobs that may involve a large code base, a substantial document set, or a sequence of tool calls that cannot be completed in one quick response.

The continuation mechanism matters because a long context limit alone doesn't make an agent durable.

The application still needs a reliable way to resume work, preserve state, and recognize what has already been done.

That combination changes the engineering question.

A large context gives the model room to see more of the task, while continuation gives the surrounding application a way to carry the work across boundaries.

Neither guarantees that the model will use all that material well.

An agent can still bring forward irrelevant history, miss an earlier constraint or resume from the wrong state.

A serious evaluation should therefore track whether the finished work is correct, how many continuations it needed, what context was carried forward and how much output it generated.

Those details reveal whether Argon is completing longer jobs efficiently or merely keeping them alive for longer.

They also help separate a model quality problem from a fault in the application's state handling.

Pricing needs a careful look before anyone designs around that scale.

Until the 30th of November, Google lists the API at $2 per million input tokens and $10 per million output tokens.

Standard pricing is then due to double to $4 for input and $20 for output.

A short evaluation may look inexpensive at the introductory rate.

An agent that repeatedly carries large histories, generates lengthy results, or runs across many users could produce a different bill after the increase.

The sensible comparison is the cost of completing a real task, not the price of one isolated model call.

Google reports leading benchmark results and gains in its own engineering work.

Those figures are useful as a description of what the company has measured, but they aren't yet independent evidence of performance across representative production systems.

Long-running work exposes weaknesses that benchmarks can miss, losing track of constraints, repeating tool actions, recovering badly from an error, or consuming more tokens than expected.

Developers now have enough access to test those behaviors directly.

My read is that Argonne's immediate value is practical access to a model designed for sustained multi-step work.

The trade-off is equally concrete.