Skip to content

Commit 9e5b34a

Browse files
committed
improve a post
1 parent b884b4d commit 9e5b34a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

_posts/2025-06-27-using-cli-on-hpc.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ Click into the directory for the Node.js version you want (e.g., v20.15.1/).
3131
- Then when you trying to start Gemini, there's a authentication process, usually a webpage will pop out and you sign in. However now we are working with and HPC, which didn't have smooth link to webpages.
3232
- I did see google log in page opened on my local web browser, I signed in and grant permissions
3333
- Here's a tricky part, your browser will redirect to a localhost URL and show an error. This is expected. Copy this entire localhost URL.
34-
- Open another terminal (don't close the one that runs the Gemini), past the full localhost URL inside the quotes in this command `curl "http://localhost:XXXXX"`
34+
- Open another terminal **on the HPC** (while leaving the Gemini CLI running in the first one). Paste the full localhost URL you copied from your browser into the following command: `curl "http://localhost:XXXXX"`
3535
- The terminal running gemini will now be authenticated.
3636
- One more issue is that the `npx` command needs to be executed everytime log into the HPC. So I added a line to create an alias in the `~/.bashrc`: `alias gemini='npx https://github.com/google-gemini/gemini-cli'`. The good news is that you don't need to be authenticated again.
3737

0 commit comments

Comments
 (0)