From 8da7a71d9a94935910908ac5cd9ab656d538e28b Mon Sep 17 00:00:00 2001 From: Brandon Keiji Date: Tue, 13 May 2025 17:49:45 +0000 Subject: refactor: shorten 'gemini' binary name (#329) --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index ebf81a80..b2ef1eb4 100644 --- a/README.md +++ b/README.md @@ -62,7 +62,7 @@ Alternatively, you can use the "Launch Program" configuration in VS Code if you ## Using Gemini Code source in other directories -To test your local version of `gemini-code` in other directories on your system, you can use `npm link`. Note, this is not the same as globally installing the released version of Gemini Code via `npm install -g @gemini-code/cli`. Rather, this creates a global symlink to your local project. +To test your local version of `gemini` in other directories on your system, you can use `npm link`. Note, this is not the same as globally installing the released version of Gemini Code via `npm install -g @gemini-code/cli`. Rather, this creates a global symlink to your local project. From the root of this repository, run: @@ -70,16 +70,16 @@ From the root of this repository, run: npm link packages/cli ``` -Then, navigate to any other directory where you want to use your local `gemini-code` and run: +Then, navigate to any other directory where you want to use your local `gemini` and run: ```bash -gemini-code +gemini ``` To breakpoint inside the sandbox container run: ```bash -DEBUG=1 gemini-code +DEBUG=1 gemini ``` Note that using `npm link` simulates a production environment. If you are testing sandboxed mode via `npm link`, you must run the full build with `npm run build:all` from the repository root after any code changes to ensure the linked version is up to date. -- cgit v1.2.3