Earlier quoted context omitted.
odd, haven't seen that one - you might file an issue https://github.com/google-gemini/gemini-cli/issues I don't think that's capacity, you should see error codes.
This is happening to me as well, and it seems to be editing a slightly wrong file path which is presumably why the issue is occurring.
Gemini CLI
741–750 of 820 posts
Re: Gemini CLI
#742Npx again ;-( Why are people continuously using it for cli applications? While writing this comment, thinking that there should be some packaging tool that would create a binaries from npx cli tools. I remember such things for python. Binaries were fat, but it is better then keep nodejs installed on my OS
What's wrong with nodejs being installed on your OS?
- the cli runs in whatever your active (nvm, asdf, etc) is configured in that directory. So for each version of node you work in you need to install a different copy of gemini.
- if you work in an older version of nodejs, then you need to run 2 different versions of node (in different tabs) to use the tool and run your project.
Re: Gemini CLI
#743Google services have become a patchwork of painfully confounding marketing terms that mean nothing and obfuscate what they actually provide.
Re: Gemini CLI
#744Hi - 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.
There is one feature in Claude Code which is often overlooked and I haven't seen it in any of the other agentic tools: There is a tool called "sub-agent", which creates a fresh context windows in which the model can independently work on a clearly defined sub-task. This effectively turns Claude Code from a single-agent model to a hierarchical multi-agent model (I am not sure if the hierarchy goes to depths >2). I won…
various forms of this are being discussed, this commentary is helpful thanks!
Re: Gemini CLI
#745Hi - 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.
Thanks for building this! The tool shows a lot of promise. Coming from Claude Code, the core functionality feels solid - just needs some permission refinements to match enterprise use cases. This is based upon quickly skimming the current code. High ROI feature requests: • Pattern-based permissions - Bash(git: ) to allow git but not rm, Write(logs/ .txt) for path scoping • CLI permission flags - --allowedTools "Read,…
Re: Gemini CLI
#746I was rather disappointed and confused that the "Google One" or "Google AI Pro" subscription does not give you access to use Gemini API keys, and you can't use this Gemini CLI either. Google services have become a patchwork of painfully confounding marketing terms that mean nothing and obfuscate what they actually provide.
Whenever some enthusiastic developer suggests a new google service at work they are quickly dissuaded by senior developers that have been through their churn before.
Re: Gemini CLI
#747Earlier quoted context omitted.
> is so simple, that you don't need a package manager! You might not know the reason ppl use package managers. Installing this "simple" way make it quite difficult to update and remove compared to using package managers. And although they are also "simple", it's quite a mess to manage packages manually in place of using such battle-tested systems
> You might not know the reason ppl use package managers. People use package managers for the following: - to manage dependencies - to update stuff to a specific version or the latest version - to downgrade stuff - to install stuff - to remove stuff any of these, except for the dependency management, are a single command, or easy to do manually, with a single compiled binary. They are so simple that they can easily b…
pip is there so you don't need to do that. In the deployment world, you really want one version per system for everything and know that everything is in sync. To get that the solution was a distribution of software and a tool to manage them. We then extended that to programming language ecosystem and pip is part of the result.
But for workstation, a lot of people wants the latest, so the next solution was to be able to abstract the programming language ecosystem from the distribution (And you may not have a choice in the case of macOS), so what we get is directory-restricted interactions (go, npm,..) or doing shell magic so that the tooling think it's the system (virtual env,...).
It's a neat trick, but the only reason to do so is if you want to distribute compiled version of a software to customer. But if the user have access to the code, It's better to adapt the software to the system (repositories, flatpak...) or build a system around it (VM, containers, ...).
Re: Gemini CLI
#748Earlier quoted context omitted.
This whole thread is a great example of the developer vs. user convenience trade-off. A single, pre-compiled binary is convenient for the user's first install only.
> A single, pre-compiled binary is convenient for the user's first install only. Its not. Its convenient for CIs, for deployment, for packaging, for running multiple versions. It's extremely simple to update (just replace the binary with another one). Now, e.g. "just replacing one file with another" may not have convenience commands like "npm update". But its not hard. My point is that a pre-compiled binary is extrem…
The easiest is running "sudo apt update && sudo apt upgrade" and have my whole system updated. Instead of writing some script to get it done from some github's releases page and hoping that it's not hijacked.
Having a sensible project is what make it easy down the line (including not depending on gnu libc if not needed as some people uses musl). And I believe it's easy to setup a repository if your code is proprietary (Just need to support the most likely distribution, like ubuntu, fedora, suse's tumbleweed,...)
Re: Gemini CLI
#749It worked yesterday, but stopped today with "Failed to login. Ensure your Google account is not a Workspace account. Message: Resource has been exhausted (e.g. check quota). " I guess I will use something else. This is all very annoying given that I actually pay for Gemini Pro...
Re: Gemini CLI
#750Earlier quoted context omitted.
Sorry, that's not correct. Did you check out the link? It doesn't describe the CLI, only the IDE. "You can find the Gemini Code Assist for individuals privacy notice and settings in two ways: - VS Code - IntelliJ "
Sorry our docs were confusing! We tried to clear things up: https://github.com/google-gemini/gemini-cli/blob/main/docs/t...
Off-topic, but I wish this kind of plain language doc existed for Google One vs Google Workspace as well.