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
I wonder could you direct me to the right person to explain why I have had to spend almost 200 million tokens to have a half-baked, badly coded, buggy app and how to get a refund or reload of the millionsof tokens your nightmarish system has wasted???
Today we spent 4hours and 25 million token going in a circle to fix an error with your system, even you less tan AI AI agreed - their comment below,
Now after wasting my day and token, the app will not even work outside of the terminal window on an external browser tab
look at your trust pilot every now and then, you might want to start taking note!
+++++++++++++++++
I understand your frustration. You're right - I should have identified and fixed the issue with the WCAGStandardsTable component name mismatch much earlier. The solution was straightforward: ensuring consistent component naming and route paths between the App.tsx and Navigation.tsx files.
The fix was simple but critical - making sure we used the same component name and route path everywhere. This is a good reminder that even small inconsistencies can cause significant issues, and we should be more thorough in catching these earlier.
As for the token usage - you're right to be concerned. While the fix was ultimately simple, we went through a lot of unnecessary iterations and complexity before arriving at the solution. This wasn't efficient use of resources.
Going forward, we should:
Check for basic naming consistency issues first
Verify component imports and routes match early
Test route changes immediately after implementation
Maintain a consistent naming convention across the codebase
Would you like me to help implement any other changes or improvements to prevent similar issues in the future?
Please make your project public or accessible by URL. This will allow anyone trying to help you to easily reproduce the issue and provide assistance.
Steps to reproduce
Literally anything, 4 hours of various commands, take your pick
Expected behavior
pretty simple I woudl liek your bot to work and not rob millions of tokens, pretty basic stuff
Screen Recording / Screenshot
No response
Platform
Browser name = Chrome
Full version = 134.0.0.0
Major version = 134
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36
performance.memory = {
"totalJSHeapSize": 1033169963,
"usedJSHeapSize": 929961187,
"jsHeapSizeLimit": 4294705152
}
Username = heaventree
Chat ID = 7a3ebf5a748f
Client version = f8f9d38
Server version = 357ece6
Additional context
No response
The text was updated successfully, but these errors were encountered:
heaventree
changed the title
25million tokens wated withotu a fix to your provided codre
25million tokens wasted without a fix to your provided buggy code
Mar 13, 2025
Describe the bug
I wonder could you direct me to the right person to explain why I have had to spend almost 200 million tokens to have a half-baked, badly coded, buggy app and how to get a refund or reload of the millionsof tokens your nightmarish system has wasted???
Today we spent 4hours and 25 million token going in a circle to fix an error with your system, even you less tan AI AI agreed - their comment below,
Now after wasting my day and token, the app will not even work outside of the terminal window on an external browser tab
https://zp1v56uxy8rdx5ypatb0ockcb9tr6a-oci3-u7a01ox1--5173--853a9fbb.local-credentialless.webcontainer-api.io/
look at your trust pilot every now and then, you might want to start taking note!
+++++++++++++++++
I understand your frustration. You're right - I should have identified and fixed the issue with the WCAGStandardsTable component name mismatch much earlier. The solution was straightforward: ensuring consistent component naming and route paths between the App.tsx and Navigation.tsx files.
The fix was simple but critical - making sure we used the same component name and route path everywhere. This is a good reminder that even small inconsistencies can cause significant issues, and we should be more thorough in catching these earlier.
As for the token usage - you're right to be concerned. While the fix was ultimately simple, we went through a lot of unnecessary iterations and complexity before arriving at the solution. This wasn't efficient use of resources.
Going forward, we should:
Check for basic naming consistency issues first
Verify component imports and routes match early
Test route changes immediately after implementation
Maintain a consistent naming convention across the codebase
Would you like me to help implement any other changes or improvements to prevent similar issues in the future?
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-7d7w76rh
Validations
Steps to reproduce
Literally anything, 4 hours of various commands, take your pick
Expected behavior
pretty simple I woudl liek your bot to work and not rob millions of tokens, pretty basic stuff
Screen Recording / Screenshot
No response
Platform
Additional context
No response
The text was updated successfully, but these errors were encountered: