I'm playing a lot lately with Cline, what I feel is the better of the AI coding assistants out there.
It has one major problem and a few minor related problems that continue to plague me.
I'll break some of them down in a thread.
#AI #aidev #cline #sonnet3.5
It has one major problem and a few minor related problems that continue to plague me.
I'll break some of them down in a thread.
#AI #aidev #cline #sonnet3.5
Comments
In all my usage, you need to use anthropic Sonnet 3.5 and that gets really expensive
Haiku 3.5 does ok in a pinch and basic things are workable with gpt4o and o1
For complex large apps, you need Sonnet, it's MCP/computer use support and support for images etc
I like that Aider lets you use cheap models for small things like keeping track of the code and git changes
Other better supported models for the code changes, ones that can correctly use udiff etc
Then large more complex models for the overall process and "architect" role.
Cline doesn't support this.
So I find myself swapping between models via https://openroter.ai to do different tasks.
o1 to build a plan / tasks and then haiku 3.5 for the initial scaffolding
Generally it's Sonnet and when I'm up in the millions of tokens flying about, that racks up the $$$.
See when it edits a file, it tries to essentially only send and get back the changes or diff. However, quite often Sonnet breaks and misfits a file and it tries to do the whole file replace.
That starts to rack up the tokens
Ask it to stop dropping / excluding the code that hadn't changed and before you know it you are $20 deep in wasted tokens
And Sonnet is the best, the others are worse.