How Auto picks a model, and when to pin one instead
What Flintr's Auto mode considers when it chooses a model for each request, why it doesn't always pick the biggest model, and when pinning a model is the better choice.
Product4 min read
Why Auto exists
Frontier models are brilliant at hard problems and wasteful on easy ones. Renaming a variable or writing a docstring doesn't need the most capable model on the market, and using one makes the request slower and more expensive. Auto exists so you don't have to make that call dozens of times a day.
What Auto looks at
For every request, Auto weighs a few things:
- The kind of task. An inline edit, a question in chat and a multi-file agent run have very different needs.
- How much context it needs. Requests that span a large part of the codebase go to models with large context windows.
- How hard it looks. Signals like failing tests, long stack traces or a request to redesign something push towards stronger reasoning models.
- Your settings. Pinned models, team allowlists and your spend cap always come first.
Why it doesn't always pick the biggest model
Because bigger isn't always better. For small, well-defined edits, fast models are often just as accurate and answer in a fraction of the time. Since on-demand usage is billed at list price, choosing the cheaper model also stretches your included usage further.
If a fast model struggles with something, ask again with a stronger model from the picker. The conversation keeps its context, so nothing is lost.
When to pin a model instead
- You have a favourite for a specific job. Many people pin Claude Sonnet for agent work and let Auto handle everything else.
- You need consistent behaviour. For long refactors, staying on one model keeps the style of the changes consistent.
- You're comparing models. Pin one, then switch mid-conversation to see how another handles the same context.
- Your team requires it. On Teams and Enterprise, admins can limit which models are available.
Seeing what Auto picked
Every response is labelled with the model that produced it, along with its token count and cost, for example "Claude Sonnet · picked by Auto · $0.07". The usage dashboard breaks spending down by model, so you can see exactly how Auto spends your included usage. Browse every available model.
Frequently asked questions
Does Auto cost extra?
No. Auto is included in every plan. You pay for the model it picks at that model's list price, like any other request.
Can I turn Auto off?
Yes. Pin a model per project or per conversation and Auto steps aside until you unpin it.
Will Auto ever pick a model my team has blocked?
No. Team allowlists and pinned models always take priority over Auto's choice.
Keep reading
Pricing4 min read
Why we bill on-demand usage at the provider's list price
No credits, no multipliers, no "fast requests". How Flintr bills usage beyond your plan, what list price means, and where our margin comes from.
Read articlePricing5 min read
Pro, Pro+ or Ultra: which plan should you pick?
A practical guide to choosing a Flintr plan, with break-even points: Pro+ becomes cheaper than Pro above $60 of monthly usage, and Ultra beats Pro+ above $210.
Read articleYour editor. Your models. Your bill.
Flintr is in development and funded by the people who'll use it. Back the launch from €5, or from €25 to get into the private beta.
Coming to macOS 12+ · Windows 10+ · Linux (deb, rpm, AppImage)