Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

So I start using it for my project and after about 20 mins - oh, no. Out of credits.

I didn't even get to try a single Gemini 3 prompt. I was out of credits before my first had completed. I guess I've burned through the free tier in some other app but the error message gave me no clues. As far as I can tell there's no link to give Google my money in the app. Maybe they think they have enough.

After switching to gpt-oss:120b it did some things quite well, and the annotation feature in the plan doc is really nice. It has potential but I suspect it's suffering from Google's typical problem that it's only really been tested on Googlers.

EDIT: Now it's stuck in a loop repeating the last thing it output. I've seen that a lot on gpt-oss models but you'd think a Google app would detect that and stop. :D

EDIT: I should know better than to beta test a FAANG app by now. I'm going back to Codex. :D



I logged into Gemini yesterday for the first time in ages. Made one image and then it said I was out of credits.

I complained to it that I had only made one image. It decided to make me one more! Then told me I was out of credits again.


What a time to be alive


> I complained to it that I had only made one image. It decided to make me one more!

What?! So was it only hallucinating that you were out of credits the first time?


More likely the credits system runs on eventual consistency, and he hit a different backend.


Don't think so, I expect that system to use Spanner, so my best guess is that the user generated an image at the end of the credit reset window (which is around noon EST).


If there's something I'd expect Google to use a strong consistency model for, it'd be a credit system like that.

Well, not that they don't do stupid things all the time, but having credits live on a system with a weak consistency model would be silly.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: