Code Studio eating tokens like candy

[David Jones]

There seems to be some sort of issue or performance optimizations are needed. When using the Code Studio with any of my api keys. I can code one Blazor chat page with side nav and it will eat through 20 dollars of credits in just 2 pages of code. 

This is a problem. I can go into Roo code and do at least 5 pages and it uses a fraction of that. I have a chat in Roo code that is pages and I only spent 5 dollars max

 So something is a miss here. Is this using prompt caching? Can it do a better job at checkpoints? Is there anyway that you can get it to save tokens. As of right now it is unusable in that sense if people are looking to maximize their token efficiency like they would with something like Cline or Roo

[Sivasankar Mathiyazhagan]

Hi David,

Thank you for sharing your experience — we really appreciate your feedback as it helps us improve Code Studio.

To better understand the token usage, you're seeing and explore possible optimizations, could you please help us with a few details:

1. Which model (LLM) are you using in Code Studio?
2. If possible, could you share a sample prompt that triggered the high token usage?
3. Could you recall whether your interactions in Code Studio and Roo Cline were conducted within the same session, or did you use separate sessions — for example, a single continuous session in Code Studio and split sessions in Roo Cline?
4. Could you also share more about the issue you faced with the checkpoints feature? For example, what behavior did you expect, and how did it differ from what you observed?

These details will help us pinpoint what might be causing the higher token consumption and explore ways to optimize it. Looking forward to your response so we can assist you better.

Regards,
Sivasankar M.