That’s great to know. I’ve come to the same conclusion. I’ve found that things work best when they happen right where I’m already working. Uploading files or recreating context in a web service adds friction, especially when everything is already available locally.

Ah, that makes sense. I’ve had similar luck with UI refactoring on cheaper models, mainly because you can quickly verify whether the output is right.

Came across this interesting article on the internals of Claude Code: https://medium.com/@outsightai/peeking-under-the-hood-of-cla... . The author redirected the LLM calls into LiteLLM to analyze how it behaves.

Ah, that’s interesting. Are there any parts of Claude Code that you feel could work differently or get in your way for these kinds of tasks?

Will check out Grok Code Fast - thanks for the pointer. In my experience, coding agents can swing a lot in quality depending on the model’s reasoning power. When the model starts making small but avoidable mistakes, the overhead tends to cancel out the benefit. Curious to see how Grok performs on multi-step coding tasks.