6.3 KiB

Raw Blame History

Gemini Code

Disclaimer: This README.md was created by gemini-code and this project was developed rapidly and currently lacks comprehensive testing, and other quality-of-life features common in mature projects.

This repository contains the Gemini Code CLI tool.

Setup

Get a Gemini API Key: Obtain your API key from Google AI Studio: https://aistudio.google.com/app/apikey
Set Environment Variable: Set the GEMINI_API_KEY environment variable to your obtained key. You can do this temporarily in your current shell session:
```
export GEMINI_API_KEY="YOUR_API_KEY"
```
Or add it to your shell's configuration file (like ~/.bashrc, ~/.zshrc, or ~/.profile) for persistence:
```
echo 'export GEMINI_API_KEY="YOUR_API_KEY"' >> ~/.bashrc # Or your preferred shell config file
source ~/.bashrc # Reload the config
```
Replace "YOUR_API_KEY" with your actual key.

Building

As with most Node projects, major development scripts can be found in the package.json. See that for the full list of commands.

Prerequisites:

The build toolchain requires npm and jq to be installed. You can use the scripts/setup-dev.sh script to install these prerequisites.

To build the entire project, CLI and Sandbox Container Image (if applicable), run the following command from the root directory:

npm install
npm run build:all

This command installs dependencies and builds the entire project, including the CLI and the Sandbox Container Image (if applicable). For a quick build without the sandbox container, you can use npm run build.

Running

To start the Gemini Code CLI, run the following command from the root directory:

npm start

This command starts the Gemini Code CLI.

Debugging

To debug the CLI application using VS Code:

Start the CLI in debug mode from the root directory:
```
npm run debug
```
This command runs node --inspect-brk dist/gemini.js within the packages/cli directory, pausing execution until a debugger attaches. You can then open chrome://inspect in your Chrome browser to connect to the debugger. Alternatively, you can achieve the same effect by running DEBUG=1 npm run start.
In VS Code, use the "Attach" launch configuration (found in .vscode/launch.json). This configuration is set up to attach to the Node.js process listening on port 9229, which is the default port used by --inspect-brk.

Alternatively, you can use the "Launch Program" configuration in VS Code if you prefer to launch the currently open file directly, but the "Attach" method is generally recommended for debugging the main CLI entry point.

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.

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:

gemini-code

To breakpoint inside the sandbox container run:

DEBUG=1 gemini-code

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.

Formatting

To format the code in this project, run the following command from the root directory:

npm run format

This command uses Prettier to format the code according to the project's style guidelines.

Linting

To lint the code in this project, run the following command fro the root directory:

npm run lint

Chances are you will need to manually address errors output. You can also try npm run lint -- --fix where some errors may be resolved.

Sandboxing

To enable sandboxing, set GEMINI_CODE_SANDBOX=true|docker|podman|<command> in your environment or .env file. Once enabled, npm run build:all will build a minimal container ("sandbox") image and npm start will launch inside a fresh instance of that container. Requires the specified command (or if true then either docker or podman) to be available on host machine.

The sandbox (container) mounts the current directory with read-write access and is started/stopped/removed automatically as you start/stop Gemini Code. You can tell you are inside the sandbox with the cwd being reported as /sandbox/<project>. Files created within the sandbox should be automatically mapped to your user/group on host machine.

The very first build of the container (with npm run build or scripts/build_sandbox.sh) can take 20-30s (mostly due to downloading of the base image) but after that both build and start overhead should be minimal (1-2s).

You can customize the sandbox in Dockerfile (e.g. for pre-installed utilities) or in scripts/build_sandbox.sh (e.g. for mounts -v ..., ports -p ..., or environment variables -e ...) and any changes should be automatically picked up by npm run build and npm start respectively.

Manual Publish

We publish an artifact for each commit to our internal registry. But if you need to manually cut a local build, then run the following commands:

npm run clean
npm install
npm run auth
npm run prerelease:dev
npm publish --workspaces

Attaching from VSCode

You can have VSCode (or forks) attach to a running sandbox using the Dev Containers extension. Simply use Dev Containers: Attach to Running Container ... command and select your container named gemini-code-sandbox-#. Once attached you can open the project folder at /sandbox/<project>. You may need to set the VSCode setting dev.containers.dockerPath (e.g. to podman) if you are not using Docker, and otherwise you may be prompted by the extension to install Docker if missing from your system.

6.3 KiB Raw Blame History