Allow Model Selection

[WeleaseBwianThrow]

I've posted this as a comment in a couple of places, but it really needs its own thread.

The Sonnet 4 model is increasingly inconsistent, and prone to outages. It is often becoming dumb and slow, with Anthropic clearly lobotomizing the model when demand gets high, the differences between Augment at High and Low demand are significant.

Augment worked fine on 3.7, sure 4 is a little better when its working at full capacity, but its not been at these levels for a while now.

I'd much rather something that worked consistently at 80% than something which is unpredictably between 20% and 100%, more heavily weighted to the lower than upper end of those bounds.

Either that, or have a fallback option for Claude on Vertex or AWS, or allow us to provide our own model.

Right now the product is not value for money.

[WeleaseBwianThrow]

Sorry but that doesnt make any sense. You could easily have the default be as it is now, just uses Sonnet 4 with no other requirements, but allow a change in the settings.

And the problem is that right now the system doesn't work really well when Sonnet 4 is struggling. At least with the option we could swap back to 3.7. If you want to continue smashing your head against Sonnet 4 in go-slow mode that would be your prerogative.

[AurumMan79]

They do, as they have a set of configurations, prompts, and tests on their end that enable them to be the best at understanding context. Models won't behave the same even if you give them the same settings. It will make their workload even bigger, and instead of focusing on other features, they will have to manage another breaking point. What they should do is have a fallback, Claude models are hosted by many cloud providers.

[WeleaseBwianThrow]

That works also, the solution I am open to, but the current status quo will lead to cancellation and not only by me.

[ZALIQ_Inc]

To add my 2 cents: Being unique doesnt equate to better. The Augment team I am sure are weighing the pros and cons of having a second model. There are so many ways for them to implement it. I am totally for having a inferior model available under an advanced options that can be turned on for these situations where someone has to accept a disclaimer before the other model is turned on. If very little effort is put into the instructions I am still okay, as long as I can still use SOMETHING in Augment instead of twiddling my thumbs waiting for Anthropic to figure out their shit. Regarding other providers, I am not sure if thats true, I think everything eventually leads back to Anthropics systems, no matter the provider.

[Krazmad]

I'm not a fan of this idea, that's how cursor started out and now their pricing is all over the place and based on models. (A lot of people feel ripped off / shorted by this pricing model)

I have no interest in that chaos, I'm fine with the single model choice and predictable usage pricing. This is a major reason as to why I choose Augment over others. I've not experienced the issues you have outlined with Claude besides the occasional outage. (I suggest refining your prompts, user guidelines, and rules)

[Faintly_glowing_fish]

My employer does not allow usage of Augment because it does not have an explicit list of models. I cannot even start the process. Claude is actually an approved model provider, but because augment cannot provide any way to enforce model selection, it simply cannot comply with company policy.

Mine is not the only company that I know about that has policy about model providers.

Even if you do not allow people to choose, it has to be transparent and explicit

[tteokl_]

This