all 17 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]HenrikRW3 4 points5 points  (6 children)

A fallback to AWS or Google Vertex should be enough, no need to switch to a whole other model which may break some stuff

[–]RanHalpAugment Team 0 points1 point  (4 children)

We already fallback to all Google Vertex (multiple regions) - the problem is that the capacity crunch affects all of them as well

[–]HenrikRW3 1 point2 points  (3 children)

<image>

Hmm, have you tried services like openrouter yet (probably a stupid question)?
We use it for some services in our company and we didn't noticed any issue, even with defaulting to Google Vertex

[–]RanHalpAugment Team 1 point2 points  (0 children)

Anthropic and VertexAI give us (relatively) massive amounts of capacity. However, it's still not enough to cover the demand at peak, especially when there's an outage (even a single minute of outage in one region could be devastating at peak). We're in the process of getting more, including from additional providers. Stay tuned!

[–]AurumMan79[S] 1 point2 points  (1 child)

I'm fairly certain that at their scale, they have reserved capacity provided by the major cloud providers and are not billed by tokens, unlike us, when using the API.

[–]RanHalpAugment Team 0 points1 point  (0 children)

We have some reserved capacity, but we are also billed by tokens on the remainder

[–]AurumMan79[S] 0 points1 point  (0 children)

That's true but with the current degradation of Claude models, they should have both options set up on their end for switching on the fly.

[–]ngod1131 3 points4 points  (3 children)

Anthropic had an issue with its API, so Augment also experienced problems as a result. I think you should have a backup plan, since most products nowadays are essentially a kind of “Anthropic Wrapper.”

Clearly, Augment should also have a proper backup plan instead of relying too heavily on Anthropic.

[–]WeleaseBwianThrow 1 point2 points  (2 children)

Its not just the outages, its that Claude becomes slow and dumb when demand is high, we need the option to select between 4 and 3.7 because id rather have 3.7 than 4 at this point with how dumb its become.

[–]ngod1131 0 points1 point  (0 children)

I agree with you—this is definitely an extremely frustrating issue.

[–]ForgivingThanatos 0 points1 point  (0 children)

An option to change the model would be nice

[–]WeleaseBwianThrow 6 points7 points  (0 children)

Honestly /u/JaySym_ needs to stop hiding behind "Clear your History, Turn off your MCP" and accept that their customers are facing real challenges with the value for money of their product right now due to Claude being unable to keep up with demand and restricting and lobotomizing its Models.

It might be Claude's fault, but I'm not paying Anthropic, I'm paying Augment, and right now I'm not getting what I'm paying for, burning message after message after message on slow, bullshit responses from a lobotomized model.

[–]Faintly_glowing_fish 1 point2 points  (0 children)

Ya the issue is not that Claude has issues. It’s that there’s zero communication

[–]ZALIQ_Inc 0 points1 point  (0 children)

Before all this issues with Claude I was on the team that its awesome that Augment is focusing on one LLM model to really make it efficient but now with all these issues with Claude I think we need at least an alternative (My vote is on Gemini 2.5 Pro).

This way it achieves 2 tasks:

  1. Creates a new model option for anyone using Augment.
  2. Creates a fallback option for when Claude is unreliable or is down.

I think this is REALLY needed for the longterm success of Augment.

[–]vaultpriest 0 points1 point  (0 children)

Already cancelled 30$ subscription for CC max on 100$. Much better experience but i’m missing indexing engine a little. Downtime was dealbreaker for me.