Skip to main content

Auto, re-tuned for the newest models

We tested how Auto handles each kind of task against the newest models, comparing answer quality, speed and cost. Auto now sends more of your work to the models that came out ahead.

Written by Babbily Support

We tested how Auto handles each kind of task against the newest models, comparing answer quality, speed and cost. Auto now sends more of your work to the models that came out ahead.

  • Hard problems go to Claude Fable 5.2. Most demanding requests, from research, planning and math to science and coding, now go to Claude Fable 5.2, which answered them best in testing.

  • Demanding writing and database work. Long or careful writing now goes to Claude Sonnet 5.5, and complex database design to GPT-6.1 Sol. Both answered these best in testing, and Claude Sonnet 5.5 uses less of your API usage budget for writing than before.

  • Science, finance and legal questions start on Claude Fable 5.2, even when they aren't the hardest kind, because it answered them best. These replies use more of your API usage budget than before.

  • Everyday work uses less of your budget. Most conversations, questions, summaries, translations, SQL queries and data extraction now go to GPT-6.1 Sol, which answered them better in testing and uses less of your API usage budget.

  • Quick factual questions are more accurate. Short questions of fact now go to GPT-6.1 Terra, which gets more of them right.

  • Code review and configuration. Code reviews now go to GPT-6.1 Terra, and server, deployment and configuration work to Gemini 4 Carbon. Both scored higher in testing and use less of your budget.

Nothing changes in how you use Auto. Choose Auto in the model picker as before, and check Auto · Models used: below the composer to see which models answered. When your budget runs low, Auto still favors models that use less of it.

Faster artifacts

Documents, code and sheets in Canvas are now written by GPT-6.1 Terra, a fast writing model, from the request your model makes. The model you chose, or the one Auto picked, still decides what goes in them. This applies to every model.

  • Much quicker. In testing, a typical artifact arrived in under a minute, against two to six minutes before.

  • Large builds finish. Writing now has up to about six and a half minutes, up from three, and large app builds that used to run out of time finished in testing.

  • Less of your API usage budget. Writing an artifact counts at GPT-6.1 Terra's rate.

  • Visual artifacts are unchanged. Babbily draws them as before.

Did this answer your question?