Merge pull request #1 from BlocksOrg/blocks/feature-resume-sessions

feat: Add --resume functionality for non-interactive sessions

Author: AlejandroEsquivel

.github/workflows/release.yml

@@ -169,15 +169,15 @@ jobs:
           registry-url: 'https://wombat-dressing-room.appspot.com'
           scope: '@google'
 
-      - name: 'Publish @google/gemini-cli-core'
+      - name: 'Publish @blocksuser/gemini-cli-core'
         env:
           IS_DRY_RUN: '${{ steps.vars.outputs.is_dry_run }}'
           NODE_AUTH_TOKEN: '${{ secrets.WOMBAT_TOKEN_CORE }}'
           NPM_TAG: '${{ steps.version.outputs.NPM_TAG }}'
         run: |-
           npm publish \
             --dry-run="${IS_DRY_RUN}" \
-            --workspace="@google/gemini-cli-core" \
+            --workspace="@blocksuser/gemini-cli-core" \
             --tag="${NPM_TAG}"
 
       - name: 'Install latest core package'
@@ -186,19 +186,19 @@ jobs:
         env:
           RELEASE_VERSION: '${{ steps.version.outputs.RELEASE_VERSION }}'
         run: |-
-          npm install "@google/gemini-cli-core@${RELEASE_VERSION}" \
-          --workspace="@google/gemini-cli" \
+          npm install "@blocksuser/gemini-cli-core@${RELEASE_VERSION}" \
+          --workspace="@blocksuser/gemini-cli" \
           --save-exact
 
-      - name: 'Publish @google/gemini-cli'
+      - name: 'Publish @blocksuser/gemini-cli'
         env:
           IS_DRY_RUN: '${{ steps.vars.outputs.is_dry_run }}'
           NODE_AUTH_TOKEN: '${{ secrets.WOMBAT_TOKEN_CLI }}'
           NPM_TAG: '${{ steps.version.outputs.NPM_TAG }}'
         run: |-
           npm publish \
             --dry-run="${IS_DRY_RUN}" \
-            --workspace="@google/gemini-cli" \
+            --workspace="@blocksuser/gemini-cli" \
             --tag="${NPM_TAG}"
 
       - name: 'Create GitHub Release and Tag'

README.md

