chore(release): v0.11.0

Co-authored-by: Victor May <mayvic@google.com>
Co-authored-by: matt korwel <matt.korwel@gmail.com>

.gemini/commands/core.toml

@@ -1,29 +0,0 @@
-description="Injects context of all relevant cli files"
-prompt = """
-The following output contains the complete
-source code of packages/core.
-**Pay extremely close attention to these files.** They define the project's
-core architecture, component patterns, and testing standards.
-
-The source code contains the content of absolutely every source code file in
-packages/core.
-You should very rarely need to read any other files from packages/core to resolve
-prompts.
-
-!{find packages/core \\( -path packages/cli/dist -o -path packages/core/dist -o -name node_modules \\) -prune -o -type f \\( -name "*.ts" -o -name "*.tsx" \\) ! -name "*.test.ts" ! -name "*.test.tsx" ! -name "*.d.ts" -exec echo "--- {} ---" \\; -exec cat {} \\;}
-
-In addition to the code context, you MUST strictly adhere to the following frontend-specific development guidelines when writing code in packages/core.
-
-## Configuration & Settings
-*   **Settings vs Args**: Use settings for user-configurable options; do not add new CLI arguments.
-*   **Schema**: Add new settings to `packages/cli/src/config/settingsSchema.ts`.
-*   **Documentation**:
-    *   If `showInDialog: true`, document in `docs/get-started/configuration.md`.
-    *   Ensure `requiresRestart` is correctly set.
-
-## General
-*   **Logging**: Use `debugLogger` for errors. NEVER leave `console.log/warn/error` in the code.
-*   **TypeScript**: Avoid the non-null assertion operator (`!`).
-
-{{args}}. 
- """

.gemini/commands/frontend.toml

@@ -1,54 +0,0 @@
-description="Injects context of all relevant cli files"
-prompt = """
-The source code contains the content of absolutely every source code file in
-packages/cli and key files from packages/core. In addition to the source code, the following test files are
-included as they are test files that conform to the project's testing standards:
-`packages/cli/src/ui/components/InputPrompt.test.tsx` and `packages/cli/src/ui/App.test.tsx`.
-You should very rarely need to read any other files from packages/cli to resolve
-prompts.
-
-!{find packages/cli -path packages/cli/dist -prune -o -type f \\( -name "*.ts" -o -name "*.tsx" \\) ! -name "*.test.ts" ! -name "*.test.tsx" ! -name "*.d.ts" -exec echo "--- {} ---" \\; -exec cat {} \\; && echo "--- packages/cli/src/ui/components/InputPrompt.test.tsx ---" && cat packages/cli/src/ui/components/InputPrompt.test.tsx && echo "--- packages/cli/src/ui/App.test.tsx ---" && cat packages/cli/src/ui/App.test.tsx && echo "--- packages/core/src/core/coreToolScheduler.ts ---" && cat packages/core/src/core/coreToolScheduler.ts && echo "--- packages/core/src/core/nonInteractiveToolExecutor.ts ---" && cat packages/core/src/core/nonInteractiveToolExecutor.ts && echo "--- packages/core/src/confirmation-bus/message-bus.ts ---" && cat packages/core/src/confirmation-bus/message-bus.ts && echo "--- packages/core/src/confirmation-bus/types.ts ---" && cat packages/core/src/confirmation-bus/types.ts && echo "--- packages/core/src/utils/events.ts ---" && cat packages/core/src/utils/events.ts && echo "--- packages/core/src/core/client.ts ---" && cat packages/core/src/core/client.ts && echo "--- packages/core/src/core/geminiChat.ts ---" && cat packages/core/src/core/geminiChat.ts && echo "--- packages/core/src/core/turn.ts ---" && cat packages/core/src/core/turn.ts && echo "--- packages/core/src/agents/executor.ts ---" && cat packages/core/src/agents/executor.ts && echo "--- packages/core/src/telemetry/types.ts ---" && cat packages/core/src/telemetry/types.ts && echo "--- packages/core/src/telemetry/loggers.ts ---" && cat packages/core/src/telemetry/loggers.ts && echo "--- packages/core/src/telemetry/uiTelemetry.ts ---" && cat packages/core/src/telemetry/uiTelemetry.ts}
-
-**Pay extremely close attention to these files.** They define the project's
-core architecture, component patterns, and testing standards.
-
-In addition to the code context, you MUST strictly adhere to the following frontend-specific development guidelines while adding code to packages/cli.
-
-## Testing Standards
-*   **Async Testing**: ALWAYS use `waitFor` from `packages/cli/src/test-utils/async.ts` instead of `vi.waitFor` to prevent flakiness and `act` warnings. NEVER use fixed waits (e.g., `await delay(100)`).
-*   **State Changes**: Wrap all blocks that change component state in `act`.
-*   **Snapshots**: Use `toMatchSnapshot` to verify rendering.
-*   **Rendering**: Use `render` or `renderWithProviders` from `packages/cli/src/test-utils/render.tsx` instead of `ink-testing-library` directly.
-*   **Mocking**:
-    *   Reuse existing mocks/fakes where possible.
-    *   **Parameterized Tests**: Use parameterized tests with explicit types to reduce duplication and ensure type safety.
-    *   Avoid mocking the file system, os, or child_process if at all possible; if you have to mock the Mock critical dependencies (`fs`, `os`, `child_process`) do so ONLY at the top of the file.
-
-## React & Ink Architecture
-*   **Keyboard Handling**: You MUST use `useKeyPress.ts` from Gemini CLI for keyboard handling, NOT the standard ink library. This is critical for supporting slow terminals and multiple events per frame.
-    *   Handle multiple events gracefully (often requires a reducer pattern, see `text-buffer.ts`).
-*   **State Management**:
-    *   NEVER trigger side effects from within the body of a `setState` callback. Use a reducer or `useRef` if necessary.
-    *   Initialize state explicitly (e.g., use `undefined` rather than `true` if unknown).
-*   **Performance**:
-    *   Avoid synchronous file I/O in components.
-    *   Do not introduce excessive property drilling; leverage or extend existing providers.
-
-## Configuration & Settings
-*   **Settings vs Args**: Use settings for user-configurable options; do not add new CLI arguments.
-*   **Schema**: Add new settings to `packages/cli/src/config/settingsSchema.ts`.
-*   **Documentation**:
-    *   If `showInDialog: true`, document in `docs/get-started/configuration.md`.
-    *   Ensure `requiresRestart` is correctly set.
-
-## Keyboard Shortcuts
-*   **Registration**: Define new shortcuts in `packages/cli/src/config/keyBindings.ts`.
-*   **Documentation**: Document all new shortcuts in `docs/cli/keyboard-shortcuts.md`.
-*   **Compatibility**: Avoid function keys and common VSCode shortcuts. Be cautious with `Meta` key (Mac-limited support).
-
-## General
-*   **Logging**: Use `debugLogger` for errors. NEVER leave `console.log/warn/error` in the code.
-*   **TypeScript**: Avoid the non-null assertion operator (`!`).
-
-{{args}}. 
- """

.gemini/commands/full-context.toml

@@ -1,57 +0,0 @@
-description="Injects context of all relevant cli files"
-prompt = """
-The following output contains the complete
-source code of the gemini cli library (`packages/cli`), and {packages/core} and representative test files
-(`packages/cli/src/ui/components/InputPrompt.test.tsx` and `packages/cli/src/ui/App.test.tsx`) that best conform to the project's testing standards.
-**Pay extremely close attention to these files.** They define the project's
-core architecture, component patterns, and testing standards.
-
-The source code contains the content of absolutely every source code file in
-packages/cli and packages/core. In addition to the source code, the following test files are
-included as they are test files that conform to the project's testing standards:
-`packages/cli/src/ui/components/InputPrompt.test.tsx` and `packages/cli/src/ui/App.test.tsx`.
-You should very rarely need to read any other files from packages/cli to resolve
-prompts.
-
-!{find packages/cli packages/core \\( -path packages/cli/dist -o -path packages/core/dist -o -name node_modules \\) -prune -o -type f \\( -name "*.ts" -o -name "*.tsx" \\) ! -name "*.test.ts" ! -name "*.test.tsx" ! -name "*.d.ts" -exec echo "--- {} ---" \\; -exec cat {} \\; && echo "--- packages/cli/src/ui/components/InputPrompt.test.tsx ---" && cat packages/cli/src/ui/components/InputPrompt.test.tsx && echo "--- packages/cli/src/ui/App.test.tsx ---" && cat packages/cli/src/ui/App.test.tsx}
-
-In addition to the code context, you MUST strictly adhere to the following frontend-specific development guidelines when writing code in packages/cli.
-
-## Testing Standards
-*   **Async Testing**: ALWAYS use `waitFor` from `packages/cli/src/test-utils/async.ts` instead of `vi.waitFor` to prevent flakiness and `act` warnings. NEVER use fixed waits (e.g., `await delay(100)`).
-*   **State Changes**: Wrap all blocks that change component state in `act`.
-*   **Snapshots**: Use `toMatchSnapshot` to verify rendering.
-*   **Rendering**: Use `render` or `renderWithProviders` from `packages/cli/src/test-utils/render.tsx` instead of `ink-testing-library` directly.
-*   **Mocking**:
-    *   Reuse existing mocks/fakes where possible.
-    *   **Parameterized Tests**: Use parameterized tests with explicit types to reduce duplication and ensure type safety.
-    *   Avoid mocking the file system, os, or child_process if at all possible; if you have to mock the Mock critical dependencies (`fs`, `os`, `child_process`) do so ONLY at the top of the file.
-
-## React & Ink Architecture
-*   **Keyboard Handling**: You MUST use `useKeyPress.ts` from Gemini CLI for keyboard handling, NOT the standard ink library. This is critical for supporting slow terminals and multiple events per frame.
-    *   Handle multiple events gracefully (often requires a reducer pattern, see `text-buffer.ts`).
-*   **State Management**:
-    *   NEVER trigger side effects from within the body of a `setState` callback. Use a reducer or `useRef` if necessary.
-    *   Initialize state explicitly (e.g., use `undefined` rather than `true` if unknown).
-*   **Performance**:
-    *   Avoid synchronous file I/O in components.
-    *   Do not introduce excessive property drilling; leverage or extend existing providers.
-
-## Configuration & Settings
-*   **Settings vs Args**: Use settings for user-configurable options; do not add new CLI arguments.
-*   **Schema**: Add new settings to `packages/cli/src/config/settingsSchema.ts`.
-*   **Documentation**:
-    *   If `showInDialog: true`, document in `docs/get-started/configuration.md`.
-    *   Ensure `requiresRestart` is correctly set.
-
-## Keyboard Shortcuts
-*   **Registration**: Define new shortcuts in `packages/cli/src/config/keyBindings.ts`.
-*   **Documentation**: Document all new shortcuts in `docs/cli/keyboard-shortcuts.md`.
-*   **Compatibility**: Avoid function keys and common VSCode shortcuts. Be cautious with `Meta` key (Mac-limited support).
-
-## General
-*   **Logging**: Use `debugLogger` for errors. NEVER leave `console.log/warn/error` in the code.
-*   **TypeScript**: Avoid the non-null assertion operator (`!`).
-
-{{args}}. 
- """

.gemini/commands/review-frontend.toml

@@ -1,140 +0,0 @@
-description="Reviews a pull request based on issue number."
-prompt = """
-Please provide a detailed pull request review on GitHub issue: {{args}}.
-
-Follow these steps:
-
-1. Use `gh pr view {{args}}` to pull the information of the PR.
-2. Use `gh pr diff {{args}}` to view the diff of the PR.
-3. Understand the intent of the PR using the PR description.
-4. If PR description is not detailed enough to understand the intent of the PR,
-   make sure to note it in your review.
-5. Make sure the PR title follows Conventional Commits, here are the last five
-   commits to the repo as examples: !{git log --pretty=format:"%s" -n 5}
-6. Search the codebase if required.
-7. Write a concise review of the PR, keeping in mind to encourage strong code
-   quality and best practices. Pay particular attention to the Gemini MD file
-   in the repo.
-8. Consider ways the code may not be consistent with existing code in the repo.
-   In particular it is critical that the react code uses patterns consistent
-   with existing code in the repo.
-9. Evaluate all tests on the PR and make sure that they are doing the following:
-   * Using `waitFor` from @{packages/cli/src/test-utils/async.ts} rather than
-     using `vi.waitFor` for all `waitFor` calls within `packages/cli`. Even if
-     tests pass, using the wrong `waitFor` could result in flaky tests as `act`
-     warnings could show up if timing is slightly different.
-   * Using `act` to wrap all blocks in tests that change component state.
-   * Using `toMatchSnapshot` to verify that rendering works as expected rather
-     than matching against the raw content of the output.
-   * If snapshots were changed as part of the pull request, review the snapshots
-     changes to ensure they are intentional and comment if any look at all
-     suspicious. Too many snapshot changes that indicate bugs have been approved
-     in the past.
-   * Use `render` or `renderWithProviders` from
-     @{packages/cli/src/test-utils/render.tsx} rather than using `render` from
-     `ink-testing-library` directly. This is needed to ensure that we do not get
-     warnings about spurious `act` calls. If test cases specify providers
-     directly, consider whether the existing `renderWithProviders` should be
-     modified to support that use case.
-   * Ensure the test cases are using parameterized tests where that might reduce
-     the number of duplicated lines significantly.
-   * NEVER use fixed waits (e.g. 'await delay(100)'). Always use 'waitFor' with
-     a predicate to ensure tests are stable and fast.
-   * Ensure mocks are properly managed:
-     * Critical dependencies (fs, os, child_process) should only be mocked at
-       the top of the file. Ideally avoid mocking these dependencies altogether.
-     * Check to see if there are existing mocks or fakes that can be used rather
-       than creating new ones for the new tests added.
-     * Try to avoid mocking the file system whenever possible. If using the real
-       file system is difficult consider whether the test should be an
-       integration test rather than a unit test.
-     * `vi.restoreAllMocks()` should be called in `afterEach` to prevent test
-       pollution.
-     * Use `vi.useFakeTimers()` for tests involving time-based logic to avoid
-       flakiness.
-     * Avoid using `any` in tests; prefer proper types or `unknown` with
-       narrowing.
-     * When creating parameterized tests, give the parameters types to ensure
-       that the tests are type-safe.
-10. Evaluate all react logic carefully keeping in mind that the author of the PR
-    is not likely an expert on React. Key areas to audit carefully are:
-    * Whether `setState` calls trigger side effects from within the body of the
-      `setState` callback. If so, you *must* propose an alternate design using
-      reducers or other ways the code might be modified to not have to modify
-      state from within a `setState`. Make sure to comment about absolutely
-      every case like this as these cases have introduced multiple bugs in the
-      past. Typically these cases should be resolved using a reducer although
-      occassionally other techniques such as useRef are appropriate. Consider
-      suggesting that jacob314@ be tagged on the code review if the solution is
-      not 100% obvious.
-    * Whether code might introduce an infinite rendering loop in React.
-    * Whether keyboard handling is robust. Keyboard handling must go through
-      `useKeyPress.ts` from the Gemini CLI package rather than using the
-      standard ink library used by most keyboard handling. Unlike the standard
-      ink library, the keyboard handling library in Gemini CLI may report
-      multiple keyboard events one after another in the same React frame. This
-      is needed to support slow terminals but introduces complexity in all our
-      code that handles keyboard events. Handling this correctly often means
-      that reducers must be used or other mechanisms to ensure that multiple
-      state updates one after another are handled gracefully rather than
-      overriding values from the first update with the second update. Refer to
-      text-buffer.ts as a canonical example of using a reducer for this sort of
-      case.
-    * Ensure code does not use `console.log`, `console.warn`, or `console.error`
-      as these indicate debug logging that was accidentally left in the code.
-    * Avoid synchronous file I/O in React components as it will hang the UI.
-    * Ensure state initialization is explicit (e.g., use 'undefined' rather than
-      'true' as a default if the state is truly unknown initially).
-    * Carefully manage 'useEffect' dependencies. Prefer to use a reducer
-      whenever practical to resolve the issues. If that is not practical it is
-      ok to use 'useRef' to access the latest value of a prop or state inside an
-      effect without adding it to the dependency array if re-running the effect
-      is undesirable (common in event listeners).
-    * NEVER disable 'react-hooks/exhaustive-deps'. Fix the code to correctly
-      declare dependencies. Disabling this lint rule will almost always lead to
-      hard to detect bugs.
-    * Avoid making types nullable unless strictly necessary, as it hurts
-      readability.
-    * Do not introduce excessive property drilling. There are multiple providers
-      that can be leveraged to avoid property drilling. Make sure one of them
-      cannot be used. Do suggest a provider that might make sense to be extended
-      to include the new property or propose a new provider to add if the
-      property drilling is excessive. Only use providers for properties that are
-      consistent for the entire application.
-11. General Gemini CLI design principles:
-    * Make sure that settings are only used for options that a user might
-      consider changing.
-    * Do not add new command line arguments and suggest settings instead.
-    * New settings must be added to packages/cli/src/config/settingsSchema.ts.
-    * If a setting has 'showInDialog: true', it MUST be documented in
-      docs/get-started/configuration.md.
-    * Ensure 'requiresRestart' is correctly set for new settings.
-    * Use 'debugLogger' for rethrown errors to avoid duplicate logging.
-    * All new keyboard shortcuts MUST be documented in
-      docs/cli/keyboard-shortcuts.md.
-    * Ensure new keyboard shortcuts are defined in
-      packages/cli/src/config/keyBindings.ts.
-    * If new keyboard shortcuts are added, remind the user to test them in
-      VSCode, iTerm2, Ghostty, and Windows to ensure they work for all
-      users.
-    * Be careful of keybindings that require the meta key as only certain
-      meta key shortcuts are supported on Mac.
-    * Be skeptical of function keys and keyboard shortcuts that are commonly
-      bound in VSCode as they may conflict.
-12. TypeScript Best Practices:
-    * Use 'checkExhaustive' in the 'default' clause of 'switch' statements to
-      ensure all cases are handled.
-    * Avoid using the non-null assertion operator ('!') unless absolutely
-      necessary and you are confident the value is not null.
-13. If the change might at all impact the prompts sent to Gemini CLI, flagged
-    that the change could impact Gemini CLI quality and make sure anj-s has been
-    tagged on the code review.
-14. Discuss with me before making any comments on the issue. I will clarify
-    which possible issues you identified are problems, which ones you need to
-    investigate further, and which ones I do not care about.
-15. If I request you to add comments to the issue, use
-    `gh pr comment {{args}} --body {{review}}` to post the review to the PR.
-
-Remember to use the GitHub CLI (`gh`) with the Shell tool for all
-GitHub-related tasks.
-"""

.github/CODEOWNERS

@@ -11,6 +11,3 @@
 /.github/workflows/ @google-gemini/gemini-cli-askmode-approvers
 /packages/cli/package.json @google-gemini/gemini-cli-askmode-approvers
 /packages/core/package.json @google-gemini/gemini-cli-askmode-approvers
-
-# Docs have a dedicated approver group in addition to maintainers
-/docs/ @google-gemini/gemini-cli-maintainers @google-gemini/gemini-cli-docs

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,6 +1,7 @@
 name: 'Bug Report'
 description: 'Report a bug to help us improve Gemini CLI'
 labels:
+  - 'kind/bug'
   - 'status/need-triage'
 body:
   - type: 'markdown'

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,8 +1,8 @@
 name: 'Feature Request'
 description: 'Suggest an idea for this project'
 labels:
+  - 'kind/enhancement'
   - 'status/need-triage'
-type: 'Feature'
 body:
   - type: 'markdown'
     attributes:

.github/ISSUE_TEMPLATE/website_issue.yml

@@ -1,7 +1,8 @@
 name: 'Website issue'
 description: 'Report an issue with the Gemini CLI Website and Gemini CLI Extensions Gallery'
 labels:
-  - 'area/extensions'
+  - 'area/website'
+  - 'status/need-triage'
 body:
   - type: 'markdown'
     attributes:

.github/actions/publish-release/action.yml

@@ -262,8 +262,7 @@ runs:
           --target "${{ steps.release_branch.outputs.BRANCH_NAME }}" \
           --title "Release ${{ inputs.release-tag }}" \
           --notes-start-tag "${{ inputs.previous-tag }}" \
-          --generate-notes \
-          ${{ inputs.npm-tag != 'latest' && '--prerelease' || '' }}
+          --generate-notes
 
     - name: '🧹 Clean up release branch'
       working-directory: '${{ inputs.working-directory }}'

.github/actions/push-docker/action.yml

@@ -75,4 +75,4 @@ runs:
         gh issue create \
           --title "Docker build failed" \
           --body "The docker build failed. See the full run for details: ${DETAILS_URL}" \
-          --label "release-failure"
+          --label "kind/bug,release-failure"

.github/actions/push-sandbox/action.yml

@@ -93,4 +93,4 @@ runs:
         gh issue create \
           --title "Docker build failed" \
           --body "The docker build failed. See the full run for details: ${DETAILS_URL}" \
-          --label "release-failure"
+          --label "kind/bug,release-failure"

.github/pull_request_template.md

@@ -1,42 +1,41 @@
-## Summary
+## TLDR
 
-<!-- Concisely describe what this PR changes and why. Focus on impact and
-urgency. -->
+<!-- Add a brief description of what this pull request changes and why and any important things for reviewers to look at -->
 
-## Details
+## Dive Deeper
 
-<!-- Add any extra context and design decisions. Keep it brief but complete. -->
+<!-- more thoughts and in-depth discussion here -->
 
-## Related Issues
+## Reviewer Test Plan
 
-<!-- Use keywords to auto-close issues (Closes #123, Fixes #456). If this PR is
-only related to an issue or is a partial fix, simply reference the issue number
-without a keyword (Related to #123). -->
+<!-- when a person reviews your code they should ideally be pulling and running that code. How would they validate your change works and if relevant what are some good classes of example prompts and ways they can exercise your changes -->
 
-## How to Validate
+## Testing Matrix
 
-<!-- List exact steps for reviewers to validate the change. Include commands,
-expected results, and edge cases. -->
+<!-- Before submitting please validate your changes on as many of these options as possible -->
 
-## Pre-Merge Checklist
+|          | 🍏  | 🪟  | 🐧  |
+| -------- | --- | --- | --- |
+| npm run  | ❓  | ❓  | ❓  |
+| npx      | ❓  | ❓  | ❓  |
+| Docker   | ❓  | ❓  | ❓  |
+| Podman   | ❓  | -   | -   |
+| Seatbelt | ❓  | -   | -   |
 
-<!-- Check all that apply before requesting review or merging. -->
+## Linked issues / bugs
 
-- [ ] Updated relevant documentation and README (if needed)
-- [ ] Added/updated tests (if needed)
-- [ ] Noted breaking changes (if any)
-- [ ] Validated on required platforms/methods:
-  - [ ] MacOS
-    - [ ] npm run
-    - [ ] npx
-    - [ ] Docker
-    - [ ] Podman
-    - [ ] Seatbelt
-  - [ ] Windows
-    - [ ] npm run
-    - [ ] npx
-    - [ ] Docker
-  - [ ] Linux
-    - [ ] npm run
-    - [ ] npx
-    - [ ] Docker
+<!--
+Link to any related issues or bugs.
+
+**If this PR fully resolves the issue, use one of the following keywords to automatically close the issue when this PR is merged:**
+
+- Closes #<issue_number>
+- Fixes #<issue_number>
+- Resolves #<issue_number>
+
+*Example: `Resolves #123`*
+
+**If this PR is only related to an issue or is a partial fix, simply reference the issue number without a keyword:**
+
+*Example: `This PR makes progress on #456` or `Related to #789`*
+-->

.github/workflows/ci.yml

@@ -43,7 +43,7 @@ jobs:
       - id: 'merge-queue-ci-skipper'
         uses: 'cariad-tech/merge-queue-ci-skipper@1032489e59437862c90a08a2c92809c903883772' # ratchet:cariad-tech/merge-queue-ci-skipper@main
         with:
-          secret: '${{ secrets.GEMINI_CLI_ROBOT_GITHUB_PAT }}'
+          secret: '${{ secrets.GITHUB_TOKEN }}'
 
   lint:
     name: 'Lint'
@@ -90,26 +90,9 @@ jobs:
       - name: 'Run Prettier'
         run: 'node scripts/lint.js --prettier'
 
-      - name: 'Build docs prerequisites'
-        run: 'npm run predocs:settings'
-
-      - name: 'Verify settings docs'
-        run: 'npm run docs:settings -- --check'
-
       - name: 'Run sensitive keyword linter'
         run: 'node scripts/lint.js --sensitive-keywords'
 
-  link_checker:
-    name: 'Link Checker'
-    runs-on: 'ubuntu-latest'
-    steps:
-      - name: 'Checkout'
-        uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8' # ratchet:actions/checkout@v5
-      - name: 'Link Checker'
-        uses: 'lycheeverse/lychee-action@885c65f3dc543b57c898c8099f4e08c8afd178a2' # ratchet: lycheeverse/lychee-action@v2.6.1
-        with:
-          args: '--verbose --accept 200,503 ./**/*.md'
-          fail: true
   test_linux:
     name: 'Test (Linux)'
     runs-on: 'gemini-cli-ubuntu-16-core'
@@ -371,7 +354,6 @@ jobs:
     if: 'always()'
     needs:
       - 'lint'
-      - 'link_checker'
       - 'test_linux'
       - 'test_mac'
       - 'codeql'
@@ -381,7 +363,6 @@ jobs:
       - name: 'Check all job results'
         run: |
           if [[ (${{ needs.lint.result }} != 'success' && ${{ needs.lint.result }} != 'skipped') || \
-               (${{ needs.link_checker.result }} != 'success' && ${{ needs.link_checker.result }} != 'skipped') || \
                (${{ needs.test_linux.result }} != 'success' && ${{ needs.test_linux.result }} != 'skipped') || \
                (${{ needs.test_mac.result }} != 'success' && ${{ needs.test_mac.result }} != 'skipped') || \
                (${{ needs.codeql.result }} != 'success' && ${{ needs.codeql.result }} != 'skipped') || \

.github/workflows/deflake.yml

@@ -24,147 +24,13 @@ concurrency:
     ${{ github.ref != 'refs/heads/main' && !startsWith(github.ref, 'refs/heads/release/') }}
 
 jobs:
-  deflake_e2e_linux:
-    name: 'E2E Test (Linux) - ${{ matrix.sandbox }}'
+  deflake:
+    name: 'Deflake'
     runs-on: 'gemini-cli-ubuntu-16-core'
     strategy:
       fail-fast: false
-      matrix:
-        sandbox:
-          - 'sandbox:none'
-          - 'sandbox:docker'
-        node-version:
-          - '20.x'
-
     steps:
-      - name: 'Checkout'
-        uses: 'actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955' # ratchet:actions/checkout@v5
-        with:
-          ref: '${{ github.event.pull_request.head.sha }}'
-          repository: '${{ github.repository }}'
-
-      - name: 'Set up Node.js ${{ matrix.node-version }}'
-        uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020' # ratchet:actions-node@v4
-        with:
-          node-version: '${{ matrix.node-version }}'
-
-      - name: 'Install dependencies'
-        run: 'npm ci'
-
-      - name: 'Build project'
-        run: 'npm run build'
-
-      - name: 'Set up Docker'
-        if: "matrix.sandbox == 'sandbox:docker'"
-        uses: 'docker/setup-buildx-action@e468171a9de216ec08956ac3ada2f0791b6bd435' # ratchet:docker/setup-buildx-action@v3
-
-      - name: 'Run E2E tests'
-        env:
-          GEMINI_API_KEY: '${{ secrets.GEMINI_API_KEY }}'
-          IS_DOCKER: "${{ matrix.sandbox == 'sandbox:docker' }}"
-          KEEP_OUTPUT: 'true'
-          RUNS: '${{ github.event.inputs.runs }}'
-          TEST_NAME_PATTERN: '${{ github.event.inputs.test_name_pattern }}'
-          VERBOSE: 'true'
+      - name: 'Deflake'
         shell: 'bash'
         run: |
-          if [[ "${{ env.IS_DOCKER }}" == "true" ]]; then
-            npm run deflake:test:integration:sandbox:docker -- --runs="${{ env.RUNS }}" -- --testNamePattern "'${{ env.TEST_NAME_PATTERN }}'"
-          else
-            npm run deflake:test:integration:sandbox:none -- --runs="${{ env.RUNS }}" -- --testNamePattern "'${{ env.TEST_NAME_PATTERN }}'"
-          fi
-
-  deflake_e2e_mac:
-    name: 'E2E Test (macOS)'
-    runs-on: 'macos-latest'
-    steps:
-      - name: 'Checkout'
-        uses: 'actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955' # ratchet:actions/checkout@v5
-        with:
-          ref: '${{ github.event.pull_request.head.sha }}'
-          repository: '${{ github.repository }}'
-
-      - name: 'Set up Node.js 20.x'
-        uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020' # ratchet:actions-node@v4
-        with:
-          node-version: '20.x'
-
-      - name: 'Install dependencies'
-        run: 'npm ci'
-
-      - name: 'Build project'
-        run: 'npm run build'
-
-      - name: 'Fix rollup optional dependencies on macOS'
-        if: "runner.os == 'macOS'"
-        run: |
-          npm cache clean --force
-      - name: 'Run E2E tests (non-Windows)'
-        if: "runner.os != 'Windows'"
-        env:
-          GEMINI_API_KEY: '${{ secrets.GEMINI_API_KEY }}'
-          KEEP_OUTPUT: 'true'
-          RUNS: '${{ github.event.inputs.runs }}'
-          SANDBOX: 'sandbox:none'
-          TEST_NAME_PATTERN: '${{ github.event.inputs.test_name_pattern }}'
-          VERBOSE: 'true'
-        run: |
-          npm run deflake:test:integration:sandbox:none -- --runs="${{ env.RUNS }}" -- --testNamePattern "'${{ env.TEST_NAME_PATTERN }}'"
-
-  deflake_e2e_windows:
-    name: 'Slow E2E - Win'
-    runs-on: 'gemini-cli-windows-16-core'
-
-    steps:
-      - name: 'Checkout'
-        uses: 'actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955' # ratchet:actions/checkout@v5
-        with:
-          ref: '${{ github.event.pull_request.head.sha }}'
-          repository: '${{ github.repository }}'
-
-      - name: 'Set up Node.js 20.x'
-        uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020' # ratchet:actions-node@v4
-        with:
-          node-version: '20.x'
-          cache: 'npm'
-
-      - name: 'Configure Windows Defender exclusions'
-        run: |
-          Add-MpPreference -ExclusionPath $env:GITHUB_WORKSPACE -Force
-          Add-MpPreference -ExclusionPath "$env:GITHUB_WORKSPACE\node_modules" -Force
-          Add-MpPreference -ExclusionPath "$env:GITHUB_WORKSPACE\packages" -Force
-          Add-MpPreference -ExclusionPath "$env:TEMP" -Force
-        shell: 'pwsh'
-
-      - name: 'Configure npm for Windows performance'
-        run: |
-          npm config set progress false
-          npm config set audit false
-          npm config set fund false
-          npm config set loglevel error
-          npm config set maxsockets 32
-          npm config set registry https://registry.npmjs.org/
-        shell: 'pwsh'
-
-      - name: 'Install dependencies'
-        run: 'npm ci'
-        shell: 'pwsh'
-
-      - name: 'Build project'
-        run: 'npm run build'
-        shell: 'pwsh'
-
-      - name: 'Run E2E tests'
-        env:
-          GEMINI_API_KEY: '${{ secrets.GEMINI_API_KEY }}'
-          KEEP_OUTPUT: 'true'
-          SANDBOX: 'sandbox:none'
-          VERBOSE: 'true'
-          NODE_OPTIONS: '--max-old-space-size=32768 --max-semi-space-size=256'
-          UV_THREADPOOL_SIZE: '32'
-          NODE_ENV: 'test'
-          RUNS: '${{ github.event.inputs.runs }}'
-          TEST_NAME_PATTERN: '${{ github.event.inputs.test_name_pattern }}'
-        shell: 'pwsh'
-        run: |
-          npm run deflake:test:integration:sandbox:none -- --runs="${{ env.RUNS }}" -- --testNamePattern "'${{ env.TEST_NAME_PATTERN }}'"
+          ECHO 'DEFLAKE WORKFLOW'

.github/workflows/e2e.yml

@@ -0,0 +1,245 @@
+name: 'Testing: E2E'
+
+on:
+  push:
+    branches:
+      - 'main'
+  # This will run for PRs from the base repository, providing secrets.
+  pull_request:
+    branches:
+      - 'main'
+      - 'release/**'
+  # This will run for PRs from forks when a label is added.
+  pull_request_target:
+    types: ['labeled']
+  merge_group:
+  workflow_dispatch:
+    inputs:
+      branch_ref:
+        description: 'Branch to run on'
+        required: true
+        default: 'main'
+        type: 'string'
+
+concurrency:
+  group: '${{ github.workflow }}-${{ github.head_ref || github.ref }}'
+  cancel-in-progress: |-
+    ${{ github.ref != 'refs/heads/main' && !startsWith(github.ref, 'refs/heads/release/') }}
+
+jobs:
+  merge_queue_skipper:
+    name: 'Merge Queue Skipper'
+    runs-on: 'gemini-cli-ubuntu-16-core'
+    outputs:
+      skip: '${{ steps.merge-queue-e2e-skipper.outputs.skip-check }}'
+    steps:
+      - id: 'merge-queue-e2e-skipper'
+        uses: 'cariad-tech/merge-queue-ci-skipper@1032489e59437862c90a08a2c92809c903883772' # ratchet:cariad-tech/merge-queue-ci-skipper@main
+        with:
+          secret: '${{ secrets.GITHUB_TOKEN }}'
+
+  e2e_linux:
+    name: 'E2E Test (Linux) - ${{ matrix.sandbox }}'
+    needs: 'merge_queue_skipper'
+    if: |
+      needs.merge_queue_skipper.outputs.skip == 'false' &&
+      (github.event_name == 'push' ||
+      github.event_name == 'merge_group' ||
+      github.event_name == 'workflow_dispatch' ||
+      (github.event.pull_request.head.repo.full_name == github.repository) ||
+      (github.event.label.name == 'maintainer:e2e:ok'))
+    runs-on: 'gemini-cli-ubuntu-16-core'
+    strategy:
+      fail-fast: false
+      matrix:
+        sandbox:
+          - 'sandbox:none'
+          - 'sandbox:docker'
+        node-version:
+          - '20.x'
+
+    steps:
+      - name: 'Checkout (fork)'
+        uses: 'actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955' # ratchet:actions/checkout@v5
+        if: "github.event_name == 'pull_request_target'"
+        with:
+          ref: '${{ github.event.pull_request.head.sha }}'
+          repository: '${{ github.event.pull_request.head.repo.full_name }}'
+
+      - name: 'Checkout (internal)'
+        uses: 'actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955' # ratchet:actions/checkout@v5
+        if: "github.event_name != 'pull_request_target'"
+        with:
+          ref: '${{ github.event.inputs.branch_ref || github.ref }}'
+
+      - name: 'Set up Node.js ${{ matrix.node-version }}'
+        uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020' # ratchet:actions-node@v4
+        with:
+          node-version: '${{ matrix.node-version }}'
+
+      - name: 'Install dependencies'
+        run: 'npm ci'
+
+      - name: 'Build project'
+        run: 'npm run build'
+
+      - name: 'Set up Docker'
+        if: "matrix.sandbox == 'sandbox:docker'"
+        uses: 'docker/setup-buildx-action@e468171a9de216ec08956ac3ada2f0791b6bd435' # ratchet:docker/setup-buildx-action@v3
+
+      - name: 'Run E2E tests'
+        env:
+          GEMINI_API_KEY: '${{ secrets.GEMINI_API_KEY }}'
+          KEEP_OUTPUT: 'true'
+          VERBOSE: 'true'
+        shell: 'bash'
+        run: |
+          if [[ "${{ matrix.sandbox }}" == "sandbox:docker" ]]; then
+            npm run test:integration:sandbox:docker
+          else
+            npm run test:integration:sandbox:none
+          fi
+
+  e2e_mac:
+    name: 'E2E Test (macOS)'
+    needs: 'merge_queue_skipper'
+    if: |
+      needs.merge_queue_skipper.outputs.skip == 'false' &&
+      (github.event_name == 'push' ||
+      github.event_name == 'merge_group' ||
+      github.event_name == 'workflow_dispatch' ||
+      (github.event.pull_request.head.repo.full_name == github.repository) ||
+      (github.event.label.name == 'maintainer:e2e:ok'))
+    runs-on: 'macos-latest'
+    steps:
+      - name: 'Checkout (fork)'
+        uses: 'actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955' # ratchet:actions/checkout@v5
+        if: "github.event_name == 'pull_request_target'"
+        with:
+          ref: '${{ github.event.pull_request.head.sha }}'
+          repository: '${{ github.event.pull_request.head.repo.full_name }}'
+
+      - name: 'Checkout (internal)'
+        uses: 'actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955' # ratchet:actions/checkout@v5
+        if: "github.event_name != 'pull_request_target'"
+        with:
+          ref: '${{ github.event.inputs.branch_ref || github.ref }}'
+
+      - name: 'Set up Node.js 20.x'
+        uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020' # ratchet:actions-node@v4
+        with:
+          node-version: '20.x'
+
+      - name: 'Install dependencies'
+        run: 'npm ci'
+
+      - name: 'Build project'
+        run: 'npm run build'
+
+      - name: 'Fix rollup optional dependencies on macOS'
+        if: "runner.os == 'macOS'"
+        run: |
+          npm cache clean --force
+      - name: 'Run E2E tests (non-Windows)'
+        if: "runner.os != 'Windows'"
+        env:
+          GEMINI_API_KEY: '${{ secrets.GEMINI_API_KEY }}'
+          KEEP_OUTPUT: 'true'
+          SANDBOX: 'sandbox:none'
+          VERBOSE: 'true'
+        run: 'npm run test:integration:sandbox:none'
+
+  e2e_windows:
+    name: 'Slow E2E - Win'
+    needs: 'merge_queue_skipper'
+    if: |
+      needs.merge_queue_skipper.outputs.skip == 'false' &&
+      (github.event_name == 'push' ||
+      github.event_name == 'merge_group' ||
+      github.event_name == 'workflow_dispatch' ||
+      (github.event.pull_request.head.repo.full_name == github.repository) ||
+      (github.event.label.name == 'maintainer:e2e:ok'))
+    runs-on: 'gemini-cli-windows-16-core'
+    continue-on-error: true
+
+    steps:
+      - name: 'Checkout (fork)'
+        uses: 'actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955' # ratchet:actions/checkout@v5
+        if: "github.event_name == 'pull_request_target'"
+        with:
+          ref: '${{ github.event.pull_request.head.sha }}'
+          repository: '${{ github.event.pull_request.head.repo.full_name }}'
+
+      - name: 'Checkout (internal)'
+        uses: 'actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955' # ratchet:actions/checkout@v5
+        if: "github.event_name != 'pull_request_target'"
+        with:
+          ref: '${{ github.event.inputs.branch_ref || github.ref }}'
+
+      - name: 'Set up Node.js 20.x'
+        uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020' # ratchet:actions-node@v4
+        with:
+          node-version: '20.x'
+          cache: 'npm'
+
+      - name: 'Configure Windows Defender exclusions'
+        run: |
+          Add-MpPreference -ExclusionPath $env:GITHUB_WORKSPACE -Force
+          Add-MpPreference -ExclusionPath "$env:GITHUB_WORKSPACE\node_modules" -Force
+          Add-MpPreference -ExclusionPath "$env:GITHUB_WORKSPACE\packages" -Force
+          Add-MpPreference -ExclusionPath "$env:TEMP" -Force
+        shell: 'pwsh'
+
+      - name: 'Configure npm for Windows performance'
+        run: |
+          npm config set progress false
+          npm config set audit false
+          npm config set fund false
+          npm config set loglevel error
+          npm config set maxsockets 32
+          npm config set registry https://registry.npmjs.org/
+        shell: 'pwsh'
+
+      - name: 'Install dependencies'
+        run: 'npm ci'
+        shell: 'pwsh'
+
+      - name: 'Build project'
+        run: 'npm run build'
+        shell: 'pwsh'
+
+      - name: 'Run E2E tests'
+        env:
+          GEMINI_API_KEY: '${{ secrets.GEMINI_API_KEY }}'
+          KEEP_OUTPUT: 'true'
+          SANDBOX: 'sandbox:none'
+          VERBOSE: 'true'
+          NODE_OPTIONS: '--max-old-space-size=32768 --max-semi-space-size=256'
+          UV_THREADPOOL_SIZE: '32'
+          NODE_ENV: 'test'
+        shell: 'pwsh'
+        run: 'npm run test:integration:sandbox:none'
+
+  e2e:
+    name: 'E2E'
+    if: |
+      always() && (
+        github.event_name == 'push' ||
+        github.event_name == 'merge_group' ||
+        github.event_name == 'workflow_dispatch' ||
+        (github.event.pull_request.head.repo.full_name == github.repository) ||
+        (github.event.label.name == 'maintainer:e2e:ok')
+      )
+    needs:
+      - 'e2e_linux'
+      - 'e2e_mac'
+    runs-on: 'gemini-cli-ubuntu-16-core'
+    steps:
+      - name: 'Check E2E test results'
+        run: |
+          if [[ (${{ needs.e2e_linux.result }} != 'success' && ${{ needs.e2e_linux.result }} != 'skipped') || \
+               (${{ needs.e2e_mac.result }} != 'success' && ${{ needs.e2e_mac.result }} != 'skipped') ]]; then
+            echo "One or more E2E jobs failed."
+            exit 1
+          fi
+          echo "All required E2E jobs passed!"

.github/workflows/gemini-automated-issue-triage.yml

@@ -39,13 +39,13 @@ jobs:
         github.event_name == 'workflow_dispatch' ||
         (
           (github.event_name == 'issues' || github.event_name == 'issue_comment') &&
+          contains(github.event.issue.labels.*.name, 'status/need-triage') &&
           (github.event_name != 'issue_comment' || (
             contains(github.event.comment.body, '@gemini-cli /triage') &&
             (github.event.comment.author_association == 'OWNER' || github.event.comment.author_association == 'MEMBER' || github.event.comment.author_association == 'COLLABORATOR')
           ))
         )
-      ) &&
-      !contains(github.event.issue.labels.*.name, 'area/')
+      )
     timeout-minutes: 5
     runs-on: 'ubuntu-latest'
     steps:
@@ -67,19 +67,14 @@ jobs:
             core.setOutput('labels', issue.labels.map(label => label.name).join(','));
             return issue;
 
-      - name: 'Manual Trigger Pre-flight Checks'
+      - name: 'Check for triage label on manual trigger'
         if: |-
-          github.event_name == 'workflow_dispatch'
+          github.event_name == 'workflow_dispatch' && !contains(steps.get_issue_data.outputs.labels, 'status/need-triage')
         env:
           ISSUE_NUMBER_INPUT: '${{ github.event.inputs.issue_number }}'
-          LABELS: '${{ steps.get_issue_data.outputs.labels }}'
         run: |
-          if echo "${LABELS}" | grep -q 'area/'; then
-            echo "Issue #${ISSUE_NUMBER_INPUT} already has 'area/' label. Stopping workflow."
-            exit 1
-          fi
-
-          echo "Manual triage checks passed."
+          echo "Issue #${ISSUE_NUMBER_INPUT} does not have the 'status/need-triage' label. Stopping workflow."
+          exit 1
 
       - name: 'Checkout'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8' # ratchet:actions/checkout@v5
@@ -102,17 +97,7 @@ jobs:
               owner: context.repo.owner,
               repo: context.repo.repo,
             });
-            const allowedLabels = [
-              'area/agent',
-              'area/enterprise',
-              'area/non-interactive',
-              'area/core',
-              'area/security',
-              'area/platform',
-              'area/extensions',
-              'area/unknown'
-            ];
-            const labelNames = labels.map(label => label.name).filter(name => allowedLabels.includes(name));
+            const labelNames = labels.map(label => label.name);
             core.setOutput('available_labels', labelNames.join(','));
             core.info(`Found ${labelNames.length} labels: ${labelNames.join(', ')}`);
             return labelNames;
@@ -141,6 +126,9 @@ jobs:
           settings: |-
             {
               "maxSessionTurns": 25,
+              "coreTools": [
+                "run_shell_command(echo)"
+              ],
               "telemetry": {
                 "enabled": true,
                 "target": "gcp"
@@ -149,100 +137,128 @@ jobs:
           prompt: |-
             ## Role
 
-            You are an issue triage assistant. Your role is to analyze a GitHub issue and determine the single most appropriate area/ label based on the definitions provided.
+            You are an issue triage assistant. Analyze the current GitHub issue
+            and identify the most appropriate existing labels by only using the provided data. Use the available
+            tools to gather information; do not ask for information to be
+            provided. Do not remove the following labels titled maintainer,  help wanted or good first issue.
 
             ## Steps
-            1. Review the issue title and body: ${{ env.ISSUE_TITLE }} and ${{ env.ISSUE_BODY }}.
-            2. Review the available labels: ${{ env.AVAILABLE_LABELS }}.
-            3. Select exactly one area/ label that best matches the issue based on Reference 1: Area Definitions.
-            4. Fallback Logic:
-                - If you cannot confidently determine the correct area/ label from the definitions, you must use area/unknown.
-            5. Output your selected label in JSON format and nothing else. Example:
-                {"labels_to_set": ["area/core"]}
+
+            1. You are only able to use the echo command. Review the available labels in the environment variable: "${AVAILABLE_LABELS}".
+            2. Review the issue title and body provided in the environment variables: "${ISSUE_TITLE}" and "${ISSUE_BODY}".
+            3. Select the most relevant labels from the existing labels, focusing on kind/*, area/*, sub-area/* and priority/*. For area/* and kind/* limit yourself to only the single most applicable label in each case.
+            4. If the issue already has area/ label, dont try to change it. Similarly, if the issue already has a kind/ label don't change it. And if the issue already has a priority/ label do not change it for example:
+               If an issue has area/core and kind/bug  you will only add a priority/ label.
+               Instead if an issue has no labels, you will could add one lable of each kind.
+            5. For each issue please check if CLI version is present, this is usually in the output of the /about command and will look like 0.1.5 for anything more than 6 versions older than the most recent should add the status/need-retesting label.
+            6. If you see that the issue doesn't look like it has sufficient information recommend the status/need-information label and leave a comment politely requesting the relevant information, eg.. if repro steps are missing request for repro steps. if version information is missing request for version information into the explanation section below.
+            7. Output the appropriate labels for this issue in JSON format with explanation, for example:
+               ```
+               {"labels_to_set": ["kind/bug", "priority/p0"], "explanation": "This is a critical bug report affecting main functionality"}
+               ```
+            8. If the issue cannot be classified using the available labels, output:
+               ```
+               {"labels_to_set": [], "explanation": "Unable to classify this issue with available labels"}
+               ```
+            9. Use Area definitions mentioned below to help you narrow down issues.
+            10. If you think an issue might be a Priority/P0 do not apply the priority/p0 label. Instead apply a status/manual-triage label and include a note in your explanation.
+            11. If you are uncertain and have not been able to apply one each of kind/, area/ and priority/ , apply the status/manual-triage label.
 
             ## Guidelines
-            - Your output must contain exactly one area/ label.
-            - Triage only the current issue based on its title and body.
-            - Output only valid JSON format.
-            - Do not include any explanation or additional text, just the JSON.
 
-            Reference 1: Area Definitions
-            area/agent
-            - Description: Issues related to the "brain" of the CLI. This includes the core agent logic, model quality, tool/function calling, and memory.
-            - Example Issues:
-              "I am not getting a reasonable or expected response."
-              "The model is not calling the tool I expected."
-              "The web search tool is not working as expected."
-              "Feature request for a new built-in tool (e.g., read file, write file)."
-              "The generated code is poor quality or incorrect."
-              "The model seems stuck in a loop."
-              "The response from the model is malformed (e.g., broken JSON, bad formatting)."
-              "Concerns about unnecessary token consumption."
-              "Issues with how memory or chat history is managed."
-              "Issues with sub-agents."
-              "Model is switching from one to another unexpectedly."
+            - Only use labels that already exist in the repository
+            - Do not add comments or modify the issue content
+            - Triage only the current issue
+            - Identify only one area/ label
+            - Identify only one kind/ label
+            - Identify all applicable sub-area/* and priority/* labels based on the issue content. It's ok to have multiple of these
+            - Once you categorize the issue if it needs information bump down the priority by 1 eg.. a p0 would become a p1 a p1 would become a p2. P2 and P3 can stay as is in this scenario
+            - Reference all shell variables as "${VAR}" (with quotes and braces)
+            - Output only valid JSON format
+            - Do not include any explanation or additional text, just the JSON
 
-            area/enterprise
-            - Description: Issues specific to enterprise-level features, including telemetry, policy, and licenses.
-            - Example Issues:
-              "Usage data is not appearing in our telemetry dashboard."
-              "A user is able to perform an action that should be blocked by an admin policy."
-              "Questions about billing, licensing tiers, or enterprise quotas."
-
-            area/non-interactive
-            - Description: Issues related to using the CLI in automated or non-interactive environments (headless mode).
-            - Example Issues:
-              "Problems using the CLI as an SDK in another surface."
-              "The CLI is behaving differently when run from a shell script vs. an interactive terminal."
-              "GitHub action is failing."
-              "I am having trouble running the CLI in headless mode"
-
-            area/core
-            - Description: Issues with the fundamental CLI app itself. This includes the user interface (UI/UX), installation, OS compatibility, and performance.
-            - Example Issues:
-              "I am seeing my screen flicker when using the CLI."
-              "The output in my terminal is malformed or unreadable."
-              "Theme changes are not taking effect."
-              "Keyboard inputs (e.g., arrow keys, Ctrl+C) are not being recognized."
-              "The CLI failed to install or update."
-              "An issue specific to running on Windows, macOS, or Linux."
-              "Problems with command parsing, flags, or argument handling."
-              "High CPU or memory usage by the CLI process."
-              "Issues related to multi-modality (e.g., handling image inputs)."
-              "Problems with the IDE integration connection or installation"
-
-            area/security
-            - Description: Issues related to user authentication, authorization, data security, and privacy.
-            - Example Issues:
-              "I am unable to sign in."
-              "The login flow is selecting the wrong authentication path"
-              "Problems with API key handling or credential storage."
-              "A report of a security vulnerability"
-              "Concerns about data sanitization or potential data leaks."
-              "Issues or requests related to privacy controls."
-              "Preventing unauthorized data access."
-
-            area/platform
-            - Description: Issues related to CI/CD, release management, testing, eval infrastructure, capacity, quota management, and sandbox environments.
-            - Example Issues:
-              "I am getting a 429 'Resource Exhausted' or 500-level server error."
-              "General slowness or high latency from the service."
-              "The build script is broken on the main branch."
-              "Tests are failing in the CI/CD pipeline."
-              "Issues with the release management or publishing process."
-              "User is running out of capacity."
-              "Problems specific to the sandbox or staging environments."
-              "Questions about quota limits or requests for increases."
-
-            area/extensions
-            - Description: Issues related to the extension ecosystem, including the marketplace and website.
-            - Example Issues:
-              "Bugs related to the extension marketplace website."
-              "Issues with a specific extension."
-              "Feature request for the extension ecosystem."
-
-            area/unknown
-            - Description: Issues that do not clearly fit into any other defined area/ category, or where information is too limited to make a determination. Use this when no other area is appropriate.
+            Categorization Guidelines:
+            P0: Critical / Blocker
+            - A P0 bug is a catastrophic failure that demands immediate attention.
+            - To be a P0 it means almost all users are running into this issue and it is blocking users from being able to use the product.
+            - You would see this in the form of many comments from different developers on the bug.
+            - It represents a complete showstopper for a significant portion of users or for the development process itself.
+            Impact:
+            - Blocks development or testing for the entire team.
+            - Major security vulnerability that could compromise user data or system integrity.
+            - Causes data loss or corruption with no workaround.
+            - Crashes the application or makes a core feature completely unusable for all or most users in a production environment. Will it cause severe quality degration? Is it preventing contributors from contributing to the repository or is it a release blocker?
+            Qualifier: Is the main function of the software broken?
+            Example: The gemini auth login command fails with an unrecoverable error, preventing any user from authenticating and using the rest of the CLI.
+            P1: High
+            - A P1 bug is a serious issue that significantly degrades the user experience or impacts a core feature.
+            - While not a complete blocker, it's a major problem that needs a fast resolution. Feature requests are almost never P1.
+            - Once again this would be affecting many users.
+            - You would see this in the form of comments from different developers on the bug.
+            Impact:
+            - A core feature is broken or behaving incorrectly for a large number of users or large number of use cases.
+            - Review the bug details and comments to try figure out if this issue affects a large set of use cases or if it's a narrow set of use cases.
+            - Severe performance degradation making the application frustratingly slow.
+            - No straightforward workaround exists, or the workaround is difficult and non-obvious.
+            Qualifier: Is a key feature unusable or giving very wrong results?
+            Example: Gemini CLI enters a loop when making read-many-files tool call. I am unable to break out of the loop and gemini doesn't follow instructions subsequently.
+            P2: Medium
+            - A P2 bug is a moderately impactful issue. It's a noticeable problem but doesn't prevent the use of the software's main functionality.
+            Impact:
+            - Affects a non-critical feature or a smaller, specific subset of users.
+            - An inconvenient but functional workaround is available and easy to execute.
+            - Noticeable UI/UX problems that don't break functionality but look unprofessional (e.g., elements are misaligned or overlapping).
+            Qualifier: Is it an annoying but non-blocking problem?
+            Example: An error message is unclear or contains a typo, causing user confusion but not halting their workflow.
+            P3: Low
+            - A P3 bug is a minor, low-impact issue that is trivial or cosmetic. It has little to no effect on the overall functionality of the application.
+            Impact:
+            - Minor cosmetic issues like color inconsistencies, typos in documentation, or slight alignment problems on a non-critical page.
+            - An edge-case bug that is very difficult to reproduce and affects a tiny fraction of users.
+            Qualifier: Is it a "nice-to-fix" issue?
+            Example: Spelling mistakes etc.
+            Things you should know:
+            - If users are talking about issues where the model gets downgraded from pro to flash then i want you to categorize that as a performance issue
+            - This product is designed to use different models eg.. using pro, downgrading to flash etc. when users report that they dont expect the model to change those would be categorized as feature requests.
+            Definition of Areas
+            area/ux:
+            - Issues concerning user-facing elements like command usability, interactive features, help docs, and perceived performance.
+            - I am seeing my screen flicker when using Gemini CLI
+            - I am seeing the output malformed
+            - Theme changes aren't taking effect
+            - My keyboard inputs arent' being recognzied
+            area/platform:
+            - Issues related to installation, packaging, OS compatibility (Windows, macOS, Linux), and the underlying CLI framework.
+            area/background: Issues related to long-running background tasks, daemons, and autonomous or proactive agent features.
+            area/models:
+            - i am not getting a response that is reasonable or expected. this can include things like
+            - I am calling a tool and the tool is not performing as expected.
+            - i am expecting a tool to be called and it is not getting called ,
+            - Including experience when using
+            - built-in tools (e.g., web search, code interpreter, read file, writefile, etc..),
+            - Function calling issues should be under this area
+            - i am getting responses from the model that are malformed.
+            - Issues concerning Gemini quality of response and inference,
+            - Issues talking about unnecessary token consumption.
+            - Issues talking about Model getting stuck in a loop be watchful as this could be the root cause for issues that otherwise seem like model performance issues.
+            - Memory compression
+            - unexpected responses,
+            - poor quality of generated code
+            area/tools:
+            - These are primarily issues related to Model Context Protocol
+            - These are issues that mention MCP support
+            - feature requests asking for support for new tools.
+            area/core: Issues with fundamental components like command parsing, configuration management, session state, and the main API client logic. Introducing multi-modality
+            area/contribution: Issues related to improving the developer contribution experience, such as CI/CD pipelines, build scripts, and test automation infrastructure.
+            area/authentication: Issues related to user identity, login flows, API key handling, credential storage, and access token management, unable to sign in selecting wrong authentication path etc..
+            area/security-privacy: Issues concerning vulnerability patching, dependency security, data sanitization, privacy controls, and preventing unauthorized data access.
+            area/extensibility: Issues related to the plugin system, extension APIs, or making the CLI's functionality available in other applications, github actions, ide support etc..
+            area/performance: Issues focused on model performance
+            - Issues with running out of capacity,
+            - 429 errors etc..
+            - could also pertain to latency,
+            - other general software performance like, memory usage, CPU consumption, and algorithmic efficiency.
+            - Switching models from one to the other unexpectedly.
 
       - name: 'Apply Labels to Issue'
         if: |-
@@ -254,61 +270,52 @@ jobs:
         uses: 'actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea'
         with:
           github-token: '${{ steps.generate_token.outputs.token }}'
-          script: |
-            const rawOutput = process.env.LABELS_OUTPUT;
-            core.info(`Raw output from model: ${rawOutput}`);
+          script: |-
+            // Strip code block markers if present
+            const rawLabels = process.env.LABELS_OUTPUT;
+            core.info(`Raw labels JSON: ${rawLabels}`);
             let parsedLabels;
             try {
-              // First, try to parse the raw output as JSON.
-              parsedLabels = JSON.parse(rawOutput);
-            } catch (jsonError) {
-              // If that fails, check for a markdown code block.
-              core.warning(`Direct JSON parsing failed: ${jsonError.message}. Trying to extract from a markdown block.`);
-              const jsonMatch = rawOutput.match(/```json\s*([\s\S]*?)\s*```/);
-              if (jsonMatch && jsonMatch[1]) {
-                try {
-                  parsedLabels = JSON.parse(jsonMatch[1].trim());
-                } catch (markdownError) {
-                  core.setFailed(`Failed to parse JSON even after extracting from markdown block: ${markdownError.message}\nRaw output: ${rawOutput}`);
-                  return;
-                }
-              } else {
-                core.setFailed(`Output is not valid JSON and does not contain a JSON markdown block.\nRaw output: ${rawOutput}`);
-                return;
+              const jsonMatch = rawLabels.match(/```json\s*([\s\S]*?)\s*```/);
+              if (!jsonMatch || !jsonMatch[1]) {
+                throw new Error("Could not find a ```json ... ``` block in the output.");
               }
-            }
-
-            const issueNumber = parseInt(process.env.ISSUE_NUMBER);
-            const labelsToAdd = parsedLabels.labels_to_set || [];
-
-            if (labelsToAdd.length !== 1) {
-              core.setFailed(`Expected exactly 1 label (area/), but got ${labelsToAdd.length}. Labels: ${labelsToAdd.join(', ')}`);
+              const jsonString = jsonMatch[1].trim();
+              parsedLabels = JSON.parse(jsonString);
+              core.info(`Parsed labels JSON: ${JSON.stringify(parsedLabels)}`);
+            } catch (err) {
+              core.setFailed(`Failed to parse labels JSON from Gemini output: ${err.message}\nRaw output: ${rawLabels}`);
               return;
             }
 
-            // Set labels based on triage result
-            await github.rest.issues.addLabels({
-              owner: context.repo.owner,
-              repo: context.repo.repo,
-              issue_number: issueNumber,
-              labels: labelsToAdd
-            });
-            core.info(`Successfully added labels for #${issueNumber}: ${labelsToAdd.join(', ')}`);
+            const issueNumber = parseInt(process.env.ISSUE_NUMBER);
+            const explanation = parsedLabels.explanation || '';
+            const labelsToSet = parsedLabels.labels_to_set || [];
+            labelsToSet.push('status/bot-triaged');
 
-            // Remove the 'status/need-triage' label
-            try {
-                await github.rest.issues.removeLabel({
-                    owner: context.repo.owner,
-                    repo: context.repo.repo,
-                    issue_number: issueNumber,
-                    name: 'status/need-triage'
-                });
-                core.info(`Successfully removed 'status/need-triage' label.`);
-            } catch (error) {
-                // If the label doesn't exist, the API call will throw a 404. We can ignore this.
-                if (error.status !== 404) {
-                    core.warning(`Failed to remove 'status/need-triage': ${error.message}`);
-                }
+            // Set labels based on triage result
+            if (labelsToSet.length > 0) {
+              await github.rest.issues.setLabels({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                issue_number: issueNumber,
+                labels: labelsToSet
+              });
+              const explanationInfo = explanation ? ` - ${explanation}` : '';
+              core.info(`Successfully set labels for #${issueNumber}: ${labelsToSet.join(', ')}${explanationInfo}`);
+            } else {
+              // If no labels to set, leave the issue as is
+              const explanationInfo = explanation ? ` - ${explanation}` : '';
+              core.info(`No labels to set for #${issueNumber}, leaving as is${explanationInfo}`);
+            }
+
+            if (explanation) {
+              await github.rest.issues.createComment({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                issue_number: issueNumber,
+                body: explanation,
+              });
             }
 
       - name: 'Post Issue Analysis Failure Comment'

.github/workflows/gemini-automated-pr-size-labeler.yml

@@ -1,127 +0,0 @@
-name: 'Gemini Automated PR Labeler'
-
-on:
-  pull_request_target:
-    types: ['opened', 'reopened', 'synchronize']
-
-jobs:
-  label-pr:
-    timeout-minutes: 10
-    if: |-
-      ${{ github.repository == 'google-gemini/gemini-cli' }}
-    permissions:
-      pull-requests: 'write'
-      contents: 'read'
-      id-token: 'write'
-
-    concurrency:
-      group: '${{ github.workflow }}-${{ github.event.pull_request.number }}'
-      cancel-in-progress: true
-
-    runs-on: 'ubuntu-latest'
-
-    steps:
-      - name: 'Generate GitHub App Token'
-        id: 'generate_token'
-        uses: 'actions/create-github-app-token@df432ceedc7162793a195dd1713ff69aefc7379e' # v2
-        with:
-          app-id: '${{ secrets.APP_ID }}'
-          private-key: '${{ secrets.PRIVATE_KEY }}'
-          permission-pull-requests: 'write'
-
-      - name: 'Run Gemini PR size and complexity labeller'
-        uses: 'google-github-actions/run-gemini-cli@a3bf79042542528e91937b3a3a6fbc4967ee3c31' # Use the specific commit SHA
-        env:
-          GH_TOKEN: '${{ steps.generate_token.outputs.token }}'
-          PR_NUMBER: '${{ github.event.pull_request.number }}'
-          REPOSITORY: '${{ github.repository }}'
-        with:
-          gcp_workload_identity_provider: '${{ vars.GCP_WIF_PROVIDER }}'
-          gcp_project_id: '${{ vars.GOOGLE_CLOUD_PROJECT }}'
-          gcp_location: '${{ vars.GOOGLE_CLOUD_LOCATION }}'
-          gcp_service_account: '${{ vars.SERVICE_ACCOUNT_EMAIL }}'
-          gemini_api_key: '${{ secrets.GEMINI_API_KEY }}'
-          use_vertex_ai: '${{ vars.GOOGLE_GENAI_USE_VERTEXAI }}'
-          use_gemini_code_assist: '${{ vars.GOOGLE_GENAI_USE_GCA }}'
-          settings: |
-            {
-              "coreTools": [
-                "run_shell_command(gh pr diff)",
-                "run_shell_command(gh pr edit)",
-                "run_shell_command(gh pr comment)",
-                "run_shell_command(gh pr view)"
-              ],
-              "telemetry": {
-                "enabled": true,
-                "target": "gcp"
-              },
-              "sandbox": false
-            }
-          prompt: |
-            You are a Pull Request labeller and Feedback Assistant. Your primary goal is to improve review velocity and help maintainers prioritize their work by automatically labeling pull requests based on size and complexity, and providing guidance for overly large PRs.
-
-            Steps:
-            1. Retrieve Pull Request Information:
-               - Use `gh pr diff ${{ env.PR_NUMBER }} --repo ${{ env.REPOSITORY }}` to get the diff content.
-               - Parse the output from `gh pr diff` to determine the total lines of code added and deleted. Calculate `TOTAL_LINES_CHANGED`.
-
-            2. Determine Pull Request Size:
-               - Use `gh pr view ${{ env.PR_NUMBER }} --repo ${{ env.REPOSITORY }} --json labels` to get the current labels on the PR.
-               - Check the current labels and identify if any `size/*` labels already exist (e.g., `size/xs`, `size/s`, etc.).
-               - If an old `size/*` label is found and it is different from the newly calculated size, remove it using:
-                 `gh pr edit ${{ env.PR_NUMBER }} --repo ${{ env.REPOSITORY }} --remove-label "size-label-to-remove"`
-               - Based on `TOTAL_LINES_CHANGED`, select the appropriate new size label:
-                 - `size/xs`: < 10 lines changed
-                 - `size/s`: 10-50 lines changed
-                 - `size/m`: 51-200 lines changed
-                 - `size/l`: 201-1000 lines changed
-                 - `size/xl`: > 1000 lines changed
-               - Do not invent new size labels.
-               - Apply the newly determined `size/*` label to the pull request using:
-                 `gh pr edit ${{ env.PR_NUMBER }} --repo ${{ env.REPOSITORY }} --add-label "your-new-size-label"`
-
-            3. Analyze Pull Request Complexity:
-                - Perform Code Change Analysis: Examine the content of the code changes obtained from `gh pr diff ${{ env.PR_NUMBER }} --repo ${{ env.REPOSITORY }}`. Look for indicators of complexity such as:
-                 - Number of files changed (can be inferred from the diff headers).
-                 - Diversity of file types (e.g., changes across different languages, configuration files, documentation).
-                 - Presence of new external dependencies.
-                 - Introduction of new architectural components or significant refactoring.
-                 - Complexity of individual code changes (e.g., deeply nested logic, complex algorithms, extensive conditional statements).
-               - Apply Heuristic-based Complexity Assessment:
-                 - If the PR touches a small number of files with minor changes (e.g., typos, simple bug fixes, small feature additions), categorize it as `review/quick`.
-                 - If the PR involves changes across multiple files, introduces new features, significantly refactors existing code, or has a high line count (even within `size/l`), categorize it as `review/involved`.
-                 - Pay close attention to changes in critical or core modules as these inherently increase complexity.
-               - **Only use the labels `review/quick` or `review/involved` for complexity. Do not invent new complexity labels.**
-               - **Remove any previous `review/*` labels if they no longer apply, similar to the size label process.**
-               - Apply the determined `review/*` label to the pull request using:
-                 `gh pr edit ${{ env.PR_NUMBER }} --repo ${{ env.REPOSITORY }} --add-label "your-complexity-label"`
-
-            4. Handle Overly Large Pull Requests (`size/xl`):
-               - **Conditional Check:** If the pull request has been labeled `size/xl` (i.e., > 1000 lines of code changed) in Step 2, proceed to the next sub-step.
-               - **Post Constructive Comment:** Post a polite and helpful comment on the pull request using:
-                 `gh pr comment ${{ env.PR_NUMBER }} --repo ${{ env.REPOSITORY }} --body "Your comment here"`
-                 The comment body should be:
-                 """
-                 Thanks for your hard work on this pull request!
-
-                 This pull request is quite large, which can make it challenging and time-consuming for reviewers to go through thoroughly.
-
-                 To help us review it more efficiently and get your changes merged faster, we kindly request you consider breaking this into smaller, more focused pull requests. Each smaller PR should ideally address a single logical change or a small set of related changes.
-
-                 For example, you could separate out refactoring, new feature additions, and bug fixes into individual PRs. This makes it easier to understand, review, and test each component independently.
-
-                 We appreciate your understanding and cooperation. Feel free to reach out if you need any assistance with this!
-                 """
-
-            Guidelines:
-            - Automation Focus: All actions should be automated and not require manual intervention.
-            - Non-intrusive: The system should add labels and comments but not modify the code or close the pull request.
-            - Polite and Constructive: All communication, especially for large PRs, must be polite, encouraging, and constructive.
-            - Prioritize Clarity: The labels applied should clearly convey the PR's size and complexity to reviewers.
-            - Adhere to Defined Labels: Only use the specified `size/*` and `review/*` labels. Do not create or apply any other labels.
-            - Utilize `gh CLI`: Interact with GitHub using the `gh` command-line tool for diffing, label management, and commenting.
-            - Execute commands strictly as described in the steps. Do not invent new commands.
-            - In no case should you change other pull request that are not the one you are working on. Which can be found by using env.PR_NUMBER
-            - Execute each step that is defined in the steps section.
-            - In no case should you execute code from the pull request because this could be malicious code.
-            - If you fail to do this step log the errors you received

.github/workflows/gemini-scheduled-issue-triage.yml

@@ -45,11 +45,11 @@ jobs:
 
           echo '🔍 Finding issues without labels...'
           NO_LABEL_ISSUES="$(gh issue list --repo "${GITHUB_REPOSITORY}" \
-            --search 'is:open is:issue no:label' --limit 10 --json number,title,body)"
+            --search 'is:open is:issue no:label' --json number,title,body)"
 
           echo '🏷️ Finding issues that need triage...'
           NEED_TRIAGE_ISSUES="$(gh issue list --repo "${GITHUB_REPOSITORY}" \
-            --search "is:open is:issue label:\"status/need-triage\"" --limit 10 --json number,title,body)"
+            --search "is:open is:issue label:\"status/need-triage\""  --limit 1000 --json number,title,body)"
 
           echo '🔄 Merging and deduplicating issues...'
           ISSUES="$(echo "${NO_LABEL_ISSUES}" "${NEED_TRIAGE_ISSUES}" | jq -c -s 'add | unique_by(.number)')"

.github/workflows/gemini-scheduled-stale-issue-closer.yml

@@ -1,152 +0,0 @@
-name: '🔒 Gemini Scheduled Stale Issue Closer'
-
-on:
-  schedule:
-    - cron: '0 0 * * 0' # Every Sunday at midnight UTC
-  workflow_dispatch:
-    inputs:
-      dry_run:
-        description: 'Run in dry-run mode (no changes applied)'
-        required: false
-        default: false
-        type: 'boolean'
-
-concurrency:
-  group: '${{ github.workflow }}'
-  cancel-in-progress: true
-
-defaults:
-  run:
-    shell: 'bash'
-
-jobs:
-  close-stale-issues:
-    runs-on: 'ubuntu-latest'
-    permissions:
-      issues: 'write'
-    steps:
-      - name: 'Generate GitHub App Token'
-        id: 'generate_token'
-        uses: 'actions/create-github-app-token@v1'
-        with:
-          app-id: '${{ secrets.APP_ID }}'
-          private-key: '${{ secrets.PRIVATE_KEY }}'
-          permission-issues: 'write'
-
-      - name: 'Process Stale Issues'
-        uses: 'actions/github-script@v7'
-        env:
-          DRY_RUN: '${{ inputs.dry_run }}'
-        with:
-          github-token: '${{ steps.generate_token.outputs.token }}'
-          script: |
-            const dryRun = process.env.DRY_RUN === 'true';
-            if (dryRun) {
-              core.info('DRY RUN MODE ENABLED: No changes will be applied.');
-            }
-            const batchLabel = 'Stale';
-
-            const threeMonthsAgo = new Date();
-            threeMonthsAgo.setMonth(threeMonthsAgo.getMonth() - 3);
-
-            const tenDaysAgo = new Date();
-            tenDaysAgo.setDate(tenDaysAgo.getDate() - 10);
-
-            core.info(`Cutoff date for creation: ${threeMonthsAgo.toISOString()}`);
-            core.info(`Cutoff date for updates: ${tenDaysAgo.toISOString()}`);
-
-            const query = `repo:${context.repo.owner}/${context.repo.repo} is:issue is:open created:<${threeMonthsAgo.toISOString()}`;
-            core.info(`Searching with query: ${query}`);
-
-            const itemsToCheck = await github.paginate(github.rest.search.issuesAndPullRequests, {
-              q: query,
-              sort: 'created',
-              order: 'asc',
-              per_page: 100
-            });
-
-            core.info(`Found ${itemsToCheck.length} open issues to check.`);
-
-            let processedCount = 0;
-
-            for (const issue of itemsToCheck) {
-              const createdAt = new Date(issue.created_at);
-              const updatedAt = new Date(issue.updated_at);
-              const reactionCount = issue.reactions.total_count;
-
-              // Basic thresholds
-              if (reactionCount >= 5) {
-                continue;
-              }
-
-              // Skip if it has a maintainer label
-              if (issue.labels.some(label => label.name.toLowerCase().includes('maintainer'))) {
-                continue;
-              }
-
-              let isStale = updatedAt < tenDaysAgo;
-
-              // If apparently active, check if it's only bot activity
-              if (!isStale) {
-                try {
-                  const comments = await github.rest.issues.listComments({
-                    owner: context.repo.owner,
-                    repo: context.repo.repo,
-                    issue_number: issue.number,
-                    per_page: 100,
-                    sort: 'created',
-                    direction: 'desc'
-                  });
-
-                  const lastHumanComment = comments.data.find(comment => comment.user.type !== 'Bot');
-                  if (lastHumanComment) {
-                    isStale = new Date(lastHumanComment.created_at) < tenDaysAgo;
-                  } else {
-                    // No human comments. Check if creator is human.
-                    if (issue.user.type !== 'Bot') {
-                       isStale = createdAt < tenDaysAgo;
-                    } else {
-                       isStale = true; // Bot created, only bot comments
-                    }
-                  }
-                } catch (error) {
-                  core.warning(`Failed to fetch comments for issue #${issue.number}: ${error.message}`);
-                  continue;
-                }
-              }
-
-              if (isStale) {
-                processedCount++;
-                const message = `Closing stale issue #${issue.number}: "${issue.title}" (${issue.html_url})`;
-                core.info(message);
-
-                if (!dryRun) {
-                  // Add label
-                  await github.rest.issues.addLabels({
-                    owner: context.repo.owner,
-                    repo: context.repo.repo,
-                    issue_number: issue.number,
-                    labels: [batchLabel]
-                  });
-
-                  // Add comment
-                  await github.rest.issues.createComment({
-                    owner: context.repo.owner,
-                    repo: context.repo.repo,
-                    issue_number: issue.number,
-                    body: 'Hello! As part of our effort to keep our backlog manageable and focus on the most active issues, we are tidying up older reports.\n\nIt looks like this issue hasn\'t been active for a while, so we are closing it for now. However, if you are still experiencing this bug on the latest stable build, please feel free to comment on this issue or create a new one with updated details.\n\nThank you for your contribution!'
-                  });
-
-                  // Close issue
-                  await github.rest.issues.update({
-                    owner: context.repo.owner,
-                    repo: context.repo.repo,
-                    issue_number: issue.number,
-                    state: 'closed',
-                    state_reason: 'not_planned'
-                  });
-                }
-              }
-            }
-
-            core.info(`\nTotal issues processed: ${processedCount}`);

.github/workflows/label-backlog-child-issues.yml

@@ -1,40 +0,0 @@
-name: 'Label Child Issues for Project Rollup'
-
-on:
-  issues:
-    types: ['opened', 'edited', 'reopened']
-
-jobs:
-  labeler:
-    runs-on: 'ubuntu-latest'
-    permissions:
-      issues: 'write'
-    steps:
-      - name: 'Check for Parent Workstream and Apply Label'
-        uses: 'actions/github-script@v7'
-        with:
-          script: |
-            const issue = context.payload.issue;
-            const labelToAdd = 'workstream-rollup';
-
-            // --- Define the FULL URLs of the allowed parent workstreams ---
-            const allowedParentUrls = [
-              'https://api.github.com/repos/google-gemini/gemini-cli/issues/15374',
-              'https://api.github.com/repos/google-gemini/gemini-cli/issues/15456',
-              'https://api.github.com/repos/google-gemini/gemini-cli/issues/15324'
-            ];
-
-            // Check if the issue has a parent_issue_url and if it's in our allowed list.
-            if (issue && issue.parent_issue_url && allowedParentUrls.includes(issue.parent_issue_url)) {
-              console.log(`SUCCESS: Issue #${issue.number} is a child of a target workstream (${issue.parent_issue_url}). Adding label.`);
-              await github.rest.issues.addLabels({
-                owner: context.repo.owner,
-                repo: context.repo.repo,
-                issue_number: issue.number,
-                labels: [labelToAdd]
-              });
-            } else if (issue && issue.parent_issue_url) {
-              console.log(`FAILURE: Issue #${issue.number} has a parent, but it's not a target workstream. Parent URL: ${issue.parent_issue_url}`);
-            } else {
-              console.log(`FAILURE: Issue #${issue.number} is not a child of any issue. No action taken.`);
-            }

.github/workflows/links.yml

@@ -1,23 +0,0 @@
-name: 'Links'
-
-on:
-  push:
-    branches: ['main']
-  pull_request:
-    branches: ['main']
-  repository_dispatch:
-  workflow_dispatch:
-  schedule:
-    - cron: '00 18 * * *'
-
-jobs:
-  linkChecker:
-    runs-on: 'ubuntu-latest'
-    steps:
-      - uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8' # ratchet:actions/checkout@v5
-
-      - name: 'Link Checker'
-        id: 'lychee'
-        uses: 'lycheeverse/lychee-action@885c65f3dc543b57c898c8099f4e08c8afd178a2' # ratchet: lycheeverse/lychee-action@v2.6.1
-        with:
-          args: '--verbose --no-progress --accept 200,503 ./**/*.md'

.github/workflows/release-manual.yml

@@ -132,4 +132,4 @@ jobs:
           gh issue create \
             --title 'Manual Release Failed for ${RELEASE_TAG} on $(date +'%Y-%m-%d')' \
             --body 'The manual release workflow failed. See the full run for details: ${DETAILS_URL}' \
-            --label 'release-failure,priority/p0'
+            --label 'kind/bug,release-failure,priority/p0'

.github/workflows/release-nightly.yml

@@ -2,7 +2,7 @@ name: 'Release: Nightly'
 
 on:
   schedule:
-    - cron: '0 0 * * *'
+    - cron: '0 20 * * *'
   workflow_dispatch:
     inputs:
       dry_run:
@@ -157,4 +157,4 @@ jobs:
           gh issue create \
             --title "Nightly Release Failed for ${RELEASE_TAG} on $(date +'%Y-%m-%d')" \
             --body "The nightly-release workflow failed. See the full run for details: ${DETAILS_URL}" \
-            --label 'release-failure,priority/p0'
+            --label 'kind/bug,release-failure,priority/p0'

.github/workflows/release-patch-1-create-pr.yml

@@ -1,8 +1,5 @@
 name: 'Release: Patch (1) Create PR'
 
-run-name: >-
-  Release Patch (1) Create PR | S:${{ inputs.channel }} | C:${{ inputs.commit }} ${{ inputs.original_pr && format('| PR:#{0}', inputs.original_pr) || '' }}
-
 on:
   workflow_dispatch:
     inputs:
@@ -99,12 +96,12 @@ jobs:
               --channel="${PATCH_CHANNEL}" \
               --pullRequestNumber="${ORIGINAL_PR}" \
               --dry-run="${DRY_RUN}"
+            echo "EXIT_CODE=$?" >> "$GITHUB_OUTPUT"
           } 2>&1 | tee >(
             echo "LOG_CONTENT<<EOF" >> "$GITHUB_ENV"
             cat >> "$GITHUB_ENV"
             echo "EOF" >> "$GITHUB_ENV"
           )
-          echo "EXIT_CODE=${PIPESTATUS[0]}" >> "$GITHUB_OUTPUT"
 
       - name: 'Comment on Original PR'
         if: 'always() && inputs.original_pr'
@@ -118,7 +115,6 @@ jobs:
           GITHUB_RUN_ID: '${{ github.run_id }}'
           LOG_CONTENT: '${{ env.LOG_CONTENT }}'
           TARGET_REF: '${{ github.event.inputs.ref }}'
-          ENVIRONMENT: '${{ github.event.inputs.environment }}'
         continue-on-error: true
         run: |
           git checkout "${TARGET_REF}"

.github/workflows/release-patch-2-trigger.yml

@@ -1,10 +1,5 @@
 name: 'Release: Patch (2) Trigger'
 
-run-name: >-
-  Release Patch (2) Trigger |
-  ${{ github.event.pull_request.number && format('PR #{0}', github.event.pull_request.number) || 'Manual' }} |
-  ${{ github.event.pull_request.head.ref || github.event.inputs.ref }}
-
 on:
   pull_request:
     types:

.github/workflows/release-patch-3-release.yml

@@ -1,8 +1,5 @@
 name: 'Release: Patch (3) Release'
 
-run-name: >-
-  Release Patch (3) Release | T:${{ inputs.type }} | R:${{ inputs.release_ref }} ${{ inputs.original_pr && format('| PR:#{0}', inputs.original_pr) || '' }}
-
 on:
   workflow_dispatch:
     inputs:
@@ -205,7 +202,7 @@ jobs:
           gh issue create \
             --title 'Patch Release Failed for ${RELEASE_TAG} on $(date +'%Y-%m-%d')' \
             --body 'The patch-release workflow failed. See the full run for details: ${DETAILS_URL}' \
-            --label 'release-failure,priority/p0'
+            --label 'kind/bug,release-failure,priority/p0'
 
       - name: 'Comment Success on Original PR'
         if: '${{ success() && github.event.inputs.original_pr }}'

.github/workflows/release-promote.yml

@@ -92,9 +92,6 @@ jobs:
           fi
           NIGHTLY_COMMAND="node scripts/get-release-version.js --type=promote-nightly"
           STABLE_JSON=$(${STABLE_COMMAND})
-          STABLE_VERSION=$(echo "${STABLE_JSON}" | jq -r .releaseVersion)
-          PREVIEW_COMMAND+=" --stable-base-version=${STABLE_VERSION}"
-          NIGHTLY_COMMAND+=" --stable-base-version=${STABLE_VERSION}"
           PREVIEW_JSON=$(${PREVIEW_COMMAND})
           NIGHTLY_JSON=$(${NIGHTLY_COMMAND})
           echo "STABLE_JSON_COMMAND=${STABLE_COMMAND}"
@@ -103,14 +100,14 @@ jobs:
           echo "STABLE_JSON: ${STABLE_JSON}"
           echo "PREVIEW_JSON: ${PREVIEW_JSON}"
           echo "NIGHTLY_JSON: ${NIGHTLY_JSON}"
-          echo "STABLE_VERSION=${STABLE_VERSION}" >> "${GITHUB_OUTPUT}"
+          echo "STABLE_VERSION=$(echo "${STABLE_JSON}" | jq -r .releaseVersion)" >> "${GITHUB_OUTPUT}"
           # shellcheck disable=SC1083
           echo "STABLE_SHA=$(git rev-parse "$(echo "${PREVIEW_JSON}" | jq -r .previousReleaseTag)"^{commit})" >> "${GITHUB_OUTPUT}"
           echo "PREVIOUS_STABLE_TAG=$(echo "${STABLE_JSON}" | jq -r .previousReleaseTag)" >> "${GITHUB_OUTPUT}"
           echo "PREVIEW_VERSION=$(echo "${PREVIEW_JSON}" | jq -r .releaseVersion)" >> "${GITHUB_OUTPUT}"
           # shellcheck disable=SC1083
           REF="${REF_INPUT}"
-          SHA=$(git ls-remote origin "$REF" | awk -v ref="$REF" '$2 == "refs/heads/"ref || $2 == "refs/tags/"ref || $2 == ref {print $1}' | head -n 1)
+          SHA=$(git ls-remote origin "$REF" | awk '{print $1}')
           if [ -z "$SHA" ]; then
             if [[ "$REF" =~ ^[0-9a-f]{7,40}$ ]]; then
               SHA="$REF"
@@ -261,7 +258,7 @@ jobs:
           gh issue create \
             --title 'Promote Release Failed for ${RELEASE_TAG} on $(date +'%Y-%m-%d')' \
             --body 'The promote-release workflow failed during preview publish. See the full run for details: ${DETAILS_URL}' \
-            --label 'release-failure,priority/p0'
+            --label 'kind/bug,release-failure,priority/p0'
 
   publish-stable:
     name: 'Publish stable'
@@ -327,7 +324,7 @@ jobs:
           gh issue create \
             --title 'Promote Release Failed for ${RELEASE_TAG} on $(date +'%Y-%m-%d')' \
             --body 'The promote-release workflow failed during stable publish. See the full run for details: ${DETAILS_URL}' \
-            --label 'release-failure,priority/p0'
+            --label 'kind/bug,release-failure,priority/p0'
 
   nightly-pr:
     name: 'Create Nightly PR'
@@ -403,4 +400,4 @@ jobs:
           gh issue create \
             --title 'Promote Release Failed for ${RELEASE_TAG} on $(date +'%Y-%m-%d')' \
             --body 'The promote-release workflow failed during nightly PR creation. See the full run for details: ${DETAILS_URL}' \
-            --label 'release-failure,priority/p0'
+            --label 'kind/bug,release-failure,priority/p0'

.github/workflows/release-sandbox.yml

@@ -46,4 +46,4 @@ jobs:
           gh issue create \
             --title 'Sandbox Release Failed on $(date +'%Y-%m-%d')' \
             --body 'The sandbox-release workflow failed. See the full run for details: ${DETAILS_URL}' \
-            --label 'release-failure,priority/p0'
+            --label 'kind/bug,release-failure,priority/p0'

.github/workflows/smoke-test.yml

@@ -47,4 +47,4 @@ jobs:
           gh issue create \
             --title 'Smoke test failed on ${REF} @ $(date +'%Y-%m-%d')' \
             --body 'Smoke test build failed. See the full run for details: ${DETAILS_URL}' \
-            --label 'priority/p0'
+            --label 'kind/bug,priority/p0'

.github/workflows/test_chained_e2e.yml

@@ -1,10 +1,6 @@
-name: 'Testing: E2E (Chained)'
+name: 'Test Chained E2E'
 
 on:
-  push:
-    branches:
-      - 'main'
-  merge_group:
   workflow_run:
     workflows: ['Trigger E2E']
     types: ['completed']
@@ -18,18 +14,13 @@ on:
         required: true
 
 concurrency:
-  group: '${{ github.workflow }}-${{ github.head_ref || github.event.workflow_run.head_branch || github.ref }}'
+  group: '${{ github.workflow }}-${{ github.head_ref || github.ref }}'
   cancel-in-progress: |-
-    ${{ github.event_name != 'push' && github.event_name != 'merge_group' }}
-
-permissions:
-  contents: 'read'
-  statuses: 'write'
+    ${{ github.ref != 'refs/heads/main' && !startsWith(github.ref, 'refs/heads/release/') }}
 
 jobs:
   merge_queue_skipper:
     name: 'Merge Queue Skipper'
-    permissions: 'read-all'
     runs-on: 'gemini-cli-ubuntu-16-core'
     outputs:
       skip: '${{ steps.merge-queue-e2e-skipper.outputs.skip-check }}'
@@ -37,18 +28,15 @@ jobs:
       - id: 'merge-queue-e2e-skipper'
         uses: 'cariad-tech/merge-queue-ci-skipper@1032489e59437862c90a08a2c92809c903883772' # ratchet:cariad-tech/merge-queue-ci-skipper@main
         with:
-          secret: '${{ secrets.GEMINI_CLI_ROBOT_GITHUB_PAT }}'
-    continue-on-error: true
+          secret: '${{ secrets.GITHUB_TOKEN }}'
 
   download_repo_name:
     runs-on: 'gemini-cli-ubuntu-16-core'
-    if: "${{github.event_name == 'workflow_dispatch' || github.event_name == 'workflow_run'}}"
     outputs:
       repo_name: '${{ steps.output-repo-name.outputs.repo_name }}'
-      head_sha: '${{ steps.output-repo-name.outputs.head_sha }}'
     steps:
       - name: 'Mock Repo Artifact'
-        if: "${{ github.event_name == 'workflow_dispatch' }}"
+        if: "${{ github.event_name != 'workflow_run' }}"
         env:
           REPO_NAME: '${{ github.event.inputs.repo_name }}'
         run: |
@@ -67,7 +55,7 @@ jobs:
           name: 'repo_name'
           run-id: '${{ env.RUN_ID }}'
           path: '${{ runner.temp }}/artifacts'
-      - name: 'Output Repo Name and SHA'
+      - name: 'Output Repo Name'
         id: 'output-repo-name'
         uses: 'actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd' # ratchet:actions/github-script@v8
         with:
@@ -76,62 +64,13 @@ jobs:
             const fs = require('fs');
             const path = require('path');
             const temp = '${{ runner.temp }}/artifacts';
-            const repoPath = path.join(temp, 'repo_name');
-            if (fs.existsSync(repoPath)) {
-              const repo_name = String(fs.readFileSync(repoPath)).trim();
-              core.setOutput('repo_name', repo_name);
-            }
-            const shaPath = path.join(temp, 'head_sha');
-            if (fs.existsSync(shaPath)) {
-              const head_sha = String(fs.readFileSync(shaPath)).trim();
-              core.setOutput('head_sha', head_sha);
-            }
-
-  parse_run_context:
-    name: 'Parse run context'
-    runs-on: 'gemini-cli-ubuntu-16-core'
-    needs: 'download_repo_name'
-    if: 'always()'
-    outputs:
-      repository: '${{ steps.set_context.outputs.REPO }}'
-      sha: '${{ steps.set_context.outputs.SHA }}'
-    steps:
-      - id: 'set_context'
-        name: 'Set dynamic repository and SHA'
-        env:
-          REPO: '${{ needs.download_repo_name.outputs.repo_name || github.repository }}'
-          SHA: '${{ needs.download_repo_name.outputs.head_sha || github.event.inputs.head_sha || github.event.workflow_run.head_sha || github.sha }}'
-        shell: 'bash'
-        run: |
-          echo "REPO=$REPO" >> "$GITHUB_OUTPUT"
-          echo "SHA=$SHA" >> "$GITHUB_OUTPUT"
-
-  set_pending_status:
-    runs-on: 'gemini-cli-ubuntu-16-core'
-    permissions: 'write-all'
-    needs:
-      - 'parse_run_context'
-    if: 'always()'
-    steps:
-      - name: 'Set pending status'
-        uses: 'myrotvorets/set-commit-status-action@16037e056d73b2d3c88e37e393ff369047f70886' # ratchet:myrotvorets/set-commit-status-action@master
-        if: 'always()'
-        with:
-          allowForks: 'true'
-          repo: '${{ github.repository }}'
-          sha: '${{ needs.parse_run_context.outputs.sha }}'
-          token: '${{ secrets.GEMINI_CLI_ROBOT_GITHUB_PAT }}'
-          status: 'pending'
-          context: 'E2E (Chained)'
+            const repo_name = String(fs.readFileSync(path.join(temp, 'repo_name')));
+            core.setOutput('repo_name', repo_name);
 
   e2e_linux:
     name: 'E2E Test (Linux) - ${{ matrix.sandbox }}'
-    needs:
-      - 'merge_queue_skipper'
-      - 'parse_run_context'
+    needs: 'download_repo_name'
     runs-on: 'gemini-cli-ubuntu-16-core'
-    if: |
-      always() && (needs.merge_queue_skipper.result !='success' || needs.merge_queue_skipper.outputs.skip != 'true')
     strategy:
       fail-fast: false
       matrix:
@@ -145,8 +84,8 @@ jobs:
       - name: 'Checkout'
         uses: 'actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955' # ratchet:actions/checkout@v5
         with:
-          ref: '${{ needs.parse_run_context.outputs.sha }}'
-          repository: '${{ needs.parse_run_context.outputs.repository }}'
+          ref: '${{ github.event.inputs.head_sha || github.event.workflow_run.head_sha }}'
+          repository: '${{ needs.download_repo_name.outputs.repo_name }}'
 
       - name: 'Set up Node.js ${{ matrix.node-version }}'
         uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020' # ratchet:actions-node@v4
@@ -160,7 +99,7 @@ jobs:
         run: 'npm run build'
 
       - name: 'Set up Docker'
-        if: "${{matrix.sandbox == 'sandbox:docker'}}"
+        if: "matrix.sandbox == 'sandbox:docker'"
         uses: 'docker/setup-buildx-action@e468171a9de216ec08956ac3ada2f0791b6bd435' # ratchet:docker/setup-buildx-action@v3
 
       - name: 'Run E2E tests'
@@ -178,18 +117,14 @@ jobs:
 
   e2e_mac:
     name: 'E2E Test (macOS)'
-    needs:
-      - 'merge_queue_skipper'
-      - 'parse_run_context'
+    needs: 'download_repo_name'
     runs-on: 'macos-latest'
-    if: |
-      always() && (needs.merge_queue_skipper.result !='success' || needs.merge_queue_skipper.outputs.skip != 'true')
     steps:
       - name: 'Checkout'
         uses: 'actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955' # ratchet:actions/checkout@v5
         with:
-          ref: '${{ needs.parse_run_context.outputs.sha }}'
-          repository: '${{ needs.parse_run_context.outputs.repository }}'
+          ref: '${{ github.event.inputs.head_sha || github.event.workflow_run.head_sha }}'
+          repository: '${{ needs.download_repo_name.outputs.repo_name }}'
 
       - name: 'Set up Node.js 20.x'
         uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020' # ratchet:actions-node@v4
@@ -203,11 +138,11 @@ jobs:
         run: 'npm run build'
 
       - name: 'Fix rollup optional dependencies on macOS'
-        if: "${{runner.os == 'macOS'}}"
+        if: "runner.os == 'macOS'"
         run: |
           npm cache clean --force
       - name: 'Run E2E tests (non-Windows)'
-        if: "${{runner.os != 'Windows'}}"
+        if: "runner.os != 'Windows'"
         env:
           GEMINI_API_KEY: '${{ secrets.GEMINI_API_KEY }}'
           KEEP_OUTPUT: 'true'
@@ -219,9 +154,9 @@ jobs:
     name: 'Slow E2E - Win'
     needs:
       - 'merge_queue_skipper'
-      - 'parse_run_context'
+      - 'download_repo_name'
     if: |
-      always() && (needs.merge_queue_skipper.result !='success' || needs.merge_queue_skipper.outputs.skip != 'true')
+      needs.merge_queue_skipper.outputs.skip == 'false'
     runs-on: 'gemini-cli-windows-16-core'
     continue-on-error: true
 
@@ -229,8 +164,8 @@ jobs:
       - name: 'Checkout'
         uses: 'actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955' # ratchet:actions/checkout@v5
         with:
-          ref: '${{ needs.parse_run_context.outputs.sha }}'
-          repository: '${{ needs.parse_run_context.outputs.repository }}'
+          ref: '${{ github.event.inputs.head_sha || github.event.workflow_run.head_sha }}'
+          repository: '${{ needs.download_repo_name.outputs.repo_name }}'
 
       - name: 'Set up Node.js 20.x'
         uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020' # ratchet:actions-node@v4
@@ -279,7 +214,7 @@ jobs:
   e2e:
     name: 'E2E'
     if: |
-      always() && (needs.merge_queue_skipper.result !='success' || needs.merge_queue_skipper.outputs.skip != 'true')
+      always() && needs.merge_queue_skipper.outputs.skip == 'false'
     needs:
       - 'e2e_linux'
       - 'e2e_mac'
@@ -294,22 +229,3 @@ jobs:
             exit 1
           fi
           echo "All required E2E jobs passed!"
-
-  set_workflow_status:
-    runs-on: 'gemini-cli-ubuntu-16-core'
-    permissions: 'write-all'
-    if: 'always()'
-    needs:
-      - 'parse_run_context'
-      - 'e2e'
-    steps:
-      - name: 'Set workflow status'
-        uses: 'myrotvorets/set-commit-status-action@16037e056d73b2d3c88e37e393ff369047f70886' # ratchet:myrotvorets/set-commit-status-action@master
-        if: 'always()'
-        with:
-          allowForks: 'true'
-          repo: '${{ github.repository }}'
-          sha: '${{ needs.parse_run_context.outputs.sha }}'
-          token: '${{ secrets.GITHUB_TOKEN }}'
-          status: '${{ needs.e2e.result }}'
-          context: 'E2E (Chained)'

.github/workflows/trigger_e2e.yml

@@ -3,15 +3,11 @@ name: 'Trigger E2E'
 on:
   workflow_dispatch:
     inputs:
-      repo_name:
-        description: 'Repository name (e.g., owner/repo)'
-        required: false
+      branch_ref:
+        description: 'Branch to run on'
+        required: true
+        default: 'main'
         type: 'string'
-      head_sha:
-        description: 'SHA of the commit to test'
-        required: false
-        type: 'string'
-  pull_request:
 
 jobs:
   save_repo_name:
@@ -19,12 +15,11 @@ jobs:
     steps:
       - name: 'Save Repo name'
         env:
-          REPO_NAME: '${{ github.event.inputs.repo_name || github.event.pull_request.head.repo.full_name }}'
-          HEAD_SHA: '${{ github.event.inputs.head_sha || github.event.pull_request.head.sha }}'
+          # Replace with github.event.pull_request.base.repo.full_name when switched to listen on pull request events. This repo name does not contain the org which is needed for checkout.
+          REPO_NAME: '${{ github.event.repository.name }}'
         run: |
           mkdir -p ./pr
           echo '${{ env.REPO_NAME }}' > ./pr/repo_name
-          echo '${{ env.HEAD_SHA }}' > ./pr/head_sha
       - uses: 'actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02' # ratchet:actions/upload-artifact@v4
         with:
           name: 'repo_name'

.gitignore

@@ -17,6 +17,7 @@
 # Dependency directory
 node_modules
 bower_components
+package-lock.json
 
 # Editors
 .idea
@@ -53,6 +54,3 @@ gha-creds-*.json
 
 # Log files
 patch_output.log
-
-.genkit
-.gemini-clipboard/

.lycheeignore

@@ -1,6 +0,0 @@
-http://localhost:16686/
-https://github.com/google-gemini/gemini-cli/issues/new/choose
-https://github.com/google-gemini/maintainers-gemini-cli/blob/main/npm.md
-https://github.com/settings/personal-access-tokens/new
-https://github.com/settings/tokens/new
-https://www.npmjs.com/package/@google/gemini-cli

.prettierignore

@@ -18,4 +18,3 @@ eslint.config.js
 gha-creds-*.json
 junit.xml
 Thumbs.db
-.pytest_cache

CONTRIBUTING.md

@@ -1,18 +1,6 @@
-# How to contribute
+# How to Contribute
 
-We would love to accept your patches and contributions to this project. This
-document includes:
-
-- **[Before you begin](#before-you-begin):** Essential steps to take before
-  becoming a Gemini CLI contributor.
-- **[Code contribution process](#code-contribution-process):** How to contribute
-  code to Gemini CLI.
-- **[Development setup and workflow](#development-setup-and-workflow):** How to
-  set up your development environment and workflow.
-- **[Documentation contribution process](#documentation-contribution-process):**
-  How to contribute documentation to Gemini CLI.
-
-We're looking forward to seeing your contributions!
+We would love to accept your patches and contributions to this project.
 
 ## Before you begin
 
@@ -35,42 +23,19 @@ sign a new one.
 This project follows
 [Google's Open Source Community Guidelines](https://opensource.google/conduct/).
 
-## Code contribution process
+## Contribution Process
 
-### Get started
-
-The process for contributing code is as follows:
-
-1.  **Find an issue** that you want to work on. If an issue is tagged as
-    "🔒Maintainers only", this means it is reserved for project maintainers. We
-    will not accept pull requests related to these issues.
-2.  **Fork the repository** and create a new branch.
-3.  **Make your changes** in the `packages/` directory.
-4.  **Ensure all checks pass** by running `npm run preflight`.
-5.  **Open a pull request** with your changes.
-
-### Code reviews
+### Code Reviews
 
 All submissions, including submissions by project members, require review. We
 use [GitHub pull requests](https://docs.github.com/articles/about-pull-requests)
 for this purpose.
 
-If your pull request involves changes to `packages/cli` (the frontend), we
-recommend running our automated frontend review tool. **Note: This tool is
-currently experimental.** It helps detect common React anti-patterns, testing
-issues, and other frontend-specific best practices that are easy to miss.
+### Self Assigning Issues
 
-To run the review tool, enter the following command from within Gemini CLI:
-
-```text
-/review-frontend <PR_NUMBER>
-```
-
-Replace `<PR_NUMBER>` with your pull request number. Authors are encouraged to
-run this on their own PRs for self-review, and reviewers should use it to
-augment their manual review process.
-
-### Self assigning issues
+If you're looking for an issue to work on, check out our list of issues that are
+labeled
+["help wanted"](https://github.com/google-gemini/gemini-cli/issues?q=is%3Aissue+state%3Aopen+label%3A%22help+wanted%22).
 
 To assign an issue to yourself, simply add a comment with the text `/assign`.
 The comment must contain only that text and nothing else. This command will
@@ -79,12 +44,12 @@ assign the issue to you, provided it is not already assigned.
 Please note that you can have a maximum of 3 issues assigned to you at any given
 time.
 
-### Pull request guidelines
+### Pull Request Guidelines
 
 To help us review and merge your PRs quickly, please follow these guidelines.
 PRs that do not meet these standards may be closed.
 
-#### 1. Link to an existing issue
+#### 1. Link to an Existing Issue
 
 All PRs should be linked to an existing issue in our tracker. This ensures that
 every change has been discussed and is aligned with the project's goals before
@@ -97,7 +62,7 @@ any code is written.
 If an issue for your change doesn't exist, please **open one first** and wait
 for feedback before you start coding.
 
-#### 2. Keep it small and focused
+#### 2. Keep It Small and Focused
 
 We favor small, atomic PRs that address a single issue or add a single,
 self-contained feature.
@@ -109,40 +74,37 @@ self-contained feature.
 Large changes should be broken down into a series of smaller, logical PRs that
 can be reviewed and merged independently.
 
-#### 3. Use draft PRs for work in progress
+#### 3. Use Draft PRs for Work in Progress
 
 If you'd like to get early feedback on your work, please use GitHub's **Draft
 Pull Request** feature. This signals to the maintainers that the PR is not yet
 ready for a formal review but is open for discussion and initial feedback.
 
-#### 4. Ensure all checks pass
+#### 4. Ensure All Checks Pass
 
 Before submitting your PR, ensure that all automated checks are passing by
 running `npm run preflight`. This command runs all tests, linting, and other
 style checks.
 
-#### 5. Update documentation
+#### 5. Update Documentation
 
 If your PR introduces a user-facing change (e.g., a new command, a modified
 flag, or a change in behavior), you must also update the relevant documentation
 in the `/docs` directory.
 
-See more about writing documentation:
-[Documentation contribution process](#documentation-contribution-process).
-
-#### 6. Write clear commit messages and a good PR description
+#### 6. Write Clear Commit Messages and a Good PR Description
 
 Your PR should have a clear, descriptive title and a detailed description of the
 changes. Follow the [Conventional Commits](https://www.conventionalcommits.org/)
 standard for your commit messages.
 
-- **Good PR title:** `feat(cli): Add --json flag to 'config get' command`
-- **Bad PR title:** `Made some changes`
+- **Good PR Title:** `feat(cli): Add --json flag to 'config get' command`
+- **Bad PR Title:** `Made some changes`
 
 In the PR description, explain the "why" behind your changes and link to the
 relevant issue (e.g., `Fixes #123`).
 
-### Forking
+## Forking
 
 If you are forking the repository you will be able to run the Build, Test and
 Integration test workflows. However in order to make the integration tests run
@@ -156,12 +118,12 @@ Additionally you will need to click on the `Actions` tab and enable workflows
 for your repository, you'll find it's the large blue button in the center of the
 screen.
 
-### Development setup and workflow
+## Development Setup and Workflow
 
 This section guides contributors on how to build, modify, and understand the
 development setup of this project.
 
-### Setting up the development environment
+### Setting Up the Development Environment
 
 **Prerequisites:**
 
@@ -173,7 +135,7 @@ development setup of this project.
       version of Node.js `>=20` is acceptable.
 2.  **Git**
 
-### Build process
+### Build Process
 
 To clone the repository:
 
@@ -198,7 +160,7 @@ This command typically compiles TypeScript to JavaScript, bundles assets, and
 prepares the packages for execution. Refer to `scripts/build.js` and
 `package.json` scripts for more details on what happens during the build.
 
-### Enabling sandboxing
+### Enabling Sandboxing
 
 [Sandboxing](#sandboxing) is highly recommended and requires, at a minimum,
 setting `GEMINI_SANDBOX=true` in your `~/.env` and ensuring a sandboxing
@@ -214,7 +176,7 @@ npm run build:all
 
 To skip building the sandbox container, you can use `npm run build` instead.
 
-### Running the CLI
+### Running
 
 To start the Gemini CLI from the source code (after building), run the following
 command from the root directory:
@@ -228,11 +190,11 @@ utilize `npm link path/to/gemini-cli/packages/cli` (see:
 [docs](https://docs.npmjs.com/cli/v9/commands/npm-link)) or
 `alias gemini="node path/to/gemini-cli/packages/cli"` to run with `gemini`
 
-### Running tests
+### Running Tests
 
 This project contains two types of tests: unit tests and integration tests.
 
-#### Unit tests
+#### Unit Tests
 
 To execute the unit test suite for the project:
 
@@ -244,7 +206,7 @@ This will run tests located in the `packages/core` and `packages/cli`
 directories. Ensure tests pass before submitting any changes. For a more
 comprehensive check, it is recommended to run `npm run preflight`.
 
-#### Integration tests
+#### Integration Tests
 
 The integration tests are designed to validate the end-to-end functionality of
 the Gemini CLI. They are not run as part of the default `npm run test` command.
@@ -256,9 +218,9 @@ npm run test:e2e
 ```
 
 For more detailed information on the integration testing framework, please see
-the [Integration Tests documentation](/docs/integration-tests.md).
+the [Integration Tests documentation](./docs/integration-tests.md).
 
-### Linting and preflight checks
+### Linting and Preflight Checks
 
 To ensure code quality and formatting consistency, run the preflight check:
 
@@ -305,7 +267,7 @@ root directory:
 npm run lint
 ```
 
-### Coding conventions
+### Coding Conventions
 
 - Please adhere to the coding style, patterns, and conventions used throughout
   the existing codebase.
@@ -317,24 +279,19 @@ npm run lint
 - **Imports:** Pay special attention to import paths. The project uses ESLint to
   enforce restrictions on relative imports between packages.
 
-### Project structure
+### Project Structure
 
 - `packages/`: Contains the individual sub-packages of the project.
-  - `a2a-server`: A2A server implementation for the Gemini CLI. (Experimental)
   - `cli/`: The command-line interface.
   - `core/`: The core backend logic for the Gemini CLI.
-  - `test-utils` Utilities for creating and cleaning temporary file systems for
-    testing.
-  - `vscode-ide-companion/`: The Gemini CLI Companion extension pairs with
-    Gemini CLI.
 - `docs/`: Contains all project documentation.
 - `scripts/`: Utility scripts for building, testing, and development tasks.
 
 For more detailed architecture, see `docs/architecture.md`.
 
-### Debugging
+## Debugging
 
-#### VS Code
+### VS Code:
 
 0.  Run the CLI to interactively debug in VS Code with `F5`
 1.  Start the CLI in debug mode from the root directory:
@@ -392,9 +349,9 @@ used for the CLI's interface, is compatible with React DevTools version 4.x.
     Your running CLI application should then connect to React DevTools.
     ![](/docs/assets/connected_devtools.png)
 
-### Sandboxing
+## Sandboxing
 
-#### macOS Seatbelt
+### macOS Seatbelt
 
 On macOS, `gemini` uses Seatbelt (`sandbox-exec`) under a `permissive-open`
 profile (see `packages/cli/src/utils/sandbox-macos-permissive-open.sb`) that
@@ -410,7 +367,7 @@ Available built-in profiles are `{permissive,restrictive}-{open,closed,proxied}`
 `.gemini/sandbox-macos-<profile>.sb` under your project settings directory
 `.gemini`.
 
-#### Container-based sandboxing (all platforms)
+### Container-based Sandboxing (All Platforms)
 
 For stronger container-based sandboxing on macOS or other platforms, you can set
 `GEMINI_SANDBOX=true|docker|podman|<command>` in your environment or `.env`
@@ -433,7 +390,7 @@ for your projects by creating the files `.gemini/sandbox.Dockerfile` and/or
 running `gemini` with `BUILD_SANDBOX=1` to trigger building of your custom
 sandbox.
 
-#### Proxied networking
+#### Proxied Networking
 
 All sandboxing methods, including macOS Seatbelt using `*-proxied` profiles,
 support restricting outbound network traffic through a custom proxy server that
@@ -444,7 +401,7 @@ connections to `example.com:443` (e.g. `curl https://example.com`) and declines
 all other requests. The proxy is started and stopped automatically alongside the
 sandbox.
 
-### Manual publish
+## 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:
@@ -456,91 +413,3 @@ npm run auth
 npm run prerelease:dev
 npm publish --workspaces
 ```
-
-## Documentation contribution process
-
-Our documentation must be kept up-to-date with our code contributions. We want
-our documentation to be clear, concise, and helpful to our users. We value:
-
-- **Clarity:** Use simple and direct language. Avoid jargon where possible.
-- **Accuracy:** Ensure all information is correct and up-to-date.
-- **Completeness:** Cover all aspects of a feature or topic.
-- **Examples:** Provide practical examples to help users understand how to use
-  Gemini CLI.
-
-### Getting started
-
-The process for contributing to the documentation is similar to contributing
-code.
-
-1. **Fork the repository** and create a new branch.
-2. **Make your changes** in the `/docs` directory.
-3. **Preview your changes locally** in Markdown rendering.
-4. **Lint and format your changes.** Our preflight check includes linting and
-   formatting for documentation files.
-   ```bash
-   npm run preflight
-   ```
-5. **Open a pull request** with your changes.
-
-### Documentation structure
-
-Our documentation is organized using [sidebar.json](/docs/sidebar.json) as the
-table of contents. When adding new documentation:
-
-1. Create your markdown file **in the appropriate directory** under `/docs`.
-2. Add an entry to `sidebar.json` in the relevant section.
-3. Ensure all internal links use relative paths and point to existing files.
-
-### Style guide
-
-We follow the
-[Google Developer Documentation Style Guide](https://developers.google.com/style).
-Please refer to it for guidance on writing style, tone, and formatting.
-
-#### Key style points
-
-- Use sentence case for headings.
-- Write in second person ("you") when addressing the reader.
-- Use present tense.
-- Keep paragraphs short and focused.
-- Use code blocks with appropriate language tags for syntax highlighting.
-- Include practical examples whenever possible.
-
-### Linting and formatting
-
-We use `prettier` to enforce a consistent style across our documentation. The
-`npm run preflight` command will check for any linting issues.
-
-You can also run the linter and formatter separately:
-
-- `npm run lint` - Check for linting issues
-- `npm run format` - Auto-format markdown files
-- `npm run lint:fix` - Auto-fix linting issues where possible
-
-Please make sure your contributions are free of linting errors before submitting
-a pull request.
-
-### Before you submit
-
-Before submitting your documentation pull request, please:
-
-1. Run `npm run preflight` to ensure all checks pass.
-2. Review your changes for clarity and accuracy.
-3. Check that all links work correctly.
-4. Ensure any code examples are tested and functional.
-5. Sign the
-   [Contributor License Agreement (CLA)](https://cla.developers.google.com/) if
-   you haven't already.
-
-### Need help?
-
-If you have questions about contributing documentation:
-
-- Check our [FAQ](/docs/faq.md).
-- Review existing documentation for examples.
-- Open [an issue](https://github.com/google-gemini/gemini-cli/issues) to discuss
-  your proposed changes.
-- Reach out to the maintainers.
-
-We appreciate your contributions to making Gemini CLI documentation better!

GEMINI.md

@@ -363,47 +363,12 @@ performance.
 - State updates should be structured to enable granular updates
 - Side effects should be isolated and dependencies clearly defined
 
-## Documentation guidelines
-
-When working in the `/docs` directory, follow the guidelines in this section:
-
-- **Role:** You are an expert technical writer and AI assistant for contributors
-  to Gemini CLI. Produce professional, accurate, and consistent documentation to
-  guide users of Gemini CLI.
-- **Technical Accuracy:** Do not invent facts, commands, code, API names, or
-  output. All technical information specific to Gemini CLI must be based on code
-  found within this directory and its subdirectories.
-- **Style Authority:** Your source for writing guidance and style is the
-  "Documentation contribution process" section in the root directory's
-  `CONTRIBUTING.md` file, as well as any guidelines provided this section.
-- **Information Architecture Consideration:** Before proposing documentation
-  changes, consider the information architecture. If a change adds significant
-  new content to existing documents, evaluate if creating a new, more focused
-  page or changes to `sidebar.json` would provide a better user experience.
-- **Proactive User Consideration:** The user experience should be a primary
-  concern when making changes to documentation. Aim to fill gaps in existing
-  knowledge whenever possible while keeping documentation concise and easy for
-  users to understand. If changes might hinder user understanding or
-  accessibility, proactively raise these concerns and propose alternatives.
-
 ## Comments policy
 
 Only write high-value comments if at all. Avoid talking to the user through
 comments.
 
-## Logging and Error Handling
+## General style requirements
 
-- **Avoid Console Statements:** Do not use `console.log`, `console.error`, or
-  similar methods directly.
-- **Non-User-Facing Logs:** For developer-facing debug messages, use
-  `debugLogger` (from `@google/gemini-cli-core`).
-- **User-Facing Feedback:** To surface errors or warnings to the user, use
-  `coreEvents.emitFeedback` (from `@google/gemini-cli-core`).
-
-## General requirements
-
-- If there is something you do not understand or is ambiguous, seek confirmation
-  or clarification from the user before making changes based on assumptions.
-- Use hyphens instead of underscores in flag names (e.g. `my-flag` instead of
-  `my_flag`).
-- Always refer to Gemini CLI as `Gemini CLI`, never `the Gemini CLI`.
+Use hyphens instead of underscores in flag names (e.g. `my-flag` instead of
+`my_flag`).

README.md

@@ -1,10 +1,9 @@
 # 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)
-[![Gemini CLI E2E (Chained)](https://github.com/google-gemini/gemini-cli/actions/workflows/chained_e2e.yml/badge.svg)](https://github.com/google-gemini/gemini-cli/actions/workflows/chained_e2e.yml)
+[![Gemini CLI E2E](https://github.com/google-gemini/gemini-cli/actions/workflows/e2e.yml/badge.svg)](https://github.com/google-gemini/gemini-cli/actions/workflows/e2e.yml)
 [![Version](https://img.shields.io/npm/v/@google/gemini-cli)](https://www.npmjs.com/package/@google/gemini-cli)
 [![License](https://img.shields.io/github/license/google-gemini/gemini-cli)](https://github.com/google-gemini/gemini-cli/blob/main/LICENSE)
-[![View Code Wiki](https://www.gstatic.com/_/boq-sdlc-agents-ui/_/r/YUi5dj2UWvE.svg)](https://codewiki.google/github.com/google-gemini/gemini-cli)
 
 ![Gemini CLI Screenshot](./docs/assets/gemini-screenshot.png)
 
@@ -28,11 +27,6 @@ Learn all about Gemini CLI in our [documentation](https://geminicli.com/docs/).
 
 ## 📦 Installation
 
-### Pre-requisites before installation
-
-- Node.js version 20 or higher
-- macOS, Linux, or Windows
-
 ### Quick Install
 
 #### Run instantly with npx
@@ -54,6 +48,11 @@ npm install -g @google/gemini-cli
 brew install gemini-cli
 ```
 
+#### System Requirements
+
+- Node.js version 20 or higher
+- macOS, Linux, or Windows
+
 ## Release Cadence and Tags
 
 See [Releases](./docs/releases.md) for more details.
@@ -80,9 +79,9 @@ npm install -g @google/gemini-cli@latest
 
 ### Nightly
 
-- New releases will be published each day at UTC 0000. 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.
+- 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
@@ -307,8 +306,6 @@ gemini
   corporate environment.
 - [**Telemetry & Monitoring**](./docs/cli/telemetry.md) - Usage tracking.
 - [**Tools API Development**](./docs/core/tools-api.md) - Create custom tools.
-- [**Local development**](./docs/local-development.md) - Local development
-  tooling.
 
 ### Troubleshooting & Support
 

docs/CONTRIBUTING.md

@@ -1 +0,0 @@
-../CONTRIBUTING.md

docs/architecture.md

@@ -37,7 +37,7 @@ input:
     - **Interaction:** `packages/core` invokes these tools based on requests
       from the Gemini model.
 
-## Interaction flow
+## Interaction Flow
 
 A typical interaction with the Gemini CLI follows this flow:
 
@@ -69,7 +69,7 @@ A typical interaction with the Gemini CLI follows this flow:
 7.  **Display to user:** The CLI package formats and displays the response to
     the user in the terminal.
 
-## Key design principles
+## Key Design Principles
 
 - **Modularity:** Separating the CLI (frontend) from the Core (backend) allows
   for independent development and potential future extensions (e.g., different

docs/changelogs/index.md

@@ -1,294 +1,9 @@
-# Gemini CLI release notes
+# Gemini CLI Changelog
 
-Gemini CLI has three major release channels: nightly, preview, and stable. For
-most users, we recommend the stable release.
+Wondering what's new in Gemini CLI? This document provides key highlights and
+notable changes to Gemini CLI.
 
-On this page, you can find information regarding the current releases and
-announcements from each release.
-
-For the full changelog, refer to
-[Releases - google-gemini/gemini-cli](https://github.com/google-gemini/gemini-cli/releases)
-on GitHub.
-
-## Current releases
-
-| Release channel       | Notes                                           |
-| :-------------------- | :---------------------------------------------- |
-| Nightly               | Nightly release with the most recent changes.   |
-| [Preview](preview.md) | Experimental features ready for early feedback. |
-| [Stable](latest.md)   | Stable, recommended for general use.            |
-
-## Announcements: v0.21.0 - 2025-12-15
-
-- **⚡️⚡️⚡️ Gemini 3 Flash + Gemini CLI:** Better, faster and cheaper than 2.5
-  Pro - and in some scenarios better than 3 Pro! For paid tiers + free tier
-  users who were on the wait list enable **Preview Features** in `/settings.`
-- For more information:
-  [Gemini 3 Flash is now available in Gemini CLI](https://developers.googleblog.com/gemini-3-flash-is-now-available-in-gemini-cli/).
-- 🎉 Gemini CLI Extensions:
-  - Rill: Utilize natural language to analyze Rill data, enabling the
-    exploration of metrics and trends without the need for manual queries.
-    `gemini extensions install https://github.com/rilldata/rill-gemini-extension`
-  - Browserbase: Interact with web pages, take screenshots, extract information,
-    and perform automated actions with atomic precision.
-    `gemini extensions install https://github.com/browserbase/mcp-server-browserbase`
-- Quota Visibility: The `/stats` command now displays quota information for all
-  available models, including those not used in the current session. (@sehoon38)
-- Fuzzy Setting Search: Users can now quickly find settings using fuzzy search
-  within the settings dialog. (@sehoon38)
-- MCP Resource Support: Users can now discover, view, and search through
-  resources using the @ command. (@MrLesk)
-- Auto-execute Simple Slash Commands: Simple slash commands are now executed
-  immediately on enter. (@jackwotherspoon)
-
-## Announcements: v0.20.0 - 2025-12-01
-
-- **Multi-file Drag & Drop:** Users can now drag and drop multiple files into
-  the terminal, and the CLI will automatically prefix each valid path with `@`.
-  ([pr](https://github.com/google-gemini/gemini-cli/pull/14832) by
-  [@jackwotherspoon](https://github.com/jackwotherspoon))
-- **Persistent "Always Allow" Policies:** Users can now save "Always Allow"
-  decisions for tool executions, with granular control over specific shell
-  commands and multi-cloud platform tools.
-  ([pr](https://github.com/google-gemini/gemini-cli/pull/14737) by
-  [@allenhutchison](https://github.com/allenhutchison))
-
-## Announcements: v0.19.0 - 2025-11-24
-
-- 🎉 **New extensions:**
-  - **Eleven Labs:** Create, play, manage your audio play tracks with the Eleven
-    Labs Gemini CLI extension:
-    `gemini extensions install https://github.com/elevenlabs/elevenlabs-mcp`
-- **Zed integration:** Users can now leverage Gemini 3 within the Zed
-  integration after enabling "Preview Features" in their CLI’s `/settings`.
-  ([pr](https://github.com/google-gemini/gemini-cli/pull/13398) by
-  [@benbrandt](https://github.com/benbrandt))
-- **Interactive shell:**
-  - **Click-to-Focus:** When "Use Alternate Buffer" setting is enabled, users
-    can click within the embedded shell output to focus it for input.
-    ([pr](https://github.com/google-gemini/gemini-cli/pull/13341) by
-    [@galz10](https://github.com/galz10))
-  - **Loading phrase:** Clearly indicates when the interactive shell is awaiting
-    user input. ([vid](https://imgur.com/a/kjK8bUK),
-    [pr](https://github.com/google-gemini/gemini-cli/pull/12535) by
-    [@jackwotherspoon](https://github.com/jackwotherspoon))
-
-## Announcements: v0.18.0 - 2025-11-17
-
-- 🎉 **New extensions:**
-  - **Google Workspace**: Integrate Gemini CLI with your Workspace data. Write
-    docs, build slides, chat with others or even get your calc on in sheets:
-    `gemini extensions install https://github.com/gemini-cli-extensions/workspace`
-    - Blog:
-      [https://allen.hutchison.org/2025/11/19/bringing-the-office-to-the-terminal/](https://allen.hutchison.org/2025/11/19/bringing-the-office-to-the-terminal/)
-  - **Redis:** Manage and search data in Redis with natural language:
-    `gemini extensions install https://github.com/redis/mcp-redis`
-  - **Anomalo:** Query your data warehouse table metadata and quality status
-    through commands and natural language:
-    `gemini extensions install https://github.com/datagravity-ai/anomalo-gemini-extension`
-- **Experimental permission improvements:** We are now experimenting with a new
-  policy engine in Gemini CLI. This allows users and administrators to create
-  fine-grained policy for tool calls. Currently behind a flag. See
-  [policy engine documentation](../core/policy-engine.md) for more information.
-  - Blog:
-    [https://allen.hutchison.org/2025/11/26/the-guardrails-of-autonomy/](https://allen.hutchison.org/2025/11/26/the-guardrails-of-autonomy/)
-- **Gemini 3 support for paid:** Gemini 3 support has been rolled out to all API
-  key, Google AI Pro or Google AI Ultra (for individuals, not businesses) and
-  Gemini Code Assist Enterprise users. Enable it via `/settings` and toggling on
-  **Preview Features**.
-- **Updated UI rollback:** We’ve temporarily rolled back our updated UI to give
-  it more time to bake. This means for a time you won’t have embedded scrolling
-  or mouse support. You can re-enable with `/settings` -> **Use Alternate Screen
-  Buffer** -> `true`.
-- **Model in history:** Users can now toggle in `/settings` to display model in
-  their chat history. ([gif](https://imgur.com/a/uEmNKnQ),
-  [pr](https://github.com/google-gemini/gemini-cli/pull/13034) by
-  [@scidomino](https://github.com/scidomino))
-- **Multi-uninstall:** Users can now uninstall multiple extensions with a single
-  command. ([pic](https://imgur.com/a/9Dtq8u2),
-  [pr](https://github.com/google-gemini/gemini-cli/pull/13016) by
-  [@JayadityaGit](https://github.com/JayadityaGit))
-
-## Announcements: v0.16.0 - 2025-11-10
-
-- **Gemini 3 + Gemini CLI:** launch 🚀🚀🚀
-- **Data Commons Gemini CLI Extension** - A new Data Commons Gemini CLI
-  extension that lets you query open-source statistical data from
-  datacommons.org. **To get started, you'll need a Data Commons API key and uv
-  installed**. These and other details to get you started with the extension can
-  be found at
-  [https://github.com/gemini-cli-extensions/datacommons](https://github.com/gemini-cli-extensions/datacommons).
-
-## Announcements: v0.15.0 - 2025-11-03
-
-- **🎉 Seamless scrollable UI and mouse support:** We’ve given Gemini CLI a
-  major facelift to make your terminal experience smoother and much more
-  polished. You now get a flicker-free display with sticky headers that keep
-  important context visible and a stable input prompt that doesn't jump around.
-  We even added mouse support so you can click right where you need to type!
-  ([gif](https://imgur.com/a/O6qc7bx),
-  [@jacob314](https://github.com/jacob314)).
-  - **Announcement:**
-    [https://developers.googleblog.com/en/making-the-terminal-beautiful-one-pixel-at-a-time/](https://developers.googleblog.com/en/making-the-terminal-beautiful-one-pixel-at-a-time/)
-- **🎉 New partner extensions:**
-  - **Arize:** Seamlessly instrument AI applications with Arize AX and grant
-    direct access to Arize support:
-
-    `gemini extensions install https://github.com/Arize-ai/arize-tracing-assistant`
-
-  - **Chronosphere:** Retrieve logs, metrics, traces, events, and specific
-    entities:
-
-    `gemini extensions install https://github.com/chronosphereio/chronosphere-mcp`
-
-  - **Transmit:** Comprehensive context, validation, and automated fixes for
-    creating production-ready authentication and identity workflows:
-
-    `gemini extensions install https://github.com/TransmitSecurity/transmit-security-journey-builder`
-
-- **Todo planning:** Complex questions now get broken down into todo lists that
-  the model can manage and check off. ([gif](https://imgur.com/a/EGDfNlZ),
-  [pr](https://github.com/google-gemini/gemini-cli/pull/12905) by
-  [@anj-s](https://github.com/anj-s))
-- **Disable GitHub extensions:** Users can now prevent the installation and
-  loading of extensions from GitHub.
-  ([pr](https://github.com/google-gemini/gemini-cli/pull/12838) by
-  [@kevinjwang1](https://github.com/kevinjwang1)).
-- **Extensions restart:** Users can now explicitly restart extensions using the
-  `/extensions restart` command.
-  ([pr](https://github.com/google-gemini/gemini-cli/pull/12739) by
-  [@jakemac53](https://github.com/jakemac53)).
-- **Better Angular support:** Angular workflows should now be more seamless
-  ([pr](https://github.com/google-gemini/gemini-cli/pull/10252) by
-  [@MarkTechson](https://github.com/MarkTechson)).
-- **Validate command:** Users can now check that local extensions are formatted
-  correctly. ([pr](https://github.com/google-gemini/gemini-cli/pull/12186) by
-  [@kevinjwang1](https://github.com/kevinjwang1)).
-
-## Announcements: v0.12.0 - 2025-10-27
-
-![Codebase investigator subagent in Gemini CLI.](https://i.imgur.com/4J1njsx.png)
-
-- **🎉 New partner extensions:**
-  - **🤗 Hugging Face extension:** Access the Hugging Face hub.
-    ([gif](https://drive.google.com/file/d/1LEzIuSH6_igFXq96_tWev11svBNyPJEB/view?usp=sharing&resourcekey=0-LtPTzR1woh-rxGtfPzjjfg))
-
-    `gemini extensions install https://github.com/huggingface/hf-mcp-server`
-
-  - **Monday.com extension**: Analyze your sprints, update your task boards,
-    etc.
-    ([gif](https://drive.google.com/file/d/1cO0g6kY1odiBIrZTaqu5ZakaGZaZgpQv/view?usp=sharing&resourcekey=0-xEr67SIjXmAXRe1PKy7Jlw))
-
-    `gemini extensions install https://github.com/mondaycom/mcp`
-
-  - **Data Commons extension:** Query public datasets or ground responses on
-    data from Data Commons
-    ([gif](https://drive.google.com/file/d/1cuj-B-vmUkeJnoBXrO_Y1CuqphYc6p-O/view?usp=sharing&resourcekey=0-0adXCXDQEd91ZZW63HbW-Q)).
-
-    `gemini extensions install https://github.com/gemini-cli-extensions/datacommons`
-
-- **Model selection:** Choose the Gemini model for your session with `/model`.
-  ([pic](https://imgur.com/a/ABFcWWw),
-  [pr](https://github.com/google-gemini/gemini-cli/pull/8940) by
-  [@abhipatel12](https://github.com/abhipatel12)).
-- **Model routing:** Gemini CLI will now intelligently pick the best model for
-  the task. Simple queries will be sent to Flash while complex analytical or
-  creative tasks will still use the power of Pro. This ensures your quota will
-  last for a longer period of time. You can always opt-out of this via `/model`.
-  ([pr](https://github.com/google-gemini/gemini-cli/pull/9262) by
-  [@abhipatel12](https://github.com/abhipatel12)).
-  - Discussion:
-    [https://github.com/google-gemini/gemini-cli/discussions/12375](https://github.com/google-gemini/gemini-cli/discussions/12375)
-- **Codebase investigator subagent:** We now have a new built-in subagent that
-  will explore your workspace and resolve relevant information to improve
-  overall performance.
-  ([pr](https://github.com/google-gemini/gemini-cli/pull/9988) by
-  [@abhipatel12](https://github.com/abhipatel12),
-  [pr](https://github.com/google-gemini/gemini-cli/pull/10282) by
-  [@silviojr](https://github.com/silviojr)).
-  - Enable, disable, or limit turns in `/settings`, plus advanced configs in
-    `settings.json` ([pic](https://imgur.com/a/yJiggNO),
-    [pr](https://github.com/google-gemini/gemini-cli/pull/10844) by
-    [@silviojr](https://github.com/silviojr)).
-- **Explore extensions with `/extension`:** Users can now open the extensions
-  page in their default browser directly from the CLI using the `/extension`
-  explore command. ([pr](https://github.com/google-gemini/gemini-cli/pull/11846)
-  by [@JayadityaGit](https://github.com/JayadityaGit)).
-- **Configurable compression:** Users can modify the compression threshold in
-  `/settings`. The default has been made more proactive
-  ([pr](https://github.com/google-gemini/gemini-cli/pull/12317) by
-  [@scidomino](https://github.com/scidomino)).
-- **API key authentication:** Users can now securely enter and store their
-  Gemini API key via a new dialog, eliminating the need for environment
-  variables and repeated entry.
-  ([pr](https://github.com/google-gemini/gemini-cli/pull/11760) by
-  [@galz10](https://github.com/galz10)).
-- **Sequential approval:** Users can now approve multiple tool calls
-  sequentially during execution.
-  ([pr](https://github.com/google-gemini/gemini-cli/pull/11593) by
-  [@joshualitt](https://github.com/joshualitt)).
-
-## Announcements: v0.11.0 - 2025-10-20
-
-![Gemini CLI and Jules](https://storage.googleapis.com/gweb-developer-goog-blog-assets/images/Jules_Extension_-_Blog_Header_O346JNt.original.png)
-
-- 🎉 **Gemini CLI Jules Extension:** Use Gemini CLI to orchestrate Jules. Spawn
-  remote workers, delegate tedious tasks, or check in on running jobs!
-  - Install:
-    `gemini extensions install https://github.com/gemini-cli-extensions/jules`
-  - Announcement:
-    [https://developers.googleblog.com/en/introducing-the-jules-extension-for-gemini-cli/](https://developers.googleblog.com/en/introducing-the-jules-extension-for-gemini-cli/)
-- **Stream JSON output:** Stream real-time JSONL events with
-  `--output-format stream-json` to monitor AI agent progress when run
-  headlessly. ([gif](https://imgur.com/a/0UCE81X),
-  [pr](https://github.com/google-gemini/gemini-cli/pull/10883) by
-  [@anj-s](https://github.com/anj-s))
-- **Markdown toggle:** Users can now switch between rendered and raw markdown
-  display using `alt+m `or` ctrl+m`. ([gif](https://imgur.com/a/lDNdLqr),
-  [pr](https://github.com/google-gemini/gemini-cli/pull/10383) by
-  [@srivatsj](https://github.com/srivatsj))
-- **Queued message editing:** Users can now quickly edit queued messages by
-  pressing the up arrow key when the input is empty.
-  ([gif](https://imgur.com/a/ioRslLd),
-  [pr](https://github.com/google-gemini/gemini-cli/pull/10392) by
-  [@akhil29](https://github.com/akhil29))
-- **JSON web fetch**: Non-HTML content like JSON APIs or raw source code are now
-  properly shown to the model (previously only supported HTML)
-  ([gif](https://imgur.com/a/Q58U4qJ),
-  [pr](https://github.com/google-gemini/gemini-cli/pull/11284) by
-  [@abhipatel12](https://github.com/abhipatel12))
-- **Non-interactive MCP commands:** Users can now run MCP slash commands in
-  non-interactive mode `gemini "/some-mcp-prompt"`.
-  ([pr](https://github.com/google-gemini/gemini-cli/pull/10194) by
-  [@capachino](https://github.com/capachino))
-- **Removal of deprecated flags:** We’ve finally removed a number of deprecated
-  flags to cleanup Gemini CLI’s invocation profile:
-  - `--all-files` / `-a` in favor of `@` from within Gemini CLI.
-    ([pr](https://github.com/google-gemini/gemini-cli/pull/11228) by
-    [@allenhutchison](https://github.com/allenhutchison))
-  - `--telemetry-*` flags in favor of
-    [environment variables](https://github.com/google-gemini/gemini-cli/pull/11318)
-    ([pr](https://github.com/google-gemini/gemini-cli/pull/11318) by
-    [@allenhutchison](https://github.com/allenhutchison))
-
-## Announcements: v0.10.0 - 2025-10-13
-
-- **Polish:** The team has been heads down bug fixing and investing heavily into
-  polishing existing flows, tools, and interactions.
-- **Interactive Shell Tool calling:** Gemini CLI can now also execute
-  interactive tools if needed
-  ([pr](https://github.com/google-gemini/gemini-cli/pull/11225) by
-  [@galz10](https://github.com/galz10)).
-- **Alt+Key support:** Enables broader support for Alt+Key keyboard shortcuts
-  across different terminals.
-  ([pr](https://github.com/google-gemini/gemini-cli/pull/10767) by
-  [@srivatsj](https://github.com/srivatsj)).
-- **Telemetry Diff stats:** Track line changes made by the model and user during
-  file operations via OTEL.
-  ([pr](https://github.com/google-gemini/gemini-cli/pull/10819) by
-  [@jerop](https://github.com/jerop)).
-
-## Announcements: v0.9.0 - 2025-10-06
+## v0.9.0 - Gemini CLI weekly update - 2025-10-06
 
 - 🎉 **Interactive Shell:** Run interactive commands like `vim`, `rebase -i`, or
   even `gemini` 😎 directly in Gemini CLI:
@@ -313,7 +28,7 @@ on GitHub.
   ([pr](https://github.com/google-gemini/gemini-cli/pull/10108) by
   [@sgnagnarella](https://github.com/sgnagnarella))
 
-## Announcements: v0.8.0 - 2025-09-29
+## v0.8.0 - Gemini CLI weekly update - 2025-09-29
 
 - 🎉 **Announcing Gemini CLI Extensions** 🎉
   - Completely customize your Gemini CLI experience to fit your workflow.
@@ -352,7 +67,7 @@ on GitHub.
   changes, smaller features, UI updates, reliability and bug fixes + general
   polish made it in this week!
 
-## Announcements: v0.7.0 - 2025-09-22
+## v0.7.0 - Gemini CLI weekly update - 2025-09-22
 
 - 🎉**Build your own Gemini CLI IDE plugin:** We've published a spec for
   creating IDE plugins to enable rich context-aware experiences and native
@@ -390,7 +105,7 @@ on GitHub.
   changes, smaller features, UI updates, reliability and bug fixes + general
   polish made it in this week!
 
-## Announcements: v0.6.0 - 2025-09-15
+## v0.6.0 - Gemini CLI weekly update - 2025-09-15
 
 - 🎉 **Higher limits for Google AI Pro and Ultra subscribers:** We’re psyched to
   finally announce that Google AI Pro and AI Ultra subscribers now get access to
@@ -471,7 +186,7 @@ on GitHub.
   changes, smaller features, UI updates, reliability and bug fixes + general
   polish made it in this week!
 
-## Announcements: v0.5.0 - 2025-09-08
+## v0.5.0 - Gemini CLI weekly update - 2025-09-08
 
 - 🎉**FastMCP + Gemini CLI**🎉: Quickly install and manage your Gemini CLI MCP
   servers with FastMCP ([video](https://imgur.com/a/m8QdCPh),
@@ -516,7 +231,7 @@ on GitHub.
   changes, smaller features, UI updates, reliability and bug fixes + general
   polish made it in this week!
 
-## Announcements: v0.4.0 - 2025-09-01
+## v0.4.0 - Gemini CLI weekly update - 2025-09-01
 
 - 🎉**Gemini CLI CloudRun and Security Integrations**🎉: Automate app deployment
   and security analysis with CloudRun and Security extension integrations. Once

docs/changelogs/latest.md

@@ -1,225 +0,0 @@
-# Latest stable release: v0.21.0 - v0.21.1
-
-Released: December 16, 2025
-
-For most users, our latest stable release is the recommended release. Install
-the latest stable version with:
-
-```
-npm install -g @google/gemini-cli
-```
-
-## Highlights
-
-- **⚡️⚡️⚡️ Gemini 3 Flash + Gemini CLI:** If you are a paid user, you can now
-  enable Gemini 3 Pro and Gemini 3 Flash. Go to `/settings` and set **Preview
-  Features** to `true` to enable Gemini 3. For more information:
-  [Gemini 3 Flash is now available in Gemini CLI](https://developers.googleblog.com/gemini-3-flash-is-now-available-in-gemini-cli/).
-
-## What's Changed
-
-- refactor(stdio): always patch stdout and use createWorkingStdio for clean
-  output by @allenhutchison in
-  https://github.com/google-gemini/gemini-cli/pull/14159
-- chore(release): bump version to 0.21.0-nightly.20251202.2d935b379 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/14409
-- implement fuzzy search inside settings by @sehoon38 in
-  https://github.com/google-gemini/gemini-cli/pull/13864
-- feat: enable message bus integration by default by @allenhutchison in
-  https://github.com/google-gemini/gemini-cli/pull/14329
-- docs: Recommend using --debug intead of --verbose for CLI debugging by @bbiggs
-  in https://github.com/google-gemini/gemini-cli/pull/14334
-- feat: consolidate remote MCP servers to use `url` in config by
-  @jackwotherspoon in https://github.com/google-gemini/gemini-cli/pull/13762
-- Restrict integration tests tools by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14403
-- track github repository names in telemetry events by @IamRiddhi in
-  https://github.com/google-gemini/gemini-cli/pull/13670
-- Allow telemetry exporters to GCP to utilize user's login credentials, if
-  requested by @mboshernitsan in
-  https://github.com/google-gemini/gemini-cli/pull/13778
-- refactor(editor): use const assertion for editor types with single source of
-  truth by @amsminn in https://github.com/google-gemini/gemini-cli/pull/8604
-- fix(security): Fix npm audit vulnerabilities in glob and body-parser by
-  @afarber in https://github.com/google-gemini/gemini-cli/pull/14090
-- Add new enterprise instructions by @chrstnb in
-  https://github.com/google-gemini/gemini-cli/pull/8641
-- feat(hooks): Hook Session Lifecycle & Compression Integration by @Edilmo in
-  https://github.com/google-gemini/gemini-cli/pull/14151
-- Avoid triggering refreshStatic unless there really is a banner to display. by
-  @jacob314 in https://github.com/google-gemini/gemini-cli/pull/14328
-- feat(hooks): Hooks Commands Panel, Enable/Disable, and Migrate by @Edilmo in
-  https://github.com/google-gemini/gemini-cli/pull/14225
-- fix: Bundle default policies for npx distribution by @allenhutchison in
-  https://github.com/google-gemini/gemini-cli/pull/14457
-- feat(hooks): Hook System Documentation by @Edilmo in
-  https://github.com/google-gemini/gemini-cli/pull/14307
-- Fix tests by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14458
-- feat: add scheduled workflow to close stale issues by @galz10 in
-  https://github.com/google-gemini/gemini-cli/pull/14404
-- feat: Support Extension Hooks with Security Warning by @abhipatel12 in
-  https://github.com/google-gemini/gemini-cli/pull/14460
-- feat: Add enableAgents experimental flag by @adamfweidman in
-  https://github.com/google-gemini/gemini-cli/pull/14371
-- docs: fix typo 'socus' to 'focus' in todos.md by @Viktor286 in
-  https://github.com/google-gemini/gemini-cli/pull/14374
-- Markdown export: move the emoji to the end of the line by @mhansen in
-  https://github.com/google-gemini/gemini-cli/pull/12278
-- fix(acp): prevent unnecessary credential cache clearing on re-authent… by
-  @h-michael in https://github.com/google-gemini/gemini-cli/pull/9410
-- fix(cli): Fix word navigation for CJK characters by @SandyTao520 in
-  https://github.com/google-gemini/gemini-cli/pull/14475
-- Remove example extension by @chrstnb in
-  https://github.com/google-gemini/gemini-cli/pull/14376
-- Add commands for listing and updating per-extension settings by @chrstnb in
-  https://github.com/google-gemini/gemini-cli/pull/12664
-- chore(tests): remove obsolete test for hierarchical memory by @pareshjoshij in
-  https://github.com/google-gemini/gemini-cli/pull/13122
-- feat(cli): support /copy in remote sessions using OSC52 by @ismellpillows in
-  https://github.com/google-gemini/gemini-cli/pull/13471
-- Update setting search UX by @Adib234 in
-  https://github.com/google-gemini/gemini-cli/pull/14451
-- Fix(cli): Improve Homebrew update instruction to specify gemini-cli by
-  @DaanVersavel in https://github.com/google-gemini/gemini-cli/pull/14502
-- do not toggle the setting item when entering space by @sehoon38 in
-  https://github.com/google-gemini/gemini-cli/pull/14489
-- fix: improve retry logic for fetch errors and network codes by @megha1188 in
-  https://github.com/google-gemini/gemini-cli/pull/14439
-- remove unused isSearching field by @sehoon38 in
-  https://github.com/google-gemini/gemini-cli/pull/14509
-- feat(mcp): add `--type` alias for `--transport` flag in gemini mcp add by
-  @jackwotherspoon in https://github.com/google-gemini/gemini-cli/pull/14503
-- feat(cli): Move key restore logic to core by @cocosheng-g in
-  https://github.com/google-gemini/gemini-cli/pull/13013
-- feat: add auto-execute on Enter behavior to argumentless MCP prompts by
-  @jackwotherspoon in https://github.com/google-gemini/gemini-cli/pull/14510
-- fix(shell): cursor visibility when using interactive mode by @aswinashok44 in
-  https://github.com/google-gemini/gemini-cli/pull/14095
-- Adding session id as part of json o/p by @MJjainam in
-  https://github.com/google-gemini/gemini-cli/pull/14504
-- fix(extensions): resolve GitHub API 415 error for source tarballs by
-  @jpoehnelt in https://github.com/google-gemini/gemini-cli/pull/13319
-- fix(client): Correctly latch hasFailedCompressionAttempt flag by @pareshjoshij
-  in https://github.com/google-gemini/gemini-cli/pull/13002
-- Disable flaky extension reloading test on linux by @chrstnb in
-  https://github.com/google-gemini/gemini-cli/pull/14528
-- Add support for MCP dynamic tool update by `notifications/tools/list_changed`
-  by @Adib234 in https://github.com/google-gemini/gemini-cli/pull/14375
-- Fix privacy screen for legacy tier users by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14522
-- feat: Exclude maintainer labeled issues from stale issue closer by @galz10 in
-  https://github.com/google-gemini/gemini-cli/pull/14532
-- Grant chained workflows proper permission. by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14534
-- Make trigger_e2e manually fireable. by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14547
-- Write e2e status to local repo not forked repo by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14549
-- Fixes [API Error: Cannot read properties of undefined (reading 'error')] by
-  @silviojr in https://github.com/google-gemini/gemini-cli/pull/14553
-- Trigger chained e2e tests on all pull requests by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14551
-- Fix bug in the shellExecutionService resulting in both truncation and 3X bloat
-  by @jacob314 in https://github.com/google-gemini/gemini-cli/pull/14545
-- Fix issue where we were passing the model content reflecting terminal line
-  wrapping. by @jacob314 in
-  https://github.com/google-gemini/gemini-cli/pull/14566
-- chore/release: bump version to 0.21.0-nightly.20251204.3da4fd5f7 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/14476
-- feat(sessions): use 1-line generated session summary to describe sessions by
-  @jackwotherspoon in https://github.com/google-gemini/gemini-cli/pull/14467
-- Use Robot PAT for chained e2e merge queue skipper by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14585
-- fix(core): improve API response error handling and retry logic by @mattKorwel
-  in https://github.com/google-gemini/gemini-cli/pull/14563
-- Docs: Model routing clarification by @jkcinouye in
-  https://github.com/google-gemini/gemini-cli/pull/14373
-- expose previewFeatures flag in a2a by @sehoon38 in
-  https://github.com/google-gemini/gemini-cli/pull/14550
-- Fix emoji width in debug console. by @jacob314 in
-  https://github.com/google-gemini/gemini-cli/pull/14593
-- Fully detach autoupgrade process by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14595
-- Docs: Update Gemini 3 on Gemini CLI documentation by @jkcinouye in
-  https://github.com/google-gemini/gemini-cli/pull/14601
-- Disallow floating promises. by @gundermanc in
-  https://github.com/google-gemini/gemini-cli/pull/14605
-- chore/release: bump version to 0.21.0-nightly.20251207.025e450ac by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/14662
-- feat(modelAvailabilityService): integrate model availability service into
-  backend logic by @adamfweidman in
-  https://github.com/google-gemini/gemini-cli/pull/14470
-- Add prompt_id propagation in a2a-server task by @koxkox111 in
-  https://github.com/google-gemini/gemini-cli/pull/14581
-- Fix: Prevent freezing in non-interactive Gemini CLI when debug mode is enabled
-  by @parthasaradhie in https://github.com/google-gemini/gemini-cli/pull/14580
-- fix(audio): improve reading of audio files by @jackwotherspoon in
-  https://github.com/google-gemini/gemini-cli/pull/14658
-- Update automated triage workflow to stop assigning priority labels by
-  @skeshive in https://github.com/google-gemini/gemini-cli/pull/14717
-- set failed status when chained e2e fails by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14725
-- feat(github action) Triage and Label Pull Requests by Size and Comple… by
-  @DaanVersavel in https://github.com/google-gemini/gemini-cli/pull/5571
-- refactor(telemetry): Improve previous PR that allows telemetry to use the CLI
-  auth and add testing by @mboshernitsan in
-  https://github.com/google-gemini/gemini-cli/pull/14589
-- Always set status in chained_e2e workflow by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14730
-- feat: Add OTEL log event `gemini_cli.startup_stats` for startup stats. by
-  @kevin-ramdass in https://github.com/google-gemini/gemini-cli/pull/14734
-- feat: auto-execute on slash command completion functions by @jackwotherspoon
-  in https://github.com/google-gemini/gemini-cli/pull/14584
-- Docs: Proper release notes by @jkcinouye in
-  https://github.com/google-gemini/gemini-cli/pull/14405
-- Add support for user-scoped extension settings by @chrstnb in
-  https://github.com/google-gemini/gemini-cli/pull/13748
-- refactor(core): Improve environment variable handling in shell execution by
-  @galz10 in https://github.com/google-gemini/gemini-cli/pull/14742
-- Remove old E2E Workflows by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14749
-- fix: handle missing local extension config and skip hooks when disabled by
-  @abhipatel12 in https://github.com/google-gemini/gemini-cli/pull/14744
-- chore/release: bump version to 0.21.0-nightly.20251209.ec9a8c7a7 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/14751
-- feat: Add support for MCP Resources by @MrLesk in
-  https://github.com/google-gemini/gemini-cli/pull/13178
-- Always set pending status in E2E tests by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14756
-- fix(lint): upgrade pip and use public pypi for yamllint by @allenhutchison in
-  https://github.com/google-gemini/gemini-cli/pull/14746
-- fix: use Gemini API supported image formats for clipboard by @jackwotherspoon
-  in https://github.com/google-gemini/gemini-cli/pull/14762
-- feat(a2a): Introduce restore command for a2a server by @cocosheng-g in
-  https://github.com/google-gemini/gemini-cli/pull/13015
-- allow final:true to be returned on a2a server edit calls. by @DavidAPierce in
-  https://github.com/google-gemini/gemini-cli/pull/14747
-- (fix) Automated pr labeller by @DaanVersavel in
-  https://github.com/google-gemini/gemini-cli/pull/14788
-- Update CODEOWNERS by @kklashtorny1 in
-  https://github.com/google-gemini/gemini-cli/pull/14830
-- Docs: Fix errors preventing site rebuild. by @jkcinouye in
-  https://github.com/google-gemini/gemini-cli/pull/14842
-- chore(deps): bump express from 5.1.0 to 5.2.0 by @dependabot[bot] in
-  https://github.com/google-gemini/gemini-cli/pull/14325
-- fix(patch): cherry-pick 3f5f030 to release/v0.21.0-preview.0-pr-14843 to patch
-  version v0.21.0-preview.0 and create version 0.21.0-preview.1 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/14851
-- fix(patch): cherry-pick ee6556c to release/v0.21.0-preview.1-pr-14691 to patch
-  version v0.21.0-preview.1 and create version 0.21.0-preview.2 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/14908
-- fix(patch): cherry-pick 54de675 to release/v0.21.0-preview.2-pr-14961 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/14968
-- fix(patch): cherry-pick 12cbe32 to release/v0.21.0-preview.3-pr-15000 to patch
-  version v0.21.0-preview.3 and create version 0.21.0-preview.4 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/15003
-- fix(patch): cherry-pick edbe548 to release/v0.21.0-preview.4-pr-15007 to patch
-  version v0.21.0-preview.4 and create version 0.21.0-preview.5 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/15015
-- fix(patch): cherry-pick 2995af6 to release/v0.21.0-preview.5-pr-15131 to patch
-  version v0.21.0-preview.5 and create version 0.21.0-preview.6 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/15153
-
-**Full Changelog**:
-https://github.com/google-gemini/gemini-cli/compare/v0.20.2...v0.21.0

docs/changelogs/preview.md

@@ -1,129 +0,0 @@
-# Preview release: Release v0.22.0-preview.0
-
-Released: December 16, 2025
-
-Our preview release includes the latest, new, and experimental features. This
-release may not be as stable as our [latest weekly release](latest.md).
-
-To install the preview release:
-
-```
-npm install -g @google/gemini-cli@preview
-```
-
-## What's Changed
-
-- feat(ide): fallback to GEMINI_CLI_IDE_AUTH_TOKEN env var by @skeshive in
-  https://github.com/google-gemini/gemini-cli/pull/14843
-- feat: display quota stats for unused models in /stats by @sehoon38 in
-  https://github.com/google-gemini/gemini-cli/pull/14764
-- feat: ensure codebase investigator uses preview model when main agent does by
-  @abhipatel12 in https://github.com/google-gemini/gemini-cli/pull/14412
-- chore: add closing reason to stale bug workflow by @galz10 in
-  https://github.com/google-gemini/gemini-cli/pull/14861
-- Send the model and CLI version with the user agent by @gundermanc in
-  https://github.com/google-gemini/gemini-cli/pull/14865
-- refactor(sessions): move session summary generation to startup by
-  @jackwotherspoon in https://github.com/google-gemini/gemini-cli/pull/14691
-- Limit search depth in path corrector by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14869
-- Fix: Correct typo in code comment by @kuishou68 in
-  https://github.com/google-gemini/gemini-cli/pull/14671
-- feat(core): Plumbing for late resolution of model configs. by @joshualitt in
-  https://github.com/google-gemini/gemini-cli/pull/14597
-- feat: attempt more error parsing by @adamfweidman in
-  https://github.com/google-gemini/gemini-cli/pull/14899
-- Add missing await. by @gundermanc in
-  https://github.com/google-gemini/gemini-cli/pull/14910
-- feat(core): Add support for transcript_path in hooks for git-ai/Gemini
-  extension by @svarlamov in
-  https://github.com/google-gemini/gemini-cli/pull/14663
-- refactor: implement DelegateToAgentTool with discriminated union by
-  @abhipatel12 in https://github.com/google-gemini/gemini-cli/pull/14769
-- feat: reset availabilityService on /auth by @adamfweidman in
-  https://github.com/google-gemini/gemini-cli/pull/14911
-- chore/release: bump version to 0.21.0-nightly.20251211.8c83e1ea9 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/14924
-- Fix: Correctly detect MCP tool errors by @kevin-ramdass in
-  https://github.com/google-gemini/gemini-cli/pull/14937
-- increase labeler timeout by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14922
-- tool(cli): tweak the frontend tool to be aware of more core files from the cli
-  by @jacob314 in https://github.com/google-gemini/gemini-cli/pull/14962
-- feat(cli): polish cached token stats and simplify stats display when quota is
-  present. by @jacob314 in
-  https://github.com/google-gemini/gemini-cli/pull/14961
-- feat(settings-validation): add validation for settings schema by @lifefloating
-  in https://github.com/google-gemini/gemini-cli/pull/12929
-- fix(ide): Update IDE extension to write auth token in env var by @skeshive in
-  https://github.com/google-gemini/gemini-cli/pull/14999
-- Revert "chore(deps): bump express from 5.1.0 to 5.2.0" by @skeshive in
-  https://github.com/google-gemini/gemini-cli/pull/14998
-- feat(a2a): Introduce /init command for a2a server by @cocosheng-g in
-  https://github.com/google-gemini/gemini-cli/pull/13419
-- feat: support multi-file drag and drop of images by @jackwotherspoon in
-  https://github.com/google-gemini/gemini-cli/pull/14832
-- fix(policy): allow codebase_investigator by default in read-only policy by
-  @abhipatel12 in https://github.com/google-gemini/gemini-cli/pull/15000
-- refactor(ide ext): Update port file name + switch to 1-based index for
-  characters + remove truncation text by @skeshive in
-  https://github.com/google-gemini/gemini-cli/pull/10501
-- fix(vscode-ide-companion): correct license generation for workspace
-  dependencies by @skeshive in
-  https://github.com/google-gemini/gemini-cli/pull/15004
-- fix: temp fix for subagent invocation until subagent delegation is merged to
-  stable by @abhipatel12 in
-  https://github.com/google-gemini/gemini-cli/pull/15007
-- test: update ide detection tests to make them more robust when run in an ide
-  by @kevin-ramdass in https://github.com/google-gemini/gemini-cli/pull/15008
-- Remove flex from stats display. See snapshots for diffs. by @jacob314 in
-  https://github.com/google-gemini/gemini-cli/pull/14983
-- Add license field into package.json by @jb-perez in
-  https://github.com/google-gemini/gemini-cli/pull/14473
-- feat: Persistent "Always Allow" policies with granular shell & MCP support by
-  @allenhutchison in https://github.com/google-gemini/gemini-cli/pull/14737
-- chore/release: bump version to 0.21.0-nightly.20251212.54de67536 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/14969
-- fix(core): commandPrefix word boundary and compound command safety by
-  @allenhutchison in https://github.com/google-gemini/gemini-cli/pull/15006
-- chore(docs): add 'Maintainers only' label info to CONTRIBUTING.md by @jacob314
-  in https://github.com/google-gemini/gemini-cli/pull/14914
-- Refresh hooks when refreshing extensions. by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14918
-- Add clarity to error messages by @gsehgal in
-  https://github.com/google-gemini/gemini-cli/pull/14879
-- chore : remove a redundant tip by @JayadityaGit in
-  https://github.com/google-gemini/gemini-cli/pull/14947
-- chore/release: bump version to 0.21.0-nightly.20251213.977248e09 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/15029
-- Disallow redundant typecasts. by @gundermanc in
-  https://github.com/google-gemini/gemini-cli/pull/15030
-- fix(auth): prioritize GEMINI_API_KEY env var and skip unnecessary key… by
-  @galz10 in https://github.com/google-gemini/gemini-cli/pull/14745
-- fix: use zod for safety check result validation by @allenhutchison in
-  https://github.com/google-gemini/gemini-cli/pull/15026
-- update(telemetry): add hashed_extension_name to field to extension events by
-  @kiranani in https://github.com/google-gemini/gemini-cli/pull/15025
-- fix: similar to policy-engine, throw error in case of requiring tool execution
-  confirmation for non-interactive mode by @MayV in
-  https://github.com/google-gemini/gemini-cli/pull/14702
-- Clean up processes in integration tests by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/15102
-- docs: update policy engine getting started and defaults by @NTaylorMullen in
-  https://github.com/google-gemini/gemini-cli/pull/15105
-- Fix tool output fragmentation by encapsulating content in functionResponse by
-  @abhipatel12 in https://github.com/google-gemini/gemini-cli/pull/13082
-- Simplify method signature. by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/15114
-- Show raw input token counts in json output. by @jacob314 in
-  https://github.com/google-gemini/gemini-cli/pull/15021
-- fix: Mark A2A requests as interactive by @MayV in
-  https://github.com/google-gemini/gemini-cli/pull/15108
-- use previewFeatures to determine which pro model to use for A2A by @sehoon38
-  in https://github.com/google-gemini/gemini-cli/pull/15131
-- refactor(cli): fix settings merging so that settings using the new json format
-  take priority over ones using the old format by @jacob314 in
-  https://github.com/google-gemini/gemini-cli/pull/15116
-
-**Full Changelog**:
-https://github.com/google-gemini/gemini-cli/compare/v0.21.0-preview.6...v0.22.0-preview.0

docs/changelogs/releases.md

@@ -1,896 +0,0 @@
-# Gemini CLI changelog
-
-Gemini CLI has three major release channels: nightly, preview, and stable. For
-most users, we recommend the stable release.
-
-On this page, you can find information regarding the current releases and
-highlights from each release.
-
-For the full changelog, including nightly releases, refer to
-[Releases - google-gemini/gemini-cli](https://github.com/google-gemini/gemini-cli/releases)
-on GitHub.
-
-## Current Releases
-
-| Release channel                             | Notes                                           |
-| :------------------------------------------ | :---------------------------------------------- |
-| Nightly                                     | Nightly release with the most recent changes.   |
-| [Preview](#release-v0220-preview-0-preview) | Experimental features ready for early feedback. |
-| [Latest](#release-v0210---v0211-latest)     | Stable, recommended for general use.            |
-
-## Release v0.21.0 - v0.21.1 (Latest)
-
-### Highlights
-
-- **⚡️⚡️⚡️ Gemini 3 Flash + Gemini CLI:** If you are a paid user, you can now
-  enable Gemini 3 Pro and Gemini 3 Flash. Go to `/settings` and set **Preview
-  Features** to `true` to enable Gemini 3. For more information:
-  [Gemini 3 Flash is now available in Gemini CLI](https://developers.googleblog.com/gemini-3-flash-is-now-available-in-gemini-cli/).
-
-### What's Changed
-
-- refactor(stdio): always patch stdout and use createWorkingStdio for clean
-  output by @allenhutchison in
-  https://github.com/google-gemini/gemini-cli/pull/14159
-- chore(release): bump version to 0.21.0-nightly.20251202.2d935b379 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/14409
-- implement fuzzy search inside settings by @sehoon38 in
-  https://github.com/google-gemini/gemini-cli/pull/13864
-- feat: enable message bus integration by default by @allenhutchison in
-  https://github.com/google-gemini/gemini-cli/pull/14329
-- docs: Recommend using --debug intead of --verbose for CLI debugging by @bbiggs
-  in https://github.com/google-gemini/gemini-cli/pull/14334
-- feat: consolidate remote MCP servers to use `url` in config by
-  @jackwotherspoon in https://github.com/google-gemini/gemini-cli/pull/13762
-- Restrict integration tests tools by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14403
-- track github repository names in telemetry events by @IamRiddhi in
-  https://github.com/google-gemini/gemini-cli/pull/13670
-- Allow telemetry exporters to GCP to utilize user's login credentials, if
-  requested by @mboshernitsan in
-  https://github.com/google-gemini/gemini-cli/pull/13778
-- refactor(editor): use const assertion for editor types with single source of
-  truth by @amsminn in https://github.com/google-gemini/gemini-cli/pull/8604
-- fix(security): Fix npm audit vulnerabilities in glob and body-parser by
-  @afarber in https://github.com/google-gemini/gemini-cli/pull/14090
-- Add new enterprise instructions by @chrstnb in
-  https://github.com/google-gemini/gemini-cli/pull/8641
-- feat(hooks): Hook Session Lifecycle & Compression Integration by @Edilmo in
-  https://github.com/google-gemini/gemini-cli/pull/14151
-- Avoid triggering refreshStatic unless there really is a banner to display. by
-  @jacob314 in https://github.com/google-gemini/gemini-cli/pull/14328
-- feat(hooks): Hooks Commands Panel, Enable/Disable, and Migrate by @Edilmo in
-  https://github.com/google-gemini/gemini-cli/pull/14225
-- fix: Bundle default policies for npx distribution by @allenhutchison in
-  https://github.com/google-gemini/gemini-cli/pull/14457
-- feat(hooks): Hook System Documentation by @Edilmo in
-  https://github.com/google-gemini/gemini-cli/pull/14307
-- Fix tests by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14458
-- feat: add scheduled workflow to close stale issues by @galz10 in
-  https://github.com/google-gemini/gemini-cli/pull/14404
-- feat: Support Extension Hooks with Security Warning by @abhipatel12 in
-  https://github.com/google-gemini/gemini-cli/pull/14460
-- feat: Add enableAgents experimental flag by @adamfweidman in
-  https://github.com/google-gemini/gemini-cli/pull/14371
-- docs: fix typo 'socus' to 'focus' in todos.md by @Viktor286 in
-  https://github.com/google-gemini/gemini-cli/pull/14374
-- Markdown export: move the emoji to the end of the line by @mhansen in
-  https://github.com/google-gemini/gemini-cli/pull/12278
-- fix(acp): prevent unnecessary credential cache clearing on re-authent… by
-  @h-michael in https://github.com/google-gemini/gemini-cli/pull/9410
-- fix(cli): Fix word navigation for CJK characters by @SandyTao520 in
-  https://github.com/google-gemini/gemini-cli/pull/14475
-- Remove example extension by @chrstnb in
-  https://github.com/google-gemini/gemini-cli/pull/14376
-- Add commands for listing and updating per-extension settings by @chrstnb in
-  https://github.com/google-gemini/gemini-cli/pull/12664
-- chore(tests): remove obsolete test for hierarchical memory by @pareshjoshij in
-  https://github.com/google-gemini/gemini-cli/pull/13122
-- feat(cli): support /copy in remote sessions using OSC52 by @ismellpillows in
-  https://github.com/google-gemini/gemini-cli/pull/13471
-- Update setting search UX by @Adib234 in
-  https://github.com/google-gemini/gemini-cli/pull/14451
-- Fix(cli): Improve Homebrew update instruction to specify gemini-cli by
-  @DaanVersavel in https://github.com/google-gemini/gemini-cli/pull/14502
-- do not toggle the setting item when entering space by @sehoon38 in
-  https://github.com/google-gemini/gemini-cli/pull/14489
-- fix: improve retry logic for fetch errors and network codes by @megha1188 in
-  https://github.com/google-gemini/gemini-cli/pull/14439
-- remove unused isSearching field by @sehoon38 in
-  https://github.com/google-gemini/gemini-cli/pull/14509
-- feat(mcp): add `--type` alias for `--transport` flag in gemini mcp add by
-  @jackwotherspoon in https://github.com/google-gemini/gemini-cli/pull/14503
-- feat(cli): Move key restore logic to core by @cocosheng-g in
-  https://github.com/google-gemini/gemini-cli/pull/13013
-- feat: add auto-execute on Enter behavior to argumentless MCP prompts by
-  @jackwotherspoon in https://github.com/google-gemini/gemini-cli/pull/14510
-- fix(shell): cursor visibility when using interactive mode by @aswinashok44 in
-  https://github.com/google-gemini/gemini-cli/pull/14095
-- Adding session id as part of json o/p by @MJjainam in
-  https://github.com/google-gemini/gemini-cli/pull/14504
-- fix(extensions): resolve GitHub API 415 error for source tarballs by
-  @jpoehnelt in https://github.com/google-gemini/gemini-cli/pull/13319
-- fix(client): Correctly latch hasFailedCompressionAttempt flag by @pareshjoshij
-  in https://github.com/google-gemini/gemini-cli/pull/13002
-- Disable flaky extension reloading test on linux by @chrstnb in
-  https://github.com/google-gemini/gemini-cli/pull/14528
-- Add support for MCP dynamic tool update by `notifications/tools/list_changed`
-  by @Adib234 in https://github.com/google-gemini/gemini-cli/pull/14375
-- Fix privacy screen for legacy tier users by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14522
-- feat: Exclude maintainer labeled issues from stale issue closer by @galz10 in
-  https://github.com/google-gemini/gemini-cli/pull/14532
-- Grant chained workflows proper permission. by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14534
-- Make trigger_e2e manually fireable. by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14547
-- Write e2e status to local repo not forked repo by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14549
-- Fixes [API Error: Cannot read properties of undefined (reading 'error')] by
-  @silviojr in https://github.com/google-gemini/gemini-cli/pull/14553
-- Trigger chained e2e tests on all pull requests by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14551
-- Fix bug in the shellExecutionService resulting in both truncation and 3X bloat
-  by @jacob314 in https://github.com/google-gemini/gemini-cli/pull/14545
-- Fix issue where we were passing the model content reflecting terminal line
-  wrapping. by @jacob314 in
-  https://github.com/google-gemini/gemini-cli/pull/14566
-- chore/release: bump version to 0.21.0-nightly.20251204.3da4fd5f7 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/14476
-- feat(sessions): use 1-line generated session summary to describe sessions by
-  @jackwotherspoon in https://github.com/google-gemini/gemini-cli/pull/14467
-- Use Robot PAT for chained e2e merge queue skipper by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14585
-- fix(core): improve API response error handling and retry logic by @mattKorwel
-  in https://github.com/google-gemini/gemini-cli/pull/14563
-- Docs: Model routing clarification by @jkcinouye in
-  https://github.com/google-gemini/gemini-cli/pull/14373
-- expose previewFeatures flag in a2a by @sehoon38 in
-  https://github.com/google-gemini/gemini-cli/pull/14550
-- Fix emoji width in debug console. by @jacob314 in
-  https://github.com/google-gemini/gemini-cli/pull/14593
-- Fully detach autoupgrade process by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14595
-- Docs: Update Gemini 3 on Gemini CLI documentation by @jkcinouye in
-  https://github.com/google-gemini/gemini-cli/pull/14601
-- Disallow floating promises. by @gundermanc in
-  https://github.com/google-gemini/gemini-cli/pull/14605
-- chore/release: bump version to 0.21.0-nightly.20251207.025e450ac by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/14662
-- feat(modelAvailabilityService): integrate model availability service into
-  backend logic by @adamfweidman in
-  https://github.com/google-gemini/gemini-cli/pull/14470
-- Add prompt_id propagation in a2a-server task by @koxkox111 in
-  https://github.com/google-gemini/gemini-cli/pull/14581
-- Fix: Prevent freezing in non-interactive Gemini CLI when debug mode is enabled
-  by @parthasaradhie in https://github.com/google-gemini/gemini-cli/pull/14580
-- fix(audio): improve reading of audio files by @jackwotherspoon in
-  https://github.com/google-gemini/gemini-cli/pull/14658
-- Update automated triage workflow to stop assigning priority labels by
-  @skeshive in https://github.com/google-gemini/gemini-cli/pull/14717
-- set failed status when chained e2e fails by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14725
-- feat(github action) Triage and Label Pull Requests by Size and Comple… by
-  @DaanVersavel in https://github.com/google-gemini/gemini-cli/pull/5571
-- refactor(telemetry): Improve previous PR that allows telemetry to use the CLI
-  auth and add testing by @mboshernitsan in
-  https://github.com/google-gemini/gemini-cli/pull/14589
-- Always set status in chained_e2e workflow by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14730
-- feat: Add OTEL log event `gemini_cli.startup_stats` for startup stats. by
-  @kevin-ramdass in https://github.com/google-gemini/gemini-cli/pull/14734
-- feat: auto-execute on slash command completion functions by @jackwotherspoon
-  in https://github.com/google-gemini/gemini-cli/pull/14584
-- Docs: Proper release notes by @jkcinouye in
-  https://github.com/google-gemini/gemini-cli/pull/14405
-- Add support for user-scoped extension settings by @chrstnb in
-  https://github.com/google-gemini/gemini-cli/pull/13748
-- refactor(core): Improve environment variable handling in shell execution by
-  @galz10 in https://github.com/google-gemini/gemini-cli/pull/14742
-- Remove old E2E Workflows by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14749
-- fix: handle missing local extension config and skip hooks when disabled by
-  @abhipatel12 in https://github.com/google-gemini/gemini-cli/pull/14744
-- chore/release: bump version to 0.21.0-nightly.20251209.ec9a8c7a7 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/14751
-- feat: Add support for MCP Resources by @MrLesk in
-  https://github.com/google-gemini/gemini-cli/pull/13178
-- Always set pending status in E2E tests by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14756
-- fix(lint): upgrade pip and use public pypi for yamllint by @allenhutchison in
-  https://github.com/google-gemini/gemini-cli/pull/14746
-- fix: use Gemini API supported image formats for clipboard by @jackwotherspoon
-  in https://github.com/google-gemini/gemini-cli/pull/14762
-- feat(a2a): Introduce restore command for a2a server by @cocosheng-g in
-  https://github.com/google-gemini/gemini-cli/pull/13015
-- allow final:true to be returned on a2a server edit calls. by @DavidAPierce in
-  https://github.com/google-gemini/gemini-cli/pull/14747
-- (fix) Automated pr labeller by @DaanVersavel in
-  https://github.com/google-gemini/gemini-cli/pull/14788
-- Update CODEOWNERS by @kklashtorny1 in
-  https://github.com/google-gemini/gemini-cli/pull/14830
-- Docs: Fix errors preventing site rebuild. by @jkcinouye in
-  https://github.com/google-gemini/gemini-cli/pull/14842
-- chore(deps): bump express from 5.1.0 to 5.2.0 by @dependabot[bot] in
-  https://github.com/google-gemini/gemini-cli/pull/14325
-- fix(patch): cherry-pick 3f5f030 to release/v0.21.0-preview.0-pr-14843 to patch
-  version v0.21.0-preview.0 and create version 0.21.0-preview.1 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/14851
-- fix(patch): cherry-pick ee6556c to release/v0.21.0-preview.1-pr-14691 to patch
-  version v0.21.0-preview.1 and create version 0.21.0-preview.2 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/14908
-- fix(patch): cherry-pick 54de675 to release/v0.21.0-preview.2-pr-14961 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/14968
-- fix(patch): cherry-pick 12cbe32 to release/v0.21.0-preview.3-pr-15000 to patch
-  version v0.21.0-preview.3 and create version 0.21.0-preview.4 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/15003
-- fix(patch): cherry-pick edbe548 to release/v0.21.0-preview.4-pr-15007 to patch
-  version v0.21.0-preview.4 and create version 0.21.0-preview.5 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/15015
-- fix(patch): cherry-pick 2995af6 to release/v0.21.0-preview.5-pr-15131 to patch
-  version v0.21.0-preview.5 and create version 0.21.0-preview.6 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/15153
-
-**Full Changelog**:
-https://github.com/google-gemini/gemini-cli/compare/v0.20.2...v0.21.0
-
-## Release v0.22.0-preview-0 (Preview)
-
-### What's Changed
-
-- feat(ide): fallback to GEMINI_CLI_IDE_AUTH_TOKEN env var by @skeshive in
-  https://github.com/google-gemini/gemini-cli/pull/14843
-- feat: display quota stats for unused models in /stats by @sehoon38 in
-  https://github.com/google-gemini/gemini-cli/pull/14764
-- feat: ensure codebase investigator uses preview model when main agent does by
-  @abhipatel12 in https://github.com/google-gemini/gemini-cli/pull/14412
-- chore: add closing reason to stale bug workflow by @galz10 in
-  https://github.com/google-gemini/gemini-cli/pull/14861
-- Send the model and CLI version with the user agent by @gundermanc in
-  https://github.com/google-gemini/gemini-cli/pull/14865
-- refactor(sessions): move session summary generation to startup by
-  @jackwotherspoon in https://github.com/google-gemini/gemini-cli/pull/14691
-- Limit search depth in path corrector by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14869
-- Fix: Correct typo in code comment by @kuishou68 in
-  https://github.com/google-gemini/gemini-cli/pull/14671
-- feat(core): Plumbing for late resolution of model configs. by @joshualitt in
-  https://github.com/google-gemini/gemini-cli/pull/14597
-- feat: attempt more error parsing by @adamfweidman in
-  https://github.com/google-gemini/gemini-cli/pull/14899
-- Add missing await. by @gundermanc in
-  https://github.com/google-gemini/gemini-cli/pull/14910
-- feat(core): Add support for transcript_path in hooks for git-ai/Gemini
-  extension by @svarlamov in
-  https://github.com/google-gemini/gemini-cli/pull/14663
-- refactor: implement DelegateToAgentTool with discriminated union by
-  @abhipatel12 in https://github.com/google-gemini/gemini-cli/pull/14769
-- feat: reset availabilityService on /auth by @adamfweidman in
-  https://github.com/google-gemini/gemini-cli/pull/14911
-- chore/release: bump version to 0.21.0-nightly.20251211.8c83e1ea9 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/14924
-- Fix: Correctly detect MCP tool errors by @kevin-ramdass in
-  https://github.com/google-gemini/gemini-cli/pull/14937
-- increase labeler timeout by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14922
-- tool(cli): tweak the frontend tool to be aware of more core files from the cli
-  by @jacob314 in https://github.com/google-gemini/gemini-cli/pull/14962
-- feat(cli): polish cached token stats and simplify stats display when quota is
-  present. by @jacob314 in
-  https://github.com/google-gemini/gemini-cli/pull/14961
-- feat(settings-validation): add validation for settings schema by @lifefloating
-  in https://github.com/google-gemini/gemini-cli/pull/12929
-- fix(ide): Update IDE extension to write auth token in env var by @skeshive in
-  https://github.com/google-gemini/gemini-cli/pull/14999
-- Revert "chore(deps): bump express from 5.1.0 to 5.2.0" by @skeshive in
-  https://github.com/google-gemini/gemini-cli/pull/14998
-- feat(a2a): Introduce /init command for a2a server by @cocosheng-g in
-  https://github.com/google-gemini/gemini-cli/pull/13419
-- feat: support multi-file drag and drop of images by @jackwotherspoon in
-  https://github.com/google-gemini/gemini-cli/pull/14832
-- fix(policy): allow codebase_investigator by default in read-only policy by
-  @abhipatel12 in https://github.com/google-gemini/gemini-cli/pull/15000
-- refactor(ide ext): Update port file name + switch to 1-based index for
-  characters + remove truncation text by @skeshive in
-  https://github.com/google-gemini/gemini-cli/pull/10501
-- fix(vscode-ide-companion): correct license generation for workspace
-  dependencies by @skeshive in
-  https://github.com/google-gemini/gemini-cli/pull/15004
-- fix: temp fix for subagent invocation until subagent delegation is merged to
-  stable by @abhipatel12 in
-  https://github.com/google-gemini/gemini-cli/pull/15007
-- test: update ide detection tests to make them more robust when run in an ide
-  by @kevin-ramdass in https://github.com/google-gemini/gemini-cli/pull/15008
-- Remove flex from stats display. See snapshots for diffs. by @jacob314 in
-  https://github.com/google-gemini/gemini-cli/pull/14983
-- Add license field into package.json by @jb-perez in
-  https://github.com/google-gemini/gemini-cli/pull/14473
-- feat: Persistent "Always Allow" policies with granular shell & MCP support by
-  @allenhutchison in https://github.com/google-gemini/gemini-cli/pull/14737
-- chore/release: bump version to 0.21.0-nightly.20251212.54de67536 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/14969
-- fix(core): commandPrefix word boundary and compound command safety by
-  @allenhutchison in https://github.com/google-gemini/gemini-cli/pull/15006
-- chore(docs): add 'Maintainers only' label info to CONTRIBUTING.md by @jacob314
-  in https://github.com/google-gemini/gemini-cli/pull/14914
-- Refresh hooks when refreshing extensions. by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14918
-- Add clarity to error messages by @gsehgal in
-  https://github.com/google-gemini/gemini-cli/pull/14879
-- chore : remove a redundant tip by @JayadityaGit in
-  https://github.com/google-gemini/gemini-cli/pull/14947
-- chore/release: bump version to 0.21.0-nightly.20251213.977248e09 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/15029
-- Disallow redundant typecasts. by @gundermanc in
-  https://github.com/google-gemini/gemini-cli/pull/15030
-- fix(auth): prioritize GEMINI_API_KEY env var and skip unnecessary key… by
-  @galz10 in https://github.com/google-gemini/gemini-cli/pull/14745
-- fix: use zod for safety check result validation by @allenhutchison in
-  https://github.com/google-gemini/gemini-cli/pull/15026
-- update(telemetry): add hashed_extension_name to field to extension events by
-  @kiranani in https://github.com/google-gemini/gemini-cli/pull/15025
-- fix: similar to policy-engine, throw error in case of requiring tool execution
-  confirmation for non-interactive mode by @MayV in
-  https://github.com/google-gemini/gemini-cli/pull/14702
-- Clean up processes in integration tests by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/15102
-- docs: update policy engine getting started and defaults by @NTaylorMullen in
-  https://github.com/google-gemini/gemini-cli/pull/15105
-- Fix tool output fragmentation by encapsulating content in functionResponse by
-  @abhipatel12 in https://github.com/google-gemini/gemini-cli/pull/13082
-- Simplify method signature. by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/15114
-- Show raw input token counts in json output. by @jacob314 in
-  https://github.com/google-gemini/gemini-cli/pull/15021
-- fix: Mark A2A requests as interactive by @MayV in
-  https://github.com/google-gemini/gemini-cli/pull/15108
-- use previewFeatures to determine which pro model to use for A2A by @sehoon38
-  in https://github.com/google-gemini/gemini-cli/pull/15131
-- refactor(cli): fix settings merging so that settings using the new json format
-  take priority over ones using the old format by @jacob314 in
-  https://github.com/google-gemini/gemini-cli/pull/15116
-
-**Full Changelog**:
-https://github.com/google-gemini/gemini-cli/compare/v0.21.0-preview.6...v0.22.0-preview.0
-
-## Release v0.20.0 - v0.20.2
-
-### What's Changed
-
-- Update error codes when process exiting the gemini cli by @megha1188 in
-  https://github.com/google-gemini/gemini-cli/pull/13728
-- chore(release): bump version to 0.20.0-nightly.20251126.d2a6cff4d by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/13835
-- feat(core): Improve request token calculation accuracy by @SandyTao520 in
-  https://github.com/google-gemini/gemini-cli/pull/13824
-- Changes in system instruction to adapt to gemini 3.0 to ensure that the CLI
-  explains its actions before calling tools by @silviojr in
-  https://github.com/google-gemini/gemini-cli/pull/13810
-- feat(hooks): Hook Tool Execution Integration by @Edilmo in
-  https://github.com/google-gemini/gemini-cli/pull/9108
-- Add support for MCP server instructions behind config option by @chrstnb in
-  https://github.com/google-gemini/gemini-cli/pull/13432
-- Update System Instructions for interactive vs non-interactive mode. by
-  @aishaneeshah in https://github.com/google-gemini/gemini-cli/pull/12315
-- Add consent flag to Link command by @kevinjwang1 in
-  https://github.com/google-gemini/gemini-cli/pull/13832
-- feat(mcp): Inject GoogleCredentialProvider headers in McpClient by
-  @sai-sunder-s in https://github.com/google-gemini/gemini-cli/pull/13783
-- feat(core): implement towards policy-driven model fallback mechanism by
-  @adamfweidman in https://github.com/google-gemini/gemini-cli/pull/13781
-- feat(core): Add configurable inactivity timeout for shell commands by @galz10
-  in https://github.com/google-gemini/gemini-cli/pull/13531
-- fix(auth): improve API key authentication flow by @galz10 in
-  https://github.com/google-gemini/gemini-cli/pull/13829
-- feat(hooks): Hook LLM Request/Response Integration by @Edilmo in
-  https://github.com/google-gemini/gemini-cli/pull/9110
-- feat(ui): Show waiting MCP servers in ConfigInitDisplay by @werdnum in
-  https://github.com/google-gemini/gemini-cli/pull/13721
-- Add usage limit remaining in /stats by @sehoon38 in
-  https://github.com/google-gemini/gemini-cli/pull/13843
-- feat(shell): Standardize pager to 'cat' for shell execution by model by
-  @galz10 in https://github.com/google-gemini/gemini-cli/pull/13878
-- chore/release: bump version to 0.20.0-nightly.20251127.5bed97064 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/13877
-- Revert to default LICENSE (Revert #13449) by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/13876
-- update(telemetry): OTel API response event with finish reasons by @kiranani in
-  https://github.com/google-gemini/gemini-cli/pull/13849
-- feat(hooks): Hooks Comprehensive Integration Testing by @Edilmo in
-  https://github.com/google-gemini/gemini-cli/pull/9112
-- chore: fix session browser test and skip hook system tests by @jackwotherspoon
-  in https://github.com/google-gemini/gemini-cli/pull/14099
-- feat(telemetry): Add Semantic logging for to ApiRequestEvents by @kiranani in
-  https://github.com/google-gemini/gemini-cli/pull/13912
-- test: Add verification for $schema property in settings schema by
-  @maryamariyan in https://github.com/google-gemini/gemini-cli/pull/13497
-- Fixes `/clear` command to preserve input history for up-arrow navigation while
-  still clearing the context window and screen by @korade-krushna in
-  https://github.com/google-gemini/gemini-cli/pull/14182
-- fix(core): handle EPIPE error in hook runner when writing to stdin by
-  @SandyTao520 in https://github.com/google-gemini/gemini-cli/pull/14231
-- fix: Exclude web-fetch tool from executing in default non-interactive mode to
-  avoid CLI hang. by @MayV in
-  https://github.com/google-gemini/gemini-cli/pull/14244
-- Always use MCP server instructions by @chrstnb in
-  https://github.com/google-gemini/gemini-cli/pull/14297
-- feat: auto-execute simple slash commands on Enter by @jackwotherspoon in
-  https://github.com/google-gemini/gemini-cli/pull/13985
-- chore/release: bump version to 0.20.0-nightly.20251201.2fe609cb6 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/14304
-- feat: Add startup profiler to measure and record application initialization
-  phases. by @kevin-ramdass in
-  https://github.com/google-gemini/gemini-cli/pull/13638
-- bug(core): Avoid stateful tool use in `executor`. by @joshualitt in
-  https://github.com/google-gemini/gemini-cli/pull/14305
-- feat(themes): add built-in holiday theme 🎁 by @jackwotherspoon in
-  https://github.com/google-gemini/gemini-cli/pull/14301
-- Updated ToC on docs intro; updated title casing to match Google style by
-  @pcoet in https://github.com/google-gemini/gemini-cli/pull/13717
-- feat(a2a): Urgent fix - Process modelInfo agent message by @cocosheng-g in
-  https://github.com/google-gemini/gemini-cli/pull/14315
-- feat(core): enhance availability routing with wrapped fallback and
-  single-model policies by @adamfweidman in
-  https://github.com/google-gemini/gemini-cli/pull/13874
-- chore(logging): log the problematic event for #12122 by @briandealwis in
-  https://github.com/google-gemini/gemini-cli/pull/14092
-- fix: remove invalid type key in bug_report.yml by @fancive in
-  https://github.com/google-gemini/gemini-cli/pull/13576
-- update screenshot by @Transient-Onlooker in
-  https://github.com/google-gemini/gemini-cli/pull/13976
-- docs: Fix grammar error in Release Cadence (Nightly section) by @JuanCS-Dev in
-  https://github.com/google-gemini/gemini-cli/pull/13866
-- fix(async): prevent missed async errors from bypassing catch handlers by
-  @amsminn in https://github.com/google-gemini/gemini-cli/pull/13714
-- fix(zed-integration): remove extra field from acp auth request by
-  @marcocondrache in https://github.com/google-gemini/gemini-cli/pull/13646
-- feat(cli): Documentation for model configs. by @joshualitt in
-  https://github.com/google-gemini/gemini-cli/pull/12967
-- fix(ui): misaligned markdown table rendering by @dumbbellcode in
-  https://github.com/google-gemini/gemini-cli/pull/8336
-- docs: Update 4 files by @g-samroberts in
-  https://github.com/google-gemini/gemini-cli/pull/13628
-- fix: Conditionally add set -eEuo pipefail in setup-github command by @Smetalo
-  in https://github.com/google-gemini/gemini-cli/pull/8550
-- fix(cli): fix issue updating a component while rendering a different component
-  by @jacob314 in https://github.com/google-gemini/gemini-cli/pull/14319
-- Increase flakey test timeout by @chrstnb in
-  https://github.com/google-gemini/gemini-cli/pull/14377
-- Remove references to deleted kind/bug label by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14383
-- Don't fail test if we can't cleanup by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/14389
-- feat(core): Implement JIT context manager and setting by @SandyTao520 in
-  https://github.com/google-gemini/gemini-cli/pull/14324
-- Use polling for extensions-reload integration test by @chrstnb in
-  https://github.com/google-gemini/gemini-cli/pull/14391
-- Add docs directive to GEMINI.md by @g-samroberts in
-  https://github.com/google-gemini/gemini-cli/pull/14327
-- Hide sessions that don't have user messages by @bl-ue in
-  https://github.com/google-gemini/gemini-cli/pull/13994
-- chore(ci): mark GitHub release as pre-release if not on "latest" npm channel
-  by @ljxfstorm in https://github.com/google-gemini/gemini-cli/pull/7386
-- fix(patch): cherry-pick d284fa6 to release/v0.20.0-preview.0-pr-14545
-  [CONFLICTS] by @gemini-cli-robot in
-  https://github.com/google-gemini/gemini-cli/pull/14559
-- fix(patch): cherry-pick 828afe1 to release/v0.20.0-preview.1-pr-14159 to patch
-  version v0.20.0-preview.1 and create version 0.20.0-preview.2 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/14733
-- fix(patch): cherry-pick 171103a to release/v0.20.0-preview.2-pr-14742 to patch
-  version v0.20.0-preview.2 and create version 0.20.0-preview.5 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/14752
-
-**Full Changelog**:
-https://github.com/google-gemini/gemini-cli/compare/v0.19.4...v0.20.0
-
-## Release v0.19.0 - v0.19.4
-
-## Highlights
-
-- **Zed integration:** Users can now leverage Gemini 3 within the Zed
-  integration after enabling "Preview Features" in their CLI’s `/settings`.
-- **Interactive shell:**
-  - **Click-to-Focus:** Go to `/settings` and enable **Use Alternate Buffer**
-    When "Use Alternate Buffer" setting is enabled users can click within the
-    embedded shell output to focus it for input.
-  - **Loading phrase:** Clearly indicates when the interactive shell is awaiting
-    user input. ([vid](https://imgur.com/a/kjK8bUK)
-    [pr](https://github.com/google-gemini/gemini-cli/pull/12535) by
-    [@jackwotherspoon](https://github.com/jackwotherspoon))
-
-### What's Changed
-
-- Use lenient MCP output schema validator by @cornmander in
-  https://github.com/google-gemini/gemini-cli/pull/13521
-- Update persistence state to track counts of messages instead of times banner
-  has been displayed by @Adib234 in
-  https://github.com/google-gemini/gemini-cli/pull/13428
-- update docs for http proxy by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/13538
-- move stdio by @jacob314 in
-  https://github.com/google-gemini/gemini-cli/pull/13528
-- chore(release): bump version to 0.19.0-nightly.20251120.8e531dc02 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/13540
-- Skip pre-commit hooks for shadow repo (#13331) by @vishvananda in
-  https://github.com/google-gemini/gemini-cli/pull/13488
-- fix(ui): Correct mouse click cursor positioning for wide characters by
-  @SandyTao520 in https://github.com/google-gemini/gemini-cli/pull/13537
-- fix(core): correct bash @P prompt transformation detection by @pyrytakala in
-  https://github.com/google-gemini/gemini-cli/pull/13544
-- Optimize and improve test coverage for cli/src/config by @megha1188 in
-  https://github.com/google-gemini/gemini-cli/pull/13485
-- Improve code coverage for cli/src/ui/privacy package by @megha1188 in
-  https://github.com/google-gemini/gemini-cli/pull/13493
-- docs: fix typos in source code and documentation by @fancive in
-  https://github.com/google-gemini/gemini-cli/pull/13577
-- Improved code coverage for cli/src/zed-integration by @megha1188 in
-  https://github.com/google-gemini/gemini-cli/pull/13570
-- feat(ui): build interactive session browser component by @bl-ue in
-  https://github.com/google-gemini/gemini-cli/pull/13351
-- Fix multiple bugs with auth flow including using the implemented but unused
-  restart support. by @jacob314 in
-  https://github.com/google-gemini/gemini-cli/pull/13565
-- feat(core): add modelAvailabilityService for managing and tracking model
-  health by @adamfweidman in
-  https://github.com/google-gemini/gemini-cli/pull/13426
-- docs: fix grammar typo "a MCP" to "an MCP" by @noahacgn in
-  https://github.com/google-gemini/gemini-cli/pull/13595
-- feat: custom loading phrase when interactive shell requires input by
-  @jackwotherspoon in https://github.com/google-gemini/gemini-cli/pull/12535
-- docs: Update uninstall command to reflect multiple extension support by
-  @JayadityaGit in https://github.com/google-gemini/gemini-cli/pull/13582
-- bug(core): Ensure we use thinking budget on fallback to 2.5 by @joshualitt in
-  https://github.com/google-gemini/gemini-cli/pull/13596
-- Remove useModelRouter experimental flag by @Adib234 in
-  https://github.com/google-gemini/gemini-cli/pull/13593
-- feat(docs): Ensure multiline JS objects are rendered properly. by @joshualitt
-  in https://github.com/google-gemini/gemini-cli/pull/13535
-- Fix exp id logging by @owenofbrien in
-  https://github.com/google-gemini/gemini-cli/pull/13430
-- Moved client id logging into createBasicLogEvent by @owenofbrien in
-  https://github.com/google-gemini/gemini-cli/pull/13607
-- Restore bracketed paste mode after external editor exit by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/13606
-- feat(core): Add support for custom aliases for model configs. by @joshualitt
-  in https://github.com/google-gemini/gemini-cli/pull/13546
-- feat(core): Add `BaseLlmClient.generateContent`. by @joshualitt in
-  https://github.com/google-gemini/gemini-cli/pull/13591
-- Turn off alternate buffer mode by default. by @jacob314 in
-  https://github.com/google-gemini/gemini-cli/pull/13623
-- fix(cli): Prevent stdout/stderr patching for extension commands by @chrstnb in
-  https://github.com/google-gemini/gemini-cli/pull/13600
-- Improve test coverage for cli/src/ui/components by @megha1188 in
-  https://github.com/google-gemini/gemini-cli/pull/13598
-- Update ink version to 6.4.6 by @jacob314 in
-  https://github.com/google-gemini/gemini-cli/pull/13631
-- chore/release: bump version to 0.19.0-nightly.20251122.42c2e1b21 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/13637
-- chore/release: bump version to 0.19.0-nightly.20251123.dadd606c0 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/13675
-- chore/release: bump version to 0.19.0-nightly.20251124.e177314a4 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/13713
-- fix(core): Fix context window overflow warning for PDF files by @kkitase in
-  https://github.com/google-gemini/gemini-cli/pull/13548
-- feat :rephrasing the extension logging messages to run the explore command
-  when there are no extensions installed by @JayadityaGit in
-  https://github.com/google-gemini/gemini-cli/pull/13740
-- Improve code coverage for cli package by @megha1188 in
-  https://github.com/google-gemini/gemini-cli/pull/13724
-- Add session subtask in /stats command by @Adib234 in
-  https://github.com/google-gemini/gemini-cli/pull/13750
-- feat(core): Migrate chatCompressionService to model configs. by @joshualitt in
-  https://github.com/google-gemini/gemini-cli/pull/12863
-- feat(hooks): Hook Telemetry Infrastructure by @Edilmo in
-  https://github.com/google-gemini/gemini-cli/pull/9082
-- fix: (some minor improvements to configs and getPackageJson return behaviour)
-  by @grMLEqomlkkU5Eeinz4brIrOVCUCkJuN in
-  https://github.com/google-gemini/gemini-cli/pull/12510
-- feat(hooks): Hook Event Handling by @Edilmo in
-  https://github.com/google-gemini/gemini-cli/pull/9097
-- feat(hooks): Hook Agent Lifecycle Integration by @Edilmo in
-  https://github.com/google-gemini/gemini-cli/pull/9105
-- feat(core): Land bool for alternate system prompt. by @joshualitt in
-  https://github.com/google-gemini/gemini-cli/pull/13764
-- bug(core): Add default chat compression config. by @joshualitt in
-  https://github.com/google-gemini/gemini-cli/pull/13766
-- feat(model-availability): introduce ModelPolicy and PolicyCatalog by
-  @adamfweidman in https://github.com/google-gemini/gemini-cli/pull/13751
-- feat(hooks): Hook System Orchestration by @Edilmo in
-  https://github.com/google-gemini/gemini-cli/pull/9102
-- feat(config): add isModelAvailabilityServiceEnabled setting by @adamfweidman
-  in https://github.com/google-gemini/gemini-cli/pull/13777
-- chore/release: bump version to 0.19.0-nightly.20251125.f6d97d448 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/13782
-- chore: remove console.error by @adamfweidman in
-  https://github.com/google-gemini/gemini-cli/pull/13779
-- fix: Add $schema property to settings.schema.json by @sacrosanctic in
-  https://github.com/google-gemini/gemini-cli/pull/12763
-- fix(cli): allow non-GitHub SCP-styled URLs for extension installation by @m0ps
-  in https://github.com/google-gemini/gemini-cli/pull/13800
-- fix(resume): allow passing a prompt via stdin while resuming using --resume by
-  @bl-ue in https://github.com/google-gemini/gemini-cli/pull/13520
-- feat(sessions): add /resume slash command to open the session browser by
-  @bl-ue in https://github.com/google-gemini/gemini-cli/pull/13621
-- docs(sessions): add documentation for chat recording and session management by
-  @bl-ue in https://github.com/google-gemini/gemini-cli/pull/13667
-- Fix TypeError: "URL.parse is not a function" for Node.js < v22 by @macarronesc
-  in https://github.com/google-gemini/gemini-cli/pull/13698
-- fallback to flash for TerminalQuota errors by @sehoon38 in
-  https://github.com/google-gemini/gemini-cli/pull/13791
-- Update Code Wiki README badge by @PatoBeltran in
-  https://github.com/google-gemini/gemini-cli/pull/13768
-- Add Databricks auth support and custom header option to gemini cli by
-  @AarushiShah in https://github.com/google-gemini/gemini-cli/pull/11893
-- Update dependency for modelcontextprotocol/sdk to 1.23.0 by @bbiggs in
-  https://github.com/google-gemini/gemini-cli/pull/13827
-- fix(patch): cherry-pick 576fda1 to release/v0.19.0-preview.0-pr-14099
-  [CONFLICTS] by @gemini-cli-robot in
-  https://github.com/google-gemini/gemini-cli/pull/14402
-
-**Full Changelog**:
-https://github.com/google-gemini/gemini-cli/compare/v0.18.4...v0.19.0
-
-## Release v0.19.0-preview.0
-
-### What's Changed
-
-- Use lenient MCP output schema validator by @cornmander in
-  https://github.com/google-gemini/gemini-cli/pull/13521
-- Update persistence state to track counts of messages instead of times banner
-  has been displayed by @Adib234 in
-  https://github.com/google-gemini/gemini-cli/pull/13428
-- update docs for http proxy by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/13538
-- move stdio by @jacob314 in
-  https://github.com/google-gemini/gemini-cli/pull/13528
-- chore(release): bump version to 0.19.0-nightly.20251120.8e531dc02 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/13540
-- Skip pre-commit hooks for shadow repo (#13331) by @vishvananda in
-  https://github.com/google-gemini/gemini-cli/pull/13488
-- fix(ui): Correct mouse click cursor positioning for wide characters by
-  @SandyTao520 in https://github.com/google-gemini/gemini-cli/pull/13537
-- fix(core): correct bash @P prompt transformation detection by @pyrytakala in
-  https://github.com/google-gemini/gemini-cli/pull/13544
-- Optimize and improve test coverage for cli/src/config by @megha1188 in
-  https://github.com/google-gemini/gemini-cli/pull/13485
-- Improve code coverage for cli/src/ui/privacy package by @megha1188 in
-  https://github.com/google-gemini/gemini-cli/pull/13493
-- docs: fix typos in source code and documentation by @fancive in
-  https://github.com/google-gemini/gemini-cli/pull/13577
-- Improved code coverage for cli/src/zed-integration by @megha1188 in
-  https://github.com/google-gemini/gemini-cli/pull/13570
-- feat(ui): build interactive session browser component by @bl-ue in
-  https://github.com/google-gemini/gemini-cli/pull/13351
-- Fix multiple bugs with auth flow including using the implemented but unused
-  restart support. by @jacob314 in
-  https://github.com/google-gemini/gemini-cli/pull/13565
-- feat(core): add modelAvailabilityService for managing and tracking model
-  health by @adamfweidman in
-  https://github.com/google-gemini/gemini-cli/pull/13426
-- docs: fix grammar typo "a MCP" to "an MCP" by @noahacgn in
-  https://github.com/google-gemini/gemini-cli/pull/13595
-- feat: custom loading phrase when interactive shell requires input by
-  @jackwotherspoon in https://github.com/google-gemini/gemini-cli/pull/12535
-- docs: Update uninstall command to reflect multiple extension support by
-  @JayadityaGit in https://github.com/google-gemini/gemini-cli/pull/13582
-- bug(core): Ensure we use thinking budget on fallback to 2.5 by @joshualitt in
-  https://github.com/google-gemini/gemini-cli/pull/13596
-- Remove useModelRouter experimental flag by @Adib234 in
-  https://github.com/google-gemini/gemini-cli/pull/13593
-- feat(docs): Ensure multiline JS objects are rendered properly. by @joshualitt
-  in https://github.com/google-gemini/gemini-cli/pull/13535
-- Fix exp id logging by @owenofbrien in
-  https://github.com/google-gemini/gemini-cli/pull/13430
-- Moved client id logging into createBasicLogEvent by @owenofbrien in
-  https://github.com/google-gemini/gemini-cli/pull/13607
-- Restore bracketed paste mode after external editor exit by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/13606
-- feat(core): Add support for custom aliases for model configs. by @joshualitt
-  in https://github.com/google-gemini/gemini-cli/pull/13546
-- feat(core): Add `BaseLlmClient.generateContent`. by @joshualitt in
-  https://github.com/google-gemini/gemini-cli/pull/13591
-- Turn off alternate buffer mode by default. by @jacob314 in
-  https://github.com/google-gemini/gemini-cli/pull/13623
-- fix(cli): Prevent stdout/stderr patching for extension commands by @chrstnb in
-  https://github.com/google-gemini/gemini-cli/pull/13600
-- Improve test coverage for cli/src/ui/components by @megha1188 in
-  https://github.com/google-gemini/gemini-cli/pull/13598
-- Update ink version to 6.4.6 by @jacob314 in
-  https://github.com/google-gemini/gemini-cli/pull/13631
-- chore/release: bump version to 0.19.0-nightly.20251122.42c2e1b21 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/13637
-- chore/release: bump version to 0.19.0-nightly.20251123.dadd606c0 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/13675
-- chore/release: bump version to 0.19.0-nightly.20251124.e177314a4 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/13713
-- fix(core): Fix context window overflow warning for PDF files by @kkitase in
-  https://github.com/google-gemini/gemini-cli/pull/13548
-- feat :rephrasing the extension logging messages to run the explore command
-  when there are no extensions installed by @JayadityaGit in
-  https://github.com/google-gemini/gemini-cli/pull/13740
-- Improve code coverage for cli package by @megha1188 in
-  https://github.com/google-gemini/gemini-cli/pull/13724
-- Add session subtask in /stats command by @Adib234 in
-  https://github.com/google-gemini/gemini-cli/pull/13750
-- feat(core): Migrate chatCompressionService to model configs. by @joshualitt in
-  https://github.com/google-gemini/gemini-cli/pull/12863
-- feat(hooks): Hook Telemetry Infrastructure by @Edilmo in
-  https://github.com/google-gemini/gemini-cli/pull/9082
-- fix: (some minor improvements to configs and getPackageJson return behaviour)
-  by @grMLEqomlkkU5Eeinz4brIrOVCUCkJuN in
-  https://github.com/google-gemini/gemini-cli/pull/12510
-- feat(hooks): Hook Event Handling by @Edilmo in
-  https://github.com/google-gemini/gemini-cli/pull/9097
-- feat(hooks): Hook Agent Lifecycle Integration by @Edilmo in
-  https://github.com/google-gemini/gemini-cli/pull/9105
-- feat(core): Land bool for alternate system prompt. by @joshualitt in
-  https://github.com/google-gemini/gemini-cli/pull/13764
-- bug(core): Add default chat compression config. by @joshualitt in
-  https://github.com/google-gemini/gemini-cli/pull/13766
-- feat(model-availability): introduce ModelPolicy and PolicyCatalog by
-  @adamfweidman in https://github.com/google-gemini/gemini-cli/pull/13751
-- feat(hooks): Hook System Orchestration by @Edilmo in
-  https://github.com/google-gemini/gemini-cli/pull/9102
-- feat(config): add isModelAvailabilityServiceEnabled setting by @adamfweidman
-  in https://github.com/google-gemini/gemini-cli/pull/13777
-- chore/release: bump version to 0.19.0-nightly.20251125.f6d97d448 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/13782
-- chore: remove console.error by @adamfweidman in
-  https://github.com/google-gemini/gemini-cli/pull/13779
-- fix: Add $schema property to settings.schema.json by @sacrosanctic in
-  https://github.com/google-gemini/gemini-cli/pull/12763
-- fix(cli): allow non-GitHub SCP-styled URLs for extension installation by @m0ps
-  in https://github.com/google-gemini/gemini-cli/pull/13800
-- fix(resume): allow passing a prompt via stdin while resuming using --resume by
-  @bl-ue in https://github.com/google-gemini/gemini-cli/pull/13520
-- feat(sessions): add /resume slash command to open the session browser by
-  @bl-ue in https://github.com/google-gemini/gemini-cli/pull/13621
-- docs(sessions): add documentation for chat recording and session management by
-  @bl-ue in https://github.com/google-gemini/gemini-cli/pull/13667
-- Fix TypeError: "URL.parse is not a function" for Node.js < v22 by @macarronesc
-  in https://github.com/google-gemini/gemini-cli/pull/13698
-- fallback to flash for TerminalQuota errors by @sehoon38 in
-  https://github.com/google-gemini/gemini-cli/pull/13791
-- Update Code Wiki README badge by @PatoBeltran in
-  https://github.com/google-gemini/gemini-cli/pull/13768
-- Add Databricks auth support and custom header option to gemini cli by
-  @AarushiShah in https://github.com/google-gemini/gemini-cli/pull/11893
-- Update dependency for modelcontextprotocol/sdk to 1.23.0 by @bbiggs in
-  https://github.com/google-gemini/gemini-cli/pull/13827
-
-**Full Changelog**:
-https://github.com/google-gemini/gemini-cli/compare/v0.18.0-preview.4...v0.19.0-preview.0
-
-## Release v0.18.0 - v0.18.4
-
-### Highlights
-
-- **Experimental permission improvements**: We're experimenting with a new
-  policy engine in Gemini CLI, letting users and administrators create
-  fine-grained policies for tool calls. This setting is currently behind a flag.
-  See our [policy engine documentation](../core/policy-engine.md) to learn how
-  to use this feature.
-- **Gemini 3 support rolled out for some users**: Some users can now enable
-  Gemini 3 by using the `/settings` flag and toggling **Preview Features**. See
-  our [Gemini 3 on Gemini CLI documentation](../get-started/gemini-3.md) to find
-  out more about using Gemini 3.
-- **Updated UI rollback:** We've temporarily rolled back a previous UI update,
-  which enabled embedded scrolling and mouse support. This can be re-enabled by
-  using the `/settings` command and setting **Use Alternate Screen Buffer** to
-  `true`.
-- **Display your model in your chat history**: You can now go use `/settings`
-  and turn on **Show Model in Chat** to display the model in your chat history.
-- **Uninstall multiple extensions**: You can uninstall multiple extensions with
-  a single command: `gemini extensions uninstall`.
-
-![Uninstalling Gemini extensions with a single command](https://i.imgur.com/pi7nEBI.png)
-
-### What's changed
-
-- Remove obsolete reference to "help wanted" label in CONTRIBUTING.md by
-  @aswinashok44 in https://github.com/google-gemini/gemini-cli/pull/13291
-- chore(release): v0.18.0-nightly.20251118.86828bb56 by @skeshive in
-  https://github.com/google-gemini/gemini-cli/pull/13309
-- Docs: Access clarification. by @jkcinouye in
-  https://github.com/google-gemini/gemini-cli/pull/13304
-- Fix links in Gemini 3 Pro documentation by @gmackall in
-  https://github.com/google-gemini/gemini-cli/pull/13312
-- Improve keyboard code parsing by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/13307
-- fix(core): Ensure `read_many_files` tool is available to zed. by @joshualitt
-  in https://github.com/google-gemini/gemini-cli/pull/13338
-- Support 3-parameter modifyOtherKeys sequences by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/13342
-- Improve pty resize error handling for Windows by @galz10 in
-  https://github.com/google-gemini/gemini-cli/pull/13353
-- fix(ui): Clear input prompt on Escape key press by @SandyTao520 in
-  https://github.com/google-gemini/gemini-cli/pull/13335
-- bug(ui) showLineNumbers had the wrong default value. by @jacob314 in
-  https://github.com/google-gemini/gemini-cli/pull/13356
-- fix(cli): fix crash on startup in NO_COLOR mode (#13343) due to ungua… by
-  @avilladsen in https://github.com/google-gemini/gemini-cli/pull/13352
-- fix: allow MCP prompts with spaces in name by @jackwotherspoon in
-  https://github.com/google-gemini/gemini-cli/pull/12910
-- Refactor createTransport to duplicate less code by @davidmcwherter in
-  https://github.com/google-gemini/gemini-cli/pull/13010
-- Followup from #10719 by @bl-ue in
-  https://github.com/google-gemini/gemini-cli/pull/13243
-- Capturing github action workflow name if present and send it to clearcut by
-  @MJjainam in https://github.com/google-gemini/gemini-cli/pull/13132
-- feat(sessions): record interactive-only errors and warnings to chat recording
-  JSON files by @bl-ue in https://github.com/google-gemini/gemini-cli/pull/13300
-- fix(zed-integration): Correctly handle cancellation errors by @benbrandt in
-  https://github.com/google-gemini/gemini-cli/pull/13399
-- docs: Add Code Wiki link to README by @holtskinner in
-  https://github.com/google-gemini/gemini-cli/pull/13289
-- Restore keyboard mode when exiting the editor by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/13350
-- feat(core, cli): Bump genai version to 1.30.0 by @joshualitt in
-  https://github.com/google-gemini/gemini-cli/pull/13435
-- [cli-ui] Keep header ASCII art colored on non-gradient terminals (#13373) by
-  @bniladridas in https://github.com/google-gemini/gemini-cli/pull/13374
-- Fix Copyright line in LICENSE by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/13449
-- Fix typo in write_todos methodology instructions by @Smetalo in
-  https://github.com/google-gemini/gemini-cli/pull/13411
-- feat: update thinking mode support to exclude gemini-2.0 models and simplify
-  logic. by @kevin-ramdass in
-  https://github.com/google-gemini/gemini-cli/pull/13454
-- remove unneeded log by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/13456
-- feat: add click-to-focus support for interactive shell by @galz10 in
-  https://github.com/google-gemini/gemini-cli/pull/13341
-- Add User email detail to about box by @ptone in
-  https://github.com/google-gemini/gemini-cli/pull/13459
-- feat(core): Wire up chat code path for model configs. by @joshualitt in
-  https://github.com/google-gemini/gemini-cli/pull/12850
-- chore/release: bump version to 0.18.0-nightly.20251120.2231497b1 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/13476
-- feat(core): Fix bug with incorrect model overriding. by @joshualitt in
-  https://github.com/google-gemini/gemini-cli/pull/13477
-- Use synchronous writes when detecting keyboard modes by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/13478
-- fix(cli): prevent race condition when restoring prompt after context overflow
-  by @SandyTao520 in https://github.com/google-gemini/gemini-cli/pull/13473
-- Revert "feat(core): Fix bug with incorrect model overriding." by @adamfweidman
-  in https://github.com/google-gemini/gemini-cli/pull/13483
-- Fix: Update system instruction when GEMINI.md memory is loaded or refreshed by
-  @lifefloating in https://github.com/google-gemini/gemini-cli/pull/12136
-- fix(zed-integration): Ensure that the zed integration is classified as
-  interactive by @benbrandt in
-  https://github.com/google-gemini/gemini-cli/pull/13394
-- Copy commands as part of setup-github by @gsehgal in
-  https://github.com/google-gemini/gemini-cli/pull/13464
-- Update banner design by @Adib234 in
-  https://github.com/google-gemini/gemini-cli/pull/13420
-- Protect stdout and stderr so JavaScript code can't accidentally write to
-  stdout corrupting ink rendering by @jacob314 in
-  https://github.com/google-gemini/gemini-cli/pull/13247
-- Enable switching preview features on/off without restart by @Adib234 in
-  https://github.com/google-gemini/gemini-cli/pull/13515
-- feat(core): Use thinking level for Gemini 3 by @joshualitt in
-  https://github.com/google-gemini/gemini-cli/pull/13445
-- Change default compress threshold to 0.5 for api key users by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/13517
-- remove duplicated mouse code by @scidomino in
-  https://github.com/google-gemini/gemini-cli/pull/13525
-- feat(zed-integration): Use default model routing for Zed integration by
-  @benbrandt in https://github.com/google-gemini/gemini-cli/pull/13398
-- feat(core): Incorporate Gemini 3 into model config hierarchy. by @joshualitt
-  in https://github.com/google-gemini/gemini-cli/pull/13447
-- fix(patch): cherry-pick 5e218a5 to release/v0.18.0-preview.0-pr-13623 to patch
-  version v0.18.0-preview.0 and create version 0.18.0-preview.1 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/13626
-- fix(patch): cherry-pick d351f07 to release/v0.18.0-preview.1-pr-12535 to patch
-  version v0.18.0-preview.1 and create version 0.18.0-preview.2 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/13813
-- fix(patch): cherry-pick 3e50be1 to release/v0.18.0-preview.2-pr-13428 to patch
-  version v0.18.0-preview.2 and create version 0.18.0-preview.3 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/13821
-- fix(patch): cherry-pick d8a3d08 to release/v0.18.0-preview.3-pr-13791 to patch
-  version v0.18.0-preview.3 and create version 0.18.0-preview.4 by
-  @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/13826
-
-  **Full Changelog**:
-  https://github.com/google-gemini/gemini-cli/compare/v0.17.1...v0.18.0

docs/cli/authentication.md

@@ -1,3 +1,3 @@
-# Authentication setup
+# Authentication Setup
 
 See: [Getting Started - Authentication Setup](../get-started/authentication.md).

docs/cli/checkpointing.md

@@ -6,19 +6,19 @@ AI-powered tools. This allows you to safely experiment with and apply code
 changes, knowing you can instantly revert back to the state before the tool was
 run.
 
-## How it works
+## How It Works
 
 When you approve a tool that modifies the file system (like `write_file` or
 `replace`), the CLI automatically creates a "checkpoint." This checkpoint
 includes:
 
-1.  **A Git snapshot:** A commit is made in a special, shadow Git repository
+1.  **A Git Snapshot:** A commit is made in a special, shadow Git repository
     located in your home directory (`~/.gemini/history/<project_hash>`). This
     snapshot captures the complete state of your project files at that moment.
     It does **not** interfere with your own project's Git repository.
-2.  **Conversation history:** The entire conversation you've had with the agent
+2.  **Conversation History:** The entire conversation you've had with the agent
     up to that point is saved.
-3.  **The tool call:** The specific tool call that was about to be executed is
+3.  **The Tool Call:** The specific tool call that was about to be executed is
     also stored.
 
 If you want to undo the change or simply go back, you can use the `/restore`
@@ -35,14 +35,24 @@ repository while the conversation history and tool calls are saved in a JSON
 file in your project's temporary directory, typically located at
 `~/.gemini/tmp/<project_hash>/checkpoints`.
 
-## Enabling the feature
+## Enabling the Feature
 
-The Checkpointing feature is disabled by default. To enable it, you need to edit
-your `settings.json` file.
+The Checkpointing feature is disabled by default. To enable it, you can either
+use a command-line flag or edit your `settings.json` file.
 
-> **Note:** The `--checkpointing` command-line flag was removed in version
-> 0.11.0. Checkpointing can now only be enabled through the `settings.json`
-> configuration file.
+### Using the Command-Line Flag
+
+You can enable checkpointing for the current session by using the
+`--checkpointing` flag when starting the Gemini CLI:
+
+```bash
+gemini --checkpointing
+```
+
+### Using the `settings.json` File
+
+To enable checkpointing by default for all sessions, you need to edit your
+`settings.json` file.
 
 Add the following key to your `settings.json`:
 
@@ -56,12 +66,12 @@ Add the following key to your `settings.json`:
 }
 ```
 
-## Using the `/restore` command
+## Using the `/restore` Command
 
 Once enabled, checkpoints are created automatically. To manage them, you use the
 `/restore` command.
 
-### List available checkpoints
+### List Available Checkpoints
 
 To see a list of all saved checkpoints for the current project, simply run:
 
@@ -74,7 +84,7 @@ typically composed of a timestamp, the name of the file being modified, and the
 name of the tool that was about to be run (e.g.,
 `2025-06-22T10-00-00_000Z-my-file.txt-write_file`).
 
-### Restore a specific checkpoint
+### Restore a Specific Checkpoint
 
 To restore your project to a specific checkpoint, use the checkpoint file from
 the list:

docs/cli/commands.md

@@ -1,4 +1,4 @@
-# CLI commands
+# CLI Commands
 
 Gemini CLI supports several built-in commands to help you manage your session,
 customize the interface, and control its behavior. These commands are prefixed
@@ -26,13 +26,12 @@ Slash commands provide meta-level control over the CLI itself.
       - **Description:** Saves the current conversation history. You must add a
         `<tag>` for identifying the conversation state.
       - **Usage:** `/chat save <tag>`
-      - **Details on checkpoint location:** The default locations for saved chat
+      - **Details on Checkpoint Location:** The default locations for saved chat
         checkpoints are:
         - Linux/macOS: `~/.gemini/tmp/<project_hash>/`
         - Windows: `C:\Users\<YourUsername>\.gemini\tmp\<project_hash>\`
-        - **Behavior:** Chats are saved into a project-specific directory,
-          determined by where you run the CLI. Consequently, saved chats are
-          only accessible when working within that same project.
+        - When you run `/chat list`, the CLI only scans these specific
+          directories to find available checkpoints.
         - **Note:** These checkpoints are for manually saving and resuming
           conversation states. For automatic checkpoints created before file
           modifications, see the
@@ -40,14 +39,8 @@ Slash commands provide meta-level control over the CLI itself.
     - **`resume`**
       - **Description:** Resumes a conversation from a previous save.
       - **Usage:** `/chat resume <tag>`
-      - **Note:** You can only resume chats that were saved within the current
-        project. To resume a chat from a different project, you must run the
-        Gemini CLI from that project's directory.
     - **`list`**
       - **Description:** Lists available tags for chat state resumption.
-      - **Note:** This command only lists chats saved within the current
-        project. Because chat history is project-scoped, chats saved in other
-        project directories will not be displayed.
     - **`delete`**
       - **Description:** Deletes a saved conversation checkpoint.
       - **Usage:** `/chat delete <tag>`
@@ -128,9 +121,6 @@ Slash commands provide meta-level control over the CLI itself.
       - **Description:** Restarts all MCP servers and re-discovers their
         available tools.
 
-- [**`/model`**](./model.md)
-  - **Description:** Opens a dialog to choose your Gemini model.
-
 - **`/memory`**
   - **Description:** Manage the AI's instructional context (hierarchical memory
     loaded from `GEMINI.md` files).
@@ -161,34 +151,17 @@ Slash commands provide meta-level control over the CLI itself.
     edits made by a tool. If run without a tool call ID, it will list available
     checkpoints to restore from.
   - **Usage:** `/restore [tool_call_id]`
-  - **Note:** Only available if checkpointing is configured via
-    [settings](../get-started/configuration.md). See
+  - **Note:** Only available if the CLI is invoked with the `--checkpointing`
+    option or configured via [settings](../get-started/configuration.md). See
     [Checkpointing documentation](../cli/checkpointing.md) for more details.
-- **`/resume`**
-  - **Description:** Browse and resume previous conversation sessions. Opens an
-    interactive session browser where you can search, filter, and select from
-    automatically saved conversations.
-  - **Features:**
-    - **Session Browser:** Interactive interface showing all saved sessions with
-      timestamps, message counts, and first user message for context
-    - **Search:** Use `/` to search through conversation content across all
-      sessions
-    - **Sorting:** Sort sessions by date or message count
-    - **Management:** Delete unwanted sessions directly from the browser
-    - **Resume:** Select any session to resume and continue the conversation
-  - **Note:** All conversations are automatically saved as you chat - no manual
-    saving required. See [Session Management](../cli/session-management.md) for
-    complete details.
 
-- [**`/settings`**](./settings.md)
+- **`/settings`**
   - **Description:** Open the settings editor to view and modify Gemini CLI
     settings.
   - **Details:** This command provides a user-friendly interface for changing
     settings that control the behavior and appearance of Gemini CLI. It is
     equivalent to manually editing the `.gemini/settings.json` file, but with
-    validation and guidance to prevent errors. See the
-    [settings documentation](./settings.md) for a full list of available
-    settings.
+    validation and guidance to prevent errors.
   - **Usage:** Simply run `/settings` and the editor will open. You can then
     browse or search for specific settings, view their current values, and
     modify them as desired. Changes to some settings are applied immediately,
@@ -256,13 +229,13 @@ Slash commands provide meta-level control over the CLI itself.
     file, making it simpler for them to provide project-specific instructions to
     the Gemini agent.
 
-### Custom commands
+### Custom Commands
 
 Custom commands allow you to create personalized shortcuts for your most-used
 prompts. For detailed instructions on how to create, manage, and use them,
 please see the dedicated [Custom Commands documentation](./custom-commands.md).
 
-## Input prompt shortcuts
+## Input Prompt Shortcuts
 
 These shortcuts apply directly to the input prompt for text manipulation.
 
@@ -320,7 +293,7 @@ your prompt to Gemini. These commands include git-aware filtering.
 - If the `read_many_files` tool encounters an error (e.g., permission issues),
   this will also be reported.
 
-## Shell mode and passthrough commands (`!`)
+## Shell mode & passthrough commands (`!`)
 
 The `!` prefix lets you interact with your system's shell directly from within
 Gemini CLI.
@@ -348,7 +321,7 @@ Gemini CLI.
 - **Caution for all `!` usage:** Commands you execute in shell mode have the
   same permissions and impact as if you ran them directly in your terminal.
 
-- **Environment variable:** When a command is executed via `!` or in shell mode,
+- **Environment Variable:** When a command is executed via `!` or in shell mode,
   the `GEMINI_CLI=1` environment variable is set in the subprocess's
   environment. This allows scripts or tools to detect if they are being run from
   within the Gemini CLI.

docs/cli/configuration.md

@@ -1,4 +1,4 @@
-# Gemini CLI configuration
+# Gemini CLI Configuration
 
 Gemini CLI offers several ways to configure its behavior, including environment
 variables, command-line arguments, and settings files. This document outlines
@@ -144,7 +144,7 @@ contain other project-specific files related to Gemini CLI's operation, such as:
     be ignored if `--allowed-mcp-server-names` is set.
   - **Default**: No MCP servers excluded.
   - **Example:** `"excludeMCPServers": ["myNodeServer"]`.
-  - **Security note:** This uses simple string matching on MCP server names,
+  - **Security Note:** This uses simple string matching on MCP server names,
     which can be modified. If you're a system administrator looking to prevent
     users from bypassing this, consider configuring the `mcpServers` at the
     system settings level such that the user will not be able to configure any
@@ -423,7 +423,7 @@ contain other project-specific files related to Gemini CLI's operation, such as:
 }
 ```
 
-## Shell history
+## Shell History
 
 The CLI keeps a history of shell commands you run. To avoid conflicts between
 different projects, this history is stored in a project-specific directory
@@ -434,7 +434,7 @@ within your user's home folder.
     path.
   - The history is stored in a file named `shell_history`.
 
-## Environment variables and `.env` files
+## Environment Variables & `.env` Files
 
 Environment variables are a common way to configure applications, especially for
 sensitive information like API keys or for settings that might change between
@@ -449,7 +449,7 @@ loading order is:
     the home directory.
 3.  If still not found, it looks for `~/.env` (in the user's home directory).
 
-**Environment variable exclusion:** Some environment variables (like `DEBUG` and
+**Environment Variable Exclusion:** Some environment variables (like `DEBUG` and
 `DEBUG_MODE`) are automatically excluded from being loaded from project `.env`
 files to prevent interference with gemini-cli behavior. Variables from
 `.gemini/.env` files are never excluded. You can customize this behavior using
@@ -464,18 +464,6 @@ the `excludedProjectEnvVars` setting in your `settings.json` file.
   - Specifies the default Gemini model to use.
   - Overrides the hardcoded default
   - Example: `export GEMINI_MODEL="gemini-2.5-flash"`
-- **`GEMINI_CLI_CUSTOM_HEADERS`**:
-  - Adds extra HTTP headers to Gemini API and Code Assist requests.
-  - Accepts a comma-separated list of `Name: value` pairs.
-  - Example:
-    `export GEMINI_CLI_CUSTOM_HEADERS="X-My-Header: foo, X-Trace-ID: abc123"`.
-- **`GEMINI_API_KEY_AUTH_MECHANISM`**:
-  - Specifies how the API key should be sent for authentication when using
-    `AuthType.USE_GEMINI` or `AuthType.USE_VERTEX_AI`.
-  - Valid values are `x-goog-api-key` (default) or `bearer`.
-  - If set to `bearer`, the API key will be sent in the
-    `Authorization: Bearer <key>` header.
-  - Example: `export GEMINI_API_KEY_AUTH_MECHANISM="bearer"`
 - **`GOOGLE_API_KEY`**:
   - Your Google Cloud API key.
   - Required for using Vertex AI in express mode.
@@ -486,7 +474,7 @@ the `excludedProjectEnvVars` setting in your `settings.json` file.
   - Required for using Code Assist or Vertex AI.
   - If using Vertex AI, ensure you have the necessary permissions in this
     project.
-  - **Cloud shell note:** When running in a Cloud Shell environment, this
+  - **Cloud Shell Note:** When running in a Cloud Shell environment, this
     variable defaults to a special project allocated for Cloud Shell users. If
     you have `GOOGLE_CLOUD_PROJECT` set in your global environment in Cloud
     Shell, it will be overridden by this default. To use a different project in
@@ -506,9 +494,6 @@ the `excludedProjectEnvVars` setting in your `settings.json` file.
 - **`GEMINI_SANDBOX`**:
   - Alternative to the `sandbox` setting in `settings.json`.
   - Accepts `true`, `false`, `docker`, `podman`, or a custom command string.
-- **`HTTP_PROXY` / `HTTPS_PROXY`**:
-  - Specifies the proxy server to use for outgoing HTTP/HTTPS requests.
-  - Example: `export HTTPS_PROXY="http://proxy.example.com:8080"`
 - **`SEATBELT_PROFILE`** (macOS specific):
   - Switches the Seatbelt (`sandbox-exec`) profile on macOS.
   - `permissive-open`: (Default) Restricts writes to the project folder (and a
@@ -547,7 +532,7 @@ the `excludedProjectEnvVars` setting in your `settings.json` file.
     relative. `~` is supported for the home directory. **Note: This will
     overwrite the file if it already exists.**
 
-## Command-line arguments
+## Command-Line Arguments
 
 Arguments passed directly when running the CLI can override other configurations
 for that specific session.
@@ -579,16 +564,18 @@ for that specific session.
 - **`--yolo`**:
   - Enables YOLO mode, which automatically approves all tool calls.
 - **`--telemetry`**:
-  - Enables [telemetry](./telemetry.md).
+  - Enables [telemetry](../telemetry.md).
 - **`--telemetry-target`**:
-  - Sets the telemetry target. See [telemetry](./telemetry.md) for more
+  - Sets the telemetry target. See [telemetry](../telemetry.md) for more
     information.
 - **`--telemetry-otlp-endpoint`**:
-  - Sets the OTLP endpoint for telemetry. See [telemetry](./telemetry.md) for
+  - Sets the OTLP endpoint for telemetry. See [telemetry](../telemetry.md) for
     more information.
 - **`--telemetry-log-prompts`**:
-  - Enables logging of prompts for telemetry. See [telemetry](./telemetry.md)
+  - Enables logging of prompts for telemetry. See [telemetry](../telemetry.md)
     for more information.
+- **`--checkpointing`**:
+  - Enables [checkpointing](./checkpointing.md).
 - **`--extensions <extension_name ...>`** (**`-e <extension_name ...>`**):
   - Specifies a list of extensions to use for the session. If not provided, all
     available extensions are used.
@@ -596,6 +583,9 @@ for that specific session.
   - Example: `gemini -e my-extension -e my-other-extension`
 - **`--list-extensions`** (**`-l`**):
   - Lists all available extensions and exits.
+- **`--proxy`**:
+  - Sets the proxy for the CLI.
+  - Example: `--proxy http://localhost:7890`.
 - **`--include-directories <dir1,dir2,...>`**:
   - Includes additional directories in the workspace for multi-directory
     support.
@@ -606,7 +596,7 @@ for that specific session.
 - **`--version`**:
   - Displays the version of the CLI.
 
-## Context files (hierarchical instructional context)
+## Context Files (Hierarchical Instructional Context)
 
 While not strictly configuration for the CLI's _behavior_, context files
 (defaulting to `GEMINI.md` but configurable via the `contextFileName` setting)
@@ -622,7 +612,7 @@ context.
   that you want the Gemini model to be aware of during your interactions. The
   system is designed to manage this instructional context hierarchically.
 
-### Example context file content (e.g., `GEMINI.md`)
+### Example Context File Content (e.g., `GEMINI.md`)
 
 Here's a conceptual example of what a context file at the root of a TypeScript
 project might contain:
@@ -663,23 +653,23 @@ more relevant and precise your context files are, the better the AI can assist
 you. Project-specific context files are highly encouraged to establish
 conventions and context.
 
-- **Hierarchical loading and precedence:** The CLI implements a sophisticated
+- **Hierarchical Loading and Precedence:** The CLI implements a sophisticated
   hierarchical memory system by loading context files (e.g., `GEMINI.md`) from
   several locations. Content from files lower in this list (more specific)
   typically overrides or supplements content from files higher up (more
   general). The exact concatenation order and final context can be inspected
   using the `/memory show` command. The typical loading order is:
-  1.  **Global context file:**
+  1.  **Global Context File:**
       - Location: `~/.gemini/<contextFileName>` (e.g., `~/.gemini/GEMINI.md` in
         your user home directory).
       - Scope: Provides default instructions for all your projects.
-  2.  **Project root and ancestors context files:**
+  2.  **Project Root & Ancestors Context Files:**
       - Location: The CLI searches for the configured context file in the
         current working directory and then in each parent directory up to either
         the project root (identified by a `.git` folder) or your home directory.
       - Scope: Provides context relevant to the entire project or a significant
         portion of it.
-  3.  **Sub-directory context files (contextual/local):**
+  3.  **Sub-directory Context Files (Contextual/Local):**
       - Location: The CLI also scans for the configured context file in
         subdirectories _below_ the current working directory (respecting common
         ignore patterns like `node_modules`, `.git`, etc.). The breadth of this
@@ -687,15 +677,15 @@ conventions and context.
         with a `memoryDiscoveryMaxDirs` field in your `settings.json` file.
       - Scope: Allows for highly specific instructions relevant to a particular
         component, module, or subsection of your project.
-- **Concatenation and UI indication:** The contents of all found context files
-  are concatenated (with separators indicating their origin and path) and
-  provided as part of the system prompt to the Gemini model. The CLI footer
-  displays the count of loaded context files, giving you a quick visual cue
-  about the active instructional context.
-- **Importing content:** You can modularize your context files by importing
+- **Concatenation & UI Indication:** The contents of all found context files are
+  concatenated (with separators indicating their origin and path) and provided
+  as part of the system prompt to the Gemini model. The CLI footer displays the
+  count of loaded context files, giving you a quick visual cue about the active
+  instructional context.
+- **Importing Content:** You can modularize your context files by importing
   other Markdown files using the `@path/to/file.md` syntax. For more details,
   see the [Memory Import Processor documentation](../core/memport.md).
-- **Commands for memory management:**
+- **Commands for Memory Management:**
   - Use `/memory refresh` to force a re-scan and reload of all context files
     from all configured locations. This updates the AI's instructional context.
   - Use `/memory show` to display the combined instructional context currently
@@ -742,7 +732,7 @@ sandbox image:
 BUILD_SANDBOX=1 gemini -s
 ```
 
-## Usage statistics
+## Usage Statistics
 
 To help us improve the Gemini CLI, we collect anonymized usage statistics. This
 data helps us understand how the CLI is used, identify common issues, and
@@ -750,22 +740,22 @@ prioritize new features.
 
 **What we collect:**
 
-- **Tool calls:** We log the names of the tools that are called, whether they
+- **Tool Calls:** We log the names of the tools that are called, whether they
   succeed or fail, and how long they take to execute. We do not collect the
   arguments passed to the tools or any data returned by them.
-- **API requests:** We log the Gemini model used for each request, the duration
+- **API Requests:** We log the Gemini model used for each request, the duration
   of the request, and whether it was successful. We do not collect the content
   of the prompts or responses.
-- **Session information:** We collect information about the configuration of the
+- **Session Information:** We collect information about the configuration of the
   CLI, such as the enabled tools and the approval mode.
 
 **What we DON'T collect:**
 
-- **Personally identifiable information (PII):** We do not collect any personal
+- **Personally Identifiable Information (PII):** We do not collect any personal
   information, such as your name, email address, or API keys.
-- **Prompt and response content:** We do not log the content of your prompts or
+- **Prompt and Response Content:** We do not log the content of your prompts or
   the responses from the Gemini model.
-- **File content:** We do not log the content of any files that are read or
+- **File Content:** We do not log the content of any files that are read or
   written by the CLI.
 
 **How to opt out:**

docs/cli/custom-commands.md

@@ -1,4 +1,4 @@
-# Custom commands
+# Custom Commands
 
 Custom commands let you save and reuse your favorite or most frequently used
 prompts as personal shortcuts within Gemini CLI. You can create commands that
@@ -9,9 +9,9 @@ all your projects, streamlining your workflow and ensuring consistency.
 
 Gemini CLI discovers commands from two locations, loaded in a specific order:
 
-1.  **User commands (global):** Located in `~/.gemini/commands/`. These commands
+1.  **User Commands (Global):** Located in `~/.gemini/commands/`. These commands
     are available in any project you are working on.
-2.  **Project commands (local):** Located in
+2.  **Project Commands (Local):** Located in
     `<your-project-root>/.gemini/commands/`. These commands are specific to the
     current project and can be checked into version control to be shared with
     your team.
@@ -30,7 +30,7 @@ separator (`/` or `\`) being converted to a colon (`:`).
 - A file at `<project>/.gemini/commands/git/commit.toml` becomes the namespaced
   command `/git:commit`.
 
-## TOML file format (v1)
+## TOML File Format (v1)
 
 Your command definition files must be written in the TOML format and use the
 `.toml` file extension.
@@ -60,7 +60,7 @@ replace that placeholder with the text the user typed after the command name.
 
 The behavior of this injection depends on where it is used:
 
-**A. Raw injection (outside shell commands)**
+**A. Raw injection (outside Shell commands)**
 
 When used in the main body of the prompt, the arguments are injected exactly as
 the user typed them.
@@ -77,7 +77,7 @@ prompt = "Please provide a code fix for the issue described here: {{args}}."
 The model receives:
 `Please provide a code fix for the issue described here: "Button is misaligned".`
 
-**B. Using arguments in shell commands (inside `!{...}` blocks)**
+**B. Using arguments in Shell commands (inside `!{...}` blocks)**
 
 When you use `{{args}}` inside a shell injection block (`!{...}`), the arguments
 are automatically **shell-escaped** before replacement. This allows you to
@@ -156,7 +156,7 @@ When you run `/changelog 1.2.0 added "New feature"`, the final text sent to the
 model will be the original prompt followed by two newlines and the command you
 typed.
 
-### 3. Executing shell commands with `!{...}`
+### 3. Executing Shell commands with `!{...}`
 
 You can make your commands dynamic by executing shell commands directly within
 your `prompt` and injecting their output. This is ideal for gathering context
@@ -302,7 +302,7 @@ Your response should include:
 """
 ```
 
-**3. Run the command:**
+**3. Run the Command:**
 
 That's it! You can now run your command in the CLI. First, you might add a file
 to the context, and then invoke your command:

docs/cli/enterprise.md

@@ -1,11 +1,11 @@
-# Gemini CLI for the enterprise
+# Gemini CLI for the Enterprise
 
 This document outlines configuration patterns and best practices for deploying
 and managing Gemini CLI in an enterprise environment. By leveraging system-level
 settings, administrators can enforce security policies, manage tool access, and
 ensure a consistent experience for all users.
 
-> **A note on security:** The patterns described in this document are intended
+> **A Note on Security:** The patterns described in this document are intended
 > to help administrators create a more controlled and secure environment for
 > using Gemini CLI. However, they should not be considered a foolproof security
 > boundary. A determined user with sufficient privileges on their local machine
@@ -14,7 +14,7 @@ ensure a consistent experience for all users.
 > managed environment, not to defend against a malicious actor with local
 > administrative rights.
 
-## Centralized configuration: The system settings file
+## Centralized Configuration: The System Settings File
 
 The most powerful tools for enterprise administration are the system-wide
 settings files. These files allow you to define a baseline configuration
@@ -33,11 +33,11 @@ settings (like `theme`) is:
 This means the System Overrides file has the final say. For settings that are
 arrays (`includeDirectories`) or objects (`mcpServers`), the values are merged.
 
-**Example of merging and precedence:**
+**Example of Merging and Precedence:**
 
 Here is how settings from different levels are combined.
 
-- **System defaults `system-defaults.json`:**
+- **System Defaults `system-defaults.json`:**
 
   ```json
   {
@@ -89,7 +89,7 @@ Here is how settings from different levels are combined.
   }
   ```
 
-- **System overrides `settings.json`:**
+- **System Overrides `settings.json`:**
   ```json
   {
     "ui": {
@@ -108,7 +108,7 @@ Here is how settings from different levels are combined.
 
 This results in the following merged configuration:
 
-- **Final merged configuration:**
+- **Final Merged Configuration:**
   ```json
   {
     "ui": {
@@ -159,51 +159,7 @@ This results in the following merged configuration:
 By using the system settings file, you can enforce the security and
 configuration patterns described below.
 
-### Enforcing system settings with a wrapper script
-
-While the `GEMINI_CLI_SYSTEM_SETTINGS_PATH` environment variable provides
-flexibility, a user could potentially override it to point to a different
-settings file, bypassing the centrally managed configuration. To mitigate this,
-enterprises can deploy a wrapper script or alias that ensures the environment
-variable is always set to the corporate-controlled path.
-
-This approach ensures that no matter how the user calls the `gemini` command,
-the enterprise settings are always loaded with the highest precedence.
-
-**Example wrapper script:**
-
-Administrators can create a script named `gemini` and place it in a directory
-that appears earlier in the user's `PATH` than the actual Gemini CLI binary
-(e.g., `/usr/local/bin/gemini`).
-
-```bash
-#!/bin/bash
-
-# Enforce the path to the corporate system settings file.
-# This ensures that the company's configuration is always applied.
-export GEMINI_CLI_SYSTEM_SETTINGS_PATH="/etc/gemini-cli/settings.json"
-
-# Find the original gemini executable.
-# This is a simple example; a more robust solution might be needed
-# depending on the installation method.
-REAL_GEMINI_PATH=$(type -aP gemini | grep -v "^$(type -P gemini)$" | head -n 1)
-
-if [ -z "$REAL_GEMINI_PATH" ]; then
-  echo "Error: The original 'gemini' executable was not found." >&2
-  exit 1
-fi
-
-# Pass all arguments to the real Gemini CLI executable.
-exec "$REAL_GEMINI_PATH" "$@"
-```
-
-By deploying this script, the `GEMINI_CLI_SYSTEM_SETTINGS_PATH` is set within
-the script's environment, and the `exec` command replaces the script process
-with the actual Gemini CLI process, which inherits the environment variable.
-This makes it significantly more difficult for a user to bypass the enforced
-settings.
-
-## Restricting tool access
+## Restricting Tool Access
 
 You can significantly enhance security by controlling which tools the Gemini
 model can use. This is achieved through the `tools.core` and `tools.exclude`
@@ -241,39 +197,19 @@ environment to a blocklist.
 }
 ```
 
-**Security note:** Blocklisting with `excludeTools` is less secure than
+**Security Note:** Blocklisting with `excludeTools` is less secure than
 allowlisting with `coreTools`, as it relies on blocking known-bad commands, and
 clever users may find ways to bypass simple string-based blocks. **Allowlisting
 is the recommended approach.**
 
-### Disabling YOLO mode
-
-To ensure that users cannot bypass the confirmation prompt for tool execution,
-you can disable YOLO mode at the policy level. This adds a critical layer of
-safety, as it prevents the model from executing tools without explicit user
-approval.
-
-**Example:** Force all tool executions to require user confirmation.
-
-```json
-{
-  "security": {
-    "disableYoloMode": true
-  }
-}
-```
-
-This setting is highly recommended in an enterprise environment to prevent
-unintended tool execution.
-
-## Managing custom tools (MCP servers)
+## Managing Custom Tools (MCP Servers)
 
 If your organization uses custom tools via
 [Model-Context Protocol (MCP) servers](../core/tools-api.md), it is crucial to
 understand how server configurations are managed to apply security policies
 effectively.
 
-### How MCP server configurations are merged
+### How MCP Server Configurations are Merged
 
 Gemini CLI loads `settings.json` files from three levels: System, Workspace, and
 User. When it comes to the `mcpServers` object, these configurations are
@@ -290,12 +226,12 @@ This means a user **cannot** override the definition of a server that is already
 defined in the system-level settings. However, they **can** add new servers with
 unique names.
 
-### Enforcing a catalog of tools
+### Enforcing a Catalog of Tools
 
 The security of your MCP tool ecosystem depends on a combination of defining the
 canonical servers and adding their names to an allowlist.
 
-### Restricting tools within an MCP server
+### Restricting Tools Within an MCP Server
 
 For even greater security, especially when dealing with third-party MCP servers,
 you can restrict which specific tools from a server are exposed to the model.
@@ -324,7 +260,7 @@ third-party MCP server, even if the server offers other tools like
 }
 ```
 
-#### More secure pattern: Define and add to allowlist in system settings
+#### More Secure Pattern: Define and Add to Allowlist in System Settings
 
 To create a secure, centrally-managed catalog of tools, the system administrator
 **must** do both of the following in the system-level `settings.json` file:
@@ -337,7 +273,7 @@ To create a secure, centrally-managed catalog of tools, the system administrator
     any servers that are not on this list. If this setting is omitted, the CLI
     will merge and allow any server defined by the user.
 
-**Example system `settings.json`:**
+**Example System `settings.json`:**
 
 1. Add the _names_ of all approved servers to an allowlist. This will prevent
    users from adding their own servers.
@@ -366,12 +302,12 @@ Any server a user defines will either be overridden by the system definition (if
 it has the same name) or blocked because its name is not in the `mcp.allowed`
 list.
 
-### Less secure pattern: Omitting the allowlist
+### Less Secure Pattern: Omitting the Allowlist
 
 If the administrator defines the `mcpServers` object but fails to also specify
 the `mcp.allowed` allowlist, users may add their own servers.
 
-**Example system `settings.json`:**
+**Example System `settings.json`:**
 
 This configuration defines servers but does not enforce the allowlist. The
 administrator has NOT included the "mcp.allowed" setting.
@@ -391,7 +327,7 @@ In this scenario, a user can add their own server in their local
 results, the user's server will be added to the list of available tools and
 allowed to run.
 
-## Enforcing sandboxing for security
+## Enforcing Sandboxing for Security
 
 To mitigate the risk of potentially harmful operations, you can enforce the use
 of sandboxing for all tool execution. The sandbox isolates tool execution in a
@@ -407,18 +343,19 @@ containerized environment.
 }
 ```
 
-You can also specify a custom, hardened Docker image for the sandbox by building
-a custom `sandbox.Dockerfile` as described in the
+You can also specify a custom, hardened Docker image for the sandbox using the
+`--sandbox-image` command-line argument or by building a custom
+`sandbox.Dockerfile` as described in the
 [Sandboxing documentation](./sandbox.md).
 
-## Controlling network access via proxy
+## Controlling Network Access via Proxy
 
 In corporate environments with strict network policies, you can configure Gemini
 CLI to route all outbound traffic through a corporate proxy. This can be set via
 an environment variable, but it can also be enforced for custom tools via the
 `mcpServers` configuration.
 
-**Example (for an MCP server):**
+**Example (for an MCP Server):**
 
 ```json
 {
@@ -435,7 +372,7 @@ an environment variable, but it can also be enforced for custom tools via the
 }
 ```
 
-## Telemetry and auditing
+## Telemetry and Auditing
 
 For auditing and monitoring purposes, you can configure Gemini CLI to send
 telemetry data to a central location. This allows you to track tool usage and
@@ -478,39 +415,7 @@ prompted to switch to the enforced method. In non-interactive mode, the CLI will
 exit with an error if the configured authentication method does not match the
 enforced one.
 
-### Restricting logins to corporate domains
-
-For enterprises using Google Workspace, you can enforce that users only
-authenticate with their corporate Google accounts. This is a network-level
-control that is configured on a proxy server, not within Gemini CLI itself. It
-works by intercepting authentication requests to Google and adding a special
-HTTP header.
-
-This policy prevents users from logging in with personal Gmail accounts or other
-non-corporate Google accounts.
-
-For detailed instructions, see the Google Workspace Admin Help article on
-[blocking access to consumer accounts](https://support.google.com/a/answer/1668854?hl=en#zippy=%2Cstep-choose-a-web-proxy-server%2Cstep-configure-the-network-to-block-certain-accounts).
-
-The general steps are as follows:
-
-1.  **Intercept Requests**: Configure your web proxy to intercept all requests
-    to `google.com`.
-2.  **Add HTTP Header**: For each intercepted request, add the
-    `X-GoogApps-Allowed-Domains` HTTP header.
-3.  **Specify Domains**: The value of the header should be a comma-separated
-    list of your approved Google Workspace domain names.
-
-**Example header:**
-
-```
-X-GoogApps-Allowed-Domains: my-corporate-domain.com, secondary-domain.com
-```
-
-When this header is present, Google's authentication service will only allow
-logins from accounts belonging to the specified domains.
-
-## Putting it all together: example system `settings.json`
+## Putting It All Together: Example System `settings.json`
 
 Here is an example of a system `settings.json` file that combines several of the
 patterns discussed above to create a secure, controlled environment for Gemini

docs/cli/gemini-ignore.md

@@ -1,4 +1,4 @@
-# Ignoring files
+# Ignoring Files
 
 This document provides an overview of the Gemini Ignore (`.geminiignore`)
 feature of the Gemini CLI.
@@ -13,8 +13,8 @@ Git).
 
 When you add a path to your `.geminiignore` file, tools that respect this file
 will exclude matching files and directories from their operations. For example,
-when you use the `@` command to share files, any paths in your `.geminiignore`
-file will be automatically excluded.
+when you use the [`read_many_files`](../tools/multi-file.md) command, any paths
+in your `.geminiignore` file will be automatically excluded.
 
 For the most part, `.geminiignore` follows the conventions of `.gitignore`
 files:

docs/cli/gemini-md.md

@@ -1,4 +1,4 @@
-# Provide context with GEMINI.md files
+# Provide Context with GEMINI.md Files
 
 Context files, which use the default name `GEMINI.md`, are a powerful feature
 for providing instructional context to the Gemini model. You can use these files

docs/cli/generation-settings.md

@@ -1,210 +0,0 @@
-# Advanced Model Configuration
-
-This guide details the Model Configuration system within the Gemini CLI.
-Designed for researchers, AI quality engineers, and advanced users, this system
-provides a rigorous framework for managing generative model hyperparameters and
-behaviors.
-
-> **Warning**: This is a power-user feature. Configuration values are passed
-> directly to the model provider with minimal validation. Incorrect settings
-> (e.g., incompatible parameter combinations) may result in runtime errors from
-> the API.
-
-## 1. System Overview
-
-The Model Configuration system (`ModelConfigService`) enables deterministic
-control over model generation. It decouples the requested model identifier
-(e.g., a CLI flag or agent request) from the underlying API configuration. This
-allows for:
-
-- **Precise Hyperparameter Tuning**: Direct control over `temperature`, `topP`,
-  `thinkingBudget`, and other SDK-level parameters.
-- **Environment-Specific Behavior**: Distinct configurations for different
-  operating contexts (e.g., testing vs. production).
-- **Agent-Scoped Customization**: Applying specific settings only when a
-  particular agent is active.
-
-The system operates on two core primitives: **Aliases** and **Overrides**.
-
-## 2. Configuration Primitives
-
-These settings are located under the `modelConfigs` key in your configuration
-file.
-
-### Aliases (`customAliases`)
-
-Aliases are named, reusable configuration presets. Users should define their own
-aliases (or override system defaults) in the `customAliases` map.
-
-- **Inheritance**: An alias can `extends` another alias (including system
-  defaults like `chat-base`), inheriting its `modelConfig`. Child aliases can
-  overwrite or augment inherited settings.
-- **Abstract Aliases**: An alias is not required to specify a concrete `model`
-  if it serves purely as a base for other aliases.
-
-**Example Hierarchy**:
-
-```json
-"modelConfigs": {
-  "customAliases": {
-    "base": {
-      "modelConfig": {
-        "generateContentConfig": { "temperature": 0.0 }
-      }
-    },
-    "chat-base": {
-      "extends": "base",
-      "modelConfig": {
-        "generateContentConfig": { "temperature": 0.7 }
-      }
-    }
-  }
-}
-```
-
-### Overrides (`overrides`)
-
-Overrides are conditional rules that inject configuration based on the runtime
-context. They are evaluated dynamically for each model request.
-
-- **Match Criteria**: Overrides apply when the request context matches the
-  specified `match` properties.
-  - `model`: Matches the requested model name or alias.
-  - `overrideScope`: Matches the distinct scope of the request (typically the
-    agent name, e.g., `codebaseInvestigator`).
-
-**Example Override**:
-
-```json
-"modelConfigs": {
-  "overrides": [
-    {
-      "match": {
-        "overrideScope": "codebaseInvestigator"
-      },
-      "modelConfig": {
-        "generateContentConfig": { "temperature": 0.1 }
-      }
-    }
-  ]
-}
-```
-
-## 3. Resolution Strategy
-
-The `ModelConfigService` resolves the final configuration through a two-step
-process:
-
-### Step 1: Alias Resolution
-
-The requested model string is looked up in the merged map of system `aliases`
-and user `customAliases`.
-
-1.  If found, the system recursively resolves the `extends` chain.
-2.  Settings are merged from parent to child (child wins).
-3.  This results in a base `ResolvedModelConfig`.
-4.  If not found, the requested string is treated as the raw model name.
-
-### Step 2: Override Application
-
-The system evaluates the `overrides` list against the request context (`model`
-and `overrideScope`).
-
-1.  **Filtering**: All matching overrides are identified.
-2.  **Sorting**: Matches are prioritized by **specificity** (the number of
-    matched keys in the `match` object).
-    - Specific matches (e.g., `model` + `overrideScope`) override broad matches
-      (e.g., `model` only).
-    - Tie-breaking: If specificity is equal, the order of definition in the
-      `overrides` array is preserved (last one wins).
-3.  **Merging**: The configurations from the sorted overrides are merged
-    sequentially onto the base configuration.
-
-## 4. Configuration Reference
-
-The configuration follows the `ModelConfigServiceConfig` interface.
-
-### `ModelConfig` Object
-
-Defines the actual parameters for the model.
-
-| Property                | Type     | Description                                                        |
-| :---------------------- | :------- | :----------------------------------------------------------------- |
-| `model`                 | `string` | The identifier of the model to be called (e.g., `gemini-2.5-pro`). |
-| `generateContentConfig` | `object` | The configuration object passed to the `@google/genai` SDK.        |
-
-### `GenerateContentConfig` (Common Parameters)
-
-Directly maps to the SDK's `GenerateContentConfig`. Common parameters include:
-
-- **`temperature`**: (`number`) Controls output randomness. Lower values (0.0)
-  are deterministic; higher values (>0.7) are creative.
-- **`topP`**: (`number`) Nucleus sampling probability.
-- **`maxOutputTokens`**: (`number`) Limit on generated response length.
-- **`thinkingConfig`**: (`object`) Configuration for models with reasoning
-  capabilities (e.g., `thinkingBudget`, `includeThoughts`).
-
-## 5. Practical Examples
-
-### Defining a Deterministic Baseline
-
-Create an alias for tasks requiring high precision, extending the standard chat
-configuration but enforcing zero temperature.
-
-```json
-"modelConfigs": {
-  "customAliases": {
-    "precise-mode": {
-      "extends": "chat-base",
-      "modelConfig": {
-        "generateContentConfig": {
-          "temperature": 0.0,
-          "topP": 1.0
-        }
-      }
-    }
-  }
-}
-```
-
-### Agent-Specific Parameter Injection
-
-Enforce extended thinking budgets for a specific agent without altering the
-global default, e.g. for the `codebaseInvestigator`.
-
-```json
-"modelConfigs": {
-  "overrides": [
-    {
-      "match": {
-        "overrideScope": "codebaseInvestigator"
-      },
-      "modelConfig": {
-        "generateContentConfig": {
-          "thinkingConfig": { "thinkingBudget": 4096 }
-        }
-      }
-    }
-  ]
-}
-```
-
-### Experimental Model Evaluation
-
-Route traffic for a specific alias to a preview model for A/B testing, without
-changing client code.
-
-```json
-"modelConfigs": {
-  "overrides": [
-    {
-      "match": {
-        "model": "gemini-2.5-pro"
-      },
-      "modelConfig": {
-        "model": "gemini-2.5-pro-experimental-001"
-      }
-    }
-  ]
-}
-```

docs/cli/headless.md

@@ -1,4 +1,4 @@
-# Headless mode
+# Headless Mode
 
 Headless mode allows you to run Gemini CLI programmatically from command line
 scripts and automation tools without any interactive UI. This is ideal for
@@ -45,9 +45,9 @@ The headless mode provides a headless interface to Gemini CLI that:
 - Enables automation and scripting workflows
 - Provides consistent exit codes for error handling
 
-## Basic usage
+## Basic Usage
 
-### Direct prompts
+### Direct Prompts
 
 Use the `--prompt` (or `-p`) flag to run in headless mode:
 
@@ -55,7 +55,7 @@ Use the `--prompt` (or `-p`) flag to run in headless mode:
 gemini --prompt "What is machine learning?"
 ```
 
-### Stdin input
+### Stdin Input
 
 Pipe input to Gemini CLI from your terminal:
 
@@ -63,7 +63,7 @@ Pipe input to Gemini CLI from your terminal:
 echo "Explain this code" | gemini
 ```
 
-### Combining with file input
+### Combining with File Input
 
 Read from files and process with Gemini:
 
@@ -71,9 +71,9 @@ Read from files and process with Gemini:
 cat README.md | gemini --prompt "Summarize this documentation"
 ```
 
-## Output formats
+## Output Formats
 
-### Text output (default)
+### Text Output (Default)
 
 Standard human-readable output:
 
@@ -87,12 +87,12 @@ Response format:
 The capital of France is Paris.
 ```
 
-### JSON output
+### JSON Output
 
 Returns structured data including response, statistics, and metadata. This
 format is ideal for programmatic processing and automation scripts.
 
-#### Response schema
+#### Response Schema
 
 The JSON output follows this high-level structure:
 
@@ -140,7 +140,7 @@ The JSON output follows this high-level structure:
 }
 ```
 
-#### Example usage
+#### Example Usage
 
 ```bash
 gemini -p "What is the capital of France?" --output-format json
@@ -218,14 +218,14 @@ Response:
 }
 ```
 
-### Streaming JSON output
+### Streaming JSON Output
 
 Returns real-time events as newline-delimited JSON (JSONL). Each significant
 action (initialization, messages, tool calls, results) emits immediately as it
 occurs. This format is ideal for monitoring long-running operations, building
 UIs with live progress, and creating automation pipelines that react to events.
 
-#### When to use streaming JSON
+#### When to Use Streaming JSON
 
 Use `--output-format stream-json` when you need:
 
@@ -237,7 +237,7 @@ Use `--output-format stream-json` when you need:
   timestamps
 - **Pipeline integration** - Stream events to logging/monitoring systems
 
-#### Event types
+#### Event Types
 
 The streaming format emits 6 event types:
 
@@ -248,7 +248,7 @@ The streaming format emits 6 event types:
 5. **`error`** - Non-fatal errors and warnings
 6. **`result`** - Final session outcome with aggregated stats
 
-#### Basic usage
+#### Basic Usage
 
 ```bash
 # Stream events to console
@@ -261,7 +261,7 @@ gemini --output-format stream-json --prompt "Analyze this code" > events.jsonl
 gemini --output-format stream-json --prompt "List files" | jq -r '.type'
 ```
 
-#### Example output
+#### Example Output
 
 Each line is a complete JSON event:
 
@@ -274,7 +274,7 @@ Each line is a complete JSON event:
 {"type":"result","status":"success","stats":{"total_tokens":250,"input_tokens":50,"output_tokens":200,"duration_ms":3000,"tool_calls":1},"timestamp":"2025-10-10T12:00:05.000Z"}
 ```
 
-### File redirection
+### File Redirection
 
 Save output to files or pipe to other commands:
 
@@ -292,7 +292,7 @@ gemini -p "Explain microservices" | wc -w
 gemini -p "List programming languages" | grep -i "python"
 ```
 
-## Configuration options
+## Configuration Options
 
 Key command-line options for headless usage:
 

docs/cli/index.md

@@ -7,17 +7,14 @@ overview of Gemini CLI, see the [main documentation page](../index.md).
 ## Basic features
 
 - **[Commands](./commands.md):** A reference for all built-in slash commands
-- **[Custom commands](./custom-commands.md):** Create your own commands and
+  (e.g., `/help`, `/chat`, `/tools`).
+- **[Custom Commands](./custom-commands.md):** Create your own commands and
   shortcuts for frequently used prompts.
-- **[Headless mode](./headless.md):** Use Gemini CLI programmatically for
+- **[Headless Mode](./headless.md):** Use Gemini CLI programmatically for
   scripting and automation.
-- **[Model selection](./model.md):** Configure the Gemini AI model used by the
-  CLI.
-- **[Settings](./settings.md):** Configure various aspects of the CLI's behavior
-  and appearance.
 - **[Themes](./themes.md):** Customizing the CLI's appearance with different
   themes.
-- **[Keyboard shortcuts](./keyboard-shortcuts.md):** A reference for all
+- **[Keyboard Shortcuts](./keyboard-shortcuts.md):** A reference for all
   keyboard shortcuts to improve your workflow.
 - **[Tutorials](./tutorials.md):** Step-by-step guides for common tasks.
 
@@ -25,21 +22,19 @@ overview of Gemini CLI, see the [main documentation page](../index.md).
 
 - **[Checkpointing](./checkpointing.md):** Automatically save and restore
   snapshots of your session and files.
-- **[Enterprise configuration](./enterprise.md):** Deploying and manage Gemini
+- **[Enterprise Configuration](./enterprise.md):** Deploying and manage Gemini
   CLI in an enterprise environment.
 - **[Sandboxing](./sandbox.md):** Isolate tool execution in a secure,
   containerized environment.
 - **[Telemetry](./telemetry.md):** Configure observability to monitor usage and
   performance.
-- **[Token caching](./token-caching.md):** Optimize API costs by caching tokens.
-- **[Trusted folders](./trusted-folders.md):** A security feature to control
+- **[Token Caching](./token-caching.md):** Optimize API costs by caching tokens.
+- **[Trusted Folders](./trusted-folders.md):** A security feature to control
   which projects can use the full capabilities of the CLI.
-- **[Ignoring files (.geminiignore)](./gemini-ignore.md):** Exclude specific
+- **[Ignoring Files (.geminiignore)](./gemini-ignore.md):** Exclude specific
   files and directories from being accessed by tools.
-- **[Context files (GEMINI.md)](./gemini-md.md):** Provide persistent,
+- **[Context Files (GEMINI.md)](./gemini-md.md):** Provide persistent,
   hierarchical context to the model.
-- **[System prompt override](./system-prompt.md):** Replace the built‑in system
-  instructions using `GEMINI_SYSTEM_MD`.
 
 ## Non-interactive mode
 
@@ -60,4 +55,4 @@ gemini -p "What is fine tuning?"
 ```
 
 For comprehensive documentation on headless usage, scripting, automation, and
-advanced examples, see the **[Headless mode](./headless.md)** guide.
+advanced examples, see the **[Headless Mode](./headless.md)** guide.

docs/cli/keyboard-shortcuts.md

@@ -1,143 +1,68 @@
-# Gemini CLI keyboard shortcuts
+# Gemini CLI Keyboard Shortcuts
 
-Gemini CLI ships with a set of default keyboard shortcuts for editing input,
-navigating history, and controlling the UI. Use this reference to learn the
-available combinations.
+This document lists the available keyboard shortcuts in the Gemini CLI.
 
-<!-- KEYBINDINGS-AUTOGEN:START -->
+## General
 
-#### Basic Controls
+| Shortcut | Description                                                                                                           |
+| -------- | --------------------------------------------------------------------------------------------------------------------- |
+| `Esc`    | Close dialogs and suggestions.                                                                                        |
+| `Ctrl+C` | Cancel the ongoing request and clear the input. Press twice to exit the application.                                  |
+| `Ctrl+D` | Exit the application if the input is empty. Press twice to confirm.                                                   |
+| `Ctrl+L` | Clear the screen.                                                                                                     |
+| `Ctrl+O` | Toggle the display of the debug console.                                                                              |
+| `Ctrl+S` | Allows long responses to print fully, disabling truncation. Use your terminal's scrollback to view the entire output. |
+| `Ctrl+Y` | Toggle auto-approval (YOLO mode) for all tool calls.                                                                  |
 
-| Action                                       | Keys    |
-| -------------------------------------------- | ------- |
-| Confirm the current selection or choice.     | `Enter` |
-| Dismiss dialogs or cancel the current focus. | `Esc`   |
+## Input Prompt
 
-#### Cursor Movement
+| Shortcut                                           | Description                                                                                                                         |
+| -------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
+| `!`                                                | Toggle shell mode when the input is empty.                                                                                          |
+| `\` (at end of line) + `Enter`                     | Insert a newline.                                                                                                                   |
+| `Down Arrow`                                       | Navigate down through the input history.                                                                                            |
+| `Enter`                                            | Submit the current prompt.                                                                                                          |
+| `Meta+Delete` / `Ctrl+Delete`                      | Delete the word to the right of the cursor.                                                                                         |
+| `Tab`                                              | Autocomplete the current suggestion if one exists.                                                                                  |
+| `Up Arrow`                                         | Navigate up through the input history.                                                                                              |
+| `Ctrl+A` / `Home`                                  | Move the cursor to the beginning of the line.                                                                                       |
+| `Ctrl+B` / `Left Arrow`                            | Move the cursor one character to the left.                                                                                          |
+| `Ctrl+C`                                           | Clear the input prompt                                                                                                              |
+| `Esc` (double press)                               | Clear the input prompt.                                                                                                             |
+| `Ctrl+D` / `Delete`                                | Delete the character to the right of the cursor.                                                                                    |
+| `Ctrl+E` / `End`                                   | Move the cursor to the end of the line.                                                                                             |
+| `Ctrl+F` / `Right Arrow`                           | Move the cursor one character to the right.                                                                                         |
+| `Ctrl+H` / `Backspace`                             | Delete the character to the left of the cursor.                                                                                     |
+| `Ctrl+K`                                           | Delete from the cursor to the end of the line.                                                                                      |
+| `Ctrl+Left Arrow` / `Meta+Left Arrow` / `Meta+B`   | Move the cursor one word to the left.                                                                                               |
+| `Ctrl+N`                                           | Navigate down through the input history.                                                                                            |
+| `Ctrl+P`                                           | Navigate up through the input history.                                                                                              |
+| `Ctrl+Right Arrow` / `Meta+Right Arrow` / `Meta+F` | Move the cursor one word to the right.                                                                                              |
+| `Ctrl+U`                                           | Delete from the cursor to the beginning of the line.                                                                                |
+| `Ctrl+V`                                           | Paste clipboard content. If the clipboard contains an image, it will be saved and a reference to it will be inserted in the prompt. |
+| `Ctrl+W` / `Meta+Backspace` / `Ctrl+Backspace`     | Delete the word to the left of the cursor.                                                                                          |
+| `Ctrl+X` / `Meta+Enter`                            | Open the current input in an external editor.                                                                                       |
 
-| Action                                    | Keys                   |
-| ----------------------------------------- | ---------------------- |
-| Move the cursor to the start of the line. | `Ctrl + A`<br />`Home` |
-| Move the cursor to the end of the line.   | `Ctrl + E`<br />`End`  |
+## Suggestions
 
-#### Editing
+| Shortcut        | Description                            |
+| --------------- | -------------------------------------- |
+| `Down Arrow`    | Navigate down through the suggestions. |
+| `Tab` / `Enter` | Accept the selected suggestion.        |
+| `Up Arrow`      | Navigate up through the suggestions.   |
 
-| Action                                           | Keys                                      |
-| ------------------------------------------------ | ----------------------------------------- |
-| Delete from the cursor to the end of the line.   | `Ctrl + K`                                |
-| Delete from the cursor to the start of the line. | `Ctrl + U`                                |
-| Clear all text in the input field.               | `Ctrl + C`                                |
-| Delete the previous word.                        | `Ctrl + Backspace`<br />`Cmd + Backspace` |
+## Radio Button Select
 
-#### Screen Control
+| Shortcut           | Description                                                                                                   |
+| ------------------ | ------------------------------------------------------------------------------------------------------------- |
+| `Down Arrow` / `j` | Move selection down.                                                                                          |
+| `Enter`            | Confirm selection.                                                                                            |
+| `Up Arrow` / `k`   | Move selection up.                                                                                            |
+| `1-9`              | Select an item by its number.                                                                                 |
+| (multi-digit)      | For items with numbers greater than 9, press the digits in quick succession to select the corresponding item. |
 
-| Action                                       | Keys       |
-| -------------------------------------------- | ---------- |
-| Clear the terminal screen and redraw the UI. | `Ctrl + L` |
+## IDE Integration
 
-#### Scrolling
-
-| Action                   | Keys                 |
-| ------------------------ | -------------------- |
-| Scroll content up.       | `Shift + Up Arrow`   |
-| Scroll content down.     | `Shift + Down Arrow` |
-| Scroll to the top.       | `Home`               |
-| Scroll to the bottom.    | `End`                |
-| Scroll up by one page.   | `Page Up`            |
-| Scroll down by one page. | `Page Down`          |
-
-#### History & Search
-
-| Action                                       | Keys                  |
-| -------------------------------------------- | --------------------- |
-| Show the previous entry in history.          | `Ctrl + P (no Shift)` |
-| Show the next entry in history.              | `Ctrl + N (no Shift)` |
-| Start reverse search through history.        | `Ctrl + R`            |
-| Insert the selected reverse-search match.    | `Enter (no Ctrl)`     |
-| Accept a suggestion while reverse searching. | `Tab`                 |
-
-#### Navigation
-
-| Action                           | Keys                                        |
-| -------------------------------- | ------------------------------------------- |
-| Move selection up in lists.      | `Up Arrow (no Shift)`                       |
-| Move selection down in lists.    | `Down Arrow (no Shift)`                     |
-| Move up within dialog options.   | `Up Arrow (no Shift)`<br />`K (no Shift)`   |
-| Move down within dialog options. | `Down Arrow (no Shift)`<br />`J (no Shift)` |
-
-#### Suggestions & Completions
-
-| Action                                  | Keys                                               |
-| --------------------------------------- | -------------------------------------------------- |
-| Accept the inline suggestion.           | `Tab`<br />`Enter (no Ctrl)`                       |
-| Move to the previous completion option. | `Up Arrow (no Shift)`<br />`Ctrl + P (no Shift)`   |
-| Move to the next completion option.     | `Down Arrow (no Shift)`<br />`Ctrl + N (no Shift)` |
-| Expand an inline suggestion.            | `Right Arrow`                                      |
-| Collapse an inline suggestion.          | `Left Arrow`                                       |
-
-#### Text Input
-
-| Action                               | Keys                                                                                        |
-| ------------------------------------ | ------------------------------------------------------------------------------------------- |
-| Submit the current prompt.           | `Enter (no Ctrl, no Shift, no Cmd, not Paste)`                                              |
-| Insert a newline without submitting. | `Ctrl + Enter`<br />`Cmd + Enter`<br />`Paste + Enter`<br />`Shift + Enter`<br />`Ctrl + J` |
-
-#### External Tools
-
-| Action                                         | Keys                      |
-| ---------------------------------------------- | ------------------------- |
-| Open the current prompt in an external editor. | `Ctrl + X`                |
-| Paste from the clipboard.                      | `Ctrl + V`<br />`Cmd + V` |
-
-#### App Controls
-
-| Action                                                            | Keys       |
-| ----------------------------------------------------------------- | ---------- |
-| Toggle detailed error information.                                | `F12`      |
-| Toggle the full TODO list.                                        | `Ctrl + T` |
-| Toggle IDE context details.                                       | `Ctrl + G` |
-| Toggle Markdown rendering.                                        | `Cmd + M`  |
-| Toggle copy mode when the terminal is using the alternate buffer. | `Ctrl + S` |
-| Expand a height-constrained response to show additional lines.    | `Ctrl + S` |
-| Toggle focus between the shell and Gemini input.                  | `Ctrl + F` |
-
-#### Session Control
-
-| Action                                       | Keys       |
-| -------------------------------------------- | ---------- |
-| Cancel the current request or quit the CLI.  | `Ctrl + C` |
-| Exit the CLI when the input buffer is empty. | `Ctrl + D` |
-
-<!-- KEYBINDINGS-AUTOGEN:END -->
-
-## Additional context-specific shortcuts
-
-- `Ctrl+Y`: Toggle YOLO (auto-approval) mode for tool calls.
-- `Shift+Tab`: Toggle Auto Edit (auto-accept edits) mode.
-- `Option+M` (macOS): Entering `µ` with Option+M also toggles Markdown
-  rendering, matching `Cmd+M`.
-- `!` on an empty prompt: Enter or exit shell mode.
-- `\` (at end of a line) + `Enter`: Insert a newline without leaving single-line
-  mode.
-- `Ctrl+Delete` / `Meta+Delete`: Delete the word to the right of the cursor.
-- `Ctrl+B` or `Left Arrow`: Move the cursor one character to the left while
-  editing text.
-- `Ctrl+F` or `Right Arrow`: Move the cursor one character to the right; with an
-  embedded shell attached, `Ctrl+F` still toggles focus.
-- `Ctrl+D` or `Delete`: Remove the character immediately to the right of the
-  cursor.
-- `Ctrl+H` or `Backspace`: Remove the character immediately to the left of the
-  cursor.
-- `Ctrl+Left Arrow` / `Meta+Left Arrow` / `Meta+B`: Move one word to the left.
-- `Ctrl+Right Arrow` / `Meta+Right Arrow` / `Meta+F`: Move one word to the
-  right.
-- `Ctrl+W`: Delete the word to the left of the cursor (in addition to
-  `Ctrl+Backspace` / `Cmd+Backspace`).
-- `Ctrl+Z` / `Ctrl+Shift+Z`: Undo or redo the most recent text edit.
-- `Meta+Enter`: Open the current input in an external editor (alias for
-  `Ctrl+X`).
-- `Esc` pressed twice quickly: Clear the current input buffer.
-- `Up Arrow` / `Down Arrow`: When the cursor is at the top or bottom of a
-  single-line input, navigate backward or forward through prompt history.
-- `Number keys (1-9, multi-digit)` inside selection dialogs: Jump directly to
-  the numbered radio option and confirm when the full number is entered.
+| Shortcut | Description                       |
+| -------- | --------------------------------- |
+| `Ctrl+G` | See context CLI received from IDE |

docs/cli/model-routing.md

@@ -1,37 +0,0 @@
-## Model routing
-
-Gemini CLI includes a model routing feature that automatically switches to a
-fallback model in case of a model failure. This feature is enabled by default
-and provides resilience when the primary model is unavailable.
-
-## How it works
-
-Model routing is managed by the `ModelAvailabilityService`, which monitors model
-health and automatically routes requests to available models based on defined
-policies.
-
-1.  **Model failure:** If the currently selected model fails (e.g., due to quota
-    or server errors), the CLI will iniate the fallback process.
-
-2.  **User consent:** Depending on the failure and the model's policy, the CLI
-    may prompt you to switch to a fallback model (by default always prompts
-    you).
-
-3.  **Model switch:** If approved, or if the policy allows for silent fallback,
-    the CLI will use an available fallback model for the current turn or the
-    remainder of the session.
-
-### Model selection precedence
-
-The model used by Gemini CLI is determined by the following order of precedence:
-
-1.  **`--model` command-line flag:** A model specified with the `--model` flag
-    when launching the CLI will always be used.
-2.  **`GEMINI_MODEL` environment variable:** If the `--model` flag is not used,
-    the CLI will use the model specified in the `GEMINI_MODEL` environment
-    variable.
-3.  **`model.name` in `settings.json`:** If neither of the above are set, the
-    model specified in the `model.name` property of your `settings.json` file
-    will be used.
-4.  **Default model:** If none of the above are set, the default model will be
-    used. The default model is `auto`

docs/cli/model.md

@@ -1,62 +0,0 @@
-# Gemini CLI model selection (`/model` command)
-
-Select your Gemini CLI model. The `/model` command lets you configure the model
-used by Gemini CLI, giving you more control over your results. Use **Pro**
-models for complex tasks and reasoning, **Flash** models for high speed results,
-or the (recommended) **Auto** setting to choose the best model for your tasks.
-
-> **Note:** The `/model` command (and the `--model` flag) does not override the
-> model used by sub-agents. Consequently, even when using the `/model` flag you
-> may see other models used in your model usage reports.
-
-## How to use the `/model` command
-
-Use the following command in Gemini CLI:
-
-```
-/model
-```
-
-Running this command will open a dialog with your options:
-
-| Option            | Description                                                    | Models                                                                 |
-| ----------------- | -------------------------------------------------------------- | ---------------------------------------------------------------------- |
-| Auto (Gemini 3)   | Let the system choose the best Gemini 3 model for your task.   | gemini-3-pro-preview (if enabled), gemini-3-flash-preview (if enabled) |
-| Auto (Gemini 2.5) | Let the system choose the best Gemini 2.5 model for your task. | gemini-2.5-pro, gemini-2.5-flash                                       |
-| Manual            | Select a specific model.                                       | Any available model.                                                   |
-
-We recommend selecting one of the above **Auto** options. However, you can
-select **Manual** to select a specific model from those available.
-
-### Gemini 3 and preview features
-
-> **Note:** Gemini 3 is not currently available on all account types. To learn
-> more about Gemini 3 access, refer to
-> [Gemini 3 on Gemini CLI](../get-started/gemini-3.md).
-
-To enable Gemini 3 Pro and Gemini 3 Flash (if available), enable
-[**Preview Features** by using the `settings` command](../cli/settings.md).
-
-You can also use the `--model` flag to specify a particular Gemini model on
-startup. For more details, refer to the
-[configuration documentation](./configuration.md).
-
-Changes to these settings will be applied to all subsequent interactions with
-Gemini CLI.
-
-## Best practices for model selection
-
-- **Default to Auto.** For most users, the _Auto_ option model provides a
-  balance between speed and performance, automatically selecting the correct
-  model based on the complexity of the task. Example: Developing a web
-  application could include a mix of complex tasks (building architecture and
-  scaffolding the project) and simple tasks (generating CSS).
-
-- **Switch to Pro if you aren't getting the results you want.** If you think you
-  need your model to be a little "smarter," you can manually select Pro. Pro
-  will provide you with the highest levels of reasoning and creativity. Example:
-  A complex or multi-stage debugging task.
-
-- **Switch to Flash or Flash-Lite if you need faster results.** If you need a
-  simple response quickly, Flash or Flash-Lite is the best option. Example:
-  Converting a JSON object to a YAML string.

docs/cli/sandbox.md

@@ -87,7 +87,7 @@ Built-in profiles (set via `SEATBELT_PROFILE` env var):
 - `restrictive-open`: Strict restrictions, network allowed
 - `restrictive-closed`: Maximum restrictions
 
-### Custom sandbox flags
+### Custom Sandbox Flags
 
 For container-based sandboxing, you can inject custom flags into the `docker` or
 `podman` command using the `SANDBOX_FLAGS` environment variable. This is useful

docs/cli/session-management.md

@@ -1,158 +0,0 @@
-# Session Management
-
-Gemini CLI includes robust session management features that automatically save
-your conversation history. This allows you to interrupt your work and resume
-exactly where you left off, review past interactions, and manage your
-conversation history effectively.
-
-## Automatic Saving
-
-Every time you interact with Gemini CLI, your session is automatically saved.
-This happens in the background without any manual intervention.
-
-- **What is saved:** The complete conversation history, including:
-  - Your prompts and the model's responses.
-  - All tool executions (inputs and outputs).
-  - Token usage statistics (input/output/cached, etc.).
-  - Assistant thoughts/reasoning summaries (when available).
-- **Location:** Sessions are stored in `~/.gemini/tmp/<project_hash>/chats/`.
-- **Scope:** Sessions are project-specific. Switching directories to a different
-  project will switch to that project's session history.
-
-## Resuming Sessions
-
-You can resume a previous session to continue the conversation with all prior
-context restored.
-
-### From the Command Line
-
-When starting the CLI, you can use the `--resume` (or `-r`) flag:
-
-- **Resume latest:**
-
-  ```bash
-  gemini --resume
-  ```
-
-  This immediately loads the most recent session.
-
-- **Resume by index:** First, list available sessions (see
-  [Listing Sessions](#listing-sessions)), then use the index number:
-
-  ```bash
-  gemini --resume 1
-  ```
-
-- **Resume by ID:** You can also provide the full session UUID:
-  ```bash
-  gemini --resume a1b2c3d4-e5f6-7890-abcd-ef1234567890
-  ```
-
-### From the Interactive Interface
-
-While the CLI is running, you can use the `/resume` slash command to open the
-**Session Browser**:
-
-```text
-/resume
-```
-
-This opens an interactive interface where you can:
-
-- **Browse:** Scroll through a list of your past sessions.
-- **Preview:** See details like the session date, message count, and the first
-  user prompt.
-- **Search:** Press `/` to enter search mode, then type to filter sessions by ID
-  or content.
-- **Select:** Press `Enter` to resume the selected session.
-
-## Managing Sessions
-
-### Listing Sessions
-
-To see a list of all available sessions for the current project from the command
-line:
-
-```bash
-gemini --list-sessions
-```
-
-Output example:
-
-```text
-Available sessions for this project (3):
-
-  1. Fix bug in auth (2 days ago) [a1b2c3d4]
-  2. Refactor database schema (5 hours ago) [e5f67890]
-  3. Update documentation (Just now) [abcd1234]
-```
-
-### Deleting Sessions
-
-You can remove old or unwanted sessions to free up space or declutter your
-history.
-
-**From the Command Line:** Use the `--delete-session` flag with an index or ID:
-
-```bash
-gemini --delete-session 2
-```
-
-**From the Session Browser:**
-
-1.  Open the browser with `/resume`.
-2.  Navigate to the session you want to remove.
-3.  Press `x`.
-
-## Configuration
-
-You can configure how Gemini CLI manages your session history in your
-`settings.json` file.
-
-### Session Retention
-
-To prevent your history from growing indefinitely, you can enable automatic
-cleanup policies.
-
-```json
-{
-  "general": {
-    "sessionRetention": {
-      "enabled": true,
-      "maxAge": "30d", // Keep sessions for 30 days
-      "maxCount": 50 // Keep the 50 most recent sessions
-    }
-  }
-}
-```
-
-- **`enabled`**: (boolean) Master switch for session cleanup. Default is
-  `false`.
-- **`maxAge`**: (string) Duration to keep sessions (e.g., "24h", "7d", "4w").
-  Sessions older than this will be deleted.
-- **`maxCount`**: (number) Maximum number of sessions to retain. The oldest
-  sessions exceeding this count will be deleted.
-- **`minRetention`**: (string) Minimum retention period (safety limit). Defaults
-  to `"1d"`; sessions newer than this period are never deleted by automatic
-  cleanup.
-
-### Session Limits
-
-You can also limit the length of individual sessions to prevent context windows
-from becoming too large and expensive.
-
-```json
-{
-  "model": {
-    "maxSessionTurns": 100
-  }
-}
-```
-
-- **`maxSessionTurns`**: (number) The maximum number of turns (user + model
-  exchanges) allowed in a single session. Set to `-1` for unlimited (default).
-
-  **Behavior when limit is reached:**
-  - **Interactive Mode:** The CLI shows an informational message and stops
-    sending requests to the model. You must manually start a new session.
-  - **Non-Interactive Mode:** The CLI exits with an error.

docs/cli/settings.md

@@ -1,114 +0,0 @@
-# Gemini CLI settings (`/settings` command)
-
-Control your Gemini CLI experience with the `/settings` command. The `/settings`
-command opens a dialog to view and edit all your Gemini CLI settings, including
-your UI experience, keybindings, and accessibility features.
-
-Your Gemini CLI settings are stored in a `settings.json` file. In addition to
-using the `/settings` command, you can also edit them in one of the following
-locations:
-
-- **User settings**: `~/.gemini/settings.json`
-- **Workspace settings**: `your-project/.gemini/settings.json`
-
-Note: Workspace settings override user settings.
-
-## Settings reference
-
-Here is a list of all the available settings, grouped by category and ordered as
-they appear in the UI.
-
-### General
-
-| UI Label                        | Setting                            | Description                                                                  | Default     |
-| ------------------------------- | ---------------------------------- | ---------------------------------------------------------------------------- | ----------- |
-| Preview Features (e.g., models) | `general.previewFeatures`          | Enable preview features (e.g., preview models).                              | `false`     |
-| Vim Mode                        | `general.vimMode`                  | Enable Vim keybindings.                                                      | `false`     |
-| Disable Auto Update             | `general.disableAutoUpdate`        | Disable automatic updates.                                                   | `false`     |
-| Enable Prompt Completion        | `general.enablePromptCompletion`   | Enable AI-powered prompt completion suggestions while typing.                | `false`     |
-| Debug Keystroke Logging         | `general.debugKeystrokeLogging`    | Enable debug logging of keystrokes to the console.                           | `false`     |
-| Session Retention               | `general.sessionRetention`         | Settings for automatic session cleanup. This feature is disabled by default. | `undefined` |
-| Enable Session Cleanup          | `general.sessionRetention.enabled` | Enable automatic session cleanup.                                            | `false`     |
-
-### Output
-
-| UI Label      | Setting         | Description                                            | Default |
-| ------------- | --------------- | ------------------------------------------------------ | ------- |
-| Output Format | `output.format` | The format of the CLI output. Can be `text` or `json`. | `text`  |
-
-### UI
-
-| UI Label                       | Setting                                  | Description                                                          | Default |
-| ------------------------------ | ---------------------------------------- | -------------------------------------------------------------------- | ------- |
-| Hide Window Title              | `ui.hideWindowTitle`                     | Hide the window title bar.                                           | `false` |
-| Show Status in Title           | `ui.showStatusInTitle`                   | Show Gemini CLI status and thoughts in the terminal window title.    | `false` |
-| Hide Tips                      | `ui.hideTips`                            | Hide helpful tips in the UI.                                         | `false` |
-| Hide Banner                    | `ui.hideBanner`                          | Hide the application banner.                                         | `false` |
-| Hide Context Summary           | `ui.hideContextSummary`                  | Hide the context summary (GEMINI.md, MCP servers) above the input.   | `false` |
-| Hide CWD                       | `ui.footer.hideCWD`                      | Hide the current working directory path in the footer.               | `false` |
-| Hide Sandbox Status            | `ui.footer.hideSandboxStatus`            | Hide the sandbox status indicator in the footer.                     | `false` |
-| Hide Model Info                | `ui.footer.hideModelInfo`                | Hide the model name and context usage in the footer.                 | `false` |
-| Hide Context Window Percentage | `ui.footer.hideContextPercentage`        | Hides the context window remaining percentage.                       | `true`  |
-| Hide Footer                    | `ui.hideFooter`                          | Hide the footer from the UI.                                         | `false` |
-| Show Memory Usage              | `ui.showMemoryUsage`                     | Display memory usage information in the UI.                          | `false` |
-| Show Line Numbers              | `ui.showLineNumbers`                     | Show line numbers in the chat.                                       | `false` |
-| Show Citations                 | `ui.showCitations`                       | Show citations for generated text in the chat.                       | `false` |
-| Use Full Width                 | `ui.useFullWidth`                        | Use the entire width of the terminal for output.                     | `true`  |
-| Use Alternate Screen Buffer    | `ui.useAlternateBuffer`                  | Use an alternate screen buffer for the UI, preserving shell history. | `true`  |
-| Disable Loading Phrases        | `ui.accessibility.disableLoadingPhrases` | Disable loading phrases for accessibility.                           | `false` |
-| Screen Reader Mode             | `ui.accessibility.screenReader`          | Render output in plain-text to be more screen reader accessible.     | `false` |
-
-### IDE
-
-| UI Label | Setting       | Description                  | Default |
-| -------- | ------------- | ---------------------------- | ------- |
-| IDE Mode | `ide.enabled` | Enable IDE integration mode. | `false` |
-
-### Model
-
-| UI Label                | Setting                      | Description                                                                            | Default |
-| ----------------------- | ---------------------------- | -------------------------------------------------------------------------------------- | ------- |
-| Max Session Turns       | `model.maxSessionTurns`      | Maximum number of user/model/tool turns to keep in a session. -1 means unlimited.      | `-1`    |
-| Compression Threshold   | `model.compressionThreshold` | The fraction of context usage at which to trigger context compression (e.g. 0.2, 0.3). | `0.2`   |
-| Skip Next Speaker Check | `model.skipNextSpeakerCheck` | Skip the next speaker check.                                                           | `true`  |
-
-### Context
-
-| UI Label                             | Setting                                           | Description                                                                                                                                     | Default |
-| ------------------------------------ | ------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | ------- |
-| Memory Discovery Max Dirs            | `context.discoveryMaxDirs`                        | Maximum number of directories to search for memory.                                                                                             | `200`   |
-| Load Memory From Include Directories | `context.loadMemoryFromIncludeDirectories`        | Controls how /memory refresh loads GEMINI.md files. When true, include directories are scanned; when false, only the current directory is used. | `false` |
-| Respect .gitignore                   | `context.fileFiltering.respectGitIgnore`          | Respect .gitignore files when searching.                                                                                                        | `true`  |
-| Respect .geminiignore                | `context.fileFiltering.respectGeminiIgnore`       | Respect .geminiignore files when searching.                                                                                                     | `true`  |
-| Enable Recursive File Search         | `context.fileFiltering.enableRecursiveFileSearch` | Enable recursive file search functionality when completing @ references in the prompt.                                                          | `true`  |
-| Disable Fuzzy Search                 | `context.fileFiltering.disableFuzzySearch`        | Disable fuzzy search when searching for files.                                                                                                  | `false` |
-
-### Tools
-
-| UI Label                         | Setting                              | Description                                                                                                     | Default |
-| -------------------------------- | ------------------------------------ | --------------------------------------------------------------------------------------------------------------- | ------- |
-| Enable Interactive Shell         | `tools.shell.enableInteractiveShell` | Use node-pty for an interactive shell experience. Fallback to child_process still applies.                      | `true`  |
-| Show Color                       | `tools.shell.showColor`              | Show color in shell output.                                                                                     | `false` |
-| Auto Accept                      | `tools.autoAccept`                   | Automatically accept and execute tool calls that are considered safe (e.g., read-only operations).              | `false` |
-| Use Ripgrep                      | `tools.useRipgrep`                   | Use ripgrep for file content search instead of the fallback implementation. Provides faster search performance. | `true`  |
-| Enable Tool Output Truncation    | `tools.enableToolOutputTruncation`   | Enable truncation of large tool outputs.                                                                        | `true`  |
-| Tool Output Truncation Threshold | `tools.truncateToolOutputThreshold`  | Truncate tool output if it is larger than this many characters. Set to -1 to disable.                           | `10000` |
-| Tool Output Truncation Lines     | `tools.truncateToolOutputLines`      | The number of lines to keep when truncating tool output.                                                        | `100`   |
-
-### Security
-
-| UI Label                      | Setting                                         | Description                                               | Default |
-| ----------------------------- | ----------------------------------------------- | --------------------------------------------------------- | ------- |
-| Disable YOLO Mode             | `security.disableYoloMode`                      | Disable YOLO mode, even if enabled by a flag.             | `false` |
-| Blocks extensions from Git    | `security.blockGitExtensions`                   | Blocks installing and loading extensions from Git.        | `false` |
-| Folder Trust                  | `security.folderTrust.enabled`                  | Setting to track whether Folder trust is enabled.         | `false` |
-| Allowed Environment Variables | `security.environmentVariableRedaction.allowed` | Environment variables to always allow (bypass redaction). | `[]`    |
-| Blocked Environment Variables | `security.environmentVariableRedaction.blocked` | Environment variables to always redact.                   | `[]`    |
-
-### Experimental
-
-| UI Label                            | Setting                                                 | Description                                                  | Default |
-| ----------------------------------- | ------------------------------------------------------- | ------------------------------------------------------------ | ------- |
-| Enable Codebase Investigator        | `experimental.codebaseInvestigatorSettings.enabled`     | Enable the Codebase Investigator agent.                      | `true`  |
-| Codebase Investigator Max Num Turns | `experimental.codebaseInvestigatorSettings.maxNumTurns` | Maximum number of turns for the Codebase Investigator agent. | `10`    |
-| Agent Skills                        | `experimental.skills`                                   | Enable Agent Skills (experimental).                          | `false` |

docs/cli/skills.md

@@ -1,156 +0,0 @@
-# Agent Skills
-
-_Note: This is an experimental feature enabled via `experimental.skills`. You
-can also search for "Skills" within the `/settings` interactive UI to toggle
-this and manage other skill-related settings._
-
-Agent Skills allow you to extend Gemini CLI with specialized expertise,
-procedural workflows, and task-specific resources. Based on the
-[Agent Skills](https://agentskills.io) open standard, a "skill" is a
-self-contained directory that packages instructions and assets into a
-discoverable capability.
-
-## Overview
-
-Unlike general context files ([`GEMINI.md`](./gemini-md.md)), which provide
-persistent project-wide background, Skills represent **on-demand expertise**.
-This allows Gemini to maintain a vast library of specialized capabilities—such
-as security auditing, cloud deployments, or codebase migrations—without
-cluttering the model's immediate context window.
-
-Gemini autonomously decides when to employ a skill based on your request and the
-skill's description. When a relevant skill is identified, the model "pulls in"
-the full instructions and resources required to complete the task using the
-`activate_skill` tool.
-
-## Key Benefits
-
-- **Shared Expertise:** Package complex workflows (like a specific team's PR
-  review process) into a folder that anyone can use.
-- **Repeatable Workflows:** Ensure complex multi-step tasks are performed
-  consistently by providing a procedural framework.
-- **Resource Bundling:** Include scripts, templates, or example data alongside
-  instructions so the agent has everything it needs.
-- **Progressive Disclosure:** Only skill metadata (name and description) is
-  loaded initially. Detailed instructions and resources are only disclosed when
-  the model explicitly activates the skill, saving context tokens.
-
-## Skill Discovery Tiers
-
-Gemini CLI discovers skills from three primary locations:
-
-1.  **Project Skills** (`.gemini/skills/`): Project-specific skills that are
-    typically committed to version control and shared with the team.
-2.  **User Skills** (`~/.gemini/skills/`): Personal skills available across all
-    your projects.
-3.  **Extension Skills**: Skills bundled within installed
-    [extensions](../extensions/index.md).
-
-**Precedence:** If multiple skills share the same name, higher-precedence
-locations override lower ones: **Project > User > Extension**.
-
-## Managing Skills
-
-### In an Interactive Session
-
-Use the `/skills` slash command to view and manage available expertise:
-
-- `/skills list` (default): Shows all discovered skills and their status.
-- `/skills disable <name>`: Prevents a specific skill from being used.
-- `/skills enable <name>`: Re-enables a disabled skill.
-- `/skills reload`: Refreshes the list of discovered skills from all tiers.
-
-_Note: `/skills disable` and `/skills enable` default to the `user` scope. Use
-`--scope project` to manage project-specific settings._
-
-### From the Terminal
-
-The `gemini skills` command provides management utilities:
-
-```bash
-# List all discovered skills
-gemini skills list
-
-# Enable/disable skills. Can use --scope to specify project or user
-gemini skills enable my-expertise
-gemini skills disable my-expertise
-```
-
-## Creating a Skill
-
-A skill is a directory containing a `SKILL.md` file at its root. This file uses
-YAML frontmatter for metadata and Markdown for instructions.
-
-### Basic Structure
-
-```markdown
----
-name: <unique-name>
-description: <what the skill does and when Gemini should use it>
----
-
-<your instructions for how the agent should behave / use the skill>
-```
-
-- **`name`**: A unique identifier (lowercase, alphanumeric, and dashes).
-- **`description`**: The most critical field. Gemini uses this to decide when
-  the skill is relevant. Be specific about the expertise provided.
-- **Body**: Everything below the second `---` is injected as expert procedural
-  guidance for the model.
-
-### Example: Team Code Reviewer
-
-```markdown
----
-name: code-reviewer
-description:
-  Expertise in reviewing code for style, security, and performance. Use when the
-  user asks for "feedback," a "review," or to "check" their changes.
----
-
-# Code Reviewer
-
-You are an expert code reviewer. When reviewing code, follow this workflow:
-
-1.  **Analyze**: Review the staged changes or specific files provided. Ensure
-    that the changes are scoped properly and represent minimal changes required
-    to address the issue.
-2.  **Style**: Ensure code follows the project's conventions and idiomatic
-    patterns as described in the `GEMINI.md` file.
-3.  **Security**: Flag any potential security vulnerabilities.
-4.  **Tests**: Verify that new logic has corresponding test coverage and that
-    the test coverage adequately validates the changes.
-
-Provide your feedback as a concise bulleted list of "Strengths" and
-"Opportunities."
-```
-
-### Resource Conventions
-
-While you can structure your skill directory however you like, the Agent Skills
-standard encourages these conventions:
-
-- **`scripts/`**: Executable scripts (bash, python, node) the agent can run.
-- **`references/`**: Static documentation, schemas, or example data for the
-  agent to consult.
-- **`assets/`**: Code templates, boilerplate, or binary resources.
-
-When a skill is activated, Gemini CLI provides the model with a tree view of the
-entire skill directory, allowing it to discover and utilize these assets.
-
-## How it Works (Security & Privacy)
-
-1.  **Discovery**: At the start of a session, Gemini CLI scans the discovery
-    tiers and injects the name and description of all enabled skills into the
-    system prompt.
-2.  **Activation**: When Gemini identifies a task matching a skill's
-    description, it calls the `activate_skill` tool.
-3.  **Consent**: You will see a confirmation prompt in the UI detailing the
-    skill's name, purpose, and the directory path it will gain access to.
-4.  **Injection**: Upon your approval:
-    - The `SKILL.md` body and folder structure is added to the conversation
-      history.
-    - The skill's directory is added to the agent's allowed file paths, granting
-      it permission to read any bundled assets.
-5.  **Execution**: The model proceeds with the specialized expertise active. It
-    is instructed to prioritize the skill's procedural guidance within reason.

docs/cli/system-prompt.md

@@ -1,93 +0,0 @@
-# System Prompt Override (GEMINI_SYSTEM_MD)
-
-The core system instructions that guide Gemini CLI can be completely replaced
-with your own Markdown file. This feature is controlled via the
-`GEMINI_SYSTEM_MD` environment variable.
-
-## Overview
-
-The `GEMINI_SYSTEM_MD` variable instructs the CLI to use an external Markdown
-file for its system prompt, completely overriding the built-in default. This is
-a full replacement, not a merge. If you use a custom file, none of the original
-core instructions will apply unless you include them yourself.
-
-This feature is intended for advanced users who need to enforce strict,
-project-specific behavior or create a customized persona.
-
-> Tip: You can export the current default system prompt to a file first, review
-> it, and then selectively modify or replace it (see
-> [“Export the default prompt”](#export-the-default-prompt-recommended)).
-
-## How to enable
-
-You can set the environment variable temporarily in your shell, or persist it
-via a `.gemini/.env` file. See
-[Persisting Environment Variables](../get-started/authentication.md#persisting-environment-variables).
-
-- Use the project default path (`.gemini/system.md`):
-  - `GEMINI_SYSTEM_MD=true` or `GEMINI_SYSTEM_MD=1`
-  - The CLI reads `./.gemini/system.md` (relative to your current project
-    directory).
-
-- Use a custom file path:
-  - `GEMINI_SYSTEM_MD=/absolute/path/to/my-system.md`
-  - Relative paths are supported and resolved from the current working
-    directory.
-  - Tilde expansion is supported (e.g., `~/my-system.md`).
-
-- Disable the override (use built‑in prompt):
-  - `GEMINI_SYSTEM_MD=false` or `GEMINI_SYSTEM_MD=0` or unset the variable.
-
-If the override is enabled but the target file does not exist, the CLI will
-error with: `missing system prompt file '<path>'`.
-
-## Quick examples
-
-- One‑off session using a project file:
-  - `GEMINI_SYSTEM_MD=1 gemini`
-- Persist for a project using `.gemini/.env`:
-  - Create `.gemini/system.md`, then add to `.gemini/.env`:
-    - `GEMINI_SYSTEM_MD=1`
-- Use a custom file under your home directory:
-  - `GEMINI_SYSTEM_MD=~/prompts/SYSTEM.md gemini`
-
-## UI indicator
-
-When `GEMINI_SYSTEM_MD` is active, the CLI shows a `|⌐■_■|` indicator in the UI
-to signal custom system‑prompt mode.
-
-## Export the default prompt (recommended)
-
-Before overriding, export the current default prompt so you can review required
-safety and workflow rules.
-
-- Write the built‑in prompt to the project default path:
-  - `GEMINI_WRITE_SYSTEM_MD=1 gemini`
-- Or write to a custom path:
-  - `GEMINI_WRITE_SYSTEM_MD=~/prompts/DEFAULT_SYSTEM.md gemini`
-
-This creates the file and writes the current built‑in system prompt to it.
-
-## Best practices: SYSTEM.md vs GEMINI.md
-
-- SYSTEM.md (firmware):
-  - Non‑negotiable operational rules: safety, tool‑use protocols, approvals, and
-    mechanics that keep the CLI reliable.
-  - Stable across tasks and projects (or per project when needed).
-- GEMINI.md (strategy):
-  - Persona, goals, methodologies, and project/domain context.
-  - Evolves per task; relies on SYSTEM.md for safe execution.
-
-Keep SYSTEM.md minimal but complete for safety and tool operation. Keep
-GEMINI.md focused on high‑level guidance and project specifics.
-
-## Troubleshooting
-
-- Error: `missing system prompt file '…'`
-  - Ensure the referenced path exists and is readable.
-  - For `GEMINI_SYSTEM_MD=1|true`, create `./.gemini/system.md` in your project.
-- Override not taking effect
-  - Confirm the variable is loaded (use `.gemini/.env` or export in your shell).
-  - Paths are resolved from the current working directory; try an absolute path.
-- Restore defaults
-  - Unset `GEMINI_SYSTEM_MD` or set it to `0`/`false`.

docs/cli/telemetry.md

@@ -3,68 +3,47 @@
 Learn how to enable and setup OpenTelemetry for Gemini CLI.
 
 - [Observability with OpenTelemetry](#observability-with-opentelemetry)
-  - [Key benefits](#key-benefits)
-  - [OpenTelemetry integration](#opentelemetry-integration)
+  - [Key Benefits](#key-benefits)
+  - [OpenTelemetry Integration](#opentelemetry-integration)
   - [Configuration](#configuration)
-  - [Google Cloud telemetry](#google-cloud-telemetry)
+  - [Google Cloud Telemetry](#google-cloud-telemetry)
     - [Prerequisites](#prerequisites)
-    - [Direct export (recommended)](#direct-export-recommended)
-    - [Collector-based export (advanced)](#collector-based-export-advanced)
-  - [Local telemetry](#local-telemetry)
-    - [File-based output (recommended)](#file-based-output-recommended)
-    - [Collector-based export (advanced)](#collector-based-export-advanced-1)
-  - [Logs and metrics](#logs-and-metrics)
+    - [Direct Export (Recommended)](#direct-export-recommended)
+    - [Collector-Based Export (Advanced)](#collector-based-export-advanced)
+  - [Local Telemetry](#local-telemetry)
+    - [File-based Output (Recommended)](#file-based-output-recommended)
+    - [Collector-Based Export (Advanced)](#collector-based-export-advanced-1)
+  - [Logs and Metrics](#logs-and-metrics)
     - [Logs](#logs)
-      - [Sessions](#sessions)
-      - [Tools](#tools)
-      - [Files](#files)
-      - [API](#api)
-      - [Model routing](#model-routing)
-      - [Chat and streaming](#chat-and-streaming)
-      - [Resilience](#resilience)
-      - [Extensions](#extensions)
-      - [Agent runs](#agent-runs)
-      - [IDE](#ide)
-      - [UI](#ui)
     - [Metrics](#metrics)
       - [Custom](#custom)
-        - [Sessions](#sessions-1)
-        - [Tools](#tools-1)
-        - [API](#api-1)
-        - [Token usage](#token-usage)
-        - [Files](#files-1)
-        - [Chat and streaming](#chat-and-streaming-1)
-        - [Model routing](#model-routing-1)
-        - [Agent runs](#agent-runs-1)
-        - [UI](#ui-1)
-        - [Performance](#performance)
-      - [GenAI semantic convention](#genai-semantic-convention)
+      - [GenAI Semantic Convention](#genai-semantic-convention)
 
-## Key benefits
+## Key Benefits
 
-- **🔍 Usage analytics**: Understand interaction patterns and feature adoption
+- **🔍 Usage Analytics**: Understand interaction patterns and feature adoption
   across your team
-- **⚡ Performance monitoring**: Track response times, token consumption, and
+- **⚡ Performance Monitoring**: Track response times, token consumption, and
   resource utilization
-- **🐛 Real-time debugging**: Identify bottlenecks, failures, and error patterns
+- **🐛 Real-time Debugging**: Identify bottlenecks, failures, and error patterns
   as they occur
-- **📊 Workflow optimization**: Make informed decisions to improve
+- **📊 Workflow Optimization**: Make informed decisions to improve
   configurations and processes
-- **🏢 Enterprise governance**: Monitor usage across teams, track costs, ensure
+- **🏢 Enterprise Governance**: Monitor usage across teams, track costs, ensure
   compliance, and integrate with existing monitoring infrastructure
 
-## OpenTelemetry integration
+## OpenTelemetry Integration
 
 Built on **[OpenTelemetry]** — the vendor-neutral, industry-standard
 observability framework — Gemini CLI's observability system provides:
 
-- **Universal compatibility**: Export to any OpenTelemetry backend (Google
+- **Universal Compatibility**: Export to any OpenTelemetry backend (Google
   Cloud, Jaeger, Prometheus, Datadog, etc.)
-- **Standardized data**: Use consistent formats and collection methods across
+- **Standardized Data**: Use consistent formats and collection methods across
   your toolchain
-- **Future-proof integration**: Connect with existing and future observability
+- **Future-Proof Integration**: Connect with existing and future observability
   infrastructure
-- **No vendor lock-in**: Switch between backends without changing your
+- **No Vendor Lock-in**: Switch between backends without changing your
   instrumentation
 
 [OpenTelemetry]: https://opentelemetry.io/
@@ -72,27 +51,26 @@ observability framework — Gemini CLI's observability system provides:
 ## Configuration
 
 All telemetry behavior is controlled through your `.gemini/settings.json` file.
-Environment variables can be used to override the settings in the file.
+These settings can be overridden by environment variables or CLI flags.
 
-| Setting        | Environment Variable             | Description                                         | Values            | Default                 |
-| -------------- | -------------------------------- | --------------------------------------------------- | ----------------- | ----------------------- |
-| `enabled`      | `GEMINI_TELEMETRY_ENABLED`       | Enable or disable telemetry                         | `true`/`false`    | `false`                 |
-| `target`       | `GEMINI_TELEMETRY_TARGET`        | Where to send telemetry data                        | `"gcp"`/`"local"` | `"local"`               |
-| `otlpEndpoint` | `GEMINI_TELEMETRY_OTLP_ENDPOINT` | OTLP collector endpoint                             | URL string        | `http://localhost:4317` |
-| `otlpProtocol` | `GEMINI_TELEMETRY_OTLP_PROTOCOL` | OTLP transport protocol                             | `"grpc"`/`"http"` | `"grpc"`                |
-| `outfile`      | `GEMINI_TELEMETRY_OUTFILE`       | Save telemetry to file (overrides `otlpEndpoint`)   | file path         | -                       |
-| `logPrompts`   | `GEMINI_TELEMETRY_LOG_PROMPTS`   | Include prompts in telemetry logs                   | `true`/`false`    | `true`                  |
-| `useCollector` | `GEMINI_TELEMETRY_USE_COLLECTOR` | Use external OTLP collector (advanced)              | `true`/`false`    | `false`                 |
-| `useCliAuth`   | `GEMINI_TELEMETRY_USE_CLI_AUTH`  | Use CLI credentials for telemetry (GCP target only) | `true`/`false`    | `false`                 |
+| Setting        | Environment Variable             | CLI Flag                                                 | Description                                       | Values            | Default                 |
+| -------------- | -------------------------------- | -------------------------------------------------------- | ------------------------------------------------- | ----------------- | ----------------------- |
+| `enabled`      | `GEMINI_TELEMETRY_ENABLED`       | `--telemetry` / `--no-telemetry`                         | Enable or disable telemetry                       | `true`/`false`    | `false`                 |
+| `target`       | `GEMINI_TELEMETRY_TARGET`        | `--telemetry-target <local\|gcp>`                        | Where to send telemetry data                      | `"gcp"`/`"local"` | `"local"`               |
+| `otlpEndpoint` | `GEMINI_TELEMETRY_OTLP_ENDPOINT` | `--telemetry-otlp-endpoint <URL>`                        | OTLP collector endpoint                           | URL string        | `http://localhost:4317` |
+| `otlpProtocol` | `GEMINI_TELEMETRY_OTLP_PROTOCOL` | `--telemetry-otlp-protocol <grpc\|http>`                 | OTLP transport protocol                           | `"grpc"`/`"http"` | `"grpc"`                |
+| `outfile`      | `GEMINI_TELEMETRY_OUTFILE`       | `--telemetry-outfile <path>`                             | Save telemetry to file (overrides `otlpEndpoint`) | file path         | -                       |
+| `logPrompts`   | `GEMINI_TELEMETRY_LOG_PROMPTS`   | `--telemetry-log-prompts` / `--no-telemetry-log-prompts` | Include prompts in telemetry logs                 | `true`/`false`    | `true`                  |
+| `useCollector` | `GEMINI_TELEMETRY_USE_COLLECTOR` | -                                                        | Use external OTLP collector (advanced)            | `true`/`false`    | `false`                 |
 
 **Note on boolean environment variables:** For the boolean settings (`enabled`,
 `logPrompts`, `useCollector`), setting the corresponding environment variable to
 `true` or `1` will enable the feature. Any other value will disable it.
 
 For detailed information about all configuration options, see the
-[Configuration guide](../get-started/configuration.md).
+[Configuration Guide](../get-started/configuration.md).
 
-## Google Cloud telemetry
+## Google Cloud Telemetry
 
 ### Prerequisites
 
@@ -131,35 +109,7 @@ Before using either method below, complete these steps:
      --project="$OTLP_GOOGLE_CLOUD_PROJECT"
    ```
 
-### Authenticating with CLI Credentials
-
-By default, the telemetry collector for Google Cloud uses Application Default
-Credentials (ADC). However, you can configure it to use the same OAuth
-credentials that you use to log in to the Gemini CLI. This is useful in
-environments where you don't have ADC set up.
-
-To enable this, set the `useCliAuth` property in your `telemetry` settings to
-`true`:
-
-```json
-{
-  "telemetry": {
-    "enabled": true,
-    "target": "gcp",
-    "useCliAuth": true
-  }
-}
-```
-
-**Important:**
-
-- This setting requires the use of **Direct Export** (in-process exporters).
-- It **cannot** be used with `useCollector: true`. If you enable both, telemetry
-  will be disabled and an error will be logged.
-- The CLI will automatically use your credentials to authenticate with Google
-  Cloud Trace, Metrics, and Logging APIs.
-
-### Direct export (recommended)
+### Direct Export (Recommended)
 
 Sends telemetry directly to Google Cloud services. No collector needed.
 
@@ -179,7 +129,7 @@ Sends telemetry directly to Google Cloud services. No collector needed.
      - Metrics: https://console.cloud.google.com/monitoring/metrics-explorer
      - Traces: https://console.cloud.google.com/traces/list
 
-### Collector-based export (advanced)
+### Collector-Based Export (Advanced)
 
 For custom processing, filtering, or routing, use an OpenTelemetry collector to
 forward data to Google Cloud.
@@ -213,11 +163,11 @@ forward data to Google Cloud.
    - Open `~/.gemini/tmp/<projectHash>/otel/collector-gcp.log` to view local
      collector logs.
 
-## Local telemetry
+## Local Telemetry
 
 For local development and debugging, you can capture telemetry data locally:
 
-### File-based output (recommended)
+### File-based Output (Recommended)
 
 1. Enable telemetry in your `.gemini/settings.json`:
    ```json
@@ -233,7 +183,7 @@ For local development and debugging, you can capture telemetry data locally:
 2. Run Gemini CLI and send prompts.
 3. View logs and metrics in the specified file (e.g., `.gemini/telemetry.log`).
 
-### Collector-based export (advanced)
+### Collector-Based Export (Advanced)
 
 1. Run the automation script:
    ```bash
@@ -249,25 +199,21 @@ For local development and debugging, you can capture telemetry data locally:
 3. View traces at http://localhost:16686 and logs/metrics in the collector log
    file.
 
-## Logs and metrics
+## Logs and Metrics
 
 The following section describes the structure of logs and metrics generated for
 Gemini CLI.
 
-The `session.id`, `installation.id`, and `user.email` (available only when
-authenticated with a Google account) are included as common attributes on all
-logs and metrics.
+The `session.id`, `installation.id`, and `user.email` are included as common
+attributes on all logs and metrics.
 
 ### Logs
 
 Logs are timestamped records of specific events. The following events are logged
-for Gemini CLI, grouped by category.
+for Gemini CLI:
 
-#### Sessions
-
-Captures startup configuration and user prompt submissions.
-
-- `gemini_cli.config`: Emitted once at startup with the CLI configuration.
+- `gemini_cli.config`: This event occurs once at startup with the CLI's
+  configuration.
   - **Attributes**:
     - `model` (string)
     - `embedding_model` (string)
@@ -276,47 +222,81 @@ Captures startup configuration and user prompt submissions.
     - `approval_mode` (string)
     - `api_key_enabled` (boolean)
     - `vertex_ai_enabled` (boolean)
-    - `log_user_prompts_enabled` (boolean)
+    - `code_assist_enabled` (boolean)
+    - `log_prompts_enabled` (boolean)
     - `file_filtering_respect_git_ignore` (boolean)
     - `debug_mode` (boolean)
     - `mcp_servers` (string)
-    - `mcp_servers_count` (int)
-    - `extensions` (string)
-    - `extension_ids` (string)
-    - `extension_count` (int)
-    - `mcp_tools` (string, if applicable)
-    - `mcp_tools_count` (int, if applicable)
-    - `output_format` ("text", "json", or "stream-json")
+    - `output_format` (string: "text", "json", or "stream-json")
 
-- `gemini_cli.user_prompt`: Emitted when a user submits a prompt.
+- `gemini_cli.user_prompt`: This event occurs when a user submits a prompt.
   - **Attributes**:
     - `prompt_length` (int)
     - `prompt_id` (string)
-    - `prompt` (string; excluded if `telemetry.logPrompts` is `false`)
+    - `prompt` (string, this attribute is excluded if `log_prompts_enabled` is
+      configured to be `false`)
     - `auth_type` (string)
 
-#### Tools
-
-Captures tool executions, output truncation, and Edit behavior.
-
-- `gemini_cli.tool_call`: Emitted for each tool (function) call.
+- `gemini_cli.tool_call`: This event occurs for each function call.
   - **Attributes**:
     - `function_name`
     - `function_args`
     - `duration_ms`
     - `success` (boolean)
-    - `decision` ("accept", "reject", "auto_accept", or "modify", if applicable)
+    - `decision` (string: "accept", "reject", "auto_accept", or "modify", if
+      applicable)
     - `error` (if applicable)
     - `error_type` (if applicable)
-    - `prompt_id` (string)
-    - `tool_type` ("native" or "mcp")
-    - `mcp_server_name` (string, if applicable)
-    - `extension_name` (string, if applicable)
-    - `extension_id` (string, if applicable)
     - `content_length` (int, if applicable)
-    - `metadata` (if applicable)
+    - `metadata` (if applicable, dictionary of string -> any)
 
-- `gemini_cli.tool_output_truncated`: Output of a tool call was truncated.
+- `gemini_cli.file_operation`: This event occurs for each file operation.
+  - **Attributes**:
+    - `tool_name` (string)
+    - `operation` (string: "create", "read", "update")
+    - `lines` (int, if applicable)
+    - `mimetype` (string, if applicable)
+    - `extension` (string, if applicable)
+    - `programming_language` (string, if applicable)
+    - `diff_stat` (json string, if applicable): A JSON string with the following
+      members:
+      - `ai_added_lines` (int)
+      - `ai_removed_lines` (int)
+      - `user_added_lines` (int)
+      - `user_removed_lines` (int)
+
+- `gemini_cli.api_request`: This event occurs when making a request to Gemini
+  API.
+  - **Attributes**:
+    - `model`
+    - `request_text` (if applicable)
+
+- `gemini_cli.api_error`: This event occurs if the API request fails.
+  - **Attributes**:
+    - `model`
+    - `error`
+    - `error_type`
+    - `status_code`
+    - `duration_ms`
+    - `auth_type`
+
+- `gemini_cli.api_response`: This event occurs upon receiving a response from
+  Gemini API.
+  - **Attributes**:
+    - `model`
+    - `status_code`
+    - `duration_ms`
+    - `error` (optional)
+    - `input_token_count`
+    - `output_token_count`
+    - `cached_content_token_count`
+    - `thoughts_token_count`
+    - `tool_token_count`
+    - `response_text` (if applicable)
+    - `auth_type`
+
+- `gemini_cli.tool_output_truncated`: This event occurs when the output of a
+  tool call is too large and gets truncated.
   - **Attributes**:
     - `tool_name` (string)
     - `original_content_length` (int)
@@ -325,226 +305,32 @@ Captures tool executions, output truncation, and Edit behavior.
     - `lines` (int)
     - `prompt_id` (string)
 
-- `gemini_cli.edit_strategy`: Edit strategy chosen.
+- `gemini_cli.malformed_json_response`: This event occurs when a `generateJson`
+  response from Gemini API cannot be parsed as a json.
   - **Attributes**:
-    - `strategy` (string)
+    - `model`
 
-- `gemini_cli.edit_correction`: Edit correction result.
+- `gemini_cli.flash_fallback`: This event occurs when Gemini CLI switches to
+  flash as fallback.
   - **Attributes**:
-    - `correction` ("success" | "failure")
+    - `auth_type`
 
-- `gen_ai.client.inference.operation.details`: This event provides detailed
-  information about the GenAI operation, aligned with [OpenTelemetry GenAI
-  semantic conventions for events].
-  - **Attributes**:
-    - `gen_ai.request.model` (string)
-    - `gen_ai.provider.name` (string)
-    - `gen_ai.operation.name` (string)
-    - `gen_ai.input.messages` (json string)
-    - `gen_ai.output.messages` (json string)
-    - `gen_ai.response.finish_reasons` (array of strings)
-    - `gen_ai.usage.input_tokens` (int)
-    - `gen_ai.usage.output_tokens` (int)
-    - `gen_ai.request.temperature` (float)
-    - `gen_ai.request.top_p` (float)
-    - `gen_ai.request.top_k` (int)
-    - `gen_ai.request.max_tokens` (int)
-    - `gen_ai.system_instructions` (json string)
-    - `server.address` (string)
-    - `server.port` (int)
-
-#### Files
-
-Tracks file operations performed by tools.
-
-- `gemini_cli.file_operation`: Emitted for each file operation.
-  - **Attributes**:
-    - `tool_name` (string)
-    - `operation` ("create" | "read" | "update")
-    - `lines` (int, optional)
-    - `mimetype` (string, optional)
-    - `extension` (string, optional)
-    - `programming_language` (string, optional)
-
-#### API
-
-Captures Gemini API requests, responses, and errors.
-
-- `gemini_cli.api_request`: Request sent to Gemini API.
-  - **Attributes**:
-    - `model` (string)
-    - `prompt_id` (string)
-    - `request_text` (string, optional)
-
-- `gemini_cli.api_response`: Response received from Gemini API.
-  - **Attributes**:
-    - `model` (string)
-    - `status_code` (int|string)
-    - `duration_ms` (int)
-    - `input_token_count` (int)
-    - `output_token_count` (int)
-    - `cached_content_token_count` (int)
-    - `thoughts_token_count` (int)
-    - `tool_token_count` (int)
-    - `total_token_count` (int)
-    - `response_text` (string, optional)
-    - `prompt_id` (string)
-    - `auth_type` (string)
-    - `finish_reasons` (array of strings)
-
-- `gemini_cli.api_error`: API request failed.
-  - **Attributes**:
-    - `model` (string)
-    - `error` (string)
-    - `error_type` (string)
-    - `status_code` (int|string)
-    - `duration_ms` (int)
-    - `prompt_id` (string)
-    - `auth_type` (string)
-
-- `gemini_cli.malformed_json_response`: `generateJson` response could not be
-  parsed.
-  - **Attributes**:
-    - `model` (string)
-
-#### Model routing
-
-- `gemini_cli.slash_command`: A slash command was executed.
+- `gemini_cli.slash_command`: This event occurs when a user executes a slash
+  command.
   - **Attributes**:
     - `command` (string)
-    - `subcommand` (string, optional)
-    - `status` ("success" | "error")
+    - `subcommand` (string, if applicable)
 
-- `gemini_cli.slash_command.model`: Model was selected via slash command.
-  - **Attributes**:
-    - `model_name` (string)
-
-- `gemini_cli.model_routing`: Model router made a decision.
-  - **Attributes**:
-    - `decision_model` (string)
-    - `decision_source` (string)
-    - `routing_latency_ms` (int)
-    - `reasoning` (string, optional)
-    - `failed` (boolean)
-    - `error_message` (string, optional)
-
-#### Chat and streaming
-
-- `gemini_cli.chat_compression`: Chat context was compressed.
-  - **Attributes**:
-    - `tokens_before` (int)
-    - `tokens_after` (int)
-
-- `gemini_cli.chat.invalid_chunk`: Invalid chunk received from a stream.
-  - **Attributes**:
-    - `error.message` (string, optional)
-
-- `gemini_cli.chat.content_retry`: Retry triggered due to a content error.
-  - **Attributes**:
-    - `attempt_number` (int)
-    - `error_type` (string)
-    - `retry_delay_ms` (int)
-    - `model` (string)
-
-- `gemini_cli.chat.content_retry_failure`: All content retries failed.
-  - **Attributes**:
-    - `total_attempts` (int)
-    - `final_error_type` (string)
-    - `total_duration_ms` (int, optional)
-    - `model` (string)
-
-- `gemini_cli.conversation_finished`: Conversation session ended.
-  - **Attributes**:
-    - `approvalMode` (string)
-    - `turnCount` (int)
-
-- `gemini_cli.next_speaker_check`: Next speaker determination.
-  - **Attributes**:
-    - `prompt_id` (string)
-    - `finish_reason` (string)
-    - `result` (string)
-
-#### Resilience
-
-Records fallback mechanisms for models and network operations.
-
-- `gemini_cli.flash_fallback`: Switched to a flash model as fallback.
-  - **Attributes**:
-    - `auth_type` (string)
-
-- `gemini_cli.ripgrep_fallback`: Switched to grep as fallback for file search.
-  - **Attributes**:
-    - `error` (string, optional)
-
-- `gemini_cli.web_fetch_fallback_attempt`: Attempted web-fetch fallback.
-  - **Attributes**:
-    - `reason` ("private_ip" | "primary_failed")
-
-#### Extensions
-
-Tracks extension lifecycle and settings changes.
-
-- `gemini_cli.extension_install`: An extension was installed.
+- `gemini_cli.extension_enable`: This event occurs when an extension is enabled
+- `gemini_cli.extension_install`: This event occurs when an extension is
+  installed
   - **Attributes**:
     - `extension_name` (string)
     - `extension_version` (string)
     - `extension_source` (string)
     - `status` (string)
-
-- `gemini_cli.extension_uninstall`: An extension was uninstalled.
-  - **Attributes**:
-    - `extension_name` (string)
-    - `status` (string)
-
-- `gemini_cli.extension_enable`: An extension was enabled.
-  - **Attributes**:
-    - `extension_name` (string)
-    - `setting_scope` (string)
-
-- `gemini_cli.extension_disable`: An extension was disabled.
-  - **Attributes**:
-    - `extension_name` (string)
-    - `setting_scope` (string)
-
-- `gemini_cli.extension_update`: An extension was updated.
-  - **Attributes**:
-    - `extension_name` (string)
-    - `extension_version` (string)
-    - `extension_previous_version` (string)
-    - `extension_source` (string)
-    - `status` (string)
-
-#### Agent runs
-
-- `gemini_cli.agent.start`: Agent run started.
-  - **Attributes**:
-    - `agent_id` (string)
-    - `agent_name` (string)
-
-- `gemini_cli.agent.finish`: Agent run finished.
-  - **Attributes**:
-    - `agent_id` (string)
-    - `agent_name` (string)
-    - `duration_ms` (int)
-    - `turn_count` (int)
-    - `terminate_reason` (string)
-
-#### IDE
-
-Captures IDE connectivity and conversation lifecycle events.
-
-- `gemini_cli.ide_connection`: IDE companion connection.
-  - **Attributes**:
-    - `connection_type` (string)
-
-#### UI
-
-Tracks terminal rendering issues and related signals.
-
-- `kitty_sequence_overflow`: Terminal kitty control sequence overflow.
-  - **Attributes**:
-    - `sequence_length` (int)
-    - `truncated_sequence` (string)
+- `gemini_cli.extension_uninstall`: This event occurs when an extension is
+  uninstalled
 
 ### Metrics
 
@@ -552,31 +338,27 @@ Metrics are numerical measurements of behavior over time.
 
 #### Custom
 
-##### Sessions
-
-Counts CLI sessions at startup.
-
 - `gemini_cli.session.count` (Counter, Int): Incremented once per CLI startup.
 
-##### Tools
-
-Measures tool usage and latency.
-
 - `gemini_cli.tool.call.count` (Counter, Int): Counts tool calls.
   - **Attributes**:
     - `function_name`
     - `success` (boolean)
-    - `decision` (string: "accept", "reject", "modify", or "auto_accept", if
-      applicable)
-    - `tool_type` (string: "mcp" or "native", if applicable)
+    - `decision` (string: "accept", "reject", or "modify", if applicable)
+    - `tool_type` (string: "mcp", or "native", if applicable)
+    - `model_added_lines` (Int, optional): Lines added by model in the proposed
+      changes, if applicable
+    - `model_removed_lines` (Int, optional): Lines removed by model in the
+      proposed changes, if applicable
+    - `user_added_lines` (Int, optional): Lines added by user edits after model
+      proposal, if applicable
+    - `user_removed_lines` (Int, optional): Lines removed by user edits after
+      model proposal, if applicable
 
 - `gemini_cli.tool.call.latency` (Histogram, ms): Measures tool call latency.
   - **Attributes**:
     - `function_name`
-
-##### API
-
-Tracks API request volume and latency.
+    - `decision` (string: "accept", "reject", or "modify", if applicable)
 
 - `gemini_cli.api.request.count` (Counter, Int): Counts all API requests.
   - **Attributes**:
@@ -588,169 +370,34 @@ Tracks API request volume and latency.
   latency.
   - **Attributes**:
     - `model`
-  - Note: Overlaps with `gen_ai.client.operation.duration` (GenAI conventions).
+  - **Note**: This metric overlaps with `gen_ai.client.operation.duration` below
+    that's compliant with GenAI Semantic Conventions.
 
-##### Token usage
-
-Tracks tokens used by model and type.
-
-- `gemini_cli.token.usage` (Counter, Int): Counts tokens used.
+- `gemini_cli.token.usage` (Counter, Int): Counts the number of tokens used.
   - **Attributes**:
     - `model`
-    - `type` ("input", "output", "thought", "cache", or "tool")
-  - Note: Overlaps with `gen_ai.client.token.usage` for `input`/`output`.
-
-##### Files
-
-Counts file operations with basic context.
+    - `type` (string: "input", "output", "thought", "cache", or "tool")
+  - **Note**: This metric overlaps with `gen_ai.client.token.usage` below for
+    `input`/`output` token types that's compliant with GenAI Semantic
+    Conventions.
 
 - `gemini_cli.file.operation.count` (Counter, Int): Counts file operations.
   - **Attributes**:
-    - `operation` ("create", "read", "update")
-    - `lines` (Int, optional)
-    - `mimetype` (string, optional)
-    - `extension` (string, optional)
-    - `programming_language` (string, optional)
-
-- `gemini_cli.lines.changed` (Counter, Int): Number of lines changed (from file
-  diffs).
-  - **Attributes**:
-    - `function_name`
-    - `type` ("added" or "removed")
-
-##### Chat and streaming
-
-Resilience counters for compression, invalid chunks, and retries.
+    - `operation` (string: "create", "read", "update"): The type of file
+      operation.
+    - `lines` (Int, if applicable): Number of lines in the file.
+    - `mimetype` (string, if applicable): Mimetype of the file.
+    - `extension` (string, if applicable): File extension of the file.
+    - `programming_language` (string, if applicable): The programming language
+      of the file.
 
 - `gemini_cli.chat_compression` (Counter, Int): Counts chat compression
-  operations.
+  operations
   - **Attributes**:
-    - `tokens_before` (Int)
-    - `tokens_after` (Int)
+    - `tokens_before`: (Int): Number of tokens in context prior to compression
+    - `tokens_after`: (Int): Number of tokens in context after compression
 
-- `gemini_cli.chat.invalid_chunk.count` (Counter, Int): Counts invalid chunks
-  from streams.
-
-- `gemini_cli.chat.content_retry.count` (Counter, Int): Counts retries due to
-  content errors.
-
-- `gemini_cli.chat.content_retry_failure.count` (Counter, Int): Counts requests
-  where all content retries failed.
-
-##### Model routing
-
-Routing latency/failures and slash-command selections.
-
-- `gemini_cli.slash_command.model.call_count` (Counter, Int): Counts model
-  selections via slash command.
-  - **Attributes**:
-    - `slash_command.model.model_name` (string)
-
-- `gemini_cli.model_routing.latency` (Histogram, ms): Model routing decision
-  latency.
-  - **Attributes**:
-    - `routing.decision_model` (string)
-    - `routing.decision_source` (string)
-
-- `gemini_cli.model_routing.failure.count` (Counter, Int): Counts model routing
-  failures.
-  - **Attributes**:
-    - `routing.decision_source` (string)
-    - `routing.error_message` (string)
-
-##### Agent runs
-
-Agent lifecycle metrics: runs, durations, and turns.
-
-- `gemini_cli.agent.run.count` (Counter, Int): Counts agent runs.
-  - **Attributes**:
-    - `agent_name` (string)
-    - `terminate_reason` (string)
-
-- `gemini_cli.agent.duration` (Histogram, ms): Agent run durations.
-  - **Attributes**:
-    - `agent_name` (string)
-
-- `gemini_cli.agent.turns` (Histogram, turns): Turns taken per agent run.
-  - **Attributes**:
-    - `agent_name` (string)
-
-##### UI
-
-UI stability signals such as flicker count.
-
-- `gemini_cli.ui.flicker.count` (Counter, Int): Counts UI frames that flicker
-  (render taller than terminal).
-
-##### Performance
-
-Optional performance monitoring for startup, CPU/memory, and phase timing.
-
-- `gemini_cli.startup.duration` (Histogram, ms): CLI startup time by phase.
-  - **Attributes**:
-    - `phase` (string)
-    - `details` (map, optional)
-
-- `gemini_cli.memory.usage` (Histogram, bytes): Memory usage.
-  - **Attributes**:
-    - `memory_type` ("heap_used", "heap_total", "external", "rss")
-    - `component` (string, optional)
-
-- `gemini_cli.cpu.usage` (Histogram, percent): CPU usage percentage.
-  - **Attributes**:
-    - `component` (string, optional)
-
-- `gemini_cli.tool.queue.depth` (Histogram, count): Number of tools in the
-  execution queue.
-
-- `gemini_cli.tool.execution.breakdown` (Histogram, ms): Tool time by phase.
-  - **Attributes**:
-    - `function_name` (string)
-    - `phase` ("validation", "preparation", "execution", "result_processing")
-
-- `gemini_cli.api.request.breakdown` (Histogram, ms): API request time by phase.
-  - **Attributes**:
-    - `model` (string)
-    - `phase` ("request_preparation", "network_latency", "response_processing",
-      "token_processing")
-
-- `gemini_cli.token.efficiency` (Histogram, ratio): Token efficiency metrics.
-  - **Attributes**:
-    - `model` (string)
-    - `metric` (string)
-    - `context` (string, optional)
-
-- `gemini_cli.performance.score` (Histogram, score): Composite performance
-  score.
-  - **Attributes**:
-    - `category` (string)
-    - `baseline` (number, optional)
-
-- `gemini_cli.performance.regression` (Counter, Int): Regression detection
-  events.
-  - **Attributes**:
-    - `metric` (string)
-    - `severity` ("low", "medium", "high")
-    - `current_value` (number)
-    - `baseline_value` (number)
-
-- `gemini_cli.performance.regression.percentage_change` (Histogram, percent):
-  Percent change from baseline when regression detected.
-  - **Attributes**:
-    - `metric` (string)
-    - `severity` ("low", "medium", "high")
-    - `current_value` (number)
-    - `baseline_value` (number)
-
-- `gemini_cli.performance.baseline.comparison` (Histogram, percent): Comparison
-  to baseline.
-  - **Attributes**:
-    - `metric` (string)
-    - `category` (string)
-    - `current_value` (number)
-    - `baseline_value` (number)
-
-#### GenAI semantic convention
+#### GenAI Semantic Convention
 
 The following metrics comply with [OpenTelemetry GenAI semantic conventions] for
 standardized observability across GenAI applications:
@@ -787,5 +434,3 @@ standardized observability across GenAI applications:
 
 [OpenTelemetry GenAI semantic conventions]:
   https://github.com/open-telemetry/semantic-conventions/blob/main/docs/gen-ai/gen-ai-metrics.md
-[OpenTelemetry GenAI semantic conventions for events]:
-  https://github.com/open-telemetry/semantic-conventions/blob/8b4f210f43136e57c1f6f47292eb6d38e3bf30bb/docs/gen-ai/gen-ai-events.md

docs/cli/themes.md

@@ -4,19 +4,19 @@ Gemini CLI supports a variety of themes to customize its color scheme and
 appearance. You can change the theme to suit your preferences via the `/theme`
 command or `"theme":` configuration setting.
 
-## Available themes
+## Available Themes
 
 Gemini CLI comes with a selection of pre-defined themes, which you can list
 using the `/theme` command within Gemini CLI:
 
-- **Dark themes:**
+- **Dark Themes:**
   - `ANSI`
   - `Atom One`
   - `Ayu`
   - `Default`
   - `Dracula`
   - `GitHub`
-- **Light themes:**
+- **Light Themes:**
   - `ANSI Light`
   - `Ayu Light`
   - `Default Light`
@@ -24,7 +24,7 @@ using the `/theme` command within Gemini CLI:
   - `Google Code`
   - `Xcode`
 
-### Changing themes
+### Changing Themes
 
 1.  Enter `/theme` into Gemini CLI.
 2.  A dialog or selection prompt appears, listing the available themes.
@@ -36,7 +36,7 @@ using the `/theme` command within Gemini CLI:
 by a file path), you must remove the `"theme"` setting from the file before you
 can change the theme using the `/theme` command.
 
-### Theme persistence
+### Theme Persistence
 
 Selected themes are saved in Gemini CLI's
 [configuration](../get-started/configuration.md) so your preference is
@@ -44,13 +44,13 @@ remembered across sessions.
 
 ---
 
-## Custom color themes
+## Custom Color Themes
 
 Gemini CLI allows you to create your own custom color themes by specifying them
 in your `settings.json` file. This gives you full control over the color palette
 used in the CLI.
 
-### How to define a custom theme
+### How to Define a Custom Theme
 
 Add a `customThemes` block to your user, project, or system `settings.json`
 file. Each custom theme is defined as an object with a unique name and a set of
@@ -88,12 +88,7 @@ color keys. For example:
 - `DiffRemoved` (optional, for removed lines in diffs)
 - `DiffModified` (optional, for modified lines in diffs)
 
-You can also override individual UI text roles by adding a nested `text` object.
-This object supports the keys `primary`, `secondary`, `link`, `accent`, and
-`response`. When `text.response` is provided it takes precedence over
-`text.primary` for rendering model responses in chat.
-
-**Required properties:**
+**Required Properties:**
 
 - `name` (must match the key in the `customThemes` object and be a string)
 - `type` (must be the string `"custom"`)
@@ -117,7 +112,7 @@ for a full list of supported names.
 You can define multiple custom themes by adding more entries to the
 `customThemes` object.
 
-### Loading themes from a file
+### Loading Themes from a File
 
 In addition to defining custom themes in `settings.json`, you can also load a
 theme directly from a JSON file by specifying the file path in your
@@ -162,17 +157,17 @@ custom theme defined in `settings.json`.
 }
 ```
 
-**Security note:** For your safety, Gemini CLI will only load theme files that
+**Security Note:** For your safety, Gemini CLI will only load theme files that
 are located within your home directory. If you attempt to load a theme from
 outside your home directory, a warning will be displayed and the theme will not
 be loaded. This is to prevent loading potentially malicious theme files from
 untrusted sources.
 
-### Example custom theme
+### Example Custom Theme
 
 <img src="../assets/theme-custom.png" alt="Custom theme example" width="600" />
 
-### Using your custom theme
+### Using Your Custom Theme
 
 - Select your custom theme using the `/theme` command in Gemini CLI. Your custom
   theme will appear in the theme selection dialog.
@@ -184,7 +179,7 @@ untrusted sources.
 
 ---
 
-## Dark themes
+## Dark Themes
 
 ### ANSI
 
@@ -210,7 +205,7 @@ untrusted sources.
 
 <img src="/assets/theme-github.png" alt="GitHub theme" width="600">
 
-## Light themes
+## Light Themes
 
 ### ANSI Light
 

docs/cli/token-caching.md

@@ -1,4 +1,4 @@
-# Token caching and cost optimization
+# Token Caching and Cost Optimization
 
 Gemini CLI automatically optimizes API costs through token caching when using
 API key authentication (Gemini API key or Vertex AI). This feature reuses

docs/cli/trusted-folders.md

@@ -5,7 +5,7 @@ which projects can use the full capabilities of the Gemini CLI. It prevents
 potentially malicious code from running by asking you to approve a folder before
 the CLI loads any project-specific configurations from it.
 
-## Enabling the feature
+## Enabling the Feature
 
 The Trusted Folders feature is **disabled by default**. To use it, you must
 first enable it in your settings.
@@ -22,7 +22,7 @@ Add the following to your user `settings.json` file:
 }
 ```
 
-## How it works: The trust dialog
+## How It Works: The Trust Dialog
 
 Once the feature is enabled, the first time you run the Gemini CLI from a
 folder, a dialog will automatically appear, prompting you to make a choice:
@@ -38,58 +38,58 @@ folder, a dialog will automatically appear, prompting you to make a choice:
 Your choice is saved in a central file (`~/.gemini/trustedFolders.json`), so you
 will only be asked once per folder.
 
-## Why trust matters: The impact of an untrusted workspace
+## Why Trust Matters: The Impact of an Untrusted Workspace
 
 When a folder is **untrusted**, the Gemini CLI runs in a restricted "safe mode"
 to protect you. In this mode, the following features are disabled:
 
-1.  **Workspace settings are ignored**: The CLI will **not** load the
+1.  **Workspace Settings are Ignored**: The CLI will **not** load the
     `.gemini/settings.json` file from the project. This prevents the loading of
     custom tools and other potentially dangerous configurations.
 
-2.  **Environment variables are ignored**: The CLI will **not** load any `.env`
+2.  **Environment Variables are Ignored**: The CLI will **not** load any `.env`
     files from the project.
 
-3.  **Extension management is restricted**: You **cannot install, update, or
+3.  **Extension Management is Restricted**: You **cannot install, update, or
     uninstall** extensions.
 
-4.  **Tool auto-acceptance is disabled**: You will always be prompted before any
+4.  **Tool Auto-Acceptance is Disabled**: You will always be prompted before any
     tool is run, even if you have auto-acceptance enabled globally.
 
-5.  **Automatic memory loading is disabled**: The CLI will not automatically
+5.  **Automatic Memory Loading is Disabled**: The CLI will not automatically
     load files into context from directories specified in local settings.
 
-6.  **MCP servers do not connect**: The CLI will not attempt to connect to any
+6.  **MCP Servers Do Not Connect**: The CLI will not attempt to connect to any
     [Model Context Protocol (MCP)](../tools/mcp-server.md) servers.
 
-7.  **Custom commands are not loaded**: The CLI will not load any custom
+7.  **Custom Commands are Not Loaded**: The CLI will not load any custom
     commands from .toml files, including both project-specific and global user
     commands.
 
 Granting trust to a folder unlocks the full functionality of the Gemini CLI for
 that workspace.
 
-## Managing your trust settings
+## Managing Your Trust Settings
 
 If you need to change a decision or see all your settings, you have a couple of
 options:
 
-- **Change the current folder's trust**: Run the `/permissions` command from
+- **Change the Current Folder's Trust**: Run the `/permissions` command from
   within the CLI. This will bring up the same interactive dialog, allowing you
   to change the trust level for the current folder.
 
-- **View all trust rules**: To see a complete list of all your trusted and
+- **View All Trust Rules**: To see a complete list of all your trusted and
   untrusted folder rules, you can inspect the contents of the
   `~/.gemini/trustedFolders.json` file in your home directory.
 
-## The trust check process (advanced)
+## The Trust Check Process (Advanced)
 
 For advanced users, it's helpful to know the exact order of operations for how
 trust is determined:
 
-1.  **IDE trust signal**: If you are using the
+1.  **IDE Trust Signal**: If you are using the
     [IDE Integration](../ide-integration/index.md), the CLI first asks the IDE
     if the workspace is trusted. The IDE's response takes highest priority.
 
-2.  **Local trust file**: If the IDE is not connected, the CLI checks the
+2.  **Local Trust File**: If the IDE is not connected, the CLI checks the
     central `~/.gemini/trustedFolders.json` file.

docs/cli/tutorials.md

@@ -2,17 +2,13 @@
 
 This page contains tutorials for interacting with Gemini CLI.
 
-## Agent Skills
-
-- [Getting Started with Agent Skills](./tutorials/skills-getting-started.md)
-
 ## Setting up a Model Context Protocol (MCP) server
 
 > [!CAUTION] Before using a third-party MCP server, ensure you trust its source
 > and understand the tools it provides. Your use of third-party servers is at
 > your own risk.
 
-This tutorial demonstrates how to set up an MCP server, using the
+This tutorial demonstrates how to set up a MCP server, using the
 [GitHub MCP server](https://github.com/github/github-mcp-server) as an example.
 The GitHub MCP server provides tools for interacting with GitHub repositories,
 such as creating issues and commenting on pull requests.

docs/cli/tutorials/skills-getting-started.md

@@ -1,124 +0,0 @@
-# Getting Started with Agent Skills
-
-Agent Skills allow you to extend Gemini CLI with specialized expertise. This
-tutorial will guide you through creating your first skill, enabling it, and
-using it in a session.
-
-## 1. Enable Agent Skills
-
-Agent Skills are currently an experimental feature and must be enabled in your
-settings.
-
-### Via the interactive UI
-
-1.  Start a Gemini CLI session by running `gemini`.
-2.  Type `/settings` to open the interactive settings dialog.
-3.  Search for "Skills".
-4.  Toggle **Agent Skills** to `true`.
-5.  Press `Esc` to save and exit. You may need to restart the CLI for the
-    changes to take effect.
-
-### Via `settings.json`
-
-Alternatively, you can manually edit your global settings file at
-`~/.gemini/settings.json` (create it if it doesn't exist):
-
-```json
-{
-  "experimental": {
-    "skills": true
-  }
-}
-```
-
-## 2. Create Your First Skill
-
-A skill is a directory containing a `SKILL.md` file. Let's create an **API
-Auditor** skill that helps you verify if local or remote endpoints are
-responding correctly.
-
-1.  **Create the skill directory structure:**
-
-    ```bash
-    mkdir -p .gemini/skills/api-auditor/scripts
-    ```
-
-2.  **Create the `SKILL.md` file:** Create a file at
-    `.gemini/skills/api-auditor/SKILL.md` with the following content:
-
-    ```markdown
-    ---
-    name: api-auditor
-    description:
-      Expertise in auditing and testing API endpoints. Use when the user asks to
-      "check", "test", or "audit" a URL or API.
-    ---
-
-    # API Auditor Instructions
-
-    You act as a QA engineer specialized in API reliability. When this skill is
-    active, you MUST:
-
-    1.  **Audit**: Use the bundled `scripts/audit.js` utility to check the
-        status of the provided URL.
-    2.  **Report**: Analyze the output (status codes, latency) and explain any
-        failures in plain English.
-    3.  **Secure**: Remind the user if they are testing a sensitive endpoint
-        without an `https://` protocol.
-    ```
-
-3.  **Create the bundled Node.js script:** Create a file at
-    `.gemini/skills/api-auditor/scripts/audit.js`. This script will be used by
-    the agent to perform the actual check:
-
-    ```javascript
-    // .gemini/skills/api-auditor/scripts/audit.js
-    const url = process.argv[2];
-
-    if (!url) {
-      console.error('Usage: node audit.js <url>');
-      process.exit(1);
-    }
-
-    console.log(`Auditing ${url}...`);
-    fetch(url, { method: 'HEAD' })
-      .then((r) => console.log(`Result: Success (Status ${r.status})`))
-      .catch((e) => console.error(`Result: Failed (${e.message})`));
-    ```
-
-## 3. Verify the Skill is Discovered
-
-Use the `/skills` slash command (or `gemini skills list` from your terminal) to
-see if Gemini CLI has found your new skill.
-
-In a Gemini CLI session:
-
-```
-/skills list
-```
-
-You should see `api-auditor` in the list of available skills.
-
-## 4. Use the Skill in a Chat
-
-Now, let's see the skill in action. Start a new session and ask a question about
-an endpoint.
-
-**User:** "Can you audit http://geminili.com"
-
-Gemini will recognize the request matches the `api-auditor` description and will
-ask for your permission to activate it.
-
-**Model:** (After calling `activate_skill`) "I've activated the **api-auditor**
-skill. I'll run the audit script now..."
-
-Gemini will then use the `run_shell_command` tool to execute your bundled Node
-script:
-
-`node .gemini/skills/api-auditor/scripts/audit.js http://geminili.com`
-
-## Next Steps
-
-- Explore [Agent Skills Authoring Guide](../skills.md#creating-a-skill) to learn
-  about more advanced skill features.
-- Learn how to share skills via [Extensions](../../extensions/index.md).

docs/cli/uninstall.md

@@ -35,7 +35,7 @@ _PowerShell_
 Remove-Item -Path (Join-Path $env:LocalAppData "npm-cache\_npx") -Recurse -Force
 ```
 
-## Method 2: Using npm (global install)
+## 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.

docs/core/index.md

@@ -1,4 +1,4 @@
-# Gemini CLI core
+# Gemini CLI Core
 
 Gemini CLI's core package (`packages/core`) is the backend portion of Gemini
 CLI, handling communication with the Gemini API, managing tools, and processing
@@ -11,8 +11,6 @@ requests sent from `packages/cli`. For a general overview of Gemini CLI, see the
   registered, and used by the core.
 - **[Memory Import Processor](./memport.md):** Documentation for the modular
   GEMINI.md import feature using @file.md syntax.
-- **[Policy Engine](./policy-engine.md):** Use the Policy Engine for
-  fine-grained control over tool execution.
 
 ## Role of the core
 

docs/core/memport.md

@@ -27,21 +27,21 @@ More content here.
 @./shared/configuration.md
 ```
 
-## Supported path formats
+## Supported Path Formats
 
-### Relative paths
+### Relative Paths
 
 - `@./file.md` - Import from the same directory
 - `@../file.md` - Import from parent directory
 - `@./components/file.md` - Import from subdirectory
 
-### Absolute paths
+### Absolute Paths
 
 - `@/absolute/path/to/file.md` - Import using absolute path
 
 ## Examples
 
-### Basic import
+### Basic Import
 
 ```markdown
 # My GEMINI.md
@@ -55,7 +55,7 @@ Welcome to my project!
 @./features/overview.md
 ```
 
-### Nested imports
+### Nested Imports
 
 The imported files can themselves contain imports, creating a nested structure:
 
@@ -73,9 +73,9 @@ The imported files can themselves contain imports, creating a nested structure:
 @./shared/title.md
 ```
 
-## Safety features
+## Safety Features
 
-### Circular import detection
+### Circular Import Detection
 
 The processor automatically detects and prevents circular imports:
 
@@ -89,37 +89,37 @@ The processor automatically detects and prevents circular imports:
 @./file-a.md <!-- This will be detected and prevented -->
 ```
 
-### File access security
+### File Access Security
 
 The `validateImportPath` function ensures that imports are only allowed from
 specified directories, preventing access to sensitive files outside the allowed
 scope.
 
-### Maximum import depth
+### Maximum Import Depth
 
 To prevent infinite recursion, there's a configurable maximum import depth
 (default: 5 levels).
 
-## Error handling
+## Error Handling
 
-### Missing files
+### Missing Files
 
 If a referenced file doesn't exist, the import will fail gracefully with an
 error comment in the output.
 
-### File access errors
+### File Access Errors
 
 Permission issues or other file system errors are handled gracefully with
 appropriate error messages.
 
-## Code region detection
+## Code Region Detection
 
 The import processor uses the `marked` library to detect code blocks and inline
 code spans, ensuring that `@` imports inside these regions are properly ignored.
 This provides robust handling of nested code blocks and complex Markdown
 structures.
 
-## Import tree structure
+## Import Tree Structure
 
 The processor returns an import tree that shows the hierarchy of imported files,
 similar to Claude's `/memory` feature. This helps users debug problems with
@@ -143,7 +143,7 @@ Memory Files
 The tree preserves the order that files were imported and shows the complete
 import chain for debugging purposes.
 
-## Comparison to Claude Code's `/memory` (`claude.md`) approach
+## Comparison to Claude Code's `/memory` (`claude.md`) Approach
 
 Claude Code's `/memory` feature (as seen in `claude.md`) produces a flat, linear
 document by concatenating all included files, always marking file boundaries
@@ -154,7 +154,7 @@ for reconstructing the hierarchy if needed.
 > [!NOTE] The import tree is mainly for clarity during development and has
 > limited relevance to LLM consumption.
 
-## API reference
+## API Reference
 
 ### `processImports(content, basePath, debugMode?, importState?)`
 
@@ -225,7 +225,7 @@ directory if no `.git` is found)
 
 ## Troubleshooting
 
-### Common issues
+### Common Issues
 
 1. **Import not working**: Check that the file exists and the path is correct
 2. **Circular import warnings**: Review your import structure for circular
@@ -235,7 +235,7 @@ directory if no `.git` is found)
 4. **Path resolution issues**: Use absolute paths if relative paths aren't
    resolving correctly
 
-### Debug mode
+### Debug Mode
 
 Enable debug mode to see detailed logging of the import process:
 

docs/core/policy-engine.md

@@ -1,267 +0,0 @@
-# Policy engine
-
-The Gemini CLI includes a powerful policy engine that provides fine-grained
-control over tool execution. It allows users and administrators to define rules
-that determine whether a tool call should be allowed, denied, or require user
-confirmation.
-
-## Quick start
-
-To create your first policy:
-
-1.  **Create the policy directory** if it doesn't exist:
-    ```bash
-    mkdir -p ~/.gemini/policies
-    ```
-2.  **Create a new policy file** (e.g., `~/.gemini/policies/my-rules.toml`). You
-    can use any filename ending in `.toml`; all such files in this directory
-    will be loaded and combined:
-    ```toml
-    [[rule]]
-    toolName = "run_shell_command"
-    commandPrefix = "git status"
-    decision = "allow"
-    priority = 100
-    ```
-3.  **Run a command** that triggers the policy (e.g., ask Gemini CLI to
-    `git status`). The tool will now execute automatically without prompting for
-    confirmation.
-
-## Core concepts
-
-The policy engine operates on a set of rules. Each rule is a combination of
-conditions and a resulting decision. When a large language model wants to
-execute a tool, the policy engine evaluates all rules to find the
-highest-priority rule that matches the tool call.
-
-A rule consists of the following main components:
-
-- **Conditions**: Criteria that a tool call must meet for the rule to apply.
-  This can include the tool's name, the arguments provided to it, or the current
-  approval mode.
-- **Decision**: The action to take if the rule matches (`allow`, `deny`, or
-  `ask_user`).
-- **Priority**: A number that determines the rule's precedence. Higher numbers
-  win.
-
-For example, this rule will ask for user confirmation before executing any `git`
-command.
-
-```toml
-[[rule]]
-toolName = "run_shell_command"
-commandPrefix = "git "
-decision = "ask_user"
-priority = 100
-```
-
-### Conditions
-
-Conditions are the criteria that a tool call must meet for a rule to apply. The
-primary conditions are the tool's name and its arguments.
-
-#### Tool Name
-
-The `toolName` in the rule must match the name of the tool being called.
-
-- **Wildcards**: For Model-hosting-protocol (MCP) servers, you can use a
-  wildcard. A `toolName` of `my-server__*` will match any tool from the
-  `my-server` MCP.
-
-#### Arguments pattern
-
-If `argsPattern` is specified, the tool's arguments are converted to a stable
-JSON string, which is then tested against the provided regular expression. If
-the arguments don't match the pattern, the rule does not apply.
-
-### Decisions
-
-There are three possible decisions a rule can enforce:
-
-- `allow`: The tool call is executed automatically without user interaction.
-- `deny`: The tool call is blocked and is not executed.
-- `ask_user`: The user is prompted to approve or deny the tool call. (In
-  non-interactive mode, this is treated as `deny`.)
-
-### Priority system and tiers
-
-The policy engine uses a sophisticated priority system to resolve conflicts when
-multiple rules match a single tool call. The core principle is simple: **the
-rule with the highest priority wins**.
-
-To provide a clear hierarchy, policies are organized into three tiers. Each tier
-has a designated number that forms the base of the final priority calculation.
-
-| Tier    | Base | Description                                                                |
-| :------ | :--- | :------------------------------------------------------------------------- |
-| Default | 1    | Built-in policies that ship with the Gemini CLI.                           |
-| User    | 2    | Custom policies defined by the user.                                       |
-| Admin   | 3    | Policies managed by an administrator (e.g., in an enterprise environment). |
-
-Within a TOML policy file, you assign a priority value from **0 to 999**. The
-engine transforms this into a final priority using the following formula:
-
-`final_priority = tier_base + (toml_priority / 1000)`
-
-This system guarantees that:
-
-- Admin policies always override User and Default policies.
-- User policies always override Default policies.
-- You can still order rules within a single tier with fine-grained control.
-
-For example:
-
-- A `priority: 50` rule in a Default policy file becomes `1.050`.
-- A `priority: 100` rule in a User policy file becomes `2.100`.
-- A `priority: 20` rule in an Admin policy file becomes `3.020`.
-
-### Approval modes
-
-Approval modes allow the policy engine to apply different sets of rules based on
-the CLI's operational mode. A rule can be associated with one or more modes
-(e.g., `yolo`, `autoEdit`). The rule will only be active if the CLI is running
-in one of its specified modes. If a rule has no modes specified, it is always
-active.
-
-## Rule matching
-
-When a tool call is made, the engine checks it against all active rules,
-starting from the highest priority. The first rule that matches determines the
-outcome.
-
-A rule matches a tool call if all of its conditions are met:
-
-1.  **Tool name**: The `toolName` in the rule must match the name of the tool
-    being called.
-    - **Wildcards**: For Model-hosting-protocol (MCP) servers, you can use a
-      wildcard. A `toolName` of `my-server__*` will match any tool from the
-      `my-server` MCP.
-2.  **Arguments pattern**: If `argsPattern` is specified, the tool's arguments
-    are converted to a stable JSON string, which is then tested against the
-    provided regular expression. If the arguments don't match the pattern, the
-    rule does not apply.
-
-## Configuration
-
-Policies are defined in `.toml` files. The CLI loads these files from Default,
-User, and (if configured) Admin directories.
-
-### TOML rule schema
-
-Here is a breakdown of the fields available in a TOML policy rule:
-
-```toml
-[[rule]]
-# A unique name for the tool, or an array of names.
-toolName = "run_shell_command"
-
-# (Optional) The name of an MCP server. Can be combined with toolName
-# to form a composite name like "mcpName__toolName".
-mcpName = "my-custom-server"
-
-# (Optional) A regex to match against the tool's arguments.
-argsPattern = '"command":"(git|npm)'
-
-# (Optional) A string or array of strings that a shell command must start with.
-# This is syntactic sugar for `toolName = "run_shell_command"` and an `argsPattern`.
-commandPrefix = "git "
-
-# (Optional) A regex to match against the entire shell command.
-# This is also syntactic sugar for `toolName = "run_shell_command"`.
-# Note: This pattern is tested against the JSON representation of the arguments (e.g., `{"command":"<your_command>"}`), so anchors like `^` or `$` will apply to the full JSON string, not just the command text.
-# You cannot use commandPrefix and commandRegex in the same rule.
-commandRegex = "^git (commit|push)"
-
-# The decision to take. Must be "allow", "deny", or "ask_user".
-decision = "ask_user"
-
-# The priority of the rule, from 0 to 999.
-priority = 10
-
-# (Optional) An array of approval modes where this rule is active.
-modes = ["autoEdit"]
-```
-
-### Using arrays (lists)
-
-To apply the same rule to multiple tools or command prefixes, you can provide an
-array of strings for the `toolName` and `commandPrefix` fields.
-
-**Example:**
-
-This single rule will apply to both the `write_file` and `replace` tools.
-
-```toml
-[[rule]]
-toolName = ["write_file", "replace"]
-decision = "ask_user"
-priority = 10
-```
-
-### Special syntax for `run_shell_command`
-
-To simplify writing policies for `run_shell_command`, you can use
-`commandPrefix` or `commandRegex` instead of the more complex `argsPattern`.
-
-- `commandPrefix`: Matches if the `command` argument starts with the given
-  string.
-- `commandRegex`: Matches if the `command` argument matches the given regular
-  expression.
-
-**Example:**
-
-This rule will ask for user confirmation before executing any `git` command.
-
-```toml
-[[rule]]
-toolName = "run_shell_command"
-commandPrefix = "git "
-decision = "ask_user"
-priority = 100
-```
-
-### Special syntax for MCP tools
-
-You can create rules that target tools from Model-hosting-protocol (MCP) servers
-using the `mcpName` field or a wildcard pattern.
-
-**1. Using `mcpName`**
-
-To target a specific tool from a specific server, combine `mcpName` and
-`toolName`.
-
-```toml
-# Allows the `search` tool on the `my-jira-server` MCP
-[[rule]]
-mcpName = "my-jira-server"
-toolName = "search"
-decision = "allow"
-priority = 200
-```
-
-**2. Using a wildcard**
-
-To create a rule that applies to _all_ tools on a specific MCP server, specify
-only the `mcpName`.
-
-```toml
-# Denies all tools from the `untrusted-server` MCP
-[[rule]]
-mcpName = "untrusted-server"
-decision = "deny"
-priority = 500
-```
-
-## Default policies
-
-The Gemini CLI ships with a set of default policies to provide a safe
-out-of-the-box experience.
-
-- **Read-only tools** (like `read_file`, `glob`) are generally **allowed**.
-- **Agent delegation** (like `delegate_to_agent`) is **allowed** (sub-agent
-  actions are checked individually).
-- **Write tools** (like `write_file`, `run_shell_command`) default to
-  **`ask_user`**.
-- In **`yolo`** mode, a high-priority rule allows all tools.
-- In **`autoEdit`** mode, rules allow certain write operations to happen without
-  prompting.

docs/core/tools-api.md

@@ -1,11 +1,11 @@
-# Gemini CLI core: Tools API
+# Gemini CLI Core: Tools API
 
 The Gemini CLI core (`packages/core`) features a robust system for defining,
 registering, and executing tools. These tools extend the capabilities of the
 Gemini model, allowing it to interact with the local environment, fetch web
 content, and perform various actions beyond simple text generation.
 
-## Core concepts
+## Core Concepts
 
 - **Tool (`tools.ts`):** An interface and base class (`BaseTool`) that defines
   the contract for all tools. Each tool must have:
@@ -32,37 +32,38 @@ content, and perform various actions beyond simple text generation.
   - `returnDisplay`: A user-friendly string (often Markdown) or a special object
     (like `FileDiff`) for display in the CLI.
 
-- **Returning rich content:** Tools are not limited to returning simple text.
+- **Returning Rich Content:** Tools are not limited to returning simple text.
   The `llmContent` can be a `PartListUnion`, which is an array that can contain
   a mix of `Part` objects (for images, audio, etc.) and `string`s. This allows a
   single tool execution to return multiple pieces of rich content.
 
-- **Tool registry (`tool-registry.ts`):** A class (`ToolRegistry`) responsible
+- **Tool Registry (`tool-registry.ts`):** A class (`ToolRegistry`) responsible
   for:
-  - **Registering tools:** Holding a collection of all available built-in tools
+  - **Registering Tools:** Holding a collection of all available built-in tools
     (e.g., `ReadFileTool`, `ShellTool`).
-  - **Discovering tools:** It can also discover tools dynamically:
-    - **Command-based discovery:** If `tools.discoveryCommand` is configured in
+  - **Discovering Tools:** It can also discover tools dynamically:
+    - **Command-based Discovery:** If `tools.discoveryCommand` is configured in
       settings, this command is executed. It's expected to output JSON
       describing custom tools, which are then registered as `DiscoveredTool`
       instances.
-    - **MCP-based discovery:** If `mcp.serverCommand` is configured, the
+    - **MCP-based Discovery:** If `mcp.serverCommand` is configured, the
       registry can connect to a Model Context Protocol (MCP) server to list and
       register tools (`DiscoveredMCPTool`).
-  - **Providing schemas:** Exposing the `FunctionDeclaration` schemas of all
+  - **Providing Schemas:** Exposing the `FunctionDeclaration` schemas of all
     registered tools to the Gemini model, so it knows what tools are available
     and how to use them.
-  - **Retrieving tools:** Allowing the core to get a specific tool by name for
+  - **Retrieving Tools:** Allowing the core to get a specific tool by name for
     execution.
 
-## Built-in tools
+## Built-in Tools
 
 The core comes with a suite of pre-defined tools, typically found in
 `packages/core/src/tools/`. These include:
 
-- **File system tools:**
+- **File System Tools:**
   - `LSTool` (`ls.ts`): Lists directory contents.
-  - `ReadFileTool` (`read-file.ts`): Reads the content of a single file.
+  - `ReadFileTool` (`read-file.ts`): Reads the content of a single file. It
+    takes an `absolute_path` parameter, which must be an absolute path.
   - `WriteFileTool` (`write-file.ts`): Writes content to a file.
   - `GrepTool` (`grep.ts`): Searches for patterns in files.
   - `GlobTool` (`glob.ts`): Finds files matching glob patterns.
@@ -70,26 +71,26 @@ The core comes with a suite of pre-defined tools, typically found in
     requiring confirmation).
   - `ReadManyFilesTool` (`read-many-files.ts`): Reads and concatenates content
     from multiple files or glob patterns (used by the `@` command in CLI).
-- **Execution tools:**
+- **Execution Tools:**
   - `ShellTool` (`shell.ts`): Executes arbitrary shell commands (requires
     careful sandboxing and user confirmation).
-- **Web tools:**
+- **Web Tools:**
   - `WebFetchTool` (`web-fetch.ts`): Fetches content from a URL.
   - `WebSearchTool` (`web-search.ts`): Performs a web search.
-- **Memory tools:**
+- **Memory Tools:**
   - `MemoryTool` (`memoryTool.ts`): Interacts with the AI's memory.
 
 Each of these tools extends `BaseTool` and implements the required methods for
 its specific functionality.
 
-## Tool execution flow
+## Tool Execution Flow
 
-1.  **Model request:** The Gemini model, based on the user's prompt and the
+1.  **Model Request:** The Gemini model, based on the user's prompt and the
     provided tool schemas, decides to use a tool and returns a `FunctionCall`
     part in its response, specifying the tool name and arguments.
-2.  **Core receives request:** The core parses this `FunctionCall`.
-3.  **Tool retrieval:** It looks up the requested tool in the `ToolRegistry`.
-4.  **Parameter validation:** The tool's `validateToolParams()` method is
+2.  **Core Receives Request:** The core parses this `FunctionCall`.
+3.  **Tool Retrieval:** It looks up the requested tool in the `ToolRegistry`.
+4.  **Parameter Validation:** The tool's `validateToolParams()` method is
     called.
 5.  **Confirmation (if needed):**
     - The tool's `shouldConfirmExecute()` method is called.
@@ -99,27 +100,27 @@ its specific functionality.
 6.  **Execution:** If validated and confirmed (or if no confirmation is needed),
     the core calls the tool's `execute()` method with the provided arguments and
     an `AbortSignal` (for potential cancellation).
-7.  **Result processing:** The `ToolResult` from `execute()` is received by the
+7.  **Result Processing:** The `ToolResult` from `execute()` is received by the
     core.
-8.  **Response to model:** The `llmContent` from the `ToolResult` is packaged as
+8.  **Response to Model:** The `llmContent` from the `ToolResult` is packaged as
     a `FunctionResponse` and sent back to the Gemini model so it can continue
     generating a user-facing response.
-9.  **Display to user:** The `returnDisplay` from the `ToolResult` is sent to
+9.  **Display to User:** The `returnDisplay` from the `ToolResult` is sent to
     the CLI to show the user what the tool did.
 
-## Extending with custom tools
+## Extending with Custom Tools
 
 While direct programmatic registration of new tools by users isn't explicitly
 detailed as a primary workflow in the provided files for typical end-users, the
 architecture supports extension through:
 
-- **Command-based discovery:** Advanced users or project administrators can
+- **Command-based Discovery:** Advanced users or project administrators can
   define a `tools.discoveryCommand` in `settings.json`. This command, when run
   by the Gemini CLI core, should output a JSON array of `FunctionDeclaration`
   objects. The core will then make these available as `DiscoveredTool`
   instances. The corresponding `tools.callCommand` would then be responsible for
   actually executing these custom tools.
-- **MCP server(s):** For more complex scenarios, one or more MCP servers can be
+- **MCP Server(s):** For more complex scenarios, one or more MCP servers can be
   set up and configured via the `mcpServers` setting in `settings.json`. The
   Gemini CLI core can then discover and use tools exposed by these servers. As
   mentioned, if you have multiple MCP servers, the tool names will be prefixed

docs/examples/proxy-script.md

@@ -1,4 +1,4 @@
-# Example proxy script
+# Example Proxy Script
 
 The following is an example of a proxy script that can be used with the
 `GEMINI_SANDBOX_PROXY_COMMAND` environment variable. This script only allows

docs/extensions/extension-releasing.md

@@ -1,4 +1,4 @@
-# Extension releasing
+# Extension Releasing
 
 There are two primary ways of releasing extensions to users:
 
@@ -15,9 +15,11 @@ if you need to ship platform specific binary files.
 
 This is the most flexible and simple option. All you need to do is create a
 publicly accessible git repo (such as a public github repository) and then users
-can install your extension using `gemini extensions install <your-repo-uri>`.
-They can optionally depend on a specific ref (branch/tag/commit) using the
-`--ref=<some-ref>` argument, this defaults to the default branch.
+can install your extension using `gemini extensions install <your-repo-uri>`, or
+for a GitHub repository they can use the simplified
+`gemini extensions install <org>/<repo>` format. They can optionally depend on a
+specific ref (branch/tag/commit) using the `--ref=<some-ref>` argument, this
+defaults to the default branch.
 
 Whenever commits are pushed to the ref that a user depends on, they will be
 prompted to update the extension. Note that this also allows for easy rollbacks,
@@ -64,7 +66,7 @@ If you plan on doing cherry picks, you may want to avoid having your default
 branch be the stable branch to avoid force-pushing to the default branch which
 should generally be avoided.
 
-## Releasing through GitHub releases
+## Releasing through Github releases
 
 Gemini CLI extensions can be distributed through
 [GitHub Releases](https://docs.github.com/en/repositories/releasing-projects-on-github/about-releases).
@@ -105,9 +107,9 @@ To ensure Gemini CLI can automatically find the correct release asset for each
 platform, you must follow this naming convention. The CLI will search for assets
 in the following order:
 
-1.  **Platform and architecture-Specific:**
+1.  **Platform and Architecture-Specific:**
     `{platform}.{arch}.{name}.{extension}`
-2.  **Platform-specific:** `{platform}.{name}.{extension}`
+2.  **Platform-Specific:** `{platform}.{name}.{extension}`
 3.  **Generic:** If only one asset is provided, it will be used as a generic
     fallback.
 

docs/extensions/getting-started-extensions.md

@@ -1,4 +1,4 @@
-# Getting started with Gemini CLI extensions
+# Getting Started with Gemini CLI Extensions
 
 This guide will walk you through creating your first Gemini CLI extension.
 You'll learn how to set up a new extension, add a custom tool via an MCP server,
@@ -10,7 +10,7 @@ file.
 Before you start, make sure you have the Gemini CLI installed and a basic
 understanding of Node.js and TypeScript.
 
-## Step 1: Create a new extension
+## Step 1: Create a New Extension
 
 The easiest way to start is by using one of the built-in templates. We'll use
 the `mcp-server` example as our foundation.
@@ -32,7 +32,7 @@ my-first-extension/
 └── tsconfig.json
 ```
 
-## Step 2: Understand the extension files
+## Step 2: Understand the Extension Files
 
 Let's look at the key files in your new extension.
 
@@ -124,7 +124,7 @@ These are standard configuration files for a TypeScript project. The
 `package.json` file defines dependencies and a `build` script, and
 `tsconfig.json` configures the TypeScript compiler.
 
-## Step 3: Build and link your extension
+## Step 3: Build and Link Your Extension
 
 Before you can use the extension, you need to compile the TypeScript code and
 link the extension to your Gemini CLI installation for local development.
@@ -158,7 +158,7 @@ link the extension to your Gemini CLI installation for local development.
 Now, restart your Gemini CLI session. The new `fetch_posts` tool will be
 available. You can test it by asking: "fetch posts".
 
-## Step 4: Add a custom command
+## Step 4: Add a Custom Command
 
 Custom commands provide a way to create shortcuts for complex prompts. Let's add
 a command that searches for a pattern in your code.
@@ -186,7 +186,7 @@ a command that searches for a pattern in your code.
 After saving the file, restart the Gemini CLI. You can now run
 `/fs:grep-code "some pattern"` to use your new command.
 
-## Step 5: Add a custom `GEMINI.md`
+## Step 5: Add a Custom `GEMINI.md`
 
 You can provide persistent context to the model by adding a `GEMINI.md` file to
 your extension. This is useful for giving the model instructions on how to
@@ -222,7 +222,7 @@ need this for extensions built to expose commands and prompts.
 Restart the CLI again. The model will now have the context from your `GEMINI.md`
 file in every session where the extension is active.
 
-## Step 6: Releasing your extension
+## Step 6: Releasing Your Extension
 
 Once you are happy with your extension, you can share it with others. The two
 primary ways of releasing extensions are via a Git repository or through GitHub

docs/extensions/index.md

@@ -1,4 +1,4 @@
-# Gemini CLI extensions
+# Gemini CLI Extensions
 
 _This documentation is up-to-date with the v0.4.0 release._
 
@@ -42,23 +42,19 @@ installed on your machine. See
 for help.
 
 ```
-gemini extensions install <source> [--ref <ref>] [--auto-update] [--pre-release] [--consent]
+gemini extensions install https://github.com/gemini-cli-extensions/security
 ```
 
-- `<source>`: The github URL or local path of the extension to install.
-- `--ref`: The git ref to install from.
-- `--auto-update`: Enable auto-update for this extension.
-- `--pre-release`: Enable pre-release versions for this extension.
-- `--consent`: Acknowledge the security risks of installing an extension and
-  skip the confirmation prompt.
+This will install the Gemini CLI Security extension, which offers support for a
+`/security:analyze` command.
 
 ### Uninstalling an extension
 
-To uninstall one or more extensions, run
-`gemini extensions uninstall <name...>`:
+To uninstall, run `gemini extensions uninstall extension-name`, so, in the case
+of the install example:
 
 ```
-gemini extensions uninstall gemini-cli-security gemini-cli-another-extension
+gemini extensions uninstall gemini-cli-security
 ```
 
 ### Disabling an extension
@@ -66,31 +62,27 @@ gemini extensions uninstall gemini-cli-security gemini-cli-another-extension
 Extensions are, by default, enabled across all workspaces. You can disable an
 extension entirely or for specific workspace.
 
-```
-gemini extensions disable <name> [--scope <scope>]
-```
-
-- `<name>`: The name of the extension to disable.
-- `--scope`: The scope to disable the extension in (`user` or `workspace`).
+For example, `gemini extensions disable extension-name` will disable the
+extension at the user level, so it will be disabled everywhere.
+`gemini extensions disable extension-name --scope=workspace` will only disable
+the extension in the current workspace.
 
 ### Enabling an extension
 
-You can enable extensions using `gemini extensions enable <name>`. You can also
-enable an extension for a specific workspace using
-`gemini extensions enable <name> --scope=workspace` from within that workspace.
+You can enable extensions using `gemini extensions enable extension-name`. You
+can also enable an extension for a specific workspace using
+`gemini extensions enable extension-name --scope=workspace` from within that
+workspace.
 
-```
-gemini extensions enable <name> [--scope <scope>]
-```
-
-- `<name>`: The name of the extension to enable.
-- `--scope`: The scope to enable the extension in (`user` or `workspace`).
+This is useful if you have an extension disabled at the top-level and only
+enabled in specific places.
 
 ### Updating an extension
 
 For extensions installed from a local path or a git repository, you can
 explicitly update to the latest version (as reflected in the
-`gemini-extension.json` `version` field) with `gemini extensions update <name>`.
+`gemini-extension.json` `version` field) with
+`gemini extensions update extension-name`.
 
 You can update all extensions with:
 
@@ -98,6 +90,10 @@ You can update all extensions with:
 gemini extensions update --all
 ```
 
+## Extension creation
+
+We offer commands to make extension development easier.
+
 ### Create a boilerplate extension
 
 We offer several example extensions `context`, `custom-commands`,
@@ -108,12 +104,9 @@ To copy one of these examples into a development directory using the type of
 your choosing, run:
 
 ```
-gemini extensions new <path> [template]
+gemini extensions new path/to/directory custom-commands
 ```
 
-- `<path>`: The path to create the extension in.
-- `[template]`: The boilerplate template to use.
-
 ### Link a local extension
 
 The `gemini extensions link` command will create a symbolic link from the
@@ -123,11 +116,9 @@ This is useful so you don't have to run `gemini extensions update` every time
 you make changes you'd like to test.
 
 ```
-gemini extensions link <path>
+gemini extensions link path/to/directory
 ```
 
-- `<path>`: The path of the extension to link.
-
 ## How it works
 
 On startup, Gemini CLI looks for extensions in `<home>/.gemini/extensions`
@@ -163,11 +154,11 @@ The file has the following structure:
   your extension in the CLI. Note that we expect this name to match the
   extension directory name.
 - `version`: The version of the extension.
-- `mcpServers`: A map of MCP servers to settings. The key is the name of the
+- `mcpServers`: A map of MCP servers to configure. The key is the name of the
   server, and the value is the server configuration. These servers will be
-  loaded on startup just like MCP servers settingsd in a
+  loaded on startup just like MCP servers configured in a
   [`settings.json` file](../get-started/configuration.md). If both an extension
-  and a `settings.json` file settings an MCP server with the same name, the
+  and a `settings.json` file configure an MCP server with the same name, the
   server defined in the `settings.json` file takes precedence.
   - Note that all MCP server configuration options are supported except for
     `trust`.
@@ -186,58 +177,6 @@ When Gemini CLI starts, it loads all the extensions and merges their
 configurations. If there are any conflicts, the workspace configuration takes
 precedence.
 
-### Settings
-
-_Note: This is an experimental feature. We do not yet recommend extension
-authors introduce settings as part of their core flows._
-
-Extensions can define settings that the user will be prompted to provide upon
-installation. This is useful for things like API keys, URLs, or other
-configuration that the extension needs to function.
-
-To define settings, add a `settings` array to your `gemini-extension.json` file.
-Each object in the array should have the following properties:
-
-- `name`: A user-friendly name for the setting.
-- `description`: A description of the setting and what it's used for.
-- `envVar`: The name of the environment variable that the setting will be stored
-  as.
-- `sensitive`: Optional boolean. If true, obfuscates the input the user provides
-  and stores the secret in keychain storage. **Example**
-
-```json
-{
-  "name": "my-api-extension",
-  "version": "1.0.0",
-  "settings": [
-    {
-      "name": "API Key",
-      "description": "Your API key for the service.",
-      "envVar": "MY_API_KEY"
-    }
-  ]
-}
-```
-
-When a user installs this extension, they will be prompted to enter their API
-key. The value will be saved to a `.env` file in the extension's directory
-(e.g., `<home>/.gemini/extensions/my-api-extension/.env`).
-
-You can view a list of an extension's settings by running:
-
-```
-gemini extensions settings list <extension name>
-```
-
-and you can update a given setting using:
-
-```
-gemini extensions settings set <extension name> <setting name> [--scope <scope>]
-```
-
-- `--scope`: The scope to set the setting in (`user` or `workspace`). This is
-  optional and will default to `user`.
-
 ### Custom commands
 
 Extensions can provide [custom commands](../cli/custom-commands.md) by placing

docs/faq.md

@@ -1,4 +1,4 @@
-# Frequently asked questions (FAQ)
+# Frequently Asked Questions (FAQ)
 
 This page provides answers to common questions and solutions to frequent
 problems encountered while using Gemini CLI.

docs/get-started/authentication.md

@@ -1,198 +1,196 @@
-# Gemini CLI authentication setup
+# Gemini CLI Authentication Setup
 
-To use Gemini CLI, you'll need to authenticate with Google. This guide helps you
-quickly find the best way to sign in based on your account type and how you're
-using the CLI.
+Gemini CLI requires authentication using Google's services. Before using Gemini
+CLI, configure **one** of the following authentication methods:
 
-For most users, we recommend starting Gemini CLI and logging in with your
-personal Google account.
+- Interactive mode:
+  - Recommended: Login with Google
+  - Use Gemini API key
+  - Use Vertex AI
+- Headless (non-interactive) mode
+- Google Cloud Shell
 
-## Choose your authentication method <a id="auth-methods"></a>
+## Quick Check: Running in Google Cloud Shell?
 
-Select the authentication method that matches your situation in the table below:
+If you are running the Gemini CLI within a Google Cloud Shell environment,
+authentication is typically automatic using your Cloud Shell credentials.
 
-| User Type / Scenario                                                   | Recommended Authentication Method                                | Google Cloud Project Required                               |
-| :--------------------------------------------------------------------- | :--------------------------------------------------------------- | :---------------------------------------------------------- |
-| Individual Google accounts                                             | [Login with Google](#login-google)                               | No, with exceptions                                         |
-| Organization users with a company, school, or Google Workspace account | [Login with Google](#login-google)                               | [Yes](#set-gcp)                                             |
-| AI Studio user with a Gemini API key                                   | [Use Gemini API Key](#gemini-api)                                | No                                                          |
-| Google Cloud Vertex AI user                                            | [Vertex AI](#vertex-ai)                                          | [Yes](#set-gcp)                                             |
-| [Headless mode](#headless)                                             | [Use Gemini API Key](#gemini-api) or<br> [Vertex AI](#vertex-ai) | No (for Gemini API Key)<br> [Yes](#set-gcp) (for Vertex AI) |
+## Authenticate in Interactive mode
 
-### What is my Google account type?
+When you run Gemini CLI through the command-line, Gemini CLI will provide the
+following options:
 
-- **Individual Google accounts:** Includes all
-  [free tier accounts](../quota-and-pricing/#free-usage) such as Gemini Code
-  Assist for individuals, as well as paid subscriptions for
-  [Google AI Pro and Ultra](https://gemini.google/subscriptions/).
+```bash
+> 1. Login with Google
+> 2. Use Gemini API key
+> 3. Vertex AI
+```
 
-- **Organization accounts:** Accounts using paid licenses through an
-  organization such as a company, school, or
-  [Google Workspace](https://workspace.google.com/). Includes
-  [Google AI Ultra for Business](https://support.google.com/a/answer/16345165)
-  subscriptions.
+The following sections provide instructions for each of these authentication
+options.
 
-## (Recommended) Login with Google <a id="login-google"></a>
+### Recommended: Login with Google
 
-If you run Gemini CLI on your local machine, the simplest authentication method
-is logging in with your Google account. This method requires a web browser on a
-machine that can communicate with the terminal running Gemini CLI (e.g., your
-local machine).
+If you are running Gemini CLI on your local machine, the simplest method is
+logging in with your Google account.
 
-> **Important:** If you are a **Google AI Pro** or **Google AI Ultra**
-> subscriber, use the Google account associated with your subscription.
+> **Important:** Use this method if you are a **Google AI Pro** or **Google AI
+> Ultra** subscriber.
 
-To authenticate and use Gemini CLI:
+1. Select **Login with Google**. Gemini CLI will open a login prompt using your
+   web browser.
 
-1. Start the CLI:
+   If you are a **Google AI Pro** or **Google AI Ultra** subscriber, login with
+   the Google account associated with your subscription.
 
-   ```bash
-   gemini
-   ```
+2. Follow the on-screen instructions. Your credentials will be cached locally
+   for future sessions.
 
-2. Select **Login with Google**. Gemini CLI opens a login prompt using your web
-   browser. Follow the on-screen instructions. Your credentials will be cached
-   locally for future sessions.
+   > **Note:** This method requires a web browser on a machine that can
+   > communicate with the terminal running the CLI (e.g., your local machine).
+   > The browser will be redirected to a `localhost` URL that the CLI listens on
+   > during setup.
 
-### Do I need to set my Google Cloud project?
+#### (Optional) Set your Google Cloud Project
 
-Most individual Google accounts (free and paid) don't require a Google Cloud
-project for authentication. However, you'll need to set a Google Cloud project
-when you meet at least one of the following conditions:
+When you log in using a Google account, you may be prompted to select a
+`GOOGLE_CLOUD_PROJECT`.
 
-- You are using a company, school, or Google Workspace account.
-- You are using a Gemini Code Assist license from the Google Developer Program.
-- You are using a license from a Gemini Code Assist subscription.
+This can be necessary if you are:
 
-For instructions, see [Set your Google Cloud Project](#set-gcp).
+- Using a Google Workspace account.
+- Using a Gemini Code Assist license from the Google Developer Program.
+- Using a license from a Gemini Code Assist subscription.
+- Using the product outside the
+  [supported regions](https://developers.google.com/gemini-code-assist/resources/available-locations)
+  for free individual usage.
+- A Google account holder under the age of 18.
 
-## Use Gemini API key <a id="gemini-api"></a>
+If you fall into one of these categories, you must:
+
+1.  Have a Google Cloud Project ID.
+2.  [Enable the Gemini for Cloud API](https://cloud.google.com/gemini/docs/discover/set-up-gemini#enable-api).
+3.  [Configure necessary IAM access permissions](https://cloud.google.com/gemini/docs/discover/set-up-gemini#grant-iam).
+
+To set the project ID, you can export either the `GOOGLE_CLOUD_PROJECT` or
+`GOOGLE_CLOUD_PROJECT_ID` environment variable. The CLI checks for
+`GOOGLE_CLOUD_PROJECT` first, then falls back to `GOOGLE_CLOUD_PROJECT_ID` :
+
+```bash
+# Replace YOUR_PROJECT_ID with your actual Google Cloud Project ID
+# Using the standard variable:
+export GOOGLE_CLOUD_PROJECT="YOUR_PROJECT_ID"
+
+# Or, using the fallback variable:
+export GOOGLE_CLOUD_PROJECT_ID="YOUR_PROJECT_ID"
+```
+
+To make this setting persistent, see
+[Persisting Environment Variables](#persisting-environment-variables).
+
+### Use Gemini API Key
 
 If you don't want to authenticate using your Google account, you can use an API
 key from Google AI Studio.
 
-To authenticate and use Gemini CLI with a Gemini API key:
+1.  Obtain your API key from
+    [Google AI Studio](https://aistudio.google.com/app/apikey).
+2.  Set the `GEMINI_API_KEY` environment variable:
 
-1. Obtain your API key from
-   [Google AI Studio](https://aistudio.google.com/app/apikey).
+    ```bash
+    # Replace YOUR_GEMINI_API_KEY with the key from AI Studio
+    export GEMINI_API_KEY="YOUR_GEMINI_API_KEY"
+    ```
 
-2. Set the `GEMINI_API_KEY` environment variable to your key. For example:
-
-   ```bash
-   # Replace YOUR_GEMINI_API_KEY with the key from AI Studio
-   export GEMINI_API_KEY="YOUR_GEMINI_API_KEY"
-   ```
-
-   To make this setting persistent, see
-   [Persisting Environment Variables](#persisting-vars).
-
-3. Start the CLI:
-
-   ```bash
-   gemini
-   ```
-
-4. Select **Use Gemini API key**.
+To make this setting persistent, see
+[Persisting Environment Variables](#persisting-environment-variables).
 
 > **Warning:** Treat API keys, especially for services like Gemini, as sensitive
 > credentials. Protect them to prevent unauthorized access and potential misuse
 > of the service under your account.
 
-## Use Vertex AI <a id="vertex-ai"></a>
+### Use Vertex AI
 
-To use Gemini CLI with Google Cloud's Vertex AI platform, choose from the
-following authentication options:
+If you intend to use Google Cloud's Vertex AI platform, you have several
+authentication options:
 
-- A. Application Default Credentials (ADC) using `gcloud`.
-- B. Service account JSON key.
-- C. Google Cloud API key.
+- Application Default Credentials (ADC) and `gcloud`.
+- A Service Account JSON key.
+- A Google Cloud API key.
 
-Regardless of your authentication method for Vertex AI, you'll need to set
-`GOOGLE_CLOUD_PROJECT` to your Google Cloud project ID with the Vertex AI API
-enabled, and `GOOGLE_CLOUD_LOCATION` to the location of your Vertex AI resources
-or the location where you want to run your jobs.
+#### First: Set required environment variables
 
-For example:
+Regardless of your method of authentication, you'll typically need to set the
+following variables: `GOOGLE_CLOUD_PROJECT` (or `GOOGLE_CLOUD_PROJECT_ID`) and
+`GOOGLE_CLOUD_LOCATION`.
+
+To set these variables:
 
 ```bash
 # Replace with your project ID and desired location (e.g., us-central1)
+# You can use GOOGLE_CLOUD_PROJECT_ID as a fallback for GOOGLE_CLOUD_PROJECT
 export GOOGLE_CLOUD_PROJECT="YOUR_PROJECT_ID"
 export GOOGLE_CLOUD_LOCATION="YOUR_PROJECT_LOCATION"
 ```
 
-To make any Vertex AI environment variable settings persistent, see
-[Persisting Environment Variables](#persisting-vars).
+#### A. Vertex AI - Application Default Credentials (ADC) using `gcloud`
 
-#### A. Vertex AI - application default credentials (ADC) using `gcloud`
-
-Consider this authentication method if you have Google Cloud CLI installed.
+Consider this method of authentication if you have Google Cloud CLI installed.
 
 > **Note:** If you have previously set `GOOGLE_API_KEY` or `GEMINI_API_KEY`, you
 > must unset them to use ADC:
->
-> ```bash
-> unset GOOGLE_API_KEY GEMINI_API_KEY
-> ```
 
-1. Verify you have a Google Cloud project and Vertex AI API is enabled.
+```bash
+unset GOOGLE_API_KEY GEMINI_API_KEY
+```
 
-2. Log in to Google Cloud:
+1.  Ensure you have a Google Cloud project and Vertex AI API is enabled.
+2.  Log in to Google Cloud:
 
-   ```bash
-   gcloud auth application-default login
-   ```
+    ```bash
+    gcloud auth application-default login
+    ```
 
-3. [Configure your Google Cloud Project](#set-gcp).
+    See
+    [Set up Application Default Credentials](https://cloud.google.com/docs/authentication/provide-credentials-adc)
+    for details.
 
-4. Start the CLI:
+3.  Ensure `GOOGLE_CLOUD_PROJECT` (or `GOOGLE_CLOUD_PROJECT_ID`) and
+    `GOOGLE_CLOUD_LOCATION` are set.
 
-   ```bash
-   gemini
-   ```
+#### B. Vertex AI - Service Account JSON key
 
-5. Select **Vertex AI**.
-
-#### B. Vertex AI - service account JSON key
-
-Consider this method of authentication in non-interactive environments, CI/CD
-pipelines, or if your organization restricts user-based ADC or API key creation.
+Consider this method of authentication in non-interactive environments, CI/CD,
+or if your organization restricts user-based ADC or API key creation.
 
 > **Note:** If you have previously set `GOOGLE_API_KEY` or `GEMINI_API_KEY`, you
 > must unset them:
->
-> ```bash
-> unset GOOGLE_API_KEY GEMINI_API_KEY
-> ```
+
+```bash
+unset GOOGLE_API_KEY GEMINI_API_KEY
+```
 
 1.  [Create a service account and key](https://cloud.google.com/iam/docs/keys-create-delete)
     and download the provided JSON file. Assign the "Vertex AI User" role to the
     service account.
-
 2.  Set the `GOOGLE_APPLICATION_CREDENTIALS` environment variable to the JSON
-    file's absolute path. For example:
+    file's absolute path:
 
     ```bash
     # Replace /path/to/your/keyfile.json with the actual path
     export GOOGLE_APPLICATION_CREDENTIALS="/path/to/your/keyfile.json"
     ```
 
-3.  [Configure your Google Cloud Project](#set-gcp).
+3.  Ensure `GOOGLE_CLOUD_PROJECT` (or `GOOGLE_CLOUD_PROJECT_ID`) and
+    `GOOGLE_CLOUD_LOCATION` are set.
 
-4.  Start the CLI:
-
-    ```bash
-    gemini
-    ```
-
-5.  Select **Vertex AI**.
-    > **Warning:** Protect your service account key file as it gives access to
-    > your resources.
+> **Warning:** Protect your service account key file as it provides access to
+> your resources.
 
 #### C. Vertex AI - Google Cloud API key
 
 1.  Obtain a Google Cloud API key:
     [Get an API Key](https://cloud.google.com/vertex-ai/generative-ai/docs/start/api-keys?usertype=newuser).
-
 2.  Set the `GOOGLE_API_KEY` environment variable:
 
     ```bash
@@ -202,59 +200,17 @@ pipelines, or if your organization restricts user-based ADC or API key creation.
 
     > **Note:** If you see errors like
     > `"API keys are not supported by this API..."`, your organization might
-    > restrict API key usage for this service. Try the other Vertex AI
-    > authentication methods instead.
+    > restrict API key usage for this service. Try the
+    > [Service Account JSON Key](#b-vertex-ai-service-account-json-key) or
+    > [ADC](#a-vertex-ai-application-default-credentials-adc-using-gcloud)
+    > methods instead.
 
-3.  [Configure your Google Cloud Project](#set-gcp).
+To make any of these Vertex AI environment variable settings persistent, see
+[Persisting Environment Variables](#persisting-environment-variables).
 
-4.  Start the CLI:
+## Persisting Environment Variables
 
-    ```bash
-    gemini
-    ```
-
-5.  Select **Vertex AI**.
-
-## Set your Google Cloud project <a id="set-gcp"></a>
-
-> **Important:** Most individual Google accounts (free and paid) don't require a
-> Google Cloud project for authentication.
-
-When you sign in using your Google account, you may need to configure a Google
-Cloud project for Gemini CLI to use. This applies when you meet at least one of
-the following conditions:
-
-- You are using a Company, School, or Google Workspace account.
-- You are using a Gemini Code Assist license from the Google Developer Program.
-- You are using a license from a Gemini Code Assist subscription.
-
-To configure Gemini CLI to use a Google Cloud project, do the following:
-
-1.  [Find your Google Cloud Project ID](https://support.google.com/googleapi/answer/7014113).
-
-2.  [Enable the Gemini for Cloud API](https://cloud.google.com/gemini/docs/discover/set-up-gemini#enable-api).
-
-3.  [Configure necessary IAM access permissions](https://cloud.google.com/gemini/docs/discover/set-up-gemini#grant-iam).
-
-4.  Configure your environment variables. Set either the `GOOGLE_CLOUD_PROJECT`
-    or `GOOGLE_CLOUD_PROJECT_ID` variable to the project ID to use with Gemini
-    CLI. Gemini CLI checks for `GOOGLE_CLOUD_PROJECT` first, then falls back to
-    `GOOGLE_CLOUD_PROJECT_ID`.
-
-    For example, to set the `GOOGLE_CLOUD_PROJECT_ID` variable:
-
-    ```bash
-    # Replace YOUR_PROJECT_ID with your actual Google Cloud project ID
-    export GOOGLE_CLOUD_PROJECT="YOUR_PROJECT_ID"
-    ```
-
-    To make this setting persistent, see
-    [Persisting Environment Variables](#persisting-vars).
-
-## Persisting environment variables <a id="persisting-vars"></a>
-
-To avoid setting environment variables for every terminal session, you can
-persist them with the following methods:
+To avoid setting environment variables in every terminal session, you can:
 
 1.  **Add your environment variables to your shell configuration file:** Append
     the `export ...` commands to your shell's startup file (e.g., `~/.bashrc`,
@@ -267,9 +223,9 @@ persist them with the following methods:
     source ~/.bashrc
     ```
 
-    > **Warning:** Be aware that when you export API keys or service account
-    > paths in your shell configuration file, any process launched from that
-    > shell can read them.
+    > **Warning:** Be advised that when you export API keys or service account
+    > paths in your shell configuration file, any process executed from the
+    > shell can potentially read them.
 
 2.  **Use a `.env` file:** Create a `.gemini/.env` file in your project
     directory or home directory. Gemini CLI automatically loads variables from
@@ -286,31 +242,27 @@ persist them with the following methods:
     EOF
     ```
 
-Variables are loaded from the first file found, not merged.
+    Variables are loaded from the first file found, not merged.
 
-## Running in Google Cloud environments <a id="cloud-env"></a>
+## Non-interactive mode / headless environments
 
-When running Gemini CLI within certain Google Cloud environments, authentication
-is automatic.
+Non-interative mode / headless environments will use your existing
+authentication method, if an existing authentication credential is cached.
 
-In a Google Cloud Shell environment, Gemini CLI typically authenticates
-automatically using your Cloud Shell credentials. In Compute Engine
-environments, Gemini CLI automatically uses Application Default Credentials
-(ADC) from the environment's metadata server.
+If you have not already logged in with an authentication credential (such as a
+Google account), you **must** configure authentication using environment
+variables:
 
-If automatic authentication fails, use one of the interactive methods described
-on this page.
+1.  **Gemini API Key:** Set `GEMINI_API_KEY`.
+2.  **Vertex AI:**
+    - Set `GOOGLE_GENAI_USE_VERTEXAI=true`.
+    - **With Google Cloud API Key:** Set `GOOGLE_API_KEY`.
+    - **With ADC:** Ensure ADC is configured (e.g., via a service account with
+      `GOOGLE_APPLICATION_CREDENTIALS`) and set `GOOGLE_CLOUD_PROJECT` (or
+      `GOOGLE_CLOUD_PROJECT_ID`) and `GOOGLE_CLOUD_LOCATION`.
 
-## Running in headless mode <a id="headless"></a>
-
-[Headless mode](../cli/headless) will use your existing authentication method,
-if an existing authentication credential is cached.
-
-If you have not already logged in with an authentication credential, you must
-configure authentication using environment variables:
-
-- [Use Gemini API Key](#gemini-api)
-- [Vertex AI](#vertex-ai)
+The CLI will exit with an error in non-interactive mode if no suitable
+environment variables are found.
 
 ## What's next?
 

docs/get-started/configuration-v1.md

@@ -1,6 +1,6 @@
-# Gemini CLI configuration
+# Gemini CLI Configuration
 
-**Note on deprecated configuration format**
+**Note on Deprecated Configuration Format**
 
 This document describes the legacy v1 format for the `settings.json` file. This
 format is now deprecated.
@@ -132,7 +132,7 @@ contain other project-specific files related to Gemini CLI's operation, such as:
     }
     ```
 
-### Troubleshooting file search performance
+### Troubleshooting File Search Performance
 
 If you are experiencing performance issues with file searching (e.g., with `@`
 completions), especially in projects with a very large number of files, here are
@@ -144,12 +144,12 @@ a few things you can try in order of recommendation:
     the total number of files crawled is the most effective way to improve
     performance.
 
-2.  **Disable fuzzy search:** If ignoring files is not enough, you can disable
+2.  **Disable Fuzzy Search:** If ignoring files is not enough, you can disable
     fuzzy search by setting `disableFuzzySearch` to `true` in your
     `settings.json` file. This will use a simpler, non-fuzzy matching algorithm,
     which can be faster.
 
-3.  **Disable recursive file search:** As a last resort, you can disable
+3.  **Disable Recursive File Search:** As a last resort, you can disable
     recursive file search entirely by setting `enableRecursiveFileSearch` to
     `false`. This will be the fastest option as it avoids a recursive crawl of
     your project. However, it means you will need to type the full path to files
@@ -194,7 +194,7 @@ a few things you can try in order of recommendation:
     `--allowed-mcp-server-names` is set.
   - **Default:** All MCP servers are available for use by the Gemini model.
   - **Example:** `"allowMCPServers": ["myPythonServer"]`.
-  - **Security note:** This uses simple string matching on MCP server names,
+  - **Security Note:** This uses simple string matching on MCP server names,
     which can be modified. If you're a system administrator looking to prevent
     users from bypassing this, consider configuring the `mcpServers` at the
     system settings level such that the user will not be able to configure any
@@ -208,7 +208,7 @@ a few things you can try in order of recommendation:
     be ignored if `--allowed-mcp-server-names` is set.
   - **Default**: No MCP servers excluded.
   - **Example:** `"excludeMCPServers": ["myNodeServer"]`.
-  - **Security note:** This uses simple string matching on MCP server names,
+  - **Security Note:** This uses simple string matching on MCP server names,
     which can be modified. If you're a system administrator looking to prevent
     users from bypassing this, consider configuring the `mcpServers` at the
     system settings level such that the user will not be able to configure any
@@ -473,6 +473,21 @@ a few things you can try in order of recommendation:
     "loadMemoryFromIncludeDirectories": true
     ```
 
+- **`chatCompression`** (object):
+  - **Description:** Controls the settings for chat history compression, both
+    automatic and when manually invoked through the /compress command.
+  - **Properties:**
+    - **`contextPercentageThreshold`** (number): A value between 0 and 1 that
+      specifies the token threshold for compression as a percentage of the
+      model's total token limit. For example, a value of `0.6` will trigger
+      compression when the chat history exceeds 60% of the token limit.
+  - **Example:**
+    ```json
+    "chatCompression": {
+      "contextPercentageThreshold": 0.6
+    }
+    ```
+
 - **`showLineNumbers`** (boolean):
   - **Description:** Controls whether line numbers are displayed in code blocks
     in the CLI output.
@@ -538,7 +553,7 @@ a few things you can try in order of recommendation:
 }
 ```
 
-## Shell history
+## Shell History
 
 The CLI keeps a history of shell commands you run. To avoid conflicts between
 different projects, this history is stored in a project-specific directory
@@ -549,7 +564,7 @@ within your user's home folder.
     path.
   - The history is stored in a file named `shell_history`.
 
-## Environment variables and `.env` files
+## Environment Variables & `.env` Files
 
 Environment variables are a common way to configure applications, especially for
 sensitive information like API keys or for settings that might change between
@@ -566,7 +581,7 @@ loading order is:
     the home directory.
 3.  If still not found, it looks for `~/.env` (in the user's home directory).
 
-**Environment variable exclusion:** Some environment variables (like `DEBUG` and
+**Environment Variable Exclusion:** Some environment variables (like `DEBUG` and
 `DEBUG_MODE`) are automatically excluded from being loaded from project `.env`
 files to prevent interference with gemini-cli behavior. Variables from
 `.gemini/.env` files are never excluded. You can customize this behavior using
@@ -591,7 +606,7 @@ the `excludedProjectEnvVars` setting in your `settings.json` file.
   - Required for using Code Assist or Vertex AI.
   - If using Vertex AI, ensure you have the necessary permissions in this
     project.
-  - **Cloud Shell note:** When running in a Cloud Shell environment, this
+  - **Cloud Shell Note:** When running in a Cloud Shell environment, this
     variable defaults to a special project allocated for Cloud Shell users. If
     you have `GOOGLE_CLOUD_PROJECT` set in your global environment in Cloud
     Shell, it will be overridden by this default. To use a different project in
@@ -611,9 +626,6 @@ the `excludedProjectEnvVars` setting in your `settings.json` file.
 - **`GEMINI_SANDBOX`**:
   - Alternative to the `sandbox` setting in `settings.json`.
   - Accepts `true`, `false`, `docker`, `podman`, or a custom command string.
-- **`HTTP_PROXY` / `HTTPS_PROXY`**:
-  - Specifies the proxy server to use for outgoing HTTP/HTTPS requests.
-  - Example: `export HTTPS_PROXY="http://proxy.example.com:8080"`
 - **`SEATBELT_PROFILE`** (macOS specific):
   - Switches the Seatbelt (`sandbox-exec`) profile on macOS.
   - `permissive-open`: (Default) Restricts writes to the project folder (and a
@@ -639,7 +651,7 @@ the `excludedProjectEnvVars` setting in your `settings.json` file.
   - Specifies the endpoint for the code assist server.
   - This is useful for development and testing.
 
-## Command-line arguments
+## Command-Line Arguments
 
 Arguments passed directly when running the CLI can override other configurations
 for that specific session.
@@ -695,6 +707,8 @@ for that specific session.
 - **`--telemetry-log-prompts`**:
   - Enables logging of prompts for telemetry. See
     [telemetry](../cli/telemetry.md) for more information.
+- **`--checkpointing`**:
+  - Enables [checkpointing](../cli/checkpointing.md).
 - **`--extensions <extension_name ...>`** (**`-e <extension_name ...>`**):
   - Specifies a list of extensions to use for the session. If not provided, all
     available extensions are used.
@@ -702,6 +716,9 @@ for that specific session.
   - Example: `gemini -e my-extension -e my-other-extension`
 - **`--list-extensions`** (**`-l`**):
   - Lists all available extensions and exits.
+- **`--proxy`**:
+  - Sets the proxy for the CLI.
+  - Example: `--proxy http://localhost:7890`.
 - **`--include-directories <dir1,dir2,...>`**:
   - Includes additional directories in the workspace for multi-directory
     support.
@@ -714,7 +731,7 @@ for that specific session.
 - **`--version`**:
   - Displays the version of the CLI.
 
-## Context files (hierarchical instructional context)
+## Context Files (Hierarchical Instructional Context)
 
 While not strictly configuration for the CLI's _behavior_, context files
 (defaulting to `GEMINI.md` but configurable via the `contextFileName` setting)
@@ -730,7 +747,7 @@ context.
   that you want the Gemini model to be aware of during your interactions. The
   system is designed to manage this instructional context hierarchically.
 
-### Example context file content (e.g., `GEMINI.md`)
+### Example Context File Content (e.g., `GEMINI.md`)
 
 Here's a conceptual example of what a context file at the root of a TypeScript
 project might contain:
@@ -771,23 +788,23 @@ more relevant and precise your context files are, the better the AI can assist
 you. Project-specific context files are highly encouraged to establish
 conventions and context.
 
-- **Hierarchical loading and precedence:** The CLI implements a sophisticated
+- **Hierarchical Loading and Precedence:** The CLI implements a sophisticated
   hierarchical memory system by loading context files (e.g., `GEMINI.md`) from
   several locations. Content from files lower in this list (more specific)
   typically overrides or supplements content from files higher up (more
   general). The exact concatenation order and final context can be inspected
   using the `/memory show` command. The typical loading order is:
-  1.  **Global context file:**
+  1.  **Global Context File:**
       - Location: `~/.gemini/<contextFileName>` (e.g., `~/.gemini/GEMINI.md` in
         your user home directory).
       - Scope: Provides default instructions for all your projects.
-  2.  **Project root and ancestors context files:**
+  2.  **Project Root & Ancestors Context Files:**
       - Location: The CLI searches for the configured context file in the
         current working directory and then in each parent directory up to either
         the project root (identified by a `.git` folder) or your home directory.
       - Scope: Provides context relevant to the entire project or a significant
         portion of it.
-  3.  **Sub-directory context files (contextual/local):**
+  3.  **Sub-directory Context Files (Contextual/Local):**
       - Location: The CLI also scans for the configured context file in
         subdirectories _below_ the current working directory (respecting common
         ignore patterns like `node_modules`, `.git`, etc.). The breadth of this
@@ -795,15 +812,15 @@ conventions and context.
         with a `memoryDiscoveryMaxDirs` field in your `settings.json` file.
       - Scope: Allows for highly specific instructions relevant to a particular
         component, module, or subsection of your project.
-- **Concatenation and UI indication:** The contents of all found context files
-  are concatenated (with separators indicating their origin and path) and
-  provided as part of the system prompt to the Gemini model. The CLI footer
-  displays the count of loaded context files, giving you a quick visual cue
-  about the active instructional context.
-- **Importing content:** You can modularize your context files by importing
+- **Concatenation & UI Indication:** The contents of all found context files are
+  concatenated (with separators indicating their origin and path) and provided
+  as part of the system prompt to the Gemini model. The CLI footer displays the
+  count of loaded context files, giving you a quick visual cue about the active
+  instructional context.
+- **Importing Content:** You can modularize your context files by importing
   other Markdown files using the `@path/to/file.md` syntax. For more details,
   see the [Memory Import Processor documentation](../core/memport.md).
-- **Commands for memory management:**
+- **Commands for Memory Management:**
   - Use `/memory refresh` to force a re-scan and reload of all context files
     from all configured locations. This updates the AI's instructional context.
   - Use `/memory show` to display the combined instructional context currently
@@ -850,7 +867,7 @@ sandbox image:
 BUILD_SANDBOX=1 gemini -s
 ```
 
-## Usage statistics
+## Usage Statistics
 
 To help us improve the Gemini CLI, we collect anonymized usage statistics. This
 data helps us understand how the CLI is used, identify common issues, and
@@ -858,22 +875,22 @@ prioritize new features.
 
 **What we collect:**
 
-- **Tool calls:** We log the names of the tools that are called, whether they
+- **Tool Calls:** We log the names of the tools that are called, whether they
   succeed or fail, and how long they take to execute. We do not collect the
   arguments passed to the tools or any data returned by them.
-- **API requests:** We log the Gemini model used for each request, the duration
+- **API Requests:** We log the Gemini model used for each request, the duration
   of the request, and whether it was successful. We do not collect the content
   of the prompts or responses.
-- **Session information:** We collect information about the configuration of the
+- **Session Information:** We collect information about the configuration of the
   CLI, such as the enabled tools and the approval mode.
 
 **What we DON'T collect:**
 
-- **Personally identifiable information (PII):** We do not collect any personal
+- **Personally Identifiable Information (PII):** We do not collect any personal
   information, such as your name, email address, or API keys.
-- **Prompt and response content:** We do not log the content of your prompts or
+- **Prompt and Response Content:** We do not log the content of your prompts or
   the responses from the Gemini model.
-- **File content:** We do not log the content of any files that are read or
+- **File Content:** We do not log the content of any files that are read or
   written by the CLI.
 
 **How to opt out:**

docs/get-started/deployment.md

@@ -1,6 +1,6 @@
 Note: This page will be replaced by [installation.md](installation.md).
 
-# Gemini CLI installation, execution, and deployment
+# Gemini CLI Installation, Execution, and Deployment
 
 Install and run Gemini CLI. This document provides an overview of Gemini CLI's
 installation methods and deployment architecture.
@@ -44,7 +44,7 @@ downloading the Gemini CLI package from the NPM registry.
 For security and isolation, Gemini CLI can be run inside a container. This is
 the default way that the CLI executes tools that might have side effects.
 
-- **Directly from the registry:** You can run the published sandbox image
+- **Directly from the Registry:** You can run the published sandbox image
   directly. This is useful for environments where you only have Docker and want
   to run the CLI.
   ```bash
@@ -63,7 +63,7 @@ the default way that the CLI executes tools that might have side effects.
 Contributors to the project will want to run the CLI directly from the source
 code.
 
-- **Development mode:** This method provides hot-reloading and is useful for
+- **Development Mode:** This method provides hot-reloading and is useful for
   active development.
   ```bash
   # From the root of the repository

docs/get-started/examples.md

@@ -1,4 +1,4 @@
-# Gemini CLI examples
+# Gemini CLI Examples
 
 Not sure where to get started with Gemini CLI? This document covers examples on
 how to use Gemini CLI for a variety of tasks.
@@ -24,7 +24,7 @@ Rename the photos in my "photos" directory based on their contents.
 
 Result: Gemini will ask for permission to rename your files.
 
-Select **Allow once** and your files will be renamed:
+Select **Yes, allow once.** and your files will be renamed:
 
 ```bash
 photos/yellow_flowers.png
@@ -57,7 +57,7 @@ Gemini CLI will return an explanation based on the actual source code:
 The `chalk` library is a popular npm package for styling terminal output with
 colors. After analyzing the source code, here's how it works:
 
-- **Core functionality:** The main file sets up a chainable API. Each color or
+- **Core Functionality:** The main file sets up a chainable API. Each color or
   modifier (like `bold` or `italic`) is a getter that appends the corresponding
   ANSI escape code to an internal stack.
 
@@ -65,7 +65,7 @@ colors. After analyzing the source code, here's how it works:
   getters. The `red` getter adds the red color code, and the `bold` getter adds
   the bold code.
 
-- **Output generation:** When the chain is treated as a string (e.g., in
+- **Output Generation:** When the chain is treated as a string (e.g., in
   `console.log`), a final `toString()` method is called. This method joins all
   the stored ANSI codes, wraps them around the input string ('Hello'), and adds
   a reset code at the end. This produces the final, styled string that the

docs/get-started/gemini-3.md

@@ -1,116 +0,0 @@
-# Gemini 3 Pro and Gemini 3 Flash on Gemini CLI
-
-Gemini 3 Pro and Gemini 3 Flash are now available on Gemini CLI! Currently, most
-paid customers of Gemini CLI will have access to both Gemini 3 Pro and Gemini 3
-Flash, including the following subscribers:
-
-- Google AI Pro and Google AI Ultra (excluding business customers).
-- Gemini Code Assist Standard and Enterprise (requires
-  [administrative enablement](#administrator-instructions)).
-- Paid Gemini API and Vertex API key holders.
-
-For free tier users:
-
-- If you signed up for the waitlist, please check your email for details. We’ve
-  onboarded everyone who signed up to the previously available waitlist.
-- If you were not on our waitlist, we’re rolling out additional access gradually
-  to ensure the experience remains fast and reliable. Stay tuned for more
-  details.
-
-## How to get started with Gemini 3 on Gemini CLI
-
-Get started by upgrading Gemini CLI to the latest version (0.21.1):
-
-```bash
-npm install -g @google/gemini-cli@latest
-```
-
-After you’ve confirmed your version is 0.21.1 or later:
-
-1. Use the `/settings` command in Gemini CLI.
-2. Toggle **Preview Features** to `true`.
-3. Run `/model` and select **Auto (Gemini 3)**.
-
-For more information, see [Gemini CLI model selection](../cli/model.md).
-
-### Usage limits and fallback
-
-Gemini CLI will tell you when you reach your Gemini 3 Pro daily usage limit.
-When you encounter that limit, you’ll be given the option to switch to Gemini
-2.5 Pro, upgrade for higher limits, or stop. You’ll also be told when your usage
-limit resets and Gemini 3 Pro can be used again.
-
-Similarly, when you reach your daily usage limit for Gemini 2.5 Pro, you’ll see
-a message prompting fallback to Gemini 2.5 Flash.
-
-### Capacity errors
-
-There may be times when the Gemini 3 Pro model is overloaded. When that happens,
-Gemini CLI will ask you to decide whether you want to keep trying Gemini 3 Pro
-or fallback to Gemini 2.5 Pro.
-
-> **Note:** The **Keep trying** option uses exponential backoff, in which Gemini
-> CLI waits longer between each retry, when the system is busy. If the retry
-> doesn't happen immediately, please wait a few minutes for the request to
-> process.
-
-### Model selection and routing types
-
-When using Gemini CLI, you may want to control how your requests are routed
-between models. By default, Gemini CLI uses **Auto** routing.
-
-When using Gemini 3 Pro, you may want to use Auto routing or Pro routing to
-manage your usage limits:
-
-- **Auto routing:** Auto routing first determines whether a prompt involves a
-  complex or simple operation. For simple prompts, it will automatically use
-  Gemini 2.5 Flash. For complex prompts, if Gemini 3 Pro is enabled, it will use
-  Gemini 3 Pro; otherwise, it will use Gemini 2.5 Pro.
-- **Pro routing:** If you want to ensure your task is processed by the most
-  capable model, use `/model` and select **Pro**. Gemini CLI will prioritize the
-  most capable model available, including Gemini 3 Pro if it has been enabled.
-
-To learn more about selecting a model and routing, refer to
-[Gemini CLI Model Selection](../cli/model.md).
-
-## How to enable Gemini 3 with Gemini CLI on Gemini Code Assist
-
-If you're using Gemini Code Assist Standard or Gemini Code Assist Enterprise,
-enabling Gemini 3 Pro on Gemini CLI requires configuring your release channels.
-Using Gemini 3 Pro will require two steps: administrative enablement and user
-enablement.
-
-To learn more about these settings, refer to
-[Configure Gemini Code Assist release channels](https://developers.google.com/gemini-code-assist/docs/configure-release-channels).
-
-### Administrator instructions
-
-An administrator with **Google Cloud Settings Admin** permissions must follow
-these directions:
-
-- Navigate to the Google Cloud Project you're using with Gemini CLI for Code
-  Assist.
-- Go to **Admin for Gemini** > **Settings**.
-- Under **Release channels for Gemini Code Assist in local IDEs** select
-  **Preview**.
-- Click **Save changes**.
-
-### User instructions
-
-Wait for two to three minutes after your administrator has enabled **Preview**,
-then:
-
-- Open Gemini CLI.
-- Use the `/settings` command.
-- Set **Preview Features** to `true`.
-
-Restart Gemini CLI and you should have access to Gemini 3.
-
-## Need help?
-
-If you need help, we recommend searching for an existing
-[GitHub issue](https://github.com/google-gemini/gemini-cli/issues). If you
-cannot find a GitHub issue that matches your concern, you can
-[create a new issue](https://github.com/google-gemini/gemini-cli/issues/new/choose).
-For comments and feedback, consider opening a
-[GitHub discussion](https://github.com/google-gemini/gemini-cli/discussions).

docs/get-started/index.md

@@ -1,4 +1,4 @@
-# Get started with Gemini CLI
+# Get Started with Gemini CLI
 
 Welcome to Gemini CLI! This guide will help you install, configure, and start
 using the Gemini CLI to enhance your workflow right from your terminal.
@@ -28,24 +28,19 @@ For more installation options, see [Gemini CLI Installation](./installation.md).
 
 ## Authenticate
 
-To begin using Gemini CLI, you must authenticate with a Google service. In most
-cases, you can log in with your existing Google account:
+To begin using Gemini CLI, you must authenticate with a Google service. The most
+straightforward authentication method uses your existing Google account:
 
 1. Run Gemini CLI after installation:
-
    ```bash
    gemini
    ```
-
 2. When asked "How would you like to authenticate for this project?" select **1.
    Login with Google**.
-
 3. Select your Google account.
-
 4. Click on **Sign in**.
 
-Certain account types may require you to configure a Google Cloud project. For
-more information, including other authentication methods, see
+For other authentication options and information, see
 [Gemini CLI Authentication Setup](./authentication.md).
 
 ## Configure
@@ -68,4 +63,3 @@ To explore the power of Gemini CLI, see [Gemini CLI examples](./examples.md).
 
 - Find out more about [Gemini CLI's tools](../tools/index.md).
 - Review [Gemini CLI's commands](../cli/commands.md).
-- Learn how to [get started with Gemini 3](./gemini-3.md).

docs/get-started/installation.md

@@ -1,4 +1,4 @@
-# Gemini CLI installation, execution, and deployment
+# Gemini CLI Installation, Execution, and Deployment
 
 Install and run Gemini CLI. This document provides an overview of Gemini CLI's
 installation methods and deployment architecture.
@@ -42,7 +42,7 @@ downloading the Gemini CLI package from the NPM registry.
 For security and isolation, Gemini CLI can be run inside a container. This is
 the default way that the CLI executes tools that might have side effects.
 
-- **Directly from the registry:** You can run the published sandbox image
+- **Directly from the Registry:** You can run the published sandbox image
   directly. This is useful for environments where you only have Docker and want
   to run the CLI.
   ```bash
@@ -61,13 +61,13 @@ the default way that the CLI executes tools that might have side effects.
 Contributors to the project will want to run the CLI directly from the source
 code.
 
-- **Development mode:** This method provides hot-reloading and is useful for
+- **Development Mode:** This method provides hot-reloading and is useful for
   active development.
   ```bash
   # From the root of the repository
   npm run start
   ```
-- **Production-like mode (linked package):** This method simulates a global
+- **Production-like mode (Linked package):** This method simulates a global
   installation by linking your local package. It's useful for testing a local
   build in a production workflow.
 

docs/hooks/best-practices.md

@@ -1,856 +0,0 @@
-# Hooks on Gemini CLI: Best practices
-
-This guide covers security considerations, performance optimization, debugging
-techniques, and privacy considerations for developing and deploying hooks in
-Gemini CLI.
-
-## Performance
-
-### Keep hooks fast
-
-Hooks run synchronously—slow hooks delay the agent loop. Optimize for speed by
-using parallel operations:
-
-```javascript
-// Sequential operations are slower
-const data1 = await fetch(url1).then((r) => r.json());
-const data2 = await fetch(url2).then((r) => r.json());
-const data3 = await fetch(url3).then((r) => r.json());
-
-// Prefer parallel operations for better performance
-// Start requests concurrently
-const p1 = fetch(url1).then((r) => r.json());
-const p2 = fetch(url2).then((r) => r.json());
-const p3 = fetch(url3).then((r) => r.json());
-
-// Wait for all results
-const [data1, data2, data3] = await Promise.all([p1, p2, p3]);
-```
-
-### Cache expensive operations
-
-Store results between invocations to avoid repeated computation:
-
-```javascript
-const fs = require('fs');
-const path = require('path');
-
-const CACHE_FILE = '.gemini/hook-cache.json';
-
-function readCache() {
-  try {
-    return JSON.parse(fs.readFileSync(CACHE_FILE, 'utf8'));
-  } catch {
-    return {};
-  }
-}
-
-function writeCache(data) {
-  fs.writeFileSync(CACHE_FILE, JSON.stringify(data, null, 2));
-}
-
-async function main() {
-  const cache = readCache();
-  const cacheKey = `tool-list-${(Date.now() / 3600000) | 0}`; // Hourly cache
-
-  if (cache[cacheKey]) {
-    console.log(JSON.stringify(cache[cacheKey]));
-    return;
-  }
-
-  // Expensive operation
-  const result = await computeExpensiveResult();
-  cache[cacheKey] = result;
-  writeCache(cache);
-
-  console.log(JSON.stringify(result));
-}
-```
-
-### Use appropriate events
-
-Choose hook events that match your use case to avoid unnecessary execution.
-`AfterAgent` fires once per agent loop completion, while `AfterModel` fires
-after every LLM call (potentially multiple times per loop):
-
-```json
-// If checking final completion, use AfterAgent instead of AfterModel
-{
-  "hooks": {
-    "AfterAgent": [
-      {
-        "matcher": "*",
-        "hooks": [
-          {
-            "name": "final-checker",
-            "command": "./check-completion.sh"
-          }
-        ]
-      }
-    ]
-  }
-}
-```
-
-### Filter with matchers
-
-Use specific matchers to avoid unnecessary hook execution. Instead of matching
-all tools with `*`, specify only the tools you need:
-
-```json
-{
-  "matcher": "write_file|replace",
-  "hooks": [
-    {
-      "name": "validate-writes",
-      "command": "./validate.sh"
-    }
-  ]
-}
-```
-
-### Optimize JSON parsing
-
-For large inputs, use streaming JSON parsers to avoid loading everything into
-memory:
-
-```javascript
-// Standard approach: parse entire input
-const input = JSON.parse(await readStdin());
-const content = input.tool_input.content;
-
-// For very large inputs: stream and extract only needed fields
-const { createReadStream } = require('fs');
-const JSONStream = require('JSONStream');
-
-const stream = createReadStream(0).pipe(JSONStream.parse('tool_input.content'));
-let content = '';
-stream.on('data', (chunk) => {
-  content += chunk;
-});
-```
-
-## Debugging
-
-### Log to files
-
-Write debug information to dedicated log files:
-
-```bash
-#!/usr/bin/env bash
-LOG_FILE=".gemini/hooks/debug.log"
-
-# Log with timestamp
-log() {
-  echo "[$(date '+%Y-%m-%d %H:%M:%S')] $*" >> "$LOG_FILE"
-}
-
-input=$(cat)
-log "Received input: ${input:0:100}..."
-
-# Hook logic here
-
-log "Hook completed successfully"
-```
-
-### Use stderr for errors
-
-Error messages on stderr are surfaced appropriately based on exit codes:
-
-```javascript
-try {
-  const result = dangerousOperation();
-  console.log(JSON.stringify({ result }));
-} catch (error) {
-  console.error(`Hook error: ${error.message}`);
-  process.exit(2); // Blocking error
-}
-```
-
-### Test hooks independently
-
-Run hook scripts manually with sample JSON input:
-
-```bash
-# Create test input
-cat > test-input.json << 'EOF'
-{
-  "session_id": "test-123",
-  "cwd": "/tmp/test",
-  "hook_event_name": "BeforeTool",
-  "tool_name": "write_file",
-  "tool_input": {
-    "file_path": "test.txt",
-    "content": "Test content"
-  }
-}
-EOF
-
-# Test the hook
-cat test-input.json | .gemini/hooks/my-hook.sh
-
-# Check exit code
-echo "Exit code: $?"
-```
-
-### Check exit codes
-
-Ensure your script returns the correct exit code:
-
-```bash
-#!/usr/bin/env bash
-set -e  # Exit on error
-
-# Hook logic
-process_input() {
-  # ...
-}
-
-if process_input; then
-  echo "Success message"
-  exit 0
-else
-  echo "Error message" >&2
-  exit 2
-fi
-```
-
-### Enable telemetry
-
-Hook execution is logged when `telemetry.logPrompts` is enabled:
-
-```json
-{
-  "telemetry": {
-    "logPrompts": true
-  }
-}
-```
-
-View hook telemetry in logs to debug execution issues.
-
-### Use hook panel
-
-The `/hooks panel` command shows execution status and recent output:
-
-```bash
-/hooks panel
-```
-
-Check for:
-
-- Hook execution counts
-- Recent successes/failures
-- Error messages
-- Execution timing
-
-## Development
-
-### Start simple
-
-Begin with basic logging hooks before implementing complex logic:
-
-```bash
-#!/usr/bin/env bash
-# Simple logging hook to understand input structure
-input=$(cat)
-echo "$input" >> .gemini/hook-inputs.log
-echo "Logged input"
-```
-
-### Use JSON libraries
-
-Parse JSON with proper libraries instead of text processing:
-
-**Bad:**
-
-```bash
-# Fragile text parsing
-tool_name=$(echo "$input" | grep -oP '"tool_name":\s*"\K[^"]+')
-```
-
-**Good:**
-
-```bash
-# Robust JSON parsing
-tool_name=$(echo "$input" | jq -r '.tool_name')
-```
-
-### Make scripts executable
-
-Always make hook scripts executable:
-
-```bash
-chmod +x .gemini/hooks/*.sh
-chmod +x .gemini/hooks/*.js
-```
-
-### Version control
-
-Commit hooks to share with your team:
-
-```bash
-git add .gemini/hooks/
-git add .gemini/settings.json
-git commit -m "Add project hooks for security and testing"
-```
-
-**`.gitignore` considerations:**
-
-```gitignore
-# Ignore hook cache and logs
-.gemini/hook-cache.json
-.gemini/hook-debug.log
-.gemini/memory/session-*.jsonl
-
-# Keep hook scripts
-!.gemini/hooks/*.sh
-!.gemini/hooks/*.js
-```
-
-### Document behavior
-
-Add descriptions to help others understand your hooks:
-
-```json
-{
-  "hooks": {
-    "BeforeTool": [
-      {
-        "matcher": "write_file|replace",
-        "hooks": [
-          {
-            "name": "secret-scanner",
-            "type": "command",
-            "command": "$GEMINI_PROJECT_DIR/.gemini/hooks/block-secrets.sh",
-            "description": "Scans code changes for API keys, passwords, and other secrets before writing"
-          }
-        ]
-      }
-    ]
-  }
-}
-```
-
-Add comments in hook scripts:
-
-```javascript
-#!/usr/bin/env node
-/**
- * RAG Tool Filter Hook
- *
- * This hook reduces the tool space from 100+ tools to ~15 relevant ones
- * by extracting keywords from the user's request and filtering tools
- * based on semantic similarity.
- *
- * Performance: ~500ms average, cached tool embeddings
- * Dependencies: @google/generative-ai
- */
-```
-
-## Troubleshooting
-
-### Hook not executing
-
-**Check hook name in `/hooks panel`:**
-
-```bash
-/hooks panel
-```
-
-Verify the hook appears in the list and is enabled.
-
-**Verify matcher pattern:**
-
-```bash
-# Test regex pattern
-echo "write_file|replace" | grep -E "write_.*|replace"
-```
-
-**Check disabled list:**
-
-```json
-{
-  "hooks": {
-    "disabled": ["my-hook-name"]
-  }
-}
-```
-
-**Ensure script is executable:**
-
-```bash
-ls -la .gemini/hooks/my-hook.sh
-chmod +x .gemini/hooks/my-hook.sh
-```
-
-**Verify script path:**
-
-```bash
-# Check path expansion
-echo "$GEMINI_PROJECT_DIR/.gemini/hooks/my-hook.sh"
-
-# Verify file exists
-test -f "$GEMINI_PROJECT_DIR/.gemini/hooks/my-hook.sh" && echo "File exists"
-```
-
-### Hook timing out
-
-**Check configured timeout:**
-
-```json
-{
-  "name": "slow-hook",
-  "timeout": 60000
-}
-```
-
-**Optimize slow operations:**
-
-```javascript
-// Before: Sequential operations (slow)
-for (const item of items) {
-  await processItem(item);
-}
-
-// After: Parallel operations (fast)
-await Promise.all(items.map((item) => processItem(item)));
-```
-
-**Use caching:**
-
-```javascript
-const cache = new Map();
-
-async function getCachedData(key) {
-  if (cache.has(key)) {
-    return cache.get(key);
-  }
-  const data = await fetchData(key);
-  cache.set(key, data);
-  return data;
-}
-```
-
-**Consider splitting into multiple faster hooks:**
-
-```json
-{
-  "hooks": {
-    "BeforeTool": [
-      {
-        "matcher": "write_file",
-        "hooks": [
-          {
-            "name": "quick-check",
-            "command": "./quick-validation.sh",
-            "timeout": 1000
-          }
-        ]
-      },
-      {
-        "matcher": "write_file",
-        "hooks": [
-          {
-            "name": "deep-check",
-            "command": "./deep-analysis.sh",
-            "timeout": 30000
-          }
-        ]
-      }
-    ]
-  }
-}
-```
-
-### Invalid JSON output
-
-**Validate JSON before outputting:**
-
-```bash
-#!/usr/bin/env bash
-output='{"decision": "allow"}'
-
-# Validate JSON
-if echo "$output" | jq empty 2>/dev/null; then
-  echo "$output"
-else
-  echo "Invalid JSON generated" >&2
-  exit 1
-fi
-```
-
-**Ensure proper quoting and escaping:**
-
-```javascript
-// Bad: Unescaped string interpolation
-const message = `User said: ${userInput}`;
-console.log(JSON.stringify({ message }));
-
-// Good: Automatic escaping
-console.log(JSON.stringify({ message: `User said: ${userInput}` }));
-```
-
-**Check for binary data or control characters:**
-
-```javascript
-function sanitizeForJSON(str) {
-  return str.replace(/[\x00-\x1F\x7F-\x9F]/g, ''); // Remove control chars
-}
-
-const cleanContent = sanitizeForJSON(content);
-console.log(JSON.stringify({ content: cleanContent }));
-```
-
-### Exit code issues
-
-**Verify script returns correct codes:**
-
-```bash
-#!/usr/bin/env bash
-set -e  # Exit on error
-
-# Processing logic
-if validate_input; then
-  echo "Success"
-  exit 0
-else
-  echo "Validation failed" >&2
-  exit 2
-fi
-```
-
-**Check for unintended errors:**
-
-```bash
-#!/usr/bin/env bash
-# Don't use 'set -e' if you want to handle errors explicitly
-# set -e
-
-if ! command_that_might_fail; then
-  # Handle error
-  echo "Command failed but continuing" >&2
-fi
-
-# Always exit explicitly
-exit 0
-```
-
-**Use trap for cleanup:**
-
-```bash
-#!/usr/bin/env bash
-
-cleanup() {
-  # Cleanup logic
-  rm -f /tmp/hook-temp-*
-}
-
-trap cleanup EXIT
-
-# Hook logic here
-```
-
-### Environment variables not available
-
-**Check if variable is set:**
-
-```bash
-#!/usr/bin/env bash
-
-if [ -z "$GEMINI_PROJECT_DIR" ]; then
-  echo "GEMINI_PROJECT_DIR not set" >&2
-  exit 1
-fi
-
-if [ -z "$CUSTOM_VAR" ]; then
-  echo "Warning: CUSTOM_VAR not set, using default" >&2
-  CUSTOM_VAR="default-value"
-fi
-```
-
-**Debug available variables:**
-
-```bash
-#!/usr/bin/env bash
-
-# List all environment variables
-env > .gemini/hook-env.log
-
-# Check specific variables
-echo "GEMINI_PROJECT_DIR: $GEMINI_PROJECT_DIR" >> .gemini/hook-env.log
-echo "GEMINI_SESSION_ID: $GEMINI_SESSION_ID" >> .gemini/hook-env.log
-echo "GEMINI_API_KEY: ${GEMINI_API_KEY:+<set>}" >> .gemini/hook-env.log
-```
-
-**Use .env files:**
-
-```bash
-#!/usr/bin/env bash
-
-# Load .env file if it exists
-if [ -f "$GEMINI_PROJECT_DIR/.env" ]; then
-  source "$GEMINI_PROJECT_DIR/.env"
-fi
-```
-
-## Using Hooks Securely
-
-### Threat Model
-
-Understanding where hooks come from and what they can do is critical for secure
-usage.
-
-| Hook Source                   | Description                                                                                                                |
-| :---------------------------- | :------------------------------------------------------------------------------------------------------------------------- |
-| **System**                    | Configured by system administrators (e.g., `/etc/gemini-cli/settings.json`, `/Library/...`). Assumed to be the **safest**. |
-| **User** (`~/.gemini/...`)    | Configured by you. You are responsible for ensuring they are safe.                                                         |
-| **Extensions**                | You explicitly approve and install these. Security depends on the extension source (integrity).                            |
-| **Project** (`./.gemini/...`) | **Untrusted by default.** Safest in trusted internal repos; higher risk in third-party/public repos.                       |
-
-#### Project Hook Security
-
-When you open a project with hooks defined in `.gemini/settings.json`:
-
-1. **Detection**: Gemini CLI detects the hooks.
-2. **Identification**: A unique identity is generated for each hook based on its
-   `name` and `command`.
-3. **Warning**: If this specific hook identity has not been seen before, a
-   **warning** is displayed.
-4. **Execution**: The hook is executed (unless specific security settings block
-   it).
-5. **Trust**: The hook is marked as "trusted" for this project.
-
-> [!IMPORTANT] **Modification Detection**: If the `command` string of a project
-> hook is changed (e.g., by a `git pull`), its identity changes. Gemini CLI will
-> treat it as a **new, untrusted hook** and warn you again. This prevents
-> malicious actors from silently swapping a verified command for a malicious
-> one.
-
-### Risks
-
-| Risk                         | Description                                                                                                                          |
-| :--------------------------- | :----------------------------------------------------------------------------------------------------------------------------------- |
-| **Arbitrary Code Execution** | Hooks run as your user. They can do anything you can do (delete files, install software).                                            |
-| **Data Exfiltration**        | A hook could read your input (prompts), output (code), or environment variables (`GEMINI_API_KEY`) and send them to a remote server. |
-| **Prompt Injection**         | Malicious content in a file or web page could trick an LLM into running a tool that triggers a hook in an unexpected way.            |
-
-### Mitigation Strategies
-
-#### Verify the source
-
-**Verify the source** of any project hooks or extensions before enabling them.
-
-- For open-source projects, a quick review of the hook scripts is recommended.
-- For extensions, ensure you trust the author or publisher (e.g., verified
-  publishers, well-known community members).
-- Be cautious with obfuscated scripts or compiled binaries from unknown sources.
-
-#### Sanitize Environment
-
-Hooks inherit the environment of the Gemini CLI process, which may include
-sensitive API keys. Gemini CLI attempts to sanitize sensitive variables, but you
-should be cautious.
-
-- **Avoid printing environment variables** to stdout/stderr unless necessary.
-- **Use `.env` files** to securely manage sensitive variables, ensuring they are
-  excluded from version control.
-
-**System Administrators:** You can enforce environment variable redaction by
-default in the system configuration (e.g., `/etc/gemini-cli/settings.json`):
-
-```json
-{
-  "security": {
-    "environmentVariableRedaction": {
-      "enabled": true,
-      "blocked": ["MY_SECRET_KEY"],
-      "allowed": ["SAFE_VAR"]
-    }
-  }
-}
-```
-
-## Authoring Secure Hooks
-
-When writing your own hooks, follow these practices to ensure they are robust
-and secure.
-
-### Validate all inputs
-
-Never trust data from hooks without validation. Hook inputs often come from the
-LLM or user prompts, which can be manipulated.
-
-```bash
-#!/usr/bin/env bash
-input=$(cat)
-
-# Validate JSON structure
-if ! echo "$input" | jq empty 2>/dev/null; then
-  echo "Invalid JSON input" >&2
-  exit 1
-fi
-
-# Validate tool_name explicitly
-tool_name=$(echo "$input" | jq -r '.tool_name // empty')
-if [[ "$tool_name" != "write_file" && "$tool_name" != "read_file" ]]; then
-  echo "Unexpected tool: $tool_name" >&2
-  exit 1
-fi
-```
-
-### Use timeouts
-
-Prevent denial-of-service (hanging agents) by enforcing timeouts. Gemini CLI
-defaults to 60 seconds, but you should set stricter limits for fast hooks.
-
-```json
-{
-  "hooks": {
-    "BeforeTool": [
-      {
-        "matcher": "*",
-        "hooks": [
-          {
-            "name": "fast-validator",
-            "command": "./hooks/validate.sh",
-            "timeout": 5000 // 5 seconds
-          }
-        ]
-      }
-    ]
-  }
-}
-```
-
-### Limit permissions
-
-Run hooks with minimal required permissions:
-
-```bash
-#!/usr/bin/env bash
-# Don't run as root
-if [ "$EUID" -eq 0 ]; then
-  echo "Hook should not run as root" >&2
-  exit 1
-fi
-
-# Check file permissions before writing
-if [ -w "$file_path" ]; then
-  # Safe to write
-else
-  echo "Insufficient permissions" >&2
-  exit 1
-fi
-```
-
-### Example: Secret Scanner
-
-Use `BeforeTool` hooks to prevent committing sensitive data. This is a powerful
-pattern for enhancing security in your workflow.
-
-```javascript
-const SECRET_PATTERNS = [
-  /api[_-]?key\s*[:=]\s*['"]?[a-zA-Z0-9_-]{20,}['"]?/i,
-  /password\s*[:=]\s*['"]?[^\s'"]{8,}['"]?/i,
-  /secret\s*[:=]\s*['"]?[a-zA-Z0-9_-]{20,}['"]?/i,
-  /AKIA[0-9A-Z]{16}/, // AWS access key
-  /ghp_[a-zA-Z0-9]{36}/, // GitHub personal access token
-  /sk-[a-zA-Z0-9]{48}/, // OpenAI API key
-];
-
-function containsSecret(content) {
-  return SECRET_PATTERNS.some((pattern) => pattern.test(content));
-}
-```
-
-## Privacy considerations
-
-Hook inputs and outputs may contain sensitive information. Gemini CLI respects
-the `telemetry.logPrompts` setting for hook data logging.
-
-### What data is collected
-
-Hook telemetry may include:
-
-- **Hook inputs:** User prompts, tool arguments, file contents
-- **Hook outputs:** Hook responses, decision reasons, added context
-- **Standard streams:** stdout and stderr from hook processes
-- **Execution metadata:** Hook name, event type, duration, success/failure
-
-### Privacy settings
-
-**Enabled (default):**
-
-Full hook I/O is logged to telemetry. Use this when:
-
-- Developing and debugging hooks
-- Telemetry is redirected to a trusted enterprise system
-- You understand and accept the privacy implications
-
-**Disabled:**
-
-Only metadata is logged (event name, duration, success/failure). Hook inputs and
-outputs are excluded. Use this when:
-
-- Sending telemetry to third-party systems
-- Working with sensitive data
-- Privacy regulations require minimizing data collection
-
-### Configuration
-
-**Disable PII logging in settings:**
-
-```json
-{
-  "telemetry": {
-    "logPrompts": false
-  }
-}
-```
-
-**Disable via environment variable:**
-
-```bash
-export GEMINI_TELEMETRY_LOG_PROMPTS=false
-```
-
-### Sensitive data in hooks
-
-If your hooks process sensitive data:
-
-1. **Minimize logging:** Don't write sensitive data to log files
-2. **Sanitize outputs:** Remove sensitive data before outputting
-3. **Use secure storage:** Encrypt sensitive data at rest
-4. **Limit access:** Restrict hook script permissions
-
-**Example sanitization:**
-
-```javascript
-function sanitizeOutput(data) {
-  const sanitized = { ...data };
-
-  // Remove sensitive fields
-  delete sanitized.apiKey;
-  delete sanitized.password;
-
-  // Redact sensitive strings
-  if (sanitized.content) {
-    sanitized.content = sanitized.content.replace(
-      /api[_-]?key\s*[:=]\s*['"]?[a-zA-Z0-9_-]{20,}['"]?/gi,
-      '[REDACTED]',
-    );
-  }
-
-  return sanitized;
-}
-
-console.log(JSON.stringify(sanitizeOutput(hookOutput)));
-```
-
-## Learn more
-
-- [Hooks Reference](index.md) - Complete API reference
-- [Writing Hooks](writing-hooks.md) - Tutorial and examples
-- [Configuration](../cli/configuration.md) - Gemini CLI settings
-- [Hooks Design Document](../hooks-design.md) - Technical architecture

docs/hooks/index.md

@@ -1,687 +0,0 @@
-# Gemini CLI hooks
-
-Hooks are scripts or programs that Gemini CLI executes at specific points in the
-agentic loop, allowing you to intercept and customize behavior without modifying
-the CLI's source code.
-
-See [writing hooks guide](writing-hooks.md) for a tutorial on creating your
-first hook and a comprehensive example.
-
-See [hooks reference](reference.md) for the technical specification of the I/O
-schemas.
-
-See [best practices](best-practices.md) for guidelines on security, performance,
-and debugging.
-
-## What are hooks?
-
-With hooks, you can:
-
-- **Add context:** Inject relevant information before the model processes a
-  request
-- **Validate actions:** Review and block potentially dangerous operations
-- **Enforce policies:** Implement security and compliance requirements
-- **Log interactions:** Track tool usage and model responses
-- **Optimize behavior:** Dynamically adjust tool selection or model parameters
-
-Hooks run synchronously as part of the agent loop—when a hook event fires,
-Gemini CLI waits for all matching hooks to complete before continuing.
-
-## Security and Risks
-
-> [!WARNING] **Hooks execute arbitrary code with your user privileges.**
-
-By configuring hooks, you are explicitly allowing Gemini CLI to run shell
-commands on your machine. Malicious or poorly configured hooks can:
-
-- **Exfiltrate data**: Read sensitive files (`.env`, ssh keys) and send them to
-  remote servers.
-- **Modify system**: Delete files, install malware, or change system settings.
-- **Consume resources**: Run infinite loops or crash your system.
-
-**Project-level hooks** (in `.gemini/settings.json`) and **Extension hooks** are
-particularly risky when opening third-party projects or extensions from
-untrusted authors. Gemini CLI will **warn you** the first time it detects a new
-project hook (identified by its name and command), but it is **your
-responsibility** to review these hooks (and any installed extensions) before
-trusting them.
-
-See [Security Considerations](best-practices.md#using-hooks-securely) for a
-detailed threat model and mitigation strategies.
-
-## Core concepts
-
-### Hook events
-
-Hooks are triggered by specific events in Gemini CLI's lifecycle. The following
-table lists all available hook events:
-
-| Event                 | When It Fires                                 | Common Use Cases                           |
-| --------------------- | --------------------------------------------- | ------------------------------------------ |
-| `SessionStart`        | When a session begins                         | Initialize resources, load context         |
-| `SessionEnd`          | When a session ends                           | Clean up, save state                       |
-| `BeforeAgent`         | After user submits prompt, before planning    | Add context, validate prompts              |
-| `AfterAgent`          | When agent loop ends                          | Review output, force continuation          |
-| `BeforeModel`         | Before sending request to LLM                 | Modify prompts, add instructions           |
-| `AfterModel`          | After receiving LLM response                  | Filter responses, log interactions         |
-| `BeforeToolSelection` | Before LLM selects tools (after BeforeModel)  | Filter available tools, optimize selection |
-| `BeforeTool`          | Before a tool executes                        | Validate arguments, block dangerous ops    |
-| `AfterTool`           | After a tool executes                         | Process results, run tests                 |
-| `PreCompress`         | Before context compression                    | Save state, notify user                    |
-| `Notification`        | When a notification occurs (e.g., permission) | Auto-approve, log decisions                |
-
-### Hook types
-
-Gemini CLI currently supports **command hooks** that run shell commands or
-scripts:
-
-```json
-{
-  "type": "command",
-  "command": "$GEMINI_PROJECT_DIR/.gemini/hooks/my-hook.sh",
-  "timeout": 30000
-}
-```
-
-**Note:** Plugin hooks (npm packages) are planned for a future release.
-
-### Matchers
-
-For tool-related events (`BeforeTool`, `AfterTool`), you can filter which tools
-trigger the hook:
-
-```json
-{
-  "hooks": {
-    "BeforeTool": [
-      {
-        "matcher": "write_file|replace",
-        "hooks": [
-          /* hooks for write operations */
-        ]
-      }
-    ]
-  }
-}
-```
-
-**Matcher patterns:**
-
-- **Exact match:** `"read_file"` matches only `read_file`
-- **Regex:** `"write_.*|replace"` matches `write_file`, `replace`
-- **Wildcard:** `"*"` or `""` matches all tools
-
-**Session event matchers:**
-
-- **SessionStart:** `startup`, `resume`, `clear`
-- **SessionEnd:** `exit`, `clear`, `logout`, `prompt_input_exit`
-- **PreCompress:** `manual`, `auto`
-- **Notification:** `ToolPermission`
-
-## Hook input/output contract
-
-### Command hook communication
-
-Hooks communicate via:
-
-- **Input:** JSON on stdin
-- **Output:** Exit code + stdout/stderr
-
-### Exit codes
-
-- **0:** Success - stdout shown to user (or injected as context for some events)
-- **2:** Blocking error - stderr shown to agent/user, operation may be blocked
-- **Other:** Non-blocking warning - logged but execution continues
-
-### Common input fields
-
-Every hook receives these base fields:
-
-```json
-{
-  "session_id": "abc123",
-  "transcript_path": "/path/to/transcript.jsonl",
-  "cwd": "/path/to/project",
-  "hook_event_name": "BeforeTool",
-  "timestamp": "2025-12-01T10:30:00Z"
-  // ... event-specific fields
-}
-```
-
-### Event-specific fields
-
-#### BeforeTool
-
-**Input:**
-
-```json
-{
-  "tool_name": "write_file",
-  "tool_input": {
-    "file_path": "/path/to/file.ts",
-    "content": "..."
-  }
-}
-```
-
-**Output (JSON on stdout):**
-
-```json
-{
-  "decision": "allow|deny|ask|block",
-  "reason": "Explanation shown to agent",
-  "systemMessage": "Message shown to user"
-}
-```
-
-Or simple exit codes:
-
-- Exit 0 = allow (stdout shown to user)
-- Exit 2 = deny (stderr shown to agent)
-
-#### AfterTool
-
-**Input:**
-
-```json
-{
-  "tool_name": "read_file",
-  "tool_input": { "file_path": "..." },
-  "tool_response": "file contents..."
-}
-```
-
-**Output:**
-
-```json
-{
-  "decision": "allow|deny",
-  "hookSpecificOutput": {
-    "hookEventName": "AfterTool",
-    "additionalContext": "Extra context for agent"
-  }
-}
-```
-
-#### BeforeAgent
-
-**Input:**
-
-```json
-{
-  "prompt": "Fix the authentication bug"
-}
-```
-
-**Output:**
-
-```json
-{
-  "decision": "allow|deny",
-  "hookSpecificOutput": {
-    "hookEventName": "BeforeAgent",
-    "additionalContext": "Recent project decisions: ..."
-  }
-}
-```
-
-#### BeforeModel
-
-**Input:**
-
-```json
-{
-  "llm_request": {
-    "model": "gemini-2.0-flash-exp",
-    "messages": [{ "role": "user", "content": "Hello" }],
-    "config": { "temperature": 0.7 },
-    "toolConfig": {
-      "functionCallingConfig": {
-        "mode": "AUTO",
-        "allowedFunctionNames": ["read_file", "write_file"]
-      }
-    }
-  }
-}
-```
-
-**Output:**
-
-```json
-{
-  "decision": "allow",
-  "hookSpecificOutput": {
-    "hookEventName": "BeforeModel",
-    "llm_request": {
-      "messages": [
-        { "role": "system", "content": "Additional instructions..." },
-        { "role": "user", "content": "Hello" }
-      ]
-    }
-  }
-}
-```
-
-#### AfterModel
-
-**Input:**
-
-```json
-{
-  "llm_request": {
-    "model": "gemini-2.0-flash-exp",
-    "messages": [
-      /* ... */
-    ],
-    "config": {
-      /* ... */
-    },
-    "toolConfig": {
-      /* ... */
-    }
-  },
-  "llm_response": {
-    "text": "string",
-    "candidates": [
-      {
-        "content": {
-          "role": "model",
-          "parts": ["array of content parts"]
-        },
-        "finishReason": "STOP"
-      }
-    ]
-  }
-}
-```
-
-**Output:**
-
-```json
-{
-  "hookSpecificOutput": {
-    "hookEventName": "AfterModel",
-    "llm_response": {
-      "candidate": {
-        /* modified response */
-      }
-    }
-  }
-}
-```
-
-#### BeforeToolSelection
-
-**Input:**
-
-```json
-{
-  "llm_request": {
-    "model": "gemini-2.0-flash-exp",
-    "messages": [
-      /* ... */
-    ],
-    "toolConfig": {
-      "functionCallingConfig": {
-        "mode": "AUTO",
-        "allowedFunctionNames": [
-          /* 100+ tools */
-        ]
-      }
-    }
-  }
-}
-```
-
-**Output:**
-
-```json
-{
-  "hookSpecificOutput": {
-    "hookEventName": "BeforeToolSelection",
-    "toolConfig": {
-      "functionCallingConfig": {
-        "mode": "ANY",
-        "allowedFunctionNames": ["read_file", "write_file", "replace"]
-      }
-    }
-  }
-}
-```
-
-Or simple output (comma-separated tool names sets mode to ANY):
-
-```bash
-echo "read_file,write_file,replace"
-```
-
-#### SessionStart
-
-**Input:**
-
-```json
-{
-  "source": "startup|resume|clear"
-}
-```
-
-**Output:**
-
-```json
-{
-  "hookSpecificOutput": {
-    "hookEventName": "SessionStart",
-    "additionalContext": "Loaded 5 project memories"
-  }
-}
-```
-
-#### SessionEnd
-
-**Input:**
-
-```json
-{
-  "reason": "exit|clear|logout|prompt_input_exit|other"
-}
-```
-
-No structured output expected (but stdout/stderr logged).
-
-#### PreCompress
-
-**Input:**
-
-```json
-{
-  "trigger": "manual|auto"
-}
-```
-
-**Output:**
-
-```json
-{
-  "systemMessage": "Compression starting..."
-}
-```
-
-#### Notification
-
-**Input:**
-
-```json
-{
-  "notification_type": "ToolPermission",
-  "message": "string",
-  "details": {
-    /* notification details */
-  }
-}
-```
-
-**Output:**
-
-```json
-{
-  "systemMessage": "Notification logged"
-}
-```
-
-## Configuration
-
-Hook definitions are configured in `settings.json` files using the `hooks`
-object. Configuration can be specified at multiple levels with defined
-precedence rules.
-
-### Configuration layers
-
-Hook configurations are applied in the following order of execution (lower
-numbers run first):
-
-1.  **Project settings:** `.gemini/settings.json` in your project directory
-    (highest priority)
-2.  **User settings:** `~/.gemini/settings.json`
-3.  **System settings:** `/etc/gemini-cli/settings.json`
-4.  **Extensions:** Internal hooks defined by installed extensions (lowest
-    priority)
-
-#### Deduplication and shadowing
-
-If multiple hooks with the identical **name** and **command** are discovered
-across different configuration layers, Gemini CLI deduplicates them. The hook
-from the higher-priority layer (e.g., Project) will be kept, and others will be
-ignored.
-
-Within each level, hooks run in the order they are declared in the
-configuration.
-
-### Configuration schema
-
-```json
-{
-  "hooks": {
-    "EventName": [
-      {
-        "matcher": "pattern",
-        "hooks": [
-          {
-            "name": "hook-identifier",
-            "type": "command",
-            "command": "./path/to/script.sh",
-            "description": "What this hook does",
-            "timeout": 30000
-          }
-        ]
-      }
-    ]
-  }
-}
-```
-
-**Configuration properties:**
-
-- **`name`** (string, recommended): Unique identifier for the hook used in
-  `/hooks enable/disable` commands. If omitted, the `command` path is used as
-  the identifier.
-- **`type`** (string, required): Hook type - currently only `"command"` is
-  supported
-- **`command`** (string, required): Path to the script or command to execute
-- **`description`** (string, optional): Human-readable description shown in
-  `/hooks panel`
-- **`timeout`** (number, optional): Timeout in milliseconds (default: 60000)
-- **`matcher`** (string, optional): Pattern to filter when hook runs (event
-  matchers only)
-
-### Environment variables
-
-Hooks have access to:
-
-- `GEMINI_PROJECT_DIR`: Project root directory
-- `GEMINI_SESSION_ID`: Current session ID
-- `GEMINI_API_KEY`: Gemini API key (if configured)
-- All other environment variables from the parent process
-
-## Managing hooks
-
-### View registered hooks
-
-Use the `/hooks panel` command to view all registered hooks:
-
-```bash
-/hooks panel
-```
-
-This command displays:
-
-- All active hooks organized by event
-- Hook source (user, project, system)
-- Hook type (command or plugin)
-- Execution status and recent output
-
-### Enable and disable hooks
-
-You can temporarily enable or disable individual hooks using commands:
-
-```bash
-/hooks enable hook-name
-/hooks disable hook-name
-```
-
-These commands allow you to control hook execution without editing configuration
-files. The hook name should match the `name` field in your hook configuration.
-Changes made via these commands are persisted to your global User settings
-(`~/.gemini/settings.json`).
-
-### Disabled hooks configuration
-
-To permanently disable hooks, add them to the `hooks.disabled` array in your
-`settings.json`:
-
-```json
-{
-  "hooks": {
-    "disabled": ["secret-scanner", "auto-test"]
-  }
-}
-```
-
-**Note:** The `hooks.disabled` array uses a UNION merge strategy. Disabled hooks
-from all configuration levels (user, project, system) are combined and
-deduplicated, meaning a hook disabled at any level remains disabled.
-
-## Migration from Claude Code
-
-If you have hooks configured for Claude Code, you can migrate them:
-
-```bash
-gemini hooks migrate --from-claude
-```
-
-This command:
-
-- Reads `.claude/settings.json`
-- Converts event names (`PreToolUse` → `BeforeTool`, etc.)
-- Translates tool names (`Bash` → `run_shell_command`, `replace` → `replace`)
-- Updates matcher patterns
-- Writes to `.gemini/settings.json`
-
-### Event name mapping
-
-| Claude Code        | Gemini CLI     |
-| ------------------ | -------------- |
-| `PreToolUse`       | `BeforeTool`   |
-| `PostToolUse`      | `AfterTool`    |
-| `UserPromptSubmit` | `BeforeAgent`  |
-| `Stop`             | `AfterAgent`   |
-| `Notification`     | `Notification` |
-| `SessionStart`     | `SessionStart` |
-| `SessionEnd`       | `SessionEnd`   |
-| `PreCompact`       | `PreCompress`  |
-
-### Tool name mapping
-
-| Claude Code | Gemini CLI            |
-| ----------- | --------------------- |
-| `Bash`      | `run_shell_command`   |
-| `Edit`      | `replace`             |
-| `Read`      | `read_file`           |
-| `Write`     | `write_file`          |
-| `Glob`      | `glob`                |
-| `Grep`      | `search_file_content` |
-| `LS`        | `list_directory`      |
-
-## Tool and Event Matchers Reference
-
-### Available tool names for matchers
-
-The following built-in tools can be used in `BeforeTool` and `AfterTool` hook
-matchers:
-
-#### File operations
-
-- `read_file` - Read a single file
-- `read_many_files` - Read multiple files at once
-- `write_file` - Create or overwrite a file
-- `replace` - Edit file content with find/replace
-
-#### File system
-
-- `list_directory` - List directory contents
-- `glob` - Find files matching a pattern
-- `search_file_content` - Search within file contents
-
-#### Execution
-
-- `run_shell_command` - Execute shell commands
-
-#### Web and external
-
-- `google_web_search` - Google Search with grounding
-- `web_fetch` - Fetch web page content
-
-#### Agent features
-
-- `write_todos` - Manage TODO items
-- `save_memory` - Save information to memory
-- `delegate_to_agent` - Delegate tasks to sub-agents
-
-#### Example matchers
-
-```json
-{
-  "matcher": "write_file|replace" // File editing tools
-}
-```
-
-```json
-{
-  "matcher": "read_.*" // All read operations
-}
-```
-
-```json
-{
-  "matcher": "run_shell_command" // Only shell commands
-}
-```
-
-```json
-{
-  "matcher": "*" // All tools
-}
-```
-
-### Event-specific matchers
-
-#### SessionStart event matchers
-
-- `startup` - Fresh session start
-- `resume` - Resuming a previous session
-- `clear` - Session cleared
-
-#### SessionEnd event matchers
-
-- `exit` - Normal exit
-- `clear` - Session cleared
-- `logout` - User logged out
-- `prompt_input_exit` - Exit from prompt input
-- `other` - Other reasons
-
-#### PreCompress event matchers
-
-- `manual` - Manually triggered compression
-- `auto` - Automatically triggered compression
-
-#### Notification event matchers
-
-- `ToolPermission` - Tool permission notifications
-
-## Learn more
-
-- [Writing Hooks](writing-hooks.md) - Tutorial and comprehensive example
-- [Best Practices](best-practices.md) - Security, performance, and debugging
-- [Custom Commands](../cli/custom-commands.md) - Create reusable prompt
-  shortcuts
-- [Configuration](../cli/configuration.md) - Gemini CLI configuration options
-- [Hooks Design Document](../hooks-design.md) - Technical architecture details

docs/hooks/reference.md

@@ -1,168 +0,0 @@
-# Hooks Reference
-
-This document provides the technical specification for Gemini CLI hooks,
-including the JSON schemas for input and output, exit code behaviors, and the
-stable model API.
-
-## Communication Protocol
-
-Hooks communicate with Gemini CLI via standard streams and exit codes:
-
-- **Input**: Gemini CLI sends a JSON object to the hook's `stdin`.
-- **Output**: The hook sends a JSON object (or plain text) to `stdout`.
-- **Exit Codes**: Used to signal success or blocking errors.
-
-### Exit Code Behavior
-
-| Exit Code | Meaning            | Behavior                                                                                        |
-| :-------- | :----------------- | :---------------------------------------------------------------------------------------------- |
-| `0`       | **Success**        | `stdout` is parsed as JSON. If parsing fails, it's treated as a `systemMessage`.                |
-| `2`       | **Blocking Error** | Interrupts the current operation. `stderr` is shown to the agent (for tool events) or the user. |
-| Other     | **Warning**        | Execution continues. `stderr` is logged as a non-blocking warning.                              |
-
----
-
-## Input Schema (`stdin`)
-
-Every hook receives a base JSON object. Extra fields are added depending on the
-specific event.
-
-### Base Fields (All Events)
-
-| Field             | Type     | Description                                           |
-| :---------------- | :------- | :---------------------------------------------------- |
-| `session_id`      | `string` | Unique identifier for the current CLI session.        |
-| `transcript_path` | `string` | Path to the session's JSON transcript (if available). |
-| `cwd`             | `string` | The current working directory.                        |
-| `hook_event_name` | `string` | The name of the firing event (e.g., `BeforeTool`).    |
-| `timestamp`       | `string` | ISO 8601 timestamp of the event.                      |
-
-### Event-Specific Fields
-
-#### Tool Events (`BeforeTool`, `AfterTool`)
-
-- `tool_name`: (`string`) The internal name of the tool (e.g., `write_file`,
-  `run_shell_command`).
-- `tool_input`: (`object`) The arguments passed to the tool.
-- `tool_response`: (`object`, **AfterTool only**) The raw output from the tool
-  execution.
-
-#### Agent Events (`BeforeAgent`, `AfterAgent`)
-
-- `prompt`: (`string`) The user's submitted prompt.
-- `prompt_response`: (`string`, **AfterAgent only**) The final response text
-  from the model.
-- `stop_hook_active`: (`boolean`, **AfterAgent only**) Indicates if a stop hook
-  is already handling a continuation.
-
-#### Model Events (`BeforeModel`, `AfterModel`, `BeforeToolSelection`)
-
-- `llm_request`: (`LLMRequest`) A stable representation of the outgoing request.
-  See [Stable Model API](#stable-model-api).
-- `llm_response`: (`LLMResponse`, **AfterModel only**) A stable representation
-  of the incoming response.
-
-#### Session & Notification Events
-
-- `source`: (`startup` | `resume` | `clear`, **SessionStart only**) The trigger
-  source.
-- `reason`: (`exit` | `clear` | `logout` | `prompt_input_exit` | `other`,
-  **SessionEnd only**) The reason for session end.
-- `trigger`: (`manual` | `auto`, **PreCompress only**) What triggered the
-  compression event.
-- `notification_type`: (`ToolPermission`, **Notification only**) The type of
-  notification being fired.
-- `message`: (`string`, **Notification only**) The notification message.
-- `details`: (`object`, **Notification only**) Payload-specific details for the
-  notification.
-
----
-
-## Output Schema (`stdout`)
-
-If the hook exits with `0`, the CLI attempts to parse `stdout` as JSON.
-
-### Common Output Fields
-
-| Field                | Type      | Description                                                              |
-| :------------------- | :-------- | :----------------------------------------------------------------------- |
-| `decision`           | `string`  | One of: `allow`, `deny`, `block`, `ask`, `approve`.                      |
-| `reason`             | `string`  | Explanation shown to the **agent** when a decision is `deny` or `block`. |
-| `systemMessage`      | `string`  | Message displayed to the **user** in the CLI terminal.                   |
-| `continue`           | `boolean` | If `false`, immediately terminates the agent loop for this turn.         |
-| `stopReason`         | `string`  | Message shown to the user when `continue` is `false`.                    |
-| `suppressOutput`     | `boolean` | If `true`, the hook execution is hidden from the CLI transcript.         |
-| `hookSpecificOutput` | `object`  | Container for event-specific data (see below).                           |
-
-### `hookSpecificOutput` Reference
-
-| Field               | Supported Events                           | Description                                                                       |
-| :------------------ | :----------------------------------------- | :-------------------------------------------------------------------------------- |
-| `additionalContext` | `SessionStart`, `BeforeAgent`, `AfterTool` | Appends text directly to the agent's context.                                     |
-| `llm_request`       | `BeforeModel`                              | A `Partial<LLMRequest>` to override parameters of the outgoing call.              |
-| `llm_response`      | `BeforeModel`                              | A **full** `LLMResponse` to bypass the model and provide a synthetic result.      |
-| `llm_response`      | `AfterModel`                               | A `Partial<LLMResponse>` to modify the model's response before the agent sees it. |
-| `toolConfig`        | `BeforeToolSelection`                      | Object containing `mode` (`AUTO`/`ANY`/`NONE`) and `allowedFunctionNames`.        |
-
----
-
-## Stable Model API
-
-Gemini CLI uses a decoupled format for model interactions to ensure hooks remain
-stable even if the underlying Gemini SDK changes.
-
-### `LLMRequest` Object
-
-Used in `BeforeModel` and `BeforeToolSelection`.
-
-> 💡 **Note**: In v1, model hooks are primarily text-focused. Non-text parts
-> (like images or function calls) provided in the `content` array will be
-> simplified to their string representation by the translator.
-
-```typescript
-{
-  "model": string,
-  "messages": Array<{
-    "role": "user" | "model" | "system",
-    "content": string | Array<{ "type": string, [key: string]: any }>
-  }>,
-  "config"?: {
-    "temperature"?: number,
-    "maxOutputTokens"?: number,
-    "topP"?: number,
-    "topK"?: number
-  },
-  "toolConfig"?: {
-    "mode"?: "AUTO" | "ANY" | "NONE",
-    "allowedFunctionNames"?: string[]
-  }
-}
-```
-
-### `LLMResponse` Object
-
-Used in `AfterModel` and as a synthetic response in `BeforeModel`.
-
-```typescript
-{
-  "text"?: string,
-  "candidates": Array<{
-    "content": {
-      "role": "model",
-      "parts": string[]
-    },
-    "finishReason"?: "STOP" | "MAX_TOKENS" | "SAFETY" | "RECITATION" | "OTHER",
-    "index"?: number,
-    "safetyRatings"?: Array<{
-      "category": string,
-      "probability": string,
-      "blocked"?: boolean
-    }>
-  }>,
-  "usageMetadata"?: {
-    "promptTokenCount"?: number,
-    "candidatesTokenCount"?: number,
-    "totalTokenCount"?: number
-  }
-}
-```

docs/ide-integration/ide-companion-spec.md

@@ -1,4 +1,4 @@
-# Gemini CLI companion plugin: Interface specification
+# Gemini CLI Companion Plugin: Interface Specification
 
 > Last Updated: September 15, 2025
 
@@ -9,11 +9,11 @@ awareness) are provided by the official extension
 This specification is for contributors who wish to bring similar functionality
 to other editors like JetBrains IDEs, Sublime Text, etc.
 
-## I. The communication interface
+## I. The Communication Interface
 
 Gemini CLI and the IDE plugin communicate through a local communication channel.
 
-### 1. Transport layer: MCP over HTTP
+### 1. Transport Layer: MCP over HTTP
 
 The plugin **MUST** run a local HTTP server that implements the **Model Context
 Protocol (MCP)**.
@@ -25,24 +25,24 @@ Protocol (MCP)**.
 - **Port:** The server **MUST** listen on a dynamically assigned port (i.e.,
   listen on port `0`).
 
-### 2. Discovery mechanism: The port file
+### 2. Discovery Mechanism: The Port File
 
 For Gemini CLI to connect, it needs to discover which IDE instance it's running
 in and what port your server is using. The plugin **MUST** facilitate this by
 creating a "discovery file."
 
-- **How the CLI finds the file:** The CLI determines the Process ID (PID) of the
+- **How the CLI Finds the File:** The CLI determines the Process ID (PID) of the
   IDE it's running in by traversing the process tree. It then looks for a
   discovery file that contains this PID in its name.
-- **File location:** The file must be created in a specific directory:
+- **File Location:** The file must be created in a specific directory:
   `os.tmpdir()/gemini/ide/`. Your plugin must create this directory if it
   doesn't exist.
-- **File naming convention:** The filename is critical and **MUST** follow the
+- **File Naming Convention:** The filename is critical and **MUST** follow the
   pattern: `gemini-ide-server-${PID}-${PORT}.json`
   - `${PID}`: The process ID of the parent IDE process. Your plugin must
     determine this PID and include it in the filename.
   - `${PORT}`: The port your MCP server is listening on.
-- **File content and workspace validation:** The file **MUST** contain a JSON
+- **File Content & Workspace Validation:** The file **MUST** contain a JSON
   object with the following structure:
 
   ```json
@@ -79,7 +79,7 @@ creating a "discovery file."
   server (e.g., `Authorization: Bearer a-very-secret-token`). Your server
   **MUST** validate this token on every request and reject any that are
   unauthorized.
-- **Tie-breaking with environment variables (recommended):** For the most
+- **Tie-Breaking with Environment Variables (Recommended):** For the most
   reliable experience, your plugin **SHOULD** both create the discovery file and
   set the `GEMINI_CLI_IDE_SERVER_PORT` environment variable in the integrated
   terminal. The file serves as the primary discovery mechanism, but the
@@ -88,18 +88,18 @@ creating a "discovery file."
   `GEMINI_CLI_IDE_SERVER_PORT` variable to identify and connect to the correct
   window's server.
 
-## II. The context interface
+## II. The Context Interface
 
 To enable context awareness, the plugin **MAY** provide the CLI with real-time
 information about the user's activity in the IDE.
 
-### `ide/contextUpdate` notification
+### `ide/contextUpdate` Notification
 
 The plugin **MAY** send an `ide/contextUpdate`
 [notification](https://modelcontextprotocol.io/specification/2025-06-18/basic/index#notifications)
 to the CLI whenever the user's context changes.
 
-- **Triggering events:** This notification should be sent (with a recommended
+- **Triggering Events:** This notification should be sent (with a recommended
   debounce of 50ms) when:
   - A file is opened, closed, or focused.
   - The user's cursor position or text selection changes in the active file.
@@ -136,16 +136,16 @@ to the CLI whenever the user's context changes.
   Virtual files (e.g., unsaved files without a path, editor settings pages)
   **MUST** be excluded.
 
-### How the CLI uses this context
+### How the CLI Uses This Context
 
 After receiving the `IdeContext` object, the CLI performs several normalization
 and truncation steps before sending the information to the model.
 
-- **File ordering:** The CLI uses the `timestamp` field to determine the most
+- **File Ordering:** The CLI uses the `timestamp` field to determine the most
   recently used files. It sorts the `openFiles` list based on this value.
   Therefore, your plugin **MUST** provide an accurate Unix timestamp for when a
   file was last focused.
-- **Active file:** The CLI considers only the most recent file (after sorting)
+- **Active File:** The CLI considers only the most recent file (after sorting)
   to be the "active" file. It will ignore the `isActive` flag on all other files
   and clear their `cursor` and `selectedText` fields. Your plugin should focus
   on setting `isActive: true` and providing cursor/selection details only for
@@ -156,14 +156,14 @@ and truncation steps before sending the information to the model.
 While the CLI handles the final truncation, it is highly recommended that your
 plugin also limits the amount of context it sends.
 
-## III. The diffing interface
+## III. The Diffing Interface
 
 To enable interactive code modifications, the plugin **MAY** expose a diffing
 interface. This allows the CLI to request that the IDE open a diff view, showing
 proposed changes to a file. The user can then review, edit, and ultimately
 accept or reject these changes directly within the IDE.
 
-### `openDiff` tool
+### `openDiff` Tool
 
 The plugin **MUST** register an `openDiff` tool on its MCP server.
 
@@ -194,7 +194,7 @@ The plugin **MUST** register an `openDiff` tool on its MCP server.
   The actual outcome of the diff (acceptance or rejection) is communicated
   asynchronously via notifications.
 
-### `closeDiff` tool
+### `closeDiff` Tool
 
 The plugin **MUST** register a `closeDiff` tool on its MCP server.
 
@@ -219,7 +219,7 @@ The plugin **MUST** register a `closeDiff` tool on its MCP server.
     **MUST** have `isError: true` and include a `TextContent` block in the
     `content` array describing the error.
 
-### `ide/diffAccepted` notification
+### `ide/diffAccepted` Notification
 
 When the user accepts the changes in a diff view (e.g., by clicking an "Apply"
 or "Save" button), the plugin **MUST** send an `ide/diffAccepted` notification
@@ -238,7 +238,7 @@ to the CLI.
   }
   ```
 
-### `ide/diffRejected` notification
+### `ide/diffRejected` Notification
 
 When the user rejects the changes (e.g., by closing the diff view without
 accepting), the plugin **MUST** send an `ide/diffRejected` notification to the
@@ -254,14 +254,14 @@ CLI.
   }
   ```
 
-## IV. The lifecycle interface
+## IV. The Lifecycle Interface
 
 The plugin **MUST** manage its resources and the discovery file correctly based
 on the IDE's lifecycle.
 
-- **On activation (IDE startup/plugin enabled):**
+- **On Activation (IDE startup/plugin enabled):**
   1.  Start the MCP server.
   2.  Create the discovery file.
-- **On deactivation (IDE shutdown/plugin disabled):**
+- **On Deactivation (IDE shutdown/plugin disabled):**
   1.  Stop the MCP server.
   2.  Delete the discovery file.

docs/ide-integration/index.md

@@ -1,28 +1,28 @@
-# IDE integration
+# IDE Integration
 
 Gemini CLI can integrate with your IDE to provide a more seamless and
 context-aware experience. This integration allows the CLI to understand your
 workspace better and enables powerful features like native in-editor diffing.
 
-Currently, the supported IDEs are [Antigravity](https://antigravity.google),
-[Visual Studio Code](https://code.visualstudio.com/), and other editors that
+Currently, the only supported IDE is
+[Visual Studio Code](https://code.visualstudio.com/) and other editors that
 support VS Code extensions. To build support for other editors, see the
 [IDE Companion Extension Spec](./ide-companion-spec.md).
 
 ## Features
 
-- **Workspace context:** The CLI automatically gains awareness of your workspace
+- **Workspace Context:** The CLI automatically gains awareness of your workspace
   to provide more relevant and accurate responses. This context includes:
   - The **10 most recently accessed files** in your workspace.
   - Your active cursor position.
   - Any text you have selected (up to a 16KB limit; longer selections will be
     truncated).
 
-- **Native diffing:** When Gemini suggests code modifications, you can view the
+- **Native Diffing:** When Gemini suggests code modifications, you can view the
   changes directly within your IDE's native diff viewer. This allows you to
   review, edit, and accept or reject the suggested changes seamlessly.
 
-- **VS Code commands:** You can access Gemini CLI features directly from the VS
+- **VS Code Commands:** You can access Gemini CLI features directly from the VS
   Code Command Palette (`Cmd+Shift+P` or `Ctrl+Shift+P`):
   - `Gemini CLI: Run`: Starts a new Gemini CLI session in the integrated
     terminal.
@@ -32,18 +32,18 @@ support VS Code extensions. To build support for other editors, see the
   - `Gemini CLI: View Third-Party Notices`: Displays the third-party notices for
     the extension.
 
-## Installation and setup
+## Installation and Setup
 
 There are three ways to set up the IDE integration:
 
-### 1. Automatic nudge (recommended)
+### 1. Automatic Nudge (Recommended)
 
 When you run Gemini CLI inside a supported editor, it will automatically detect
 your environment and prompt you to connect. Answering "Yes" will automatically
 run the necessary setup, which includes installing the companion extension and
 enabling the connection.
 
-### 2. Manual installation from CLI
+### 2. Manual Installation from CLI
 
 If you previously dismissed the prompt or want to install the extension
 manually, you can run the following command inside Gemini CLI:
@@ -54,13 +54,13 @@ manually, you can run the following command inside Gemini CLI:
 
 This will find the correct extension for your IDE and install it.
 
-### 3. Manual installation from a marketplace
+### 3. Manual Installation from a Marketplace
 
 You can also install the extension directly from a marketplace.
 
 - **For Visual Studio Code:** Install from the
   [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=google.gemini-cli-vscode-ide-companion).
-- **For VS Code forks:** To support forks of VS Code, the extension is also
+- **For VS Code Forks:** To support forks of VS Code, the extension is also
   published on the
   [Open VSX Registry](https://open-vsx.org/extension/google/gemini-cli-vscode-ide-companion).
   Follow your editor's instructions for installing extensions from this
@@ -75,7 +75,7 @@ You can also install the extension directly from a marketplace.
 
 ## Usage
 
-### Enabling and disabling
+### Enabling and Disabling
 
 You can control the IDE integration from within the CLI:
 
@@ -91,7 +91,7 @@ You can control the IDE integration from within the CLI:
 When enabled, Gemini CLI will automatically attempt to connect to the IDE
 companion extension.
 
-### Checking the status
+### Checking the Status
 
 To check the connection status and see the context the CLI has received from the
 IDE, run:
@@ -106,7 +106,7 @@ recently opened files it is aware of.
 > [!NOTE] The file list is limited to 10 recently accessed files within your
 > workspace and only includes local files on disk.)
 
-### Working with diffs
+### Working with Diffs
 
 When you ask Gemini to modify a file, it can open a diff view directly in your
 editor.
@@ -128,17 +128,17 @@ editor.
 You can also **modify the suggested changes** directly in the diff view before
 accepting them.
 
-If you select ‘Allow for this session’ in the CLI, changes will no longer show
-up in the IDE as they will be auto-accepted.
+If you select ‘Yes, allow always’ in the CLI, changes will no longer show up in
+the IDE as they will be auto-accepted.
 
-## Using with sandboxing
+## Using with Sandboxing
 
 If you are using Gemini CLI within a sandbox, please be aware of the following:
 
 - **On macOS:** The IDE integration requires network access to communicate with
   the IDE companion extension. You must use a Seatbelt profile that allows
   network access.
-- **In a Docker container:** If you run Gemini CLI inside a Docker (or Podman)
+- **In a Docker Container:** If you run Gemini CLI inside a Docker (or Podman)
   container, the IDE integration can still connect to the VS Code extension
   running on your host machine. The CLI is configured to automatically find the
   IDE server on `host.docker.internal`. No special configuration is usually
@@ -150,7 +150,7 @@ If you are using Gemini CLI within a sandbox, please be aware of the following:
 If you encounter issues with IDE integration, here are some common error
 messages and how to resolve them.
 
-### Connection errors
+### Connection Errors
 
 - **Message:**
   `🔴 Disconnected: Failed to connect to IDE companion extension in [IDE Name]. Please ensure the extension is running. To install the extension, run /ide install.`
@@ -170,7 +170,7 @@ messages and how to resolve them.
   - **Solution:** Run `/ide enable` to try and reconnect. If the issue
     continues, open a new terminal window or restart your IDE.
 
-### Configuration errors
+### Configuration Errors
 
 - **Message:**
   `🔴 Disconnected: Directory mismatch. Gemini CLI is running in a different location than the open workspace in [IDE Name]. Please run the CLI from one of the following directories: [List of directories]`
@@ -184,14 +184,14 @@ messages and how to resolve them.
   - **Cause:** You have no workspace open in your IDE.
   - **Solution:** Open a workspace in your IDE and restart the CLI.
 
-### General errors
+### General Errors
 
 - **Message:**
   `IDE integration is not supported in your current environment. To use this feature, run Gemini CLI in one of these supported IDEs: [List of IDEs]`
   - **Cause:** You are running Gemini CLI in a terminal or environment that is
     not a supported IDE.
   - **Solution:** Run Gemini CLI from the integrated terminal of a supported
-    IDE, like Antigravity or VS Code.
+    IDE, like VS Code.
 
 - **Message:**
   `No installer is available for IDE. Please install the Gemini CLI Companion extension manually from the marketplace.`

docs/index.md

@@ -1,10 +1,10 @@
 # Welcome to Gemini CLI documentation
 
 This documentation provides a comprehensive guide to installing, using, and
-developing Gemini CLI, a tool that lets you interact with Gemini models through
-a command-line interface.
+developing Gemini CLI. This tool lets you interact with Gemini models through a
+command-line interface.
 
-## Gemini CLI overview
+## Overview
 
 Gemini CLI brings the capabilities of Gemini models to your terminal in an
 interactive Read-Eval-Print Loop (REPL) environment. Gemini CLI consists of a
@@ -18,130 +18,87 @@ file system operations, running shells, and web fetching, which are managed by
 
 This documentation is organized into the following sections:
 
-### Overview
-
-- **[Architecture overview](./architecture.md):** Understand the high-level
-  design of Gemini CLI, including its components and how they interact.
-- **[Contribution guide](../CONTRIBUTING.md):** Information for contributors and
-  developers, including setup, building, testing, and coding conventions.
-
 ### Get started
 
-- **[Gemini CLI quickstart](./get-started/index.md):** Let's get started with
+- **[Gemini CLI Quickstart](./get-started/index.md):** Let's get started with
   Gemini CLI.
-- **[Gemini 3 Pro on Gemini CLI](./get-started/gemini-3.md):** Learn how to
-  enable and use Gemini 3.
-- **[Authentication](./get-started/authentication.md):** Authenticate to Gemini
-  CLI.
-- **[Configuration](./get-started/configuration.md):** Learn how to configure
-  the CLI.
 - **[Installation](./get-started/installation.md):** Install and run Gemini CLI.
+- **[Authentication](./get-started/authentication.md):** Authenticate Gemini
+  CLI.
+- **[Configuration](./get-started/configuration.md):** Information on
+  configuring the CLI.
 - **[Examples](./get-started/examples.md):** Example usage of Gemini CLI.
 
 ### CLI
 
-- **[Introduction: Gemini CLI](./cli/index.md):** Overview of the command-line
-  interface.
+- **[CLI overview](./cli/index.md):** Overview of the command-line interface.
 - **[Commands](./cli/commands.md):** Description of available CLI commands.
+- **[Enterprise](./cli/enterprise.md):** Gemini CLI for enterprise.
+- **[Themes](./cli/themes.md):** Themes for Gemini CLI.
+- **[Token Caching](./cli/token-caching.md):** Token caching and optimization.
+- **[Tutorials](./cli/tutorials.md):** Tutorials for Gemini CLI.
 - **[Checkpointing](./cli/checkpointing.md):** Documentation for the
   checkpointing feature.
-- **[Custom commands](./cli/custom-commands.md):** Create your own commands and
-  shortcuts for frequently used prompts.
-- **[Enterprise](./cli/enterprise.md):** Gemini CLI for enterprise.
-- **[Headless mode](./cli/headless.md):** Use Gemini CLI programmatically for
-  scripting and automation.
-- **[Keyboard shortcuts](./cli/keyboard-shortcuts.md):** A reference for all
-  keyboard shortcuts to improve your workflow.
-- **[Model selection](./cli/model.md):** Select the model used to process your
-  commands with `/model`.
-- **[Sandbox](./cli/sandbox.md):** Isolate tool execution in a secure,
-  containerized environment.
-- **[Settings](./cli/settings.md):** Configure various aspects of the CLI's
-  behavior and appearance with `/settings`.
 - **[Telemetry](./cli/telemetry.md):** Overview of telemetry in the CLI.
-- **[Themes](./cli/themes.md):** Themes for Gemini CLI.
-- **[Token caching](./cli/token-caching.md):** Token caching and optimization.
 - **[Trusted Folders](./cli/trusted-folders.md):** An overview of the Trusted
   Folders security feature.
-- **[Tutorials](./cli/tutorials.md):** Tutorials for Gemini CLI.
-- **[Uninstall](./cli/uninstall.md):** Methods for uninstalling the Gemini CLI.
 
 ### Core
 
-- **[Introduction: Gemini CLI core](./core/index.md):** Information about Gemini
-  CLI core.
+- **[Gemini CLI core overview](./core/index.md):** Information about Gemini CLI
+  core.
 - **[Memport](./core/memport.md):** Using the Memory Import Processor.
 - **[Tools API](./core/tools-api.md):** Information on how the core manages and
   exposes tools.
-- **[System Prompt Override](./cli/system-prompt.md):** Replace built-in system
-  instructions using `GEMINI_SYSTEM_MD`.
-
-- **[Policy Engine](./core/policy-engine.md):** Use the Policy Engine for
-  fine-grained control over tool execution.
 
 ### Tools
 
-- **[Introduction: Gemini CLI tools](./tools/index.md):** Information about
-  Gemini CLI's tools.
-- **[File system tools](./tools/file-system.md):** Documentation for the
+- **[Gemini CLI tools overview](./tools/index.md):** Information about Gemini
+  CLI's tools.
+- **[File System Tools](./tools/file-system.md):** Documentation for the
   `read_file` and `write_file` tools.
-- **[Shell tool](./tools/shell.md):** Documentation for the `run_shell_command`
-  tool.
-- **[Web fetch tool](./tools/web-fetch.md):** Documentation for the `web_fetch`
-  tool.
-- **[Web search tool](./tools/web-search.md):** Documentation for the
-  `google_web_search` tool.
-- **[Memory tool](./tools/memory.md):** Documentation for the `save_memory`
-  tool.
-- **[Todo tool](./tools/todos.md):** Documentation for the `write_todos` tool.
 - **[MCP servers](./tools/mcp-server.md):** Using MCP servers with Gemini CLI.
+- **[Multi-File Read Tool](./tools/multi-file.md):** Documentation for the
+  `read_many_files` tool.
+- **[Shell Tool](./tools/shell.md):** Documentation for the `run_shell_command`
+  tool.
+- **[Web Fetch Tool](./tools/web-fetch.md):** Documentation for the `web_fetch`
+  tool.
+- **[Web Search Tool](./tools/web-search.md):** Documentation for the
+  `google_web_search` tool.
+- **[Memory Tool](./tools/memory.md):** Documentation for the `save_memory`
+  tool.
 
 ### Extensions
 
-- **[Introduction: Extensions](./extensions/index.md):** How to extend the CLI
-  with new functionality.
-- **[Get Started with extensions](./extensions/getting-started-extensions.md):**
+- **[Extensions](./extensions/index.md):** How to extend the CLI with new
+  functionality.
+- **[Get Started with Extensions](./extensions/getting-started-extensions.md):**
   Learn how to build your own extension.
-- **[Extension releasing](./extensions/extension-releasing.md):** How to release
+- **[Extension Releasing](./extensions/extension-releasing.md):** How to release
   Gemini CLI extensions.
 
-### Hooks
-
-- **[Hooks](./hooks/index.md):** Intercept and customize Gemini CLI behavior at
-  key lifecycle points.
-- **[Writing Hooks](./hooks/writing-hooks.md):** Learn how to create your first
-  hook with a comprehensive example.
-- **[Best Practices](./hooks/best-practices.md):** Security, performance, and
-  debugging guidelines for hooks.
-
 ### IDE integration
 
-- **[Introduction to IDE integration](./ide-integration/index.md):** Connect the
-  CLI to your editor.
-- **[IDE companion extension spec](./ide-integration/ide-companion-spec.md):**
+- **[IDE Integration](./ide-integration/index.md):** Connect the CLI to your
+  editor.
+- **[IDE Companion Extension Spec](./ide-integration/ide-companion-spec.md):**
   Spec for building IDE companion extensions.
 
-### Development
+### About the Gemini CLI project
 
+- **[Architecture Overview](./architecture.md):** Understand the high-level
+  design of Gemini CLI, including its components and how they interact.
+- **[Contributing & Development Guide](../CONTRIBUTING.md):** Information for
+  contributors and developers, including setup, building, testing, and coding
+  conventions.
 - **[NPM](./npm.md):** Details on how the project's packages are structured.
+- **[Troubleshooting Guide](./troubleshooting.md):** Find solutions to common
+  problems.
+- **[FAQ](./faq.md):** Frequently asked questions.
+- **[Terms of Service and Privacy Notice](./tos-privacy.md):** Information on
+  the terms of service and privacy notices applicable to your use of Gemini CLI.
 - **[Releases](./releases.md):** Information on the project's releases and
   deployment cadence.
-- **[Changelog](./changelogs/index.md):** Highlights and notable changes to
-  Gemini CLI.
-- **[Integration tests](./integration-tests.md):** Information about the
-  integration testing framework used in this project.
-- **[Issue and PR automation](./issue-and-pr-automation.md):** A detailed
-  overview of the automated processes we use to manage and triage issues and
-  pull requests.
-
-### Support
-
-- **[FAQ](./faq.md):** Frequently asked questions.
-- **[Troubleshooting guide](./troubleshooting.md):** Find solutions to common
-  problems.
-- **[Quota and pricing](./quota-and-pricing.md):** Learn about the free tier and
-  paid options.
-- **[Terms of service and privacy notice](./tos-privacy.md):** Information on
-  the terms of service and privacy notices applicable to your use of Gemini CLI.
 
 We hope this documentation helps you make the most of Gemini CLI!

docs/integration-tests.md

@@ -1,4 +1,4 @@
-# Integration tests
+# Integration Tests
 
 This document provides information about the integration testing framework used
 in this project.
@@ -56,42 +56,15 @@ To run a single test by its name, use the `--test-name-pattern` flag:
 npm run test:e2e -- --test-name-pattern "reads a file"
 ```
 
-### Regenerating model responses
-
-Some integration tests use faked out model responses, which may need to be
-regenerated from time to time as the implementations change.
-
-To regenerate these golden files, set the REGENERATE_MODEL_GOLDENS environment
-variable to "true" when running the tests, for example:
-
-**WARNING**: If running locally you should review these updated responses for
-any information about yourself or your system that gemini may have included in
-these responses.
-
-```bash
-REGENERATE_MODEL_GOLDENS="true" npm run test:e2e
-```
-
-**WARNING**: Make sure you run **await rig.cleanup()** at the end of your test,
-else the golden files will not be updated.
-
 ### Deflaking a test
 
 Before adding a **new** integration test, you should test it at least 5 times
-with the deflake script or workflow to make sure that it is not flaky.
-
-### Deflake script
+with the deflake script to make sure that it is not flaky.
 
 ```bash
 npm run deflake -- --runs=5 --command="npm run test:e2e -- -- --test-name-pattern '<your-new-test-name>'"
 ```
 
-#### Deflake workflow
-
-```bash
-gh workflow run deflake.yml --ref <your-branch> -f test_name_pattern="<your-test-name-pattern>"
-```
-
 ### Running all tests
 
 To run the entire suite of integration tests, use the following command:
@@ -199,9 +172,9 @@ file, or case.
 ## Continuous integration
 
 To ensure the integration tests are always run, a GitHub Actions workflow is
-defined in `.github/workflows/chained_e2e.yml`. This workflow automatically runs
-the integrations tests for pull requests against the `main` branch, or when a
-pull request is added to a merge queue.
+defined in `.github/workflows/e2e.yml`. This workflow automatically runs the
+integrations tests for pull requests against the `main` branch, or when a pull
+request is added to a merge queue.
 
 The workflow runs the tests in different sandboxing environments to ensure
 Gemini CLI is tested across each:

docs/issue-and-pr-automation.md

@@ -1,4 +1,4 @@
-# Automation and triage processes
+# Automation and Triage Processes
 
 This document provides a detailed overview of the automated processes we use to
 manage and triage issues and pull requests. Our goal is to provide prompt
@@ -6,7 +6,7 @@ feedback and ensure that contributions are reviewed and integrated efficiently.
 Understanding this automation will help you as a contributor know what to expect
 and how to best interact with our repository bots.
 
-## Guiding principle: Issues and pull requests
+## Guiding Principle: Issues and Pull Requests
 
 First and foremost, almost every Pull Request (PR) should be linked to a
 corresponding Issue. The issue describes the "what" and the "why" (the bug or
@@ -14,17 +14,14 @@ feature), while the PR is the "how" (the implementation). This separation helps
 us track work, prioritize features, and maintain clear historical context. Our
 automation is built around this principle.
 
-> **Note:** Issues tagged as "🔒Maintainers only" are reserved for project
-> maintainers. We will not accept pull requests related to these issues.
-
 ---
 
-## Detailed automation workflows
+## Detailed Automation Workflows
 
 Here is a breakdown of the specific automation workflows that run in our
 repository.
 
-### 1. When you open an issue: `Automated Issue Triage`
+### 1. When you open an Issue: `Automated Issue Triage`
 
 This is the first bot you will interact with when you create an issue. Its job
 is to perform an initial analysis and apply the correct labels.
@@ -51,7 +48,7 @@ is to perform an initial analysis and apply the correct labels.
   - If the `status/need-information` label is added, please provide the
     requested details in a comment.
 
-### 2. When you open a pull request: `Continuous Integration (CI)`
+### 2. When you open a Pull Request: `Continuous Integration (CI)`
 
 This workflow ensures that all changes meet our quality standards before they
 can be merged.
@@ -73,7 +70,7 @@ can be merged.
   - If a check fails (a red "X" ❌), click the "Details" link next to the failed
     check to view the logs, identify the problem, and push a fix.
 
-### 3. Ongoing triage for pull requests: `PR Auditing and Label Sync`
+### 3. Ongoing Triage for Pull Requests: `PR Auditing and Label Sync`
 
 This workflow runs periodically to ensure all open PRs are correctly linked to
 issues and have consistent labels.
@@ -96,7 +93,7 @@ issues and have consistent labels.
   - This will ensure your PR is correctly categorized and moves through the
     review process smoothly.
 
-### 4. Ongoing triage for issues: `Scheduled Issue Triage`
+### 4. Ongoing Triage for Issues: `Scheduled Issue Triage`
 
 This is a fallback workflow to ensure that no issue gets missed by the triage
 process.
@@ -113,7 +110,7 @@ process.
     ensure every issue is eventually categorized, even if the initial triage
     fails.
 
-### 5. Release automation
+### 5. Release Automation
 
 This workflow handles the process of packaging and publishing new versions of
 the Gemini CLI.

docs/local-development.md

@@ -1,128 +0,0 @@
-# Local development guide
-
-This guide provides instructions for setting up and using local development
-features, such as development tracing.
-
-## Development tracing
-
-Development traces (dev traces) are OpenTelemetry (OTel) traces that help you
-debug your code by instrumenting interesting events like model calls, tool
-scheduler, tool calls, etc.
-
-Dev traces are verbose and are specifically meant for understanding agent
-behaviour and debugging issues. They are disabled by default.
-
-To enable dev traces, set the `GEMINI_DEV_TRACING=true` environment variable
-when running Gemini CLI.
-
-### Viewing dev traces
-
-You can view dev traces using either Jaeger or the Genkit Developer UI.
-
-#### Using Genkit
-
-Genkit provides a web-based UI for viewing traces and other telemetry data.
-
-1.  **Start the Genkit telemetry server:**
-
-    Run the following command to start the Genkit server:
-
-    ```bash
-    npm run telemetry -- --target=genkit
-    ```
-
-    The script will output the URL for the Genkit Developer UI, for example:
-
-    ```
-    Genkit Developer UI: http://localhost:4000
-    ```
-
-2.  **Run Gemini CLI with dev tracing:**
-
-    In a separate terminal, run your Gemini CLI command with the
-    `GEMINI_DEV_TRACING` environment variable:
-
-    ```bash
-    GEMINI_DEV_TRACING=true gemini
-    ```
-
-3.  **View the traces:**
-
-    Open the Genkit Developer UI URL in your browser and navigate to the
-    **Traces** tab to view the traces.
-
-#### Using Jaeger
-
-You can view dev traces in the Jaeger UI. To get started, follow these steps:
-
-1.  **Start the telemetry collector:**
-
-    Run the following command in your terminal to download and start Jaeger and
-    an OTEL collector:
-
-    ```bash
-    npm run telemetry -- --target=local
-    ```
-
-    This command also configures your workspace for local telemetry and provides
-    a link to the Jaeger UI (usually `http://localhost:16686`).
-
-2.  **Run Gemini CLI with dev tracing:**
-
-    In a separate terminal, run your Gemini CLI command with the
-    `GEMINI_DEV_TRACING` environment variable:
-
-    ```bash
-    GEMINI_DEV_TRACING=true gemini
-    ```
-
-3.  **View the traces:**
-
-    After running your command, open the Jaeger UI link in your browser to view
-    the traces.
-
-For more detailed information on telemetry, see the
-[telemetry documentation](./cli/telemetry.md).
-
-### Instrumenting code with dev traces
-
-You can add dev traces to your own code for more detailed instrumentation. This
-is useful for debugging and understanding the flow of execution.
-
-Use the `runInDevTraceSpan` function to wrap any section of code in a trace
-span.
-
-Here is a basic example:
-
-```typescript
-import { runInDevTraceSpan } from '@google/gemini-cli-core';
-
-await runInDevTraceSpan({ name: 'my-custom-span' }, async ({ metadata }) => {
-  // The `metadata` object allows you to record the input and output of the
-  // operation as well as other attributes.
-  metadata.input = { key: 'value' };
-  // Set custom attributes.
-  metadata.attributes['gen_ai.request.model'] = 'gemini-4.0-mega';
-
-  // Your code to be traced goes here
-  try {
-    const output = await somethingRisky();
-    metadata.output = output;
-    return output;
-  } catch (e) {
-    metadata.error = e;
-    throw e;
-  }
-});
-```
-
-In this example:
-
-- `name`: The name of the span, which will be displayed in the trace.
-- `metadata.input`: (Optional) An object containing the input data for the
-  traced operation.
-- `metadata.output`: (Optional) An object containing the output data from the
-  traced operation.
-- `metadata.attributes`: (Optional) A record of custom attributes to add to the
-  span.
-- `metadata.error`: (Optional) An error object to record if the operation fails.

docs/npm.md

@@ -1,4 +1,4 @@
-# Package overview
+# Package Overview
 
 This monorepo contains two main packages: `@google/gemini-cli` and
 `@google/gemini-cli-core`.
@@ -25,7 +25,7 @@ Node.js package with its own dependencies. This allows it to be used as a
 standalone package in other projects, if needed. All transpiled js code in the
 `dist` folder is included in the package.
 
-## NPM workspaces
+## NPM Workspaces
 
 This project uses
 [NPM Workspaces](https://docs.npmjs.com/cli/v10/using-npm/workspaces) to manage
@@ -33,7 +33,7 @@ the packages within this monorepo. This simplifies development by allowing us to
 manage dependencies and run scripts across multiple packages from the root of
 the project.
 
-### How it works
+### How it Works
 
 The root `package.json` file defines the workspaces for this project:
 
@@ -46,17 +46,17 @@ The root `package.json` file defines the workspaces for this project:
 This tells NPM that any folder inside the `packages` directory is a separate
 package that should be managed as part of the workspace.
 
-### Benefits of workspaces
+### Benefits of Workspaces
 
-- **Simplified dependency management**: Running `npm install` from the root of
+- **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.
+- **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
+- **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`.

docs/quota-and-pricing.md

@@ -1,17 +1,18 @@
-# Gemini CLI: Quotas and pricing
+# Gemini CLI: Quotas and Pricing
 
-Gemini CLI offers a generous free tier that covers many individual developers'
-use cases. For enterprise or professional usage, or if you need higher limits,
-several options are available depending on your authentication account type.
+Gemini CLI offers a generous free tier that covers the use cases for many
+individual developers. For enterprise / professional usage, or if you need
+higher limits, there are multiple possible avenues depending on what type of
+account you use to authenticate.
 
-See [privacy and terms](./tos-privacy.md) for details on the Privacy Policy and
+See [privacy and terms](./tos-privacy.md) for details on Privacy policy and
 Terms of Service.
 
-> **Note:** Published prices are list price; additional negotiated commercial
+> [!NOTE] Published prices are list price; additional negotiated commercial
 > discounting may apply.
 
-This article outlines the specific quotas and pricing applicable to Gemini CLI
-when using different authentication methods.
+This article outlines the specific quotas and pricing applicable to the Gemini
+CLI when using different authentication methods.
 
 Generally, there are three categories to choose from:
 
@@ -21,7 +22,7 @@ Generally, there are three categories to choose from:
 - Pay-As-You-Go: The most flexible option for professional use, long-running
   tasks, or when you need full control over your usage.
 
-## Free usage
+## Free Usage
 
 Your journey begins with a generous free tier, perfect for experimentation and
 light use.
@@ -41,7 +42,7 @@ Assist for individuals. This includes:
 Learn more at
 [Gemini Code Assist for Individuals Limits](https://developers.google.com/gemini-code-assist/resources/quotas#quotas-for-agent-mode-gemini-cli).
 
-### Log in with Gemini API Key (unpaid)
+### Log in with Gemini API Key (Unpaid)
 
 If you are using a Gemini API key, you can also benefit from a free tier. This
 includes:
@@ -69,9 +70,11 @@ Learn more at
 If you use up your initial number of requests, you can continue to benefit from
 Gemini CLI by upgrading to one of the following subscriptions:
 
-- [Google AI Pro and AI Ultra](https://gemini.google/subscriptions/). This is
-  recommended for individual developers. Quotas and pricing are based on a fixed
-  price subscription.
+- [Google AI Pro and AI Ultra](https://cloud.google.com/products/gemini/pricing)
+  by signing up at
+  [Set up Gemini Code Assist](https://goo.gle/set-up-gemini-code-assist). This
+  is recommended for individual developers. Quotas and pricing are based on a
+  fixed price subscription.
 
   For predictable costs, you can log in with Google.
 
@@ -79,11 +82,10 @@ Gemini CLI by upgrading to one of the following subscriptions:
   [Gemini Code Assist Quotas and Limits](https://developers.google.com/gemini-code-assist/resources/quotas)
 
 - [Purchase a Gemini Code Assist Subscription through Google Cloud ](https://cloud.google.com/gemini/docs/codeassist/overview)
-  by signing up in the Google Cloud console. Learn more at
-  [Set up Gemini Code Assist](https://cloud.google.com/gemini/docs/discover/set-up-gemini).
-
-  Quotas and pricing are based on a fixed price subscription with assigned
-  license seats. For predictable costs, you can sign in with Google.
+  by signing up in the Google Cloud console. Learn more at [Set up Gemini Code
+  Assist] (https://cloud.google.com/gemini/docs/discover/set-up-gemini) Quotas
+  and pricing are based on a fixed price subscription with assigned license
+  seats. For predictable costs, you can sign in with Google.
 
   This includes:
   - Gemini Code Assist Standard edition:
@@ -97,7 +99,7 @@ Gemini CLI by upgrading to one of the following subscriptions:
 
   [Learn more about Gemini Code Assist Standard and Enterprise license limits](https://developers.google.com/gemini-code-assist/resources/quotas#quotas-for-agent-mode-gemini-cli).
 
-## Pay as you go
+## Pay As You Go
 
 If you hit your daily request limits or exhaust your Gemini Pro quota even after
 upgrading, the most flexible solution is to switch to a pay-as-you-go model,
@@ -127,7 +129,7 @@ It’s important to highlight that when using an API key, you pay per token/call
 This can be more expensive for many small calls with few tokens, but it's the
 only way to ensure your workflow isn't interrupted by quota limits.
 
-## Gemini for workspace plans
+## Gemini for Workspace plans
 
 These plans currently apply only to the use of Gemini web-based products
 provided by Google-based experiences (for example, the Gemini web app or the
@@ -135,7 +137,7 @@ Flow video editor). These plans do not apply to the API usage which powers the
 Gemini CLI. Supporting these plans is under active consideration for future
 support.
 
-## Tips to avoid high costs
+## Tips to Avoid High Costs
 
 When using a Pay as you Go API key, be mindful of your usage to avoid unexpected
 costs.

docs/release-confidence.md

@@ -1,21 +1,21 @@
-# Release confidence strategy
+# Release Confidence Strategy
 
 This document outlines the strategy for gaining confidence in every release of
 the Gemini CLI. It serves as a checklist and quality gate for release manager to
 ensure we are shipping a high-quality product.
 
-## The goal
+## The Goal
 
 To answer the question, "Is this release _truly_ ready for our users?" with a
 high degree of confidence, based on a holistic evaluation of automated signals,
 manual verification, and data.
 
-## Level 1: Automated gates (must pass)
+## Level 1: Automated Gates (Must Pass)
 
 These are the baseline requirements. If any of these fail, the release is a
 no-go.
 
-### 1. CI/CD health
+### 1. CI/CD Health
 
 All workflows in `.github/workflows/ci.yml` must pass on the `main` branch (for
 nightly) or the release branch (for preview/stable).
@@ -31,15 +31,15 @@ nightly) or the release branch (for preview/stable).
     pass.
   - **Build:** The project must build and bundle successfully.
 
-### 2. End-to-end (E2E) tests
+### 2. End-to-End (E2E) Tests
 
-All workflows in `.github/workflows/chained_e2e.yml` must pass.
+All workflows in `.github/workflows/e2e.yml` must pass.
 
 - **Platforms:** **Linux, macOS and Windows**.
 - **Sandboxing:** Tests must pass with both `sandbox:none` and `sandbox:docker`
   on Linux.
 
-### 3. Post-deployment smoke tests
+### 3. Post-Deployment Smoke Tests
 
 After a release is published to npm, the `smoke-test.yml` workflow runs. This
 must pass to confirm the package is installable and the binary is executable.
@@ -48,11 +48,11 @@ must pass to confirm the package is installable and the binary is executable.
   correct version without error.
 - **Platform:** Currently runs on `ubuntu-latest`.
 
-## Level 2: Manual verification and dogfooding
+## Level 2: Manual Verification & Dogfooding
 
 Automated tests cannot catch everything, especially UX issues.
 
-### 1. Dogfooding via `preview` tag
+### 1. Dogfooding via `preview` Tag
 
 The weekly release cadence promotes code from `main` -> `nightly` -> `preview`
 -> `stable`.
@@ -66,7 +66,7 @@ The weekly release cadence promotes code from `main` -> `nightly` -> `preview`
 - **Goal:** To catch regressions and UX issues in day-to-day usage before they
   reach the broad user base.
 
-### 2. Critical user journey (CUJ) checklist
+### 2. Critical User Journey (CUJ) Checklist
 
 Before promoting a `preview` release to `stable`, a release manager must
 manually run through this checklist.
@@ -84,15 +84,15 @@ manually run through this checklist.
     - [ ] API Key
     - [ ] Vertex AI
 
-- **Basic prompting:**
+- **Basic Prompting:**
   - [ ] Run `gemini "Tell me a joke"` and verify a sensible response.
   - [ ] Run in interactive mode: `gemini`. Ask a follow-up question to test
         context.
 
-- **Piped input:**
+- **Piped Input:**
   - [ ] Run `echo "Summarize this" | gemini` and verify it processes stdin.
 
-- **Context management:**
+- **Context Management:**
   - [ ] In interactive mode, use `@file` to add a local file to context. Ask a
         question about it.
 
@@ -100,20 +100,20 @@ manually run through this checklist.
   - [ ] In interactive mode run `/settings` and make modifications
   - [ ] Validate that setting is changed
 
-- **Function calling:**
+- **Function Calling:**
   - [ ] In interactive mode, ask gemini to "create a file named hello.md with
         the content 'hello world'" and verify the file is created correctly.
 
 If any of these CUJs fail, the release is a no-go until a patch is applied to
 the `preview` channel.
 
-### 3. Pre-Launch bug bash (tier 1 and 2 launches)
+### 3. Pre-Launch Bug Bash (Tier 1 & 2 Launches)
 
 For high-impact releases, an organized bug bash is required to ensure a higher
 level of quality and to catch issues across a wider range of environments and
 use cases.
 
-**Definition of tiers:**
+**Definition of Tiers:**
 
 - **Tier 1:** Industry-Moving News 🚀
 - **Tier 2:** Important News for Our Users 📣
@@ -125,7 +125,7 @@ use cases.
 A bug bash must be scheduled at least **72 hours in advance** of any Tier 1 or
 Tier 2 launch.
 
-**Rule of thumb:**
+**Rule of Thumb:**
 
 A bug bash should be considered for any release that involves:
 
@@ -134,22 +134,22 @@ A bug bash should be considered for any release that involves:
 - Media relations or press outreach
 - A "Turbo" launch event
 
-## Level 3: Telemetry and data review
+## Level 3: Telemetry & Data Review
 
-### Dashboard health
+### Dashboard Health
 
 - [ ] Go to `go/gemini-cli-dash`.
 - [ ] Navigate to the "Tool Call" tab.
 - [ ] Validate that there are no spikes in errors for the release you would like
       to promote.
 
-### Model evaluation
+### Model Evaluation
 
 - [ ] Navigate to `go/gemini-cli-offline-evals-dash`.
 - [ ] Make sure that the release you want to promote's recurring run is within
       average eval runs.
 
-## The "go/no-go" decision
+## The "Go/No-Go" Decision
 
 Before triggering the `Release: Promote` workflow to move `preview` to `stable`: