I think thats a Visual bug only, though maybe someone else saw it too?
in the usage Tab it shows Composer-1 Free
despite it being charged on request
anyone else? or was it always showing like that? (i dont use composer that much anymore when we have Opus Gemini PRo and GPT 5.1 being fast enough and smarter)
Hey @Eddy!
I can see the mismatch. I’ll make some noise about it!
Thank you Sir Colin
so is that an UI bug falsely displaying it as free?
It should be free as we announced some free composer credit to close out the year! And, it looks like the requests still show up as counting towards your request limit. I’ve flagged this for the team.
Oh i see, You guys are really awesome <3
thought im gonna be chillin end of the year but guess not. back to cursor ^^
Though to be honest, i dont use Composer much at all, so to skip you guys headache, just leave it be no need for the extra $10 credits there, am already more than satisfied with the gemini 3 and opus models <3
Hey why are we customers never being briefed about freebies?
A short newsletter would be sufficient!
ahha there might have been a notif somewhere, which i probably didnt see ^^
thought it was a bug too xD
try it out, if it works for you then awesome
It was announced in the UI!
But we agree, we could have made a bit more noise about it. Good feedback for next time. 
Announcing freebies in a temporary overlay dialog in a UI which is THAT broken is not a proper way to go.
eMail-Addresses are here for a reason, use them! It is the oldest and most solid solution to inform customers. You can easily build a workflow to announce news through that channel in under an hour.
Also:
I always want to know when and which models are in what state - free, unlimited, discontinued?, aso. .
I.e. you seemed to have removed GPT5 - Why??
I need that particular snapshot to verify/validate work being done by other versions/models and you took that ability away without a single word.
I don’t care what others say, i very much recognize particular and detailed behaviors from model to model, version to version and i’m adapting my workflow to these personalities. .Point.Number-steps in model versioning are mostly derivates from their major versions.
Thanks for considering my recommendations!
Hey @Smali
This is a community forum with lots of different categories available to express your feedback/concerns. Taking over this thread is not one of them.
This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.