@@ -1,7 +1,7 @@
 # Gemini CLI
 
 [![Gemini CLI CI](https://github.com/google-gemini/gemini-cli/actions/workflows/ci.yml/badge.svg)](https://github.com/google-gemini/gemini-cli/actions/workflows/ci.yml)
-[![Version](https://img.shields.io/npm/v/@google/gemini-cli)](https://www.npmjs.com/package/@google/gemini-cli)
+[![Version](https://img.shields.io/npm/v/@blocksuser/gemini-cli)](https://www.npmjs.com/package/@blocksuser/gemini-cli)
 [![License](https://img.shields.io/github/license/google-gemini/gemini-cli)](https://github.com/google-gemini/gemini-cli/blob/main/LICENSE)
 
 ![Gemini CLI Screenshot](./docs/assets/gemini-screenshot.png)
@@ -31,7 +31,7 @@ npx https://github.com/google-gemini/gemini-cli
 #### Install globally with npm
 
 ```bash
-npm install -g @google/gemini-cli
+npm install -g @blocksuser/gemini-cli
 ```
 
 #### Install globally with Homebrew (macOS/Linux)
@@ -54,23 +54,23 @@ See [Releases](./docs/releases.md) for more details.
 New preview releases will be published each week at UTC 2359 on Tuesdays. These releases will not have been fully vetted and may contain regressions or other outstanding issues. Please help us test and install with `preview` tag.
 
 ```bash
-npm install -g @google/gemini-cli@preview
+npm install -g @blocksuser/gemini-cli@preview
 ```
 
 ### Stable
 
 - New stable releases will be published each week at UTC 2000 on Tuesdays, this will be the full promotion of last week's `preview` release + any bug fixes and validations. Use `latest` tag.
 
 ```bash
-npm install -g @google/gemini-cli@latest
+npm install -g @blocksuser/gemini-cli@latest
 ```
 
 ### Nightly
 
 - New releases will be published each week at UTC 0000 each day, This will be all changes from the main branch as represented at time of release. It should be assumed there are pending validations and issues. Use `nightly` tag.
 
 ```bash
-npm install -g @google/gemini-cli@nightly
+npm install -g @blocksuser/gemini-cli@nightly
 ```
 
 ## 📋 Key Features
@@ -289,7 +289,7 @@ Check our [Official Roadmap](https://github.com/orgs/google-gemini/projects/11/)
 ## 📖 Resources
 
 - **[Official Roadmap](./ROADMAP.md)** - See what's coming next
-- **[NPM Package](https://www.npmjs.com/package/@google/gemini-cli)** - Package registry
+- **[NPM Package](https://www.npmjs.com/package/@blocksuser/gemini-cli)** - Package registry
 - **[GitHub Issues](https://github.com/google-gemini/gemini-cli/issues)** - Report bugs or request features
 - **[Security Advisories](https://github.com/google-gemini/gemini-cli/security/advisories)** - Security updates
 

docs/Uninstall.md

@@ -33,10 +33,10 @@ Remove-Item -Path (Join-Path $env:LocalAppData "npm-cache\_npx") -Recurse -Force
 
 ## Method 2: Using npm (Global Install)
 
-If you installed the CLI globally (e.g., `npm install -g @google/gemini-cli`), use the `npm uninstall` command with the `-g` flag to remove it.
+If you installed the CLI globally (e.g., `npm install -g @blocksuser/gemini-cli`), use the `npm uninstall` command with the `-g` flag to remove it.
 
 ```bash
-npm uninstall -g @google/gemini-cli
+npm uninstall -g @blocksuser/gemini-cli
 ```
 
 This command completely removes the package from your system.

docs/deployment.md

@@ -15,7 +15,7 @@ This is the recommended way for end-users to install Gemini CLI. It involves dow
 - **Global install:**
 
   ```bash
-  npm install -g @google/gemini-cli
+  npm install -g @blocksuser/gemini-cli
   ```
 
   Then, run the CLI from anywhere:
@@ -28,7 +28,7 @@ This is the recommended way for end-users to install Gemini CLI. It involves dow
 
   ```bash
   # Execute the latest version from NPM without a global install
-  npx @google/gemini-cli
+  npx @blocksuser/gemini-cli
   ```
 
 ---
@@ -91,16 +91,16 @@ The execution methods described above are made possible by the following archite
 
 Gemini CLI project is a monorepo that publishes two core packages to the NPM registry:
 
-- `@google/gemini-cli-core`: The backend, handling logic and tool execution.
-- `@google/gemini-cli`: The user-facing frontend.
+- `@blocksuser/gemini-cli-core`: The backend, handling logic and tool execution.
+- `@blocksuser/gemini-cli`: The user-facing frontend.
 
 These packages are used when performing the standard installation and when running Gemini CLI from the source.
 
 **Build and packaging processes**
 
 There are two distinct build processes used, depending on the distribution channel:
 
-- **NPM publication:** For publishing to the NPM registry, the TypeScript source code in `@google/gemini-cli-core` and `@google/gemini-cli` is transpiled into standard JavaScript using the TypeScript Compiler (`tsc`). The resulting `dist/` directory is what gets published in the NPM package. This is a standard approach for TypeScript libraries.
+- **NPM publication:** For publishing to the NPM registry, the TypeScript source code in `@blocksuser/gemini-cli-core` and `@blocksuser/gemini-cli` is transpiled into standard JavaScript using the TypeScript Compiler (`tsc`). The resulting `dist/` directory is what gets published in the NPM package. This is a standard approach for TypeScript libraries.
 
 - **GitHub `npx` execution:** When running the latest version of Gemini CLI directly from GitHub, a different process is triggered by the `prepare` script in `package.json`. This script uses `esbuild` to bundle the entire application and its dependencies into a single, self-contained JavaScript file. This bundle is created on-the-fly on the user's machine and is not checked into the repository.
 

docs/npm.md

@@ -1,14 +1,14 @@
 # Package Overview
 
-This monorepo contains two main packages: `@google/gemini-cli` and `@google/gemini-cli-core`.
+This monorepo contains two main packages: `@blocksuser/gemini-cli` and `@blocksuser/gemini-cli-core`.
 
-## `@google/gemini-cli`
+## `@blocksuser/gemini-cli`
 
 This is the main package for the Gemini CLI. It is responsible for the user interface, command parsing, and all other user-facing functionality.
 
-When this package is published, it is bundled into a single executable file. This bundle includes all of the package's dependencies, including `@google/gemini-cli-core`. This means that whether a user installs the package with `npm install -g @google/gemini-cli` or runs it directly with `npx @google/gemini-cli`, they are using this single, self-contained executable.
+When this package is published, it is bundled into a single executable file. This bundle includes all of the package's dependencies, including `@blocksuser/gemini-cli-core`. This means that whether a user installs the package with `npm install -g @blocksuser/gemini-cli` or runs it directly with `npx @blocksuser/gemini-cli`, they are using this single, self-contained executable.
 
-## `@google/gemini-cli-core`
+## `@blocksuser/gemini-cli-core`
 
 This package contains the core logic for interacting with the Gemini API. It is responsible for making API requests, handling authentication, and managing the local cache.
 
@@ -34,4 +34,4 @@ This tells NPM that any folder inside the `packages` directory is a separate pac
 
 - **Simplified Dependency Management**: Running `npm install` from the root of the project will install all dependencies for all packages in the workspace and link them together. This means you don't need to run `npm install` in each package's directory.
 - **Automatic Linking**: Packages within the workspace can depend on each other. When you run `npm install`, NPM will automatically create symlinks between the packages. This means that when you make changes to one package, the changes are immediately available to other packages that depend on it.
-- **Simplified Script Execution**: You can run scripts in any package from the root of the project using the `--workspace` flag. For example, to run the `build` script in the `cli` package, you can run `npm run build --workspace @google/gemini-cli`.
+- **Simplified Script Execution**: You can run scripts in any package from the root of the project using the `--workspace` flag. For example, to run the `build` script in the `cli` package, you can run `npm run build --workspace @blocksuser/gemini-cli`.

docs/releases.md

@@ -9,23 +9,23 @@ We will follow https://semver.org/ as closely as possible but will call out when
 New preview releases will be published each week at UTC 2359 on Tuesdays. These releases will not have been fully vetted and may contain regressions or other outstanding issues. Please help us test and install with `preview` tag.
 
 ```bash
-npm install -g @google/gemini-cli@preview
+npm install -g @blocksuser/gemini-cli@preview
 ```
 
 ### Stable
 
 - New stable releases will be published each week at UTC 2000 on Tuesdays, this will be the full promotion of last week's release + any bug fixes and validations. Use `latest` tag.
 
 ```bash
-npm install -g @google/gemini-cli@latest
+npm install -g @blocksuser/gemini-cli@latest
 ```
 
 ### Nightly
 
 - New releases will be published each week at UTC 0000 each day, This will be all changes from the main branch as represted at time of release. It should be assumed there are pending validations and issues. Use `nightly` tag.
 
 ```bash
-npm install -g @google/gemini-cli@nightly
+npm install -g @blocksuser/gemini-cli@nightly
 ```
 
 # Release Process.
@@ -202,9 +202,9 @@ We also run a Google cloud build called [release-docker.yml](../.gcp/release-doc
 
 After pushing a new release smoke testing should be performed to ensure that the packages are working as expected. This can be done by installing the packages locally and running a set of tests to ensure that they are functioning correctly.
 
-- `npx -y @google/gemini-cli@latest --version` to validate the push worked as expected if you were not doing a rc or dev tag
-- `npx -y @google/gemini-cli@<release tag> --version` to validate the tag pushed appropriately
-- _This is destructive locally_ `npm uninstall @google/gemini-cli && npm uninstall -g @google/gemini-cli && npm cache clean --force &&  npm install @google/gemini-cli@<version>`
+- `npx -y @blocksuser/gemini-cli@latest --version` to validate the push worked as expected if you were not doing a rc or dev tag
+- `npx -y @blocksuser/gemini-cli@<release tag> --version` to validate the tag pushed appropriately
+- _This is destructive locally_ `npm uninstall @blocksuser/gemini-cli && npm uninstall -g @blocksuser/gemini-cli && npm cache clean --force &&  npm install @blocksuser/gemini-cli@<version>`
 - Smoke testing a basic run through of exercising a few llm commands and tools is recommended to ensure that the packages are working as expected. We'll codify this more in the future.
 
 ## Local Testing and Validation: Changes to the Packaging and Publishing Process

docs/sandbox.md

@@ -7,7 +7,7 @@ This document provides a guide to sandboxing in the Gemini CLI, including prereq
 Before using sandboxing, you need to install and set up the Gemini CLI:
 
 ```bash
-npm install -g @google/gemini-cli
+npm install -g @blocksuser/gemini-cli
 ```
 
 To verify the installation

docs/troubleshooting.md

@@ -27,7 +27,7 @@ This guide provides solutions to common issues and debugging tips, including top
 ## Frequently asked questions (FAQs)
 
 - **Q: How do I update Gemini CLI to the latest version?**
-  - A: If you installed it globally via `npm`, update it using the command `npm install -g @google/gemini-cli@latest`. If you compiled it from source, pull the latest changes from the repository, and then rebuild using the command `npm run build`.
+  - A: If you installed it globally via `npm`, update it using the command `npm install -g @blocksuser/gemini-cli@latest`. If you compiled it from source, pull the latest changes from the repository, and then rebuild using the command `npm run build`.
 
 - **Q: Where are the Gemini CLI configuration or settings files stored?**
   - A: The Gemini CLI configuration is stored in two `settings.json` files:
@@ -50,7 +50,7 @@ This guide provides solutions to common issues and debugging tips, including top
   - **Cause:** Gemini CLI is not correctly installed or it is not in your system's `PATH`.
   - **Solution:**
     The update depends on how you installed Gemini CLI:
-    - If you installed `gemini` globally, check that your `npm` global binary directory is in your `PATH`. You can update Gemini CLI using the command `npm install -g @google/gemini-cli@latest`.
+    - If you installed `gemini` globally, check that your `npm` global binary directory is in your `PATH`. You can update Gemini CLI using the command `npm install -g @blocksuser/gemini-cli@latest`.
     - If you are running `gemini` from source, ensure you are using the correct command to invoke it (e.g., `node packages/cli/dist/index.js ...`). To update Gemini CLI, pull the latest changes from the repository, and then rebuild using the command `npm run build`.
 
 - **Error: `MODULE_NOT_FOUND` or import errors.**

package.json

@@ -1,5 +1,5 @@
 {
-  "name": "@google/gemini-cli",
+  "name": "@blocksuser/gemini-cli",
   "version": "0.3.3",
   "engines": {
     "node": ">=20.0.0"
@@ -8,7 +8,6 @@
   "workspaces": [
     "packages/*"
   ],
-  "private": "true",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/google-gemini/gemini-cli.git"
@@ -18,7 +17,7 @@
   },
   "scripts": {
     "start": "node scripts/start.js",
-    "start:a2a-server": "CODER_AGENT_PORT=41242 npm run start --workspace @google/gemini-cli-a2a-server",
+    "start:a2a-server": "CODER_AGENT_PORT=41242 npm run start --workspace @blocksuser/gemini-cli-a2a-server",
     "debug": "cross-env DEBUG=1 node --inspect-brk scripts/start.js",
     "auth:npm": "npx google-artifactregistry-auth",
     "auth:docker": "gcloud auth configure-docker us-west1-docker.pkg.dev",

packages/a2a-server/package.json

@@ -1,5 +1,5 @@
 {
-  "name": "@google/gemini-cli-a2a-server",
+  "name": "@blocksuser/gemini-cli-a2a-server",
   "version": "0.3.3",
   "private": true,
   "description": "Gemini CLI A2A Server",
@@ -25,7 +25,7 @@
   "dependencies": {
     "@a2a-js/sdk": "^0.3.2",
     "@google-cloud/storage": "^7.16.0",
-    "@google/gemini-cli-core": "file:../core",
+    "@blocksuser/gemini-cli-core": "file:../core",
     "express": "^5.1.0",
     "fs-extra": "^11.3.0",
     "tar": "^7.4.3",