You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: New version of Auggie (v0.6.0) having delayed responses #28
When sending a message to Auggie, sometimes it would take a long time to receive a response, there is no immediate indication or anything that suggests that it is processing my request, but eventually it does. Has something changed in the recent version of Auggie?
What did you expect to happen?
It should process the prompt immediately and indicate it is responding to it as usual.
Steps to reproduce
Send a prompt to Auggie, perhaps this only happens with large prompts? I am not sure what the logic is.
Hi @rishitank , could you provide a little more info on what you're seeing?
How are you invoking the tool, and what exactly do you mean by it takes a long time to receive a response? Is it that the TUI takes a long time to open, or that you send a message in interactive mode and don't get feedback, or something else? If possible a video would be very helpful.
Is this happening consistently or rarely? Does there seem to be a pattern to when it happens?
You mention you're on 0.6.0 which was newly released yesterday. Do you recall seeing this issue before that update?
Hi @rishitank , could you provide a little more info on what you're seeing?
How are you invoking the tool, and what exactly do you mean by it takes a long time to receive a response? Is it that the TUI takes a long time to open, or that you send a message in interactive mode and don't get feedback, or something else? If possible a video would be very helpful.
Is this happening consistently or rarely? Does there seem to be a pattern to when it happens?
You mention you're on 0.6.0 which was newly released yesterday. Do you recall seeing this issue before that update?
Sending a message in interactive mode takes a long time and I don't get feedback until after a while, like there is some delay.
It seems to be happening consistently, it happens with small or large prompts.
I definitely didn't see this before the update. I have another Auggie CLI session running right now using the old version and don't have this issue where it just waits a long time before giving feedback.
I am not sure if this is related, but tool calls in general are much slower in v0.6.0. So even when processing the response it it taking too long. I suspect it has something to do with the new feature Parallel Tool Calls: Added support for models calling multiple tools simultaneously 🤔
Thanks for providing the details. We think we have a root cause for the issue and have created a new prerelease version 0.6.1-prerelease.0 that we think addresses it. This can be tested using npx -y @augmentcode/auggie@0.6.1-prerelease.0 (npm install -g ... will work too, though it might try to auto upgrade the version). I'm doing some validation internally but if you end up trying this and see it fixing the issue (or not!), please do update here.
Activity
mtpauly commentedon Oct 31, 2025
Hi @rishitank , could you provide a little more info on what you're seeing?
rishitank commentedon Oct 31, 2025
I have attached a video.
Screen.Recording.2025-10-31.at.14.10.58.mov
rishitank commentedon Oct 31, 2025
I am not sure if this is related, but tool calls in general are much slower in v0.6.0. So even when processing the response it it taking too long. I suspect it has something to do with the new feature
Parallel Tool Calls: Added support for models calling multiple tools simultaneously🤔mtpauly commentedon Oct 31, 2025
Thanks for providing the details. We think we have a root cause for the issue and have created a new prerelease version 0.6.1-prerelease.0 that we think addresses it. This can be tested using
npx -y @augmentcode/auggie@0.6.1-prerelease.0(npm install -g ...will work too, though it might try to auto upgrade the version). I'm doing some validation internally but if you end up trying this and see it fixing the issue (or not!), please do update here.rishitank commentedon Oct 31, 2025
Thanks, it seemed to upgrade me to
0.7.0-prerelease.1when launching but it looks like the issue is fixed.mtpauly commentedon Oct 31, 2025
Great. I've just released 0.6.1 as a stable version. Thanks for your help here!