o1 (normal) does not work in composor but just uses credits! Well… it worked after using $2.4 of my current and deleted entire my code and added +1 one line. What is going on… Cursor…
o1 should work fine in the Composer - sorry to hear you are having issues!
Are you using an API key, or have you enabled usage-based pricing?
I use usage-based pricing. It is hit or miss mostly. It spends $0.8 for one prompt and spends a few minutes just to delete entire code. Not sure what I am doing wrong so little frustrated.
Hey, my best recommendation here is to keep your composers relatively short-lived, making a new one when you start work on a different feature or area of your codebase.
Models like Claude 3.5 Sonnet already start to degrade in output quality when they are given long chat histories, or lots of context across different files, but this is even worse with models like o1, as they include the reasoning steps to “check” their work - and when they don’t have a concise and focused context, they get thrown off.
Additionally, consider writing down information in files that you provide to o1 as context, such as a brief project overview, to it has better context over your project structure before it starts to make any changes.
We do hope to improve on issues like this in future updates!