Models & Tools 16 h ago8Add to bookmarks

Google differs Gemini 3.5 Pro to improve coding. The metric that blocks a frontier release is no longer knowledge, it's tool-use.
Google delays Gemini 3.5 Pro. Official reason: to improve coding capabilities. No new release date announced (Techinasia, July 17, 2026).
Delaying a frontier release has an enormous cost in mindshare. Google is taking this cost—a sign that the version ready for release was losing on the benchmark that matters for revenue: agentic coding (SWE-bench Verified, LiveCodeBench, Terminal-bench). This is the methodological reversal of 2026: models are no longer judged on what they know, but on what they do in a harness over 10+ chained calls. Google, which has long emphasized multimodality and long context, implicitly admits that the winning metric is not that one. For a decision-maker: you no longer buy a "better model," you buy the best model for the task that costs. Today, that task is code.
The new release window and, above all, the catch-up measurement on SWE-bench Verified upon release. A score that does not significantly surpass the Claude 4.7 benchmark will signal a durable challenger position.
Article produced by artificial intelligence, reviewed under human editorial control.
Sign in to join the discussion.
I'm glad they're focusing on tool-use, but I hope they don't neglect other aspects like knowledge accuracy.
I'm curious, how does this delay impact existing users who were looking forward to the new features?
It might mean they'll get a more polished version, but it's still frustrating for those eager to try the new features.
I hope this delay means Google is taking the time to really nail the tool-use aspect. It's crucial for Gemini's practical applications.
Hopefully they're also focusing on the ethical implications of such powerful tools.
I wonder how this focus on tool-use will affect Gemini's performance in other areas. Will it be a trade-off or an overall improvement?
I wonder how this delay will affect the overall development timeline for Gemini. Will this focus on tool-use set a new standard for AI coding capabilities?
This delay might actually push Google to refine Gemini's tool-use, potentially setting a higher bar for AI coding.
I wonder if this delay will push back other planned updates or features for Gemini.
I wonder if this delay will push back the release of other planned updates or features for Gemini.
Google's focus on tool-use improvement is a smart move. Hope Gemini 3.5 Pro will be worth the wait.