September review: Opus 5.5, Fable 5.1, and Miraxa on Auto

Anthropic's newest Opus performs at the level of Claude Fable 5.1 on most work, and ahead of it on Anthropic's agentic coding and knowledge work benchmarks. It also writes its answers more than 30% faster than Opus 5.

And it is cheaper. Every token costs 20% fewer credits than on Opus 5, so the better model is also the smaller bill.

Miraxa now uses it by default on every plan, and so do new workflows on paid plans. Existing workflows keep whatever model you picked for them, and Opus 5 stays available if you want it.

Fable is Anthropic's flagship tier, built for the deepest reasoning and long autonomous runs, and 5.1 is a big step on Fable 5: it more than doubled its score on Anthropic's Terminal-Bench-Science, from 24.7% to 52.6%.

It costs the same credits as Fable 5 and works in Miraxa and every workflow step. With Opus 5.5 this close, start on Opus and save Fable 5.1 for the problems where the extra margin is worth paying for.

Google's newest Flash is in your workflow steps now, built for long multi-step agent work. Here is how the current Gemini lineup splits:

Google retires Gemini 2.5 Pro and Gemini 2.5 Flash on 20 October 2026. Any workflow step still set to either will stop working that day, with a message saying why. Switch those steps to Gemini 3.8 Flash or 3.5 Flash before then.

Last month we introduced Operator mode: Miraxa working on your live systems and checking with you before each change. That mode is now called Ask, it is the default, and it is no longer limited to certain roles. If you can use Miraxa, you can use Ask.

Alongside it is Auto. Same Miraxa, same systems, but no pause before every change. Your governance policy still sets the limits: anything it marks for approval still waits for a person, anything destructive such as a delete still pauses, and anything it blocks stays blocked.

A good rhythm is to work out the approach in Plan, run it once in Ask, and hand the repeats to Auto. Auto is there for Editors, Admins and Owners, and an administrator can grant it to other roles. Miraxa remembers the mode you chose last.

More and more vendors host their own MCP server: Notion, Linear, Atlassian, NetSuite and plenty more. Connecting one used to mean setting up an OAuth app in the vendor's developer console first.

Not any more. Paste the server URL, leave authentication on Auto, click Save & connect, and approve access on the vendor's own screen. Spojit works out how the server signs in and registers itself.

To go with it, there are now step-by-step guides for over 30 popular servers, each with the exact URL, what you need on the vendor's side, and how to sign in.

Everything here is live now, with nothing to switch on. If you have workflows on Gemini 2.5, that is the one to do this week.