MediaMetz/gemini-cli
1
0
Fork 0
mirror of https://github.com/google-gemini/gemini-cli.git synced 2026-03-10 22:21:22 -07:00
Code Issues Packages Projects Releases Wiki Activity
Files
aca034fdfec0ec29bdb47c5feaa4eafd6e68fac7
gemini-cli/package.json

78 lines
3.5 KiB
JSON
Raw Normal View History

Initial commit of Gemini Code CLI This commit introduces the initial codebase for the Gemini Code CLI, a command-line interface designed to facilitate interaction with the Gemini API for software engineering tasks. The code was migrated from a previous git repository as a single squashed commit. Core Features & Components: * **Gemini Integration:** Leverages the `@google/genai` SDK to interact with the Gemini models, supporting chat history, streaming responses, and function calling (tools). * **Terminal UI:** Built with Ink (React for CLIs) providing an interactive chat interface within the terminal, including input prompts, message display, loading indicators, and tool interaction elements. * **Tooling Framework:** Implements a robust tool system allowing Gemini to interact with the local environment. Includes tools for: * File system listing (`ls`) * File reading (`read-file`) * Content searching (`grep`) * File globbing (`glob`) * File editing (`edit`) * File writing (`write-file`) * Executing bash commands (`terminal`) * **State Management:** Handles the streaming state of Gemini responses and manages the conversation history. * **Configuration:** Parses command-line arguments (`yargs`) and loads environment variables (`dotenv`) for setup. * **Project Structure:** Organized into `core`, `ui`, `tools`, `config`, and `utils` directories using TypeScript. Includes basic build (`tsc`) and start scripts. This initial version establishes the foundation for a powerful CLI tool enabling developers to use Gemini for coding assistance directly in their terminal environment. --- Created by yours truly: __Gemini Code__
2025-04-15 21:41:08 -07:00
{
fix name in package.json
2025-05-29 18:25:52 +00:00
"name": "gemini-cli",
fix: point npmrc to dogfood artifact registry (#108)
2025-04-21 23:11:51 -07:00
"version": "0.1.0",
Configure linter + prettier. - This is based on existing expectations for TS code in Google-esc repos. - First part of the change (we have not run any linter or formatting commands). After this changeset goes in I'll do a mass changeset push. Fixes https://b.corp.google.com/issues/411384603
2025-04-17 17:57:39 -04:00
"type": "module",
Initial commit of Gemini Code CLI This commit introduces the initial codebase for the Gemini Code CLI, a command-line interface designed to facilitate interaction with the Gemini API for software engineering tasks. The code was migrated from a previous git repository as a single squashed commit. Core Features & Components: * **Gemini Integration:** Leverages the `@google/genai` SDK to interact with the Gemini models, supporting chat history, streaming responses, and function calling (tools). * **Terminal UI:** Built with Ink (React for CLIs) providing an interactive chat interface within the terminal, including input prompts, message display, loading indicators, and tool interaction elements. * **Tooling Framework:** Implements a robust tool system allowing Gemini to interact with the local environment. Includes tools for: * File system listing (`ls`) * File reading (`read-file`) * Content searching (`grep`) * File globbing (`glob`) * File editing (`edit`) * File writing (`write-file`) * Executing bash commands (`terminal`) * **State Management:** Handles the streaming state of Gemini responses and manages the conversation history. * **Configuration:** Parses command-line arguments (`yargs`) and loads environment variables (`dotenv`) for setup. * **Project Structure:** Organized into `core`, `ui`, `tools`, `config`, and `utils` directories using TypeScript. Includes basic build (`tsc`) and start scripts. This initial version establishes the foundation for a powerful CLI tool enabling developers to use Gemini for coding assistance directly in their terminal environment. --- Created by yours truly: __Gemini Code__
2025-04-15 21:41:08 -07:00
"workspaces": [
"packages/*"
],
"scripts": {
Windows: Refactor Shell Scripts to Node.js for Cross-Platform Compatibility (#784)
2025-06-09 12:19:42 -07:00
"generate": "node scripts/generate-git-commit-info.js",
"build": "node scripts/build.js",
"build:sandbox": "node scripts/build_sandbox.js",
feat: add build:sandbox and build:all npm scripts (#274)
2025-05-07 14:46:47 +00:00
"build:all": "npm run build && npm run build:sandbox",
Windows: Refactor Shell Scripts to Node.js for Cross-Platform Compatibility (#784)
2025-06-09 12:19:42 -07:00
"clean": "node scripts/clean.js",
feat: Enable npx execution directly from GitHub URL This commit modifies the packaging setup to allow the CLI to be executed directly from its GitHub URL using `npx`, for example: `npx https://github.com/google-gemini/gemini-cli` (once merged to main). This is achieved without requiring the bundle to be checked into the repository. Key changes and motivations: - Modify `scripts.prepare` to run `npm run bundle`: Ensures the CLI bundle is generated automatically when `npx` installs the package from a git URL. This replaces previous approaches (e.g., using `prepack`) which were not consistently triggered in the `npx` environment. - Update `scripts.bundle` to use a direct path for `esbuild` and externalize `sqlite3`: Using `node_modules/.bin/esbuild` provides a more reliable way to invoke the bundler. Externalizing `sqlite3` is crucial for correctly handling its native addon, preventing runtime errors. - Add `bin`, `files`, and root `sqlite3` dependency: - The `bin` field defines the `gemini` command. - The `files` array ensures the generated `bundle/` directory is recognized by npm. - `sqlite3` is added as a root dependency to ensure it's installed by `npx` when `gemini-code` is fetched, allowing the externalized module to be resolved. These changes collectively ensure that the necessary build artifacts are created on-the-fly during `npx` installation, providing a seamless execution experience directly from the GitHub repository URL.
2025-05-23 12:27:48 -07:00
"prepare": "npm run bundle",
Initial commit of Gemini Code CLI This commit introduces the initial codebase for the Gemini Code CLI, a command-line interface designed to facilitate interaction with the Gemini API for software engineering tasks. The code was migrated from a previous git repository as a single squashed commit. Core Features & Components: * **Gemini Integration:** Leverages the `@google/genai` SDK to interact with the Gemini models, supporting chat history, streaming responses, and function calling (tools). * **Terminal UI:** Built with Ink (React for CLIs) providing an interactive chat interface within the terminal, including input prompts, message display, loading indicators, and tool interaction elements. * **Tooling Framework:** Implements a robust tool system allowing Gemini to interact with the local environment. Includes tools for: * File system listing (`ls`) * File reading (`read-file`) * Content searching (`grep`) * File globbing (`glob`) * File editing (`edit`) * File writing (`write-file`) * Executing bash commands (`terminal`) * **State Management:** Handles the streaming state of Gemini responses and manages the conversation history. * **Configuration:** Parses command-line arguments (`yargs`) and loads environment variables (`dotenv`) for setup. * **Project Structure:** Organized into `core`, `ui`, `tools`, `config`, and `utils` directories using TypeScript. Includes basic build (`tsc`) and start scripts. This initial version establishes the foundation for a powerful CLI tool enabling developers to use Gemini for coding assistance directly in their terminal environment. --- Created by yours truly: __Gemini Code__
2025-04-15 21:41:08 -07:00
"test": "npm run test --workspaces",
feat: Publish test coverage summaries to PRs (#513)
2025-05-27 12:45:28 -07:00
"test:ci": "npm run test:ci --workspaces --if-present",
Preflight and integration npx (#1096)
2025-06-16 08:27:29 -07:00
"test:e2e": "npm run test:integration:sandbox:none -- --verbose --keep-output",
"test:integration:all": "npm run test:integration:sandbox:none && npm run test:integration:sandbox:docker && npm run test:integration:sandbox:podman",
"test:integration:sandbox:none": "GEMINI_SANDBOX=false node integration-tests/run-tests.js",
"test:integration:sandbox:docker": "GEMINI_SANDBOX=docker node integration-tests/run-tests.js",
"test:integration:sandbox:podman": "GEMINI_SANDBOX=podman node integration-tests/run-tests.js",
Windows: Refactor Shell Scripts to Node.js for Cross-Platform Compatibility (#784)
2025-06-09 12:19:42 -07:00
"start": "node scripts/start.js",
feat: Only show ctrl-s when idle (#1299)
2025-06-22 16:57:53 +01:00
"debug": "cross-env DEBUG=1 node --inspect-brk scripts/start.js",
Preflight and integration npx (#1096)
2025-06-16 08:27:29 -07:00
"lint:fix": "eslint . --fix && eslint integration-tests --fix",
"lint": "eslint . --ext .ts,.tsx && eslint integration-tests",
fix: Ensure filename is available for diff rendering in write-file This commit resolves a bug where the `write-file` operation could fail to render content due to a missing filename. The fix involves: - Ensuring `fileName` is consistently passed to `DiffRenderer.tsx` through `ToolConfirmationMessage.tsx`, `ToolMessage.tsx`, and `useGeminiStream.ts`. - Modifying `edit.ts` and `write-file.ts` to include `fileName` in the `FileDiff` object. - Expanding the `FileDiff` interface in `tools.ts` to include `fileName`. Additionally, this commit enhances the diff rendering by: - Adding syntax highlighting based on file extension in `DiffRenderer.tsx`. - Adding more language mappings to `getLanguageFromExtension` in `DiffRenderer.tsx`. - Added lots of tests for all the above. Fixes https://b.corp.google.com/issues/418125982
2025-05-15 23:51:53 -07:00
"typecheck": "npm run typecheck --workspaces --if-present",
infra: add multipackage support (#34)
2025-04-18 14:37:02 -07:00
"format": "prettier --write .",
Auth First Run (#1207) Co-authored-by: Tommaso Sciortino <sciortino@gmail.com> Co-authored-by: N. Taylor Mullen <ntaylormullen@google.com>
2025-06-19 16:52:22 -07:00
"preflight": "npm run clean && npm ci && npm run format && npm run lint:fix && npm run build && npm run typecheck && npm run test:ci",
feat: prototype publish sandbox script with npm package (#182)
2025-04-26 00:30:50 +00:00
"auth:npm": "npx google-artifactregistry-auth",
"auth:docker": "gcloud auth configure-docker us-west1-docker.pkg.dev",
"auth": "npm run auth:npm && npm run auth:docker",
Add bundling support. - This can now be invoked with `npm run bundle`, it creates a `bundle/` folder that has: - gemini.js - sandbox-macos-minimal.sb - sandbox-macos-strict.sb - shell.json - shell.md - This doesn't include any sort of automation for auto bundling pieces. It's just the root capability which we can weave into other locations. Fixes https://b.corp.google.com/issues/411432723
2025-05-08 16:09:26 -07:00
"prerelease:dev": "npm run prerelease:version --workspaces && npm run prerelease:deps --workspaces",
Windows: Refactor Shell Scripts to Node.js for Cross-Platform Compatibility (#784)
2025-06-09 12:19:42 -07:00
"bundle": "npm run generate && node esbuild.config.js && node scripts/copy_bundle_assets.js",
feat: publish root Dockerfile to our image registry (#599)
2025-05-29 21:01:44 +00:00
"build:cli": "npm run build --workspace packages/cli",
Refactor: Align build scripts with core package rename (#641)
2025-05-30 20:16:35 -07:00
"build:core": "npm run build --workspace packages/core",
"build:packages": "npm run build:core && npm run build:cli",
Windows: Refactor Shell Scripts to Node.js for Cross-Platform Compatibility (#784)
2025-06-09 12:19:42 -07:00
"build:docker": "node scripts/build_sandbox.js -s",
feat: publish root Dockerfile to our image registry (#599)
2025-05-29 21:01:44 +00:00
"prepare:cli-packagejson": "node scripts/prepare-cli-packagejson.js",
Windows: Refactor Shell Scripts to Node.js for Cross-Platform Compatibility (#784)
2025-06-09 12:19:42 -07:00
"publish:sandbox": "node scripts/publish-sandbox.js",
fix: publish @gemini-code/server (#605)
2025-05-29 23:55:34 +00:00
"publish:npm": "npm publish --workspaces ${NPM_PUBLISH_TAG:+--tag=$NPM_PUBLISH_TAG} ${NPM_DRY_RUN:+--dry-run}",
refactor: remove docker tagging step from sandbox publishing (#1223)
2025-06-19 12:19:39 -07:00
"publish:release": "npm run build:packages && npm run prepare:cli-packagejson && npm run build:docker && npm run publish:sandbox && npm run publish:npm",
Add a command for starting Gemini CLI with GCP telemetry (#1079) This command enables starting the application with GCP telemetry: ```shell npm run start:gcp ```
2025-06-15 21:28:29 -04:00
"telemetry": "node scripts/telemetry.js",
Use concurrently to run start script with GCP telemetry (#1329) ## TLDR Introduces the `concurrently` package to simplify the dev startup process with GCP telemetry enabled. ## Dive Deeper Previously, developers had to run the telemetry script and the main application start script in separate terminals. This change updates the `start:gcp` script to use `concurrently`, allowing both processes to be launched and managed with a single command. This improves the developer experience and reduces the chance of forgetting to start one of the required processes. ## Reviewer Test Plan Set the required environment variable: ```shell export OTLP_GOOGLE_CLOUD_PROJECT=<your-project-id> ``` Run the following command: ```shell npm run start:gcp ``` #750 cc @teeler
2025-06-23 18:01:22 -04:00
"start:gcp": "concurrently --raw --kill-others \"npm run telemetry -- --target=gcp\" \"npm start\""
feat: Enable npx execution directly from GitHub URL This commit modifies the packaging setup to allow the CLI to be executed directly from its GitHub URL using `npx`, for example: `npx https://github.com/google-gemini/gemini-cli` (once merged to main). This is achieved without requiring the bundle to be checked into the repository. Key changes and motivations: - Modify `scripts.prepare` to run `npm run bundle`: Ensures the CLI bundle is generated automatically when `npx` installs the package from a git URL. This replaces previous approaches (e.g., using `prepack`) which were not consistently triggered in the `npx` environment. - Update `scripts.bundle` to use a direct path for `esbuild` and externalize `sqlite3`: Using `node_modules/.bin/esbuild` provides a more reliable way to invoke the bundler. Externalizing `sqlite3` is crucial for correctly handling its native addon, preventing runtime errors. - Add `bin`, `files`, and root `sqlite3` dependency: - The `bin` field defines the `gemini` command. - The `files` array ensures the generated `bundle/` directory is recognized by npm. - `sqlite3` is added as a root dependency to ensure it's installed by `npx` when `gemini-code` is fetched, allowing the externalized module to be resolved. These changes collectively ensure that the necessary build artifacts are created on-the-fly during `npx` installation, providing a seamless execution experience directly from the GitHub repository URL.
2025-05-23 12:27:48 -07:00
},
"bin": {
"gemini": "bundle/gemini.js"
},
"files": [
"bundle/",
feat: Enable npx execution on tagged versions - Modify root package.json to allow publishing - Update "files" to include only essential bundled assets This change makes it possible to use npx with tagged versions of the gemini-cli package (e.g., npx https://github.com/google-gemini/gemini-cli@early-access). It removes "private: true" and refines the "files" array to ensure that only the necessary bundled assets are included when the package is fetched by npx, optimizing download size and ensuring correct execution.
2025-05-23 15:22:13 -07:00
"README.md",
Rollforward AST changes to unblock Sandboxing (#863)
2025-06-08 19:07:25 -07:00
"LICENSE"
feat: Enable npx execution directly from GitHub URL This commit modifies the packaging setup to allow the CLI to be executed directly from its GitHub URL using `npx`, for example: `npx https://github.com/google-gemini/gemini-cli` (once merged to main). This is achieved without requiring the bundle to be checked into the repository. Key changes and motivations: - Modify `scripts.prepare` to run `npm run bundle`: Ensures the CLI bundle is generated automatically when `npx` installs the package from a git URL. This replaces previous approaches (e.g., using `prepack`) which were not consistently triggered in the `npx` environment. - Update `scripts.bundle` to use a direct path for `esbuild` and externalize `sqlite3`: Using `node_modules/.bin/esbuild` provides a more reliable way to invoke the bundler. Externalizing `sqlite3` is crucial for correctly handling its native addon, preventing runtime errors. - Add `bin`, `files`, and root `sqlite3` dependency: - The `bin` field defines the `gemini` command. - The `files` array ensures the generated `bundle/` directory is recognized by npm. - `sqlite3` is added as a root dependency to ensure it's installed by `npx` when `gemini-code` is fetched, allowing the externalized module to be resolved. These changes collectively ensure that the necessary build artifacts are created on-the-fly during `npx` installation, providing a seamless execution experience directly from the GitHub repository URL.
2025-05-23 12:27:48 -07:00
],
Configure linter + prettier. - This is based on existing expectations for TS code in Google-esc repos. - First part of the change (we have not run any linter or formatting commands). After this changeset goes in I'll do a mass changeset push. Fixes https://b.corp.google.com/issues/411384603
2025-04-17 17:57:39 -04:00
"devDependencies": {
Add support for `.geminiignore` file (#757)
2025-06-05 10:15:27 -07:00
"@types/micromatch": "^4.0.9",
feat: add emphasis to tool confirmations (#502)
2025-05-23 05:28:31 +00:00
"@types/mime-types": "^2.1.4",
Checks for diff changes before displaying the code snippet (#751)
2025-06-05 06:48:03 -07:00
"@types/minimatch": "^5.1.2",
Feat: Add test coverage scripts and ignore reports (#477)
2025-05-21 17:03:22 -07:00
"@vitest/coverage-v8": "^3.1.1",
Use concurrently to run start script with GCP telemetry (#1329) ## TLDR Introduces the `concurrently` package to simplify the dev startup process with GCP telemetry enabled. ## Dive Deeper Previously, developers had to run the telemetry script and the main application start script in separate terminals. This change updates the `start:gcp` script to use `concurrently`, allowing both processes to be launched and managed with a single command. This improves the developer experience and reduces the chance of forgetting to start one of the required processes. ## Reviewer Test Plan Set the required environment variable: ```shell export OTLP_GOOGLE_CLOUD_PROJECT=<your-project-id> ``` Run the following command: ```shell npm run start:gcp ``` #750 cc @teeler
2025-06-23 18:01:22 -04:00
"concurrently": "^9.2.0",
Windows: Refactor Shell Scripts to Node.js for Cross-Platform Compatibility (#784)
2025-06-09 12:19:42 -07:00
"cross-env": "^7.0.3",
chore(deps-dev): bump esbuild from 0.23.1 to 0.25.0 (#872) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2025-06-12 06:21:50 +00:00
"esbuild": "^0.25.0",
Configure linter + prettier. - This is based on existing expectations for TS code in Google-esc repos. - First part of the change (we have not run any linter or formatting commands). After this changeset goes in I'll do a mass changeset push. Fixes https://b.corp.google.com/issues/411384603
2025-04-17 17:57:39 -04:00
"eslint": "^9.24.0",
"eslint-config-prettier": "^10.1.2",
"eslint-plugin-import": "^2.31.0",
add linter for checking license headers (and eslint --fix target to match, and fix missing license headers while we're here) (#62)
2025-04-20 17:16:25 -07:00
"eslint-plugin-license-header": "^0.8.0",
Configure linter + prettier. - This is based on existing expectations for TS code in Google-esc repos. - First part of the change (we have not run any linter or formatting commands). After this changeset goes in I'll do a mass changeset push. Fixes https://b.corp.google.com/issues/411384603
2025-04-17 17:57:39 -04:00
"eslint-plugin-react": "^7.37.5",
"eslint-plugin-react-hooks": "^5.2.0",
Preflight and integration npx (#1096)
2025-06-16 08:27:29 -07:00
"glob": "^10.4.5",
Configure linter + prettier. - This is based on existing expectations for TS code in Google-esc repos. - First part of the change (we have not run any linter or formatting commands). After this changeset goes in I'll do a mass changeset push. Fixes https://b.corp.google.com/issues/411384603
2025-04-17 17:57:39 -04:00
"globals": "^16.0.0",
Checks for diff changes before displaying the code snippet (#751)
2025-06-05 06:48:03 -07:00
"json": "^11.0.0",
fix: point npmrc to dogfood artifact registry (#108)
2025-04-21 23:11:51 -07:00
"lodash": "^4.17.21",
feat: add git branch name to footer (#589)
2025-05-28 23:30:05 +00:00
"memfs": "^4.17.2",
Configure linter + prettier. - This is based on existing expectations for TS code in Google-esc repos. - First part of the change (we have not run any linter or formatting commands). After this changeset goes in I'll do a mass changeset push. Fixes https://b.corp.google.com/issues/411384603
2025-04-17 17:57:39 -04:00
"prettier": "^3.5.3",
feat: add react dev tools (#143)
2025-04-24 01:16:15 +00:00
"react-devtools-core": "^4.28.5",
feat: add flag to customize package version during pre-release staging (#155)
2025-04-24 20:02:49 +00:00
"typescript-eslint": "^8.30.1",
Checks for diff changes before displaying the code snippet (#751)
2025-06-05 06:48:03 -07:00
"yargs": "^17.7.2"
}
Initial commit of Gemini Code CLI This commit introduces the initial codebase for the Gemini Code CLI, a command-line interface designed to facilitate interaction with the Gemini API for software engineering tasks. The code was migrated from a previous git repository as a single squashed commit. Core Features & Components: * **Gemini Integration:** Leverages the `@google/genai` SDK to interact with the Gemini models, supporting chat history, streaming responses, and function calling (tools). * **Terminal UI:** Built with Ink (React for CLIs) providing an interactive chat interface within the terminal, including input prompts, message display, loading indicators, and tool interaction elements. * **Tooling Framework:** Implements a robust tool system allowing Gemini to interact with the local environment. Includes tools for: * File system listing (`ls`) * File reading (`read-file`) * Content searching (`grep`) * File globbing (`glob`) * File editing (`edit`) * File writing (`write-file`) * Executing bash commands (`terminal`) * **State Management:** Handles the streaming state of Gemini responses and manages the conversation history. * **Configuration:** Parses command-line arguments (`yargs`) and loads environment variables (`dotenv`) for setup. * **Project Structure:** Organized into `core`, `ui`, `tools`, `config`, and `utils` directories using TypeScript. Includes basic build (`tsc`) and start scripts. This initial version establishes the foundation for a powerful CLI tool enabling developers to use Gemini for coding assistance directly in their terminal environment. --- Created by yours truly: __Gemini Code__
2025-04-15 21:41:08 -07:00
}
Reference in New Issue Copy Permalink