Allow Model-Based "Pay-As-You-Go" Selection for Optimal Usage

Hi team,

First of all, I want to express how impressed I am with your AI-powered coding assistant — it’s fast, smart, and incredibly helpful. The integration within the IDE feels natural and is a real productivity booster. Great job!

Suggestion: Enable per-model configuration for pay-as-you-go billing

I’d like to suggest a feature that I believe could significantly improve cost-efficiency and user control: the ability to choose which models I’m willing to use with pay-as-you-go billing.

Expanded reasoning:

Some models are already fast and efficient enough for my workflow, so using pay-as-you-go for them doesn’t offer real benefit — it just increases cost without noticeable gains. On the other hand, for more advanced models (especially the ones used for deeper reasoning or complex tasks), I’m happy to pay for better speed and performance.

Giving users the ability to opt-in to pay-as-you-go on a per-model basis would allow us to fine-tune the experience based on our actual needs, balancing performance and cost more effectively.

Thanks again for a fantastic tool — looking forward to seeing how it continues to evolve!

Best regards,

That would really be great, also to avoid accidental mistaken model selection for paid models that the user wouldnt usually want to use.

@danperks you need read it. It great!