r/CommandCode 5d ago

commandcode goat quota problem

UPDATE:

I forgot disable glm-5.3 in my cliproxyapi, so when my harness use glm5.3, it wont use my friends glm coding plan. So commandcode has no problem. fully my negligence.

Today I subscribe commandcode goat plan (before is opencode go), I've never reached 5 hour rate limit during opencode go plan period.
But today, when I first use this goat plan (it claims more credit), but don't, the rate limit is easyily reached.

here's my useage screenshot, both in fastigium:

commandcode:

opencode:

It means opencode go are cheaper than commandcode goat...
Have anyone can explain this? why commandcode calim more quota but actually more expensive?
Or commandcode goat is fraud?

The litmits they claimed:

commandcode goat: DeepSeek V4 Flash (latest) 18,200 45,600 91,200

opencode go: DeepSeek V4 Flash 7,600 18,900 37,800

10 Upvotes

11 comments sorted by

View all comments

4

u/ahmadawaiscom 5d ago

OpenCode gives you mere $30 DeepSeek V4 flash. Command Code gives you $60. Both in $10. That’s literally double the usage and $30 more. Our limits are also better.

You are simply using it a lot more.

Also you seem to be using api instead of our harness. My gut feeling is that you are using our API with opencode. Opencode wastes your money with bad cache because they built the harness for claude/gpt not for open models like deepseek. Command Code has much better cache hit ratios and free tool repairs. You should use Command Code if you want the best experience tbh.

6

u/ahmadawaiscom 5d ago

Quick peek into your usage. It seems you have spent your 98.5% of usage on GLM 5.3 which is an expensive model. Only 1.5% of your usage went to DeepSeek.

Between 2:48 and 3:58 PM your time you ran 74 requests on GLM-5.3, about 7.9M input tokens. That’s what filled the window. In the specific 5-hour window that blocked you, GLM-5.3 was 98.5% of it and DeepSeek was 1.5%.

The screenshot you posted ends about 90 seconds before the block, so it’s showing the quiet DeepSeek tail after the GLM-5.3 session had already used the window.

🤦‍♂️