←back to thread

Gemini CLI

(blog.google)
1342 points sync | 1 comments | 25 Jun 25 13:10 UTC | HN request time: 0s | source
Show context
cperry ◴[25 Jun 25 13:50 UTC] No.44377336[source]▶
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.

replies(38): >>44377379 #>>44377463 #>>44377522 #>>44377570 #>>44377664 #>>44377874 #>>44378010 #>>44378095 #>>44378282 #>>44378477 #>>44378483 #>>44378624 #>>44378661 #>>44378918 #>>44378935 #>>44379294 #>>44379599 #>>44379809 #>>44379831 #>>44380039 #>>44380415 #>>44380918 #>>44380943 #>>44381462 #>>44381702 #>>44382998 #>>44383306 #>>44383505 #>>44384705 #>>44385575 #>>44385992 #>>44386024 #>>44386107 #>>44386388 #>>44387079 #>>44387136 #>>44387432 #>>44388145 #
ebiester ◴[25 Jun 25 14:02 UTC] No.44377463[source]▶
So, as a member of an organization who pays for google workspace with gemini, I get the message `GOOGLE_CLOUD_PROJECT environment variable not found. Add that to your .env and try again, no reload needed!`

At the very least, we need better documentation on how to get that environment variable, as we are not on GCP and this is not immediately obvious how to do so. At the worst, it means that your users paying for gemini don't have access to this where your general google users do.

replies(3): >>44377507 #>>44377677 #>>44381397 #
1. fooey ◴[25 Jun 25 20:12 UTC] No.44381397[source]▶
workspace accounts always seems like an unsupported mess at google, which is a very strange strategy