> For comparison, let’s take two $20 subscriptions, one for GPT and one for Cursor. With gpt-6.1-sol, my 5-hour limit runs out after just a few requests. If I ask it to change a couple of lines in a readme file, that uses up 10% of the limit. If I ask it to change something in a large codebase, the entire limit gets used up just reading dozens of files, without writing a single line of code.

Either this is hyperbole or something is wrong. I tried 6.1 Sol for a significant chunk of non-critical work this week and did not encounter usage depletion like this. I ran several tests that went upward of 450K tokens without depleting the 5-hour window, though I didn’t pay attention to how much.

Either this person is exaggerating, or something is extremely wrong with their harness.

I’m equally confused that their solution was to switch to Luna and try to use the small and fast model for big coding tasks. They could have switched to Claude $20/month and had ample Opus usage right new.

Most of the complaints in this article could have been avoided by not using Luna and not using a configuration that’s blowing their quota out for unclear reasons.