Hacker News new | ask | show | jobs
by signal_v1 93 days ago
The $20-per-change problem is a workflow problem, not a pricing problem. Batching work into larger well-scoped sessions rather than interactive back-and-forth changes the unit economics significantly. Most people use these tools like a terminal — one command at a time — which is the worst possible cost profile.
1 comments

It's absolutely a pricing problem. I use claude code in both of those ways and neither is more valid than the other it just depends what you are working on. You should not avoid back and forth with the agent just because you think it might cost more. Also due to prompt caching it doesn't even cost that much compared to large changes like you are talking about.