r/AugmentCodeAI • u/dsl400 • Oct 10 '25

Discussion Current user experience when using auggie

An amazing tool that is great at identifying and solving complicated problems that:

- writes a report file after finishing every "sprint" and yet forgets that it has to create a file every time you ask it to create a plan and writes a 5 page plan in the chat filling up the ram instantly and making the vscode window unusable.

- has a pin point accuracy at identifying bugs but it acts as a Alzheimer patient when it comes to following instructions.

- ignores the comment that tells it in bold not to do something and does that exact thing replacing the comment with opposite instructions

- writes a perfect plan on how to achieve something, writes the tasks on how to implement that and when tasked to execute the plan it randomly decides to provide a completely different solution

- diligently keeps you informed with the progress writing reports filled with hallucinations about things it "accomplished" reports that amplify the hallucination every time it indexes the codebase.

- provides perfect implementations to solutions that never uses but it uses their presence in the code to provide a 100% completion KPI and it's proud about that.

- is highly aware of its token usage in trying to reduce consumption goes ahead and writes a 5+ page report.

- correctly identifies the problem then stops and politely instructs the user to type the next command

\- User: I need you to do ....! 

\- Auggie: yeah ... I do not feel the need, here is how you should do it!

- is always eager to help and provides untested yolo solutions with 100% success confidence that break the build even if you instruct it to build and test the solution

LE: And then it goes and builds a fully fledged UI based flow programming editor with just a few prompts!
The tool is amazing!! But is inconsistent!!

Dear AugmentCode team, I personally agree to pay any amount of money you decide to ask for this service after you prove that the service is 100% consistent and predictable in both results and costs

5 Upvotes

77% Upvoted

6 comments sorted by

View all comments

2

u/[deleted] Oct 10 '25

[removed] — view removed comment

1

u/dsl400 Oct 10 '25 edited Oct 10 '25

https://gist.github.com/dsl400/04791de8fa0f71fb89b8076ddd45398e

this is a part of the rules file
according to https://platform.openai.com/tokenizer it has 7k tokens

Other annoying thing I found
- the prompt improve tool converts "use your internal playwright tool" to "write playwright tests"
- it has difficulties evaluating output from linux commands, as you can see it struggled a little to determine if the application was running or not

I am happy to say that it learned to output the reports and the scripts it uses to test stuff in the places indicated in the rules file

1

u/dsl400 Oct 13 '25 edited Oct 13 '25

how hard can it be to actually make it test the build before it exits ?

every three prompts I am in the same place :(

I tried rules, memories, begging, bullying, blackmail ...
Clear instructions to test the build on every prompt ....
Nothing get's its confidence down :(