Live data from Hacker News

Gemini CLI

blog.google

561–570 of 820 posts

Re: Gemini CLI

#561

Earlier quoted context omitted.

It seems that you need to set up an env variable called GOOGLE_CLOUD_PROJECT https://github.com/google-gemini/gemini-cli/issues/1434 ... and other stuff.

The barrier to use this project is maddening. I went through all of the setup instructions and getting the workspace error for a personal gmail account. Googlers, we should not have to do all of this setup and prep work for a single account. Enterprise I get, but for a single user? This is insufferable.

Same story with me. It says for both Workspace and Personal accounts that they are Workspace.

Have you managed to overcome that?

Re: Gemini CLI

#562

Earlier quoted context omitted.

Using the Gemini CLI the first thing I tried to do was "Create GEMINI.md files to customize your interactions with Gemini." The command ran for about a minute before receiving a too many requests error. > You exceeded your current quota, please check your plan and billing details. For more information on this error, head to: https://ai.google.dev/gemini-api/docs/rate-limits . Discouraging

Super weird! I've been using it the last week, and never hit the quota limit for free users. We're having some capacity issues right now, but that should not affect the quota. Would love it if you can try tomorrow or so again!

[deleted]

Re: Gemini CLI

#563

Earlier quoted context omitted.

read my comment above. G Studio API is limited.

Ah I think I see based on the other comment but just to confirm - you want to use Vertex provided Gemini API endpoints without having to create a Google Cloud project. Is that correct? (I’m just trying to get as precise about the problem statement and what success looks like - that helps me figure out a path to the best solution.) Appreciate the feedback!

Yes! The main pain points I've faced are:

1. There should be no need to create a project to use the Vertex Gemini API. I know Google AI Studio doesn't need a project, but that API is limited compared to Vertex API, which brings me to the next point.

2. There should be one unified API, not two! That'll help scale products with ease. Currently Google recommends using Google AI Studio API for simple projects and one-off scripts, and Vertex for "real" projects. No other competitor does this (look at OpenAI for instance).

3. The OpenAI compatibility layer isn't complete and doesn't support other Gemini features that only the Gemini API supports (e.g,. setting safety level).

4. Devs should need to install only one package to use Google Gemini. Please get rid of gauth.

5. The documentation on Gemini API is fragmented. Ironically, Googling "gemini api doc" doesn't lead to the page that discusses how to get started easily and quickly.

Re: Gemini CLI

#564
post #243

If you use this, all of your code data will be sent to Google. From their terms: https://developers.google.com/gemini-code-assist/resources/p... When you use Gemini Code Assist for individuals, Google collects your prompts, related code, generated output, code edits, related feature usage information, and your feedback to provide, improve, and develop Google products and services and machine learning technologies. To…

Hey all, This is a really great discussion, and you've raised some important points. We realize the privacy policies for the Gemini CLI were confusing depending on how you log in, and we appreciate you calling that out. To clear everything up, we've put together a single doc that breaks down the Terms of Service and data policies for each account type, including an FAQ that covers the questions from this thread. Here…

Thanks for clarification!

Re: Gemini CLI

#566

Earlier quoted context omitted.

I wonder how much of this had to do with the context window size? Gemini’s window is 5x larger than Cladue’s. I’ve been using Claude for a side project for the past few weeks and I find that we really get into a groove planning or debugging something and then by the time we are ready to implement, we’ve run out of context window space. Despite my best efforts to write good /compact instructions, when it’s ready to ro…

Does /compact help with this? I ran out of context with claude code for the first time today, so looking for any tips. I'm trying to get better at the /resume and memories to try and get more value out of the tool.

I thought I read that best practice was to start a new session every time you work on a new feature / task. That’s what I’ve been doing. I also often ask Claude to update my readme and claude.md with details about architecture or how something works.

As for /compact, if I’m nearing the end of my context window (around 15%) and are still in the middle of something, I’ll give /compact very specific details about how and what to compact. Let’s say we are debugging an error - I might write something along the lines of “This session is about to close and we will continue debugging in next session. We will be debugging this error message [error message…]. Outline everything we’ve tried that didn’t work, make suggestions about what to try next, and outline any architecture or files that will be critical for this work. Everything else from earlier on in this session can be ignored.” I’ve had decent success with that. More so on debugging than trying to hand off all the details of a feature that’s being implemented.

Reminder: you need context space for compact, so leave a little head room.

Re: Gemini CLI

#567
Oh man I tried dual wielding with cursor, setting up a communication so they both can work at the same time on the same thing, got banned from cursor Then tried with windsurf, ran a bad shellscript without reading it, used up the limit instantly, kill the script, oh man somehow it's still not working either I used the daily limit in an impossible way despite the minute limit supposedly existing, or the way it communicated sidestepped it into a limbo where it is just permanently confused and thinks for 300s then cancels a "test" prompt in the cli

Re: Gemini CLI

#568
post #41

Hi - I work on this. Uptake is a steep curve right now, spare a thought for the TPUs today. Appreciate all the takes so far, the team is reading this thread for feedback. Feel free to pile on with bugs or feature requests we'll all be reading.

Google Gemini Google Gemini Ultra AI Studio Vertex AI Notebook LLM Jules All different products doing the sameish thing. I don’t know where to send users to do anything. They are all licensed differently. Bonkers town.

Is it really that confusing? Gemini is the equivalent of ChatGPT; AI Studio is for advanced users that want to control e.g. temperature; Vertex AI is the GCP integrated API; Notebook LLM is basically personal RAG; and Jules is a developer agent.

Many of these are not even remotely similar.

Re: Gemini CLI

#569

Earlier quoted context omitted.

Please, for the love of God, stop your models always answering with essays or littering code with tutorial style comments. Almost every task devolves into "now get rid of the comments". It seems impossible to prevent this. And thinking is stupid. "Show me how to generate a random number in python"... 15s later you get an answer.

They have to do that, it's how they think. If they were trained not to do that they'd produce lower quality code.

So why don't Claude and Open AI models do this?

Re: Gemini CLI

#570

Earlier quoted context omitted.

Please, for the love of God, stop your models always answering with essays or littering code with tutorial style comments. Almost every task devolves into "now get rid of the comments". It seems impossible to prevent this. And thinking is stupid. "Show me how to generate a random number in python"... 15s later you get an answer.

Take some time to understand how the technology works, and how you can configure it yourself when it comes to thinking budget. None of these problems sound familiar to me as a frequent user of LLMs.

Take some time to compare the output of Gemini vs other models instead of patronising people.
Post reply on HN