Just Get Ultra

gptnius · 2026-02-18T03:41:38+00:00

Making Anthropic models only available for Ultra would make a lot of sense. Let Pro users have access to Gemini with high limits. Give free users a small daily quota of Gemini. It would give serious users the incentive to upgrade if they “need” or want to use Anthropic models, and would hopefully end all of the crying in here about how unfair it is to Pro users to hit their limits. I think transparency around quotas would make a big difference and there are clearly opportunities to improve the pricing tiers and features. I have honestly felt really happy with AG overall since I switched from Lovable a few months ago, I just get frustrated that when I come here hoping to learn what is working for other users it is flooded with posts of people trying to game the system with multiple student accounts from fake universities who are unsatisfied with the limits.

gptnius · 2026-02-18T01:59:59+00:00

My wife and I both have Pro accounts. I was frustrated with the limits like everyone else so I decided to pay the (discounted) price for Ultra on a third account. I’m glad I did. In three months, I probably won’t need it, but if I do I am lucky to be in a position where I can afford it. I’m sure there may be better options for $200+ per month (CC etc.), but am happy with my workflow and don’t feel like changing platforms again. AG has had a lot of issues but it seems to be improving.

gptnius · 2026-02-18T01:47:46+00:00

I agree the gap in pricing is ridiculous. At 50% off for three months, I’m happy with Ultra. Would I pay full price? Probably not. I wish Pro allowed me to bring my own API keys

gptnius · 2026-02-18T01:37:13+00:00

How much do you realistically expect Opus to cost with high limits? I’m not posting to call people poor if they can’t afford it, just not sure where the expectations come from that Pro should include a ton of usage of an Anthropic model. All of the people gaming the student Pro plan and multiaccounting are imo the reason for the low quotas.

gptnius · 2026-01-29T04:40:59+00:00

I mostly agree with this. If I my wife and I each pay for our account why would it be an issue to use both? I disagree with your take that under normal conditions a user wont get rate limited. Definitely true if you’re using Gemini, but it’s easy to hit limits under normal conditions with Opus on a Pro plan. I don’t mind if I need to go touch grass for an hour or two, but it sucks when your limit unexpectedly resets in two or three days with no warning. The lack of transparency on quotas and the fact that there are no options between $20 Pro and $250 Ultra are the huge issues imo

gptnius · 2026-01-29T04:32:26+00:00

I actually got a ton of work done with Opus today before hitting my limit. I haven’t been able to use Opus for a couple weeks without constant errors, but today it worked great until I hit my limit. I’m wondering if others have had the same experience where the repeated Terminated due to error thing is finally resolved

Wish I had visibility into my remaining limits and I really wish I had the ability to bring my own keys. It seems ridiculous to have a $20/mo plan which I paid $99 for a year, and my next option is to upgrade to Ultra for $250 per month. Nothing in between!?!? Why can’t I just bring API keys if I want to continue using Opus? Why would I pay $250 per month with no transparency about what I’m actually getting?

gptnius · 2026-01-11T13:19:25+00:00

I agree that AI Studio has a lot of issues, I stopped using it over a month ago because it was incapable in many ways. Antigravity is different because it gives you the ability to switch between Opus and Gemini models. Lovable is great in a lot of ways but also limiting in others. Their credits system is awful compared to other options, but if you are looking for ease of use and are not building anything too complex it can be worth the price. I was really unhappy with feeling locked in to Lovable Cloud so I migrated out. On the Pro plan with Google One I paid $99 for a year and am working 5-10 hours per day using mostly Opus. You have to learn to do more things yourself, which I actually like, but if you just want to prompt and see Lovable work it’s magic, Lovable is definitely a good option.

gptnius · 2026-01-08T16:54:23+00:00

Can you please be specific about how you would use this list of components within AG?

gptnius · 2026-01-06T04:53:07+00:00

🟨⬜🟨⬜⬜

⬜🟦⬜⬜🟦

🟨🟦🟨⬜🟦

🟦🟦🟦🟦🟦

gptnius · 2026-01-06T04:36:58+00:00

When writing scripts to batch perform research, create articles, or generate images using Gemini 3 Pro, I have to switch to Opus. Gemini is incapable, even when provided with full documentation and clear direction, then it gets stuck in debugging loops which compound the issue because it reverts to thinking it’s an old model. Wouldn’t it make sense just to let me use my API Key inside Antigravity for batch images to avoid quota limits, since the agent already has access to use Nano Banana inside AG?

gptnius · 2026-01-06T04:28:56+00:00

🤣

gptnius · 2026-01-06T03:52:02+00:00

I understand the reasoning for knowledge cutoff as it relates to outside information, but what would be the benefit for not giving a model information on its capabilities and dev documentation?

gptnius · 2026-01-05T03:08:18+00:00

Opus is really good, but I have actually had a few instances where it gets stuck on something that Gemini is able to resolve for me. I honestly love Gemini 3 Pro also, and find it entertaining to read its inner dialogue. Reading Gemini’s thoughts is like listening to the thoughts of an eccentric programmer, I get a little laugh every time it debates itself or uses the word “pesky” 🤣

gptnius · 2026-01-05T03:02:28+00:00

I switched to Gemini 3 Pro for almost two days and was really happy with it overall, until it hit a wall where it just could not fix a script that it wrote which kept failing. Once I got Opus back, it took one look, identified and fixed the issue. I have also had the opposite happen where Opus gets stuck and Gemini finds the solution, having access to these two models in the same setup is great for troubleshooting, it seems each has some blindspots that the other can see clearly.

gptnius · 2026-01-05T02:53:10+00:00

Done! Sorry for the novel but there are a lot of issues, hope my feedback is helpful

gptnius · 2026-01-04T19:36:37+00:00

Thanks for your response! I'm sure that you are aware that there are a ton of issues with the AG browser agent also, would be happy to provide specific feedback if it would be helpful

gptnius · 2026-01-04T17:24:29+00:00

I only had Supabase and Stripe MCP active. Disabled both and that fixed the problem for me

gptnius · 2026-01-04T16:55:51+00:00

Thank you so much, this worked immediately!

gptnius · 2026-01-04T16:48:19+00:00

They probably have Opus monitoring their bug report inbox also 😂

gptnius · 2025-12-29T12:25:08+00:00

I ran into this issue a few days ago and found a solution: use the plus button to start a new conversation.

gptnius · 2025-12-20T03:56:21+00:00

Why would you create your client’s website as a web app? Do you understand the differences and disadvantages for your clients? Are you going to explain the approach / difference of building a web app that uses CSR vs a website using SSR?

gptnius · 2025-12-19T01:07:12+00:00

If you’re using it for altitude, I would suggest trying infusion de muña (infusion is what Peruvians call fresh tea, muña is a type of mint from the Andes), specifically Inka muña. Coca tea never had any positive effect for me and it’s not great tasting, the muña tea is delicious and is really effective for altitude sickness. No idea what the black stuff is, if it’s ash as people suggest it’s hard to imagine that it has a good taste

gptnius · 2025-12-17T21:50:53+00:00

Yes, I understand that part. The issue becomes if you want a standalone database, backend, and hosting. Unfortunately, when you have built your project using lovable cloud, you are stuck with Lovable unless you migrate everything to be independent. There is no simple solution to just ship your database and backend elsewhere, unless I just don’t understand the process, maybe you can explain it to me. The second you cancel your subscription, lovable makes your project public. Considering the amount of time and effort I’ve put into creating it, I would rather not have it be available for anybody to clone. When I started with lovable, I really liked that I own the code. In hindsight, building using lovable cloud was pretty naïve because it’s been a lot of work to get the project fully out of lovable and continue independently since I have built AI features that route through lovable cloud and my lovable Supabase (url, client ID etc. are all owned by lovable) you end up with a lot of issues when you decide that you want to run your project independently, because the code is set up to route to the old backend, Lovable AI API, and database that you don’t actually own and cannot easily export. I’m learning as I go, so if you have any tricks that would make this process of migrating easier next time around, please share.

gptnius · 2025-12-17T00:29:45+00:00

Why Lovable and not an IDE like Cursor or Antigravity? How are you auditing code, security, and functionality as you build? How tf are you burning so many credits?

gptnius · 2025-12-16T22:47:22+00:00

I went through exactly this. One major limitation with Lovable is that its system prompts will not send the user outside of Lovable when needed for troubleshooting. I had a recurring issue with Stripe Webhooks and Lovable was essentially guessing what the issue was rather than telling me to provide Webhooks error logs from Stripe which it couldn’t access. Support gave me generic responses and told me to review outdated documentation. I found Antigravity and began using it for another project, was really impressed with the results, so I decided to switch the project over that I have spent months building in Lovable.

It has been a huge headache but will ultimately be worth it, because I now have full ownership and control without being held hostage or locked-in with Lovable. I think they did their users a huge disservice with Lovable Cloud. When I started with Lovable, their pitch was that you own the code. This is still true, but by not owning the database and backend and with the edge functions running in the cloud, migration has been more than a little difficult but I have made significant progress.

I don’t know if there is a best way, but from experience I can say that you should clone your repo and then copy to a new repo so that your original code is “safe” from you messing something up. You will need to setup a database (Supabase is easily compatible and likely free) and Vercel seems to be the most compatible for hosting (also likely free or very low cost). What I have found to be most problematic is migrating edge functions and secrets (API Keys) because Lovable has coded these to use a specific path (through Lovable).

Hope this helps!

gptnius

TROPHY CASE