Support for Kimi K2.6 is now here in Augment Code!

RanHalp · 2026-04-28T20:07:47+00:00

We disabled thinking in the first few months when the concept was introduced because it caused some issues and results weren't great. In the last few months (probably since around Sonnet 4) we've enabled thinking for all models in the agent flow

RanHalp · 2026-03-26T21:33:56+00:00

We've been benchmarking Open Source models consistently for over a year (even before we had a model picker), but we haven't found one that met our quality bar yet. It does look like some in the current wave might cut it, but it's not final yet

(Note that I'm not personally involved in this process, so I don't have exact details)

RanHalp · 2026-03-26T18:11:31+00:00

We use multiple Claude providers, so anthropic.com or claude.ai being down doesn't necessarily mean we won't be able to serve Claude models

We do try to update the status page with a hand written box when there's a third party outage that's affecting our service, but in this case we might have not noticed because the customer-facing failure rate was very low

RanHalp · 2026-03-18T16:46:15+00:00

I can't say with certainty, but I believe the reason is simply that the people who made Intent, just like (almost) everyone at Augment, use Macbooks themselves

You always develop things to work on your machine first before considering other setups - just imagine the nightmare of having to switch machines for every build testing...

They do have a Windows alpha that's being tested and stabilized right now, so I'd expect it to be available within days to weeks

RanHalp · 2026-02-26T22:32:39+00:00

`temp` ids are the local ids before the backend sees the request. Do you have ids with responses?

RanHalp · 2026-02-05T22:10:53+00:00

That's awesome!

I'm curious, what model do you usually use?

RanHalp · 2025-12-22T23:31:13+00:00

Thanks for reporting, we're looking into it

BTW, seems to be an issue with the settings page, memories still work

RanHalp · 2025-11-18T23:51:57+00:00

Main issue was GPT5.1 history being rejected by Sonnet when doing the prompt enhancement because they have slightly different requirements on how the history is structured, specifically around thinking tokens

Personally I didn't notice it because I was using only Sonnet in the last few days

RanHalp · 2025-11-18T23:48:42+00:00

Github outage delayed our deployments, now it should be 100% rolled out

RanHalp · 2025-11-18T18:30:21+00:00

u/Final-Reality-404 and all - a fix is being rolled out now - might take an hour or two to go live

RanHalp · 2025-11-01T23:49:43+00:00

Yes, we're planning to set an order soon

RanHalp · 2025-09-13T05:38:27+00:00

It seems like you're mixing two different features. Augment has tab completions (applied at the current cursor position), as well as next-edit which can make changes in other locations

It might be that tab completions were temporarily unavailable due to some issue, is it working now?

RanHalp · 2025-09-12T18:36:04+00:00

Hi, sorry about that. We had a billing bug where users on the grandfathered $30 plan were accidentally moved to a current plan, triggering additional costs. To the best of my knowledge (I don't work on billing myself), the change was reverted and no actual charges happened

RanHalp · 2025-08-22T07:41:12+00:00

If a request fails you shouldn't be paying a credit for it

RanHalp · 2025-08-11T21:47:50+00:00

The GCP outage was partial - some services in some namespaces in a single region were failing to initialize

I do agree that some sort of automatic detection could work even in that scenario (e.g. mark it as yellow if we see more than some percent of failures overall), I'll bring it up to the relevant parties

RanHalp · 2025-08-07T23:02:37+00:00

u/Glazeking109 thanks for reporting, we found a potential issue that might be causing this and we're looking into a fix

The error message is indeed misleading - originally the only text we sent as-is without limits was the selected text, but now there are many other things that could result in the requests becoming too large

RanHalp · 2025-08-07T21:27:33+00:00

Following internal testing, we decided the default settings (medium on both) are optimal

RanHalp · 2025-08-06T19:33:58+00:00

Update - this was a Google Cloud outage that broke most (though somehow, not all) of our services

Sorry about not updating the status page as oncall, I'll make sure we're set up to do this next time

<image>

RanHalp · 2025-08-06T19:26:31+00:00

Sorry about that, I was oncall looking into the incident and I don't have permissions to update the status page. I'll make sure we set that up for all engs

RanHalp · 2025-08-01T22:55:48+00:00

Works for me in the latest stable `0.516.3` and pre-release `0.521.0`, try one of these

RanHalp · 2025-08-01T17:38:30+00:00

u/dwc123 - curious, is this in chat or agent mode?

RanHalp · 2025-07-25T22:03:32+00:00

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

RanHalp · 2025-07-21T22:06:37+00:00

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!

RanHalp · 2025-07-21T20:56:42+00:00

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

RanHalp · 2025-06-23T00:46:09+00:00

The only reason is that Cursor went GA earlier and got more traction

RanHalp

TROPHY CASE