Intentionally cause memory leaks on pressing x

.dockerignore

@@ -1,17 +0,0 @@
-# Git history - not needed in build context
-.git
-
-# Root node_modules - reinstalled inside container via npm ci
-node_modules
-
-# Package-level node_modules - reinstalled inside container
-packages/*/node_modules
-
-# Development and IDE files
-.github
-.vscode
-npm-debug.log*
-
-# Misc
-.DS_Store
-*.tmp

.gemini/commands/strict-development-rules.md

@@ -53,27 +53,11 @@ Gemini CLI project.
   overriding values. Refer to `text-buffer.ts` for a canonical example.
 - **Logging**: Do not leave `console.log`, `console.warn`, or `console.error` in
   the code.
-- **State**: Ensure state initialization is explicit (e.g., use `undefined`
-  rather than `true` as a default if the state is truly unknown). Prefer a
-  reducer whenever practical. NEVER disable `react-hooks/exhaustive-deps`; fix
-  the code to correctly declare dependencies instead. Evaluate all the React
-  states in a component and ensure that the `useState` calls are necessary and
-  not cases where values could be derived on render. Ensure there are no stale
-  closures that are relying on a value from a previous render. React Components
-  that modify Settings should effectively use the `useSettingsStore` pattern.
-  Components that configure application Settings (e.g settings.json) are the
-  only reasonable case for unsaved changes to drive UX; in these cases, the
-  Settings store should only be written to on save. If the user experience does
-  not utilize unsaved changes because there is no option to exit without saving
-  or reverting the unsaved changes, then the component should directly read from
-  and write to the Settings store without holding pending changes in component
-  level UI state.
-- **Effect**: `useEffect` should not be used to synchronize React states, it
-  should only be used for genuine side effects that occur outside of React.
-  Contributors should be able to strongly justify the need for an effect.
-  Consider whether the effect should instead be inside an event handler, or
-  whether it is better off being computed on render. Carefully manage
-  `useEffect` dependencies.
+- **State & Effects**: Ensure state initialization is explicit (e.g., use
+  `undefined` rather than `true` as a default if the state is truly unknown).
+  Carefully manage `useEffect` dependencies. Prefer a reducer whenever
+  practical. NEVER disable `react-hooks/exhaustive-deps`; fix the code to
+  correctly declare dependencies instead.
 - **Context & Props**: Avoid excessive property drilling. Leverage existing
   providers, extend them, or propose a new one if necessary. Only use providers
   for properties that are consistent across the entire application.

.gemini/settings.json

@@ -2,12 +2,7 @@
   "experimental": {
     "extensionReloading": true,
     "modelSteering": true,
-    "autoMemory": true,
-    "topicUpdateNarration": true,
-    "voiceMode": true,
-    "adk": {
-      "agentSessionNoninteractiveEnabled": true
-    }
+    "topicUpdateNarration": true
   },
   "general": {
     "devtools": true

.gemini/skills/agent-tui/SKILL.md

@@ -1,330 +0,0 @@
----
-name: agent-tui
-description: >
-  Main Agents: Do NOT use this skill directly. If you need to test the TUI, invoke the `tui_tester` subagent.
-  Drive terminal UI (TUI) applications programmatically for testing, automation, and inspection.
-  Use when: automating CLI/TUI interactions, regression testing terminal apps, or verifying interactive behavior.
-  Also use when: user asks "what is agent-tui", "what does agent-tui do", "demo agent-tui", "show me agent-tui", "how does agent-tui work", or wants to see it in action.
----
-
-## 🚨 CRITICAL: macOS Daemon Workaround & Gemini CLI Usage 🚨
-
-When using `agent-tui` in this macOS environment, the default background daemonization process crashes, causing `Connection refused (os error 61)` errors. 
-
-**You MUST start the daemon manually shielded from TTY hangups before running any `agent-tui` commands.** Using `nohup` is insufficient; you must use `tmux` to provide a fully isolated pseudo-terminal. 
-
-To support parallel runs, **only restart the daemon if it is not currently running:**
-
-```bash
-# Check if daemon is alive, start it in tmux if it is not
-if ! agent-tui sessions >/dev/null 2>&1; then
-  tmux kill-session -t agent-tui 2>/dev/null || true
-  agent-tui daemon stop 2>/dev/null || true
-  rm -f /tmp/agent-tui*
-  tmux new-session -d -s agent-tui 'agent-tui daemon start --foreground > /tmp/agent-tui-daemon.log 2>&1'
-  sleep 1
-fi
-```
-
-### Session ID vs PID (Crucial for Reconnection)
-
-When `agent-tui run` returns JSON, it includes both a `session_id` and a `pid`. The `pid` is purely informational (the OS process ID of the child command). You **do not** use the `pid` to reconnect or issue commands. You must always use the `session_id` (e.g., `--session <id>`). 
-
-If the daemon crashes (`os error 61`), the pseudo-terminal is destroyed. Even if the child `pid` survives as an orphan, you cannot reconnect to it. You must restart the daemon using the workaround above and start a completely new session.
-
-### Testing the Gemini CLI
-
-When testing the Gemini CLI with `agent-tui`, there are several strict requirements to ensure deterministic and accurate behavior:
-
-1. **Build Before Running**: `agent-tui` runs the built JS files, not TypeScript. You **MUST** run `npm run build` or `npm run build:all` after making code changes and before launching the CLI with `agent-tui`.
-2. **Bypass Trust Modals**: Always pass `GEMINI_CLI_TRUST_WORKSPACE=true` in the environment. If you don't, any new project-level agents or extensions will trigger a full-screen "Acknowledge and Enable" modal. This modal steals focus, swallows automation keystrokes, and causes `agent-tui wait` commands to time out.
-3. **Isolated Environments**: If you need to test without real user credentials or existing agents interfering, isolate the global settings using `GEMINI_CLI_HOME=<some-test-dir>`.
-4. **Testing State Deltas (e.g., Reloads)**: If you are testing features that report deltas (e.g., `/agents reload` outputting "1 new local subagent"), you **MUST**:
-   - Start the CLI *first* so it establishes its baseline registry.
-   - Use a separate shell command (outside of `agent-tui`) to write the new agent `.md`/`.toml` file.
-   - Use `agent-tui type` and `press` to trigger the `/agents reload` command inside the running session.
-   - (If you add the files before starting the CLI, they become part of the baseline and won't trigger the delta logic).
-
-```bash
-# Example: Standard isolated run (sandboxed config + bypass trust modals)
-env GEMINI_CLI_TRUST_WORKSPACE=true GEMINI_CLI_HOME=test-gemini-home agent-tui run -d "$(pwd)" node packages/cli/dist/index.js
-```
-
-# Terminal Automation Mastery
-
-## Prerequisites
-
-- **Supported OS**: macOS or Linux (Windows not supported yet).
-- **Verify install**:
-
-```bash
-agent-tui --version
-```
-
-If not installed, use one of:
-
-```bash
-# Recommended: one-line install (macOS/Linux)
-curl -fsSL https://raw.githubusercontent.com/pproenca/agent-tui/master/install.sh | sh
-```
-
-```bash
-# Package manager
-npm i -g agent-tui
-pnpm add -g agent-tui
-bun add -g agent-tui
-```
-
-```bash
-# Build from source
-cargo install --git https://github.com/pproenca/agent-tui.git --path cli/crates/agent-tui
-```
-
-If you used the install script, ensure `~/.local/bin` is on your PATH.
-
-## Philosophy: Why Terminal Automation Is Different
-
-Terminal UIs are **stateless from the observer's perspective**. Unlike web browsers with a persistent DOM, terminal automation works with a constantly-refreshed character grid. This fundamental difference shapes everything:
-
-| Web Automation | Terminal Automation |
-|----------------|---------------------|
-| DOM persists across interactions | Screen buffer is redrawn constantly |
-| Selectors are stable | Text positions may shift |
-| Query once, act many times | Must re-verify before EVERY action |
-| Network events signal completion | Must detect visual stability |
-
-**The Core Insight**: agent-tui gives you vision without memory. Each screenshot is a fresh observation. Previous state means nothing after the UI changes. This isn't a limitation—it's the nature of terminal interaction.
-
-## Mental Model: The Feedback Loop
-
-Think of terminal automation as a **closed-loop control system**:
-
-```
-    ┌──────────────────────────────────────────────┐
-    │                                              │
-    ▼                                              │
-OBSERVE ──► DECIDE ──► ACT ──► WAIT ──► VERIFY ───┘
-   │                                        │
-   │                                        │
-   └─────── NEVER skip ◄────────────────────┘
-```
-
-**Each phase is mandatory.** Skipping verification is the #1 cause of flaky automation.
-
-### The "Fresh Eyes" Principle
-
-Every time you need to interact with the UI:
-
-1. **Take a fresh screenshot** — your previous one is now stale
-2. **Locate your target visually** — text positions may have changed
-3. **Verify the state** — the UI may have changed unexpectedly
-4. **Act only when stable** — animations and loading states cause failures
-
-This feels slower, but it's the only reliable approach. Optimistic reuse of stale state causes intermittent failures that are painful to debug.
-
-## Critical Rules (Non-Negotiable)
-
-> **RULE 1: Atomic Execution (No Pipelining)**
-> You are FORBIDDEN from chaining commands with `&&` (e.g., `type "x" && press Enter && wait`). Modals or UI updates can intercept your keystrokes. You MUST execute one atomic action, wait, screenshot, and verify before taking the next action in a new turn.
-
-> **RULE 2: Re-snapshot after EVERY action**
-> The UI state is invalidated by any change. Always take a fresh screenshot before acting again.
-
-> **RULE 3: Never act on unstable UI**
-> If the UI is animating, loading, or transitioning, `wait --stable` first. Acting during transitions because race conditions.
-
-> **RULE 4: Verify before claiming success**
-> Use `wait "expected text" --assert` to confirm outcomes. Don't assume an action worked—prove it.
-
-> **RULE 5: Error Recovery**
-> If a `wait` command times out, DO NOT blindly restart or kill the session. Execute `screenshot` to visually diagnose what unexpected UI element (modal, error dialog, lost focus) intercepted the flow.
-
-> **RULE 6: Clean up sessions**
-> Always end with `agent-tui kill`. Orphaned sessions consume resources and can interfere with future runs.
-
-## Decision Framework
-
-### Which Screenshot Mode?
-
-Use `screenshot --format json` when parsing automation output, or plain `screenshot` for human readable text.
-
-### How to Wait?
-
-```
-What are you waiting for?
-│
-├─► Specific text to appear
-│   └─► `wait "text" --assert` (fails if not found)
-│
-├─► Specific text to disappear
-│   └─► `wait "text" --gone --assert`
-│
-├─► UI to stop changing (animations, loading)
-│   └─► `wait --stable`
-│
-└─► Multiple conditions
-    └─► Chain waits sequentially
-```
-
-### How to Act?
-
-```
-What do you need to do?
-│
-├─► Type text into the terminal
-│   └─► `type "text"`
-│
-├─► Send keyboard shortcuts/navigation
-│   └─► `press Ctrl+C` or `press ArrowDown Enter`
-```
-
-## Core Workflow
-
-The canonical automation loop:
-
-```bash
-# 1. START: Launch the TUI app
-agent-tui run <command> [-- args...]
-
-# 2. OBSERVE: Get current UI state
-agent-tui screenshot --format json
-
-# 3. DECIDE: Based on text, determine next action
-# (This happens in your head/code)
-
-# 4. ACT: Execute the action
-agent-tui type "text"
-agent-tui press Enter
-
-# 5. WAIT: Synchronize with UI changes
-agent-tui wait "Expected" --assert    # or wait --stable
-
-# 6. VERIFY: Confirm the outcome (often combined with step 5)
-# If verification fails, handle the error
-
-# 7. REPEAT: Go back to step 2 until done
-
-# 8. CLEANUP: Always clean up
-agent-tui kill
-```
-
-## Anti-Patterns (What NOT to Do)
-
-### ❌ Acting During Animation/Loading
-
-```bash
-# WRONG: Acting immediately on dynamic UI
-agent-tui run my-app
-agent-tui screenshot --format json    # UI might still be loading!
-agent-tui type "value"                # ❌ Might miss the input field
-
-# RIGHT: Wait for stability first
-agent-tui run my-app
-agent-tui wait --stable               # Let UI settle
-agent-tui screenshot --format json    # Now it's reliable
-agent-tui type "value"
-```
-
-### ❌ Assuming Success Without Verification
-
-```bash
-# WRONG: Assuming the type worked
-agent-tui type "value"
-agent-tui press Enter
-# ...proceed as if success...       # ❌ What if it failed silently?
-
-# RIGHT: Verify the outcome
-agent-tui type "value"
-agent-tui press Enter
-agent-tui wait "Success" --assert    # ✓ Proves the action worked
-```
-
-### ❌ Skipping Cleanup
-
-```bash
-# WRONG: Forgetting to kill the session
-agent-tui run my-app
-# ...do stuff...
-# script ends                        # ❌ Session left running!
-
-# RIGHT: Always clean up
-agent-tui run my-app
-# ...do stuff...
-agent-tui kill                       # ✓ Clean exit
-```
-
-## Before You Start: Clarify Requirements
-
-Before automating any TUI, gather this information:
-
-1. **Command**: What exactly to run? (`my-app --flag` or `npm start`?)
-2. **Success criteria**: What text/state indicates success?
-3. **Input sequence**: What keystrokes/data to enter, in what order?
-4. **Safety**: Is it safe to submit forms, delete data, etc.?
-5. **Auth**: Does it need login? Test credentials?
-6. **Live preview**: Does the user want to watch? (`agent-tui live start --open`)
-
-If any of these are unclear, ask before running.
-
-## Demo Mode: Showing What agent-tui Can Do
-
-When a user asks what agent-tui is, wants a demo, or asks "show me how it works":
-
-1. **Don't explain—demonstrate.** Actions speak louder than words.
-2. **Use the live preview** so they can watch in real-time.
-3. **Run `top`**—it's universal and shows dynamic real-time updates.
-
-**Quick demo trigger phrases:**
-- "What is agent-tui?" / "What does agent-tui do?"
-- "Demo agent-tui" / "Show me agent-tui"
-- "How does agent-tui work?" / "See it in action"
-
-## Failure Recovery
-
-| Symptom | Diagnosis | Solution |
-|---------|-----------|----------|
-| "Text not found" | Stale view or text moved | Re-snapshot, locate text again |
-| Wait times out | UI didn't reach expected state | Check screenshot, verify expectations |
-| "Daemon not running" | Daemon crashed or not started | `agent-tui daemon start` |
-| Unexpected layout | Wrong terminal size | `agent-tui resize --cols 120 --rows 40` |
-| Session unresponsive | App crashed or hung | `agent-tui kill`, then re-run |
-| Repeated failures | Something fundamentally wrong | Stop after 3-5 attempts, ask user |
-
-## Self-Discovery: Use --help
-
-You don't need to memorize every flag. The CLI is self-documenting:
-
-```bash
-agent-tui --help                     # List all commands
-agent-tui run --help                 # Options for 'run'
-agent-tui screenshot --help          # Options for 'screenshot'
-agent-tui wait --help                # Options for 'wait'
-```
-
-**When in doubt, ask the CLI.** This skill teaches *when* and *why* to use commands. For exact flags and syntax, `--help` is authoritative.
-
-## Quick Reference
-
-```bash
-# Start app
-agent-tui run <cmd> [-- args]        # Launch TUI under control
-
-# Observe
-agent-tui screenshot                  # Plain text view
-agent-tui screenshot --format json    # Machine-readable output
-
-# Act
-agent-tui press Enter                 # Press key(s)
-agent-tui press Ctrl+C                # Keyboard shortcuts
-agent-tui type "text"                 # Type text
-
-# Wait/Verify
-agent-tui wait "text" --assert        # Wait for text, fail if not found
-agent-tui wait "text" --gone --assert # Wait for text to disappear
-agent-tui wait --stable               # Wait for UI to stop changing
-
-# Manage
-agent-tui sessions                    # List active sessions
-agent-tui live start --open           # Start live preview
-agent-tui kill                        # End current session
-```

.gemini/skills/docs-changelog/SKILL.md

@@ -162,7 +162,5 @@ instructions for the other section.
 
 ## Finalize
 
-- After making changes, if `npm run format` fails, it may be necessary to run
-  `npm install` first to ensure all formatting dependencies are available.
-  Then, run `npm run format` to ensure consistency.
+- After making changes, run `npm run format` ONLY to ensure consistency.
 - Delete any temporary files created during the process.

.gemini/skills/docs-writer/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: docs-writer
 description:
-  Always use this skill when the task involves writing, reviewing, or editing
+  Always use this skill when the task involves writing, reviewing, or editing 
   files in the `/docs` directory or any `.md` files in the repository.
 ---
 
@@ -24,7 +24,7 @@ approach.
 
 - **Perspective and tense:** Address the reader as "you." Use active voice and
   present tense (e.g., "The API returns...").
-- **Tone:** Professional, friendly, and direct.
+- **Tone:** Professional, friendly, and direct. 
 - **Clarity:** Use simple vocabulary. Avoid jargon, slang, and marketing hype.
 - **Global Audience:** Write in standard US English. Avoid idioms and cultural
   references.
@@ -47,8 +47,8 @@ Write precisely to ensure your instructions are unambiguous.
   "foo" or "bar."
 - **Quota and limit terminology:** For any content involving resource capacity
   or using the word "quota" or "limit", strictly adhere to the guidelines in
-  the `quota-limit-style-guide.md` resource file. Generally, Use "quota" for
-  the administrative bucket and "limit" for the numerical ceiling.
+  the `quota-limit-style-guide.md` resource file. Generally, Use "quota" for the
+  administrative bucket and "limit" for the numerical ceiling.
 
 ### Formatting and syntax
 Apply consistent formatting to make documentation visually organized and
@@ -85,25 +85,17 @@ accessible.
 
 - **Callouts**: Use GitHub-flavored markdown alerts to highlight important
   information. To ensure the formatting is preserved by `npm run format`, place
-  an empty line, then a prettier ignore comment directly before the callout
-  block. Use `<!-- prettier-ignore -->` for standard Markdown files (`.md`) and
-  `{/* prettier-ignore */}` for MDX files (`.mdx`). The callout type (`[!TYPE]`)
-  should be on the first line, followed by a newline, and then the content, with
-  each subsequent line of content starting with `>`. Available types are `NOTE`,
-  `TIP`, `IMPORTANT`, `WARNING`, and `CAUTION`.
+  an empty line, then the `<!-- prettier-ignore -->` comment directly before
+  the callout block. The callout type (`[!TYPE]`) should be on the first line,
+  followed by a newline, and then the content, with each subsequent line of
+  content starting with `>`. Available types are `NOTE`, `TIP`, `IMPORTANT`,
+  `WARNING`, and `CAUTION`.
 
-  Example (.md):
+  Example:
 
 <!-- prettier-ignore -->
 > [!NOTE]
 > This is an example of a multi-line note that will be preserved
-> by Prettier.
-
-  Example (.mdx):
-
-{/* prettier-ignore */}
-> [!NOTE]
-> This is an example of a multi-line note that will be preserved
 > by Prettier.
 
 ### Links
@@ -126,10 +118,9 @@ accessible.
 <!-- prettier-ignore -->
 > [!NOTE]
 > This is an experimental feature currently under active development.
-(Note: Use `{/* prettier-ignore */}` if editing an `.mdx` file.)
 
 - **Headings:** Use hierarchical headings to support the user journey.
-- **Procedures:**
+- **Procedures:** 
   - Introduce lists of steps with a complete sentence.
   - Start each step with an imperative verb.
   - Number sequential steps; use bullets for non-sequential lists.
@@ -143,7 +134,7 @@ accessible.
 
 ## Phase 2: Preparation
 Before modifying any documentation, thoroughly investigate the request and the
-surrounding context.
+surrounding context. 
 
 1.  **Clarify:** Understand the core request. Differentiate between writing new
     content and editing existing content. If the request is ambiguous (e.g.,
@@ -154,8 +145,6 @@ surrounding context.
 4.  **Connect:** Identify all referencing pages if changing behavior. Check if
     `docs/sidebar.json` needs updates.
 5.  **Plan:** Create a step-by-step plan before making changes.
-6.  **Audit Docset:** If asked to audit the documentation, follow the procedural
-    guide in [docs-auditing.md](./references/docs-auditing.md).
 
 ## Phase 3: Execution
 Implement your plan by either updating existing files or creating new ones
@@ -168,7 +157,7 @@ documentation.
 
 - **Gaps:** Identify areas where the documentation is incomplete or no longer
   reflects existing code.
-- **Structure:** Apply "Structure (New Docs)" rules (BLUF, headings, etc.) when
+- **Structure:** Apply "Structure (New Docs)" rules (BLUF, headings, etc.) when 
   adding new sections to existing pages.
 - **Headers**: If you change a header, you must check for links that lead to
   that header and update them.
@@ -179,16 +168,15 @@ documentation.
   documents.
 
 ## Phase 4: Verification and finalization
-Perform a final quality check to ensure that all changes are correctly
-formatted and that all links are functional.
+Perform a final quality check to ensure that all changes are correctly formatted
+and that all links are functional.
 
 1.  **Accuracy:** Ensure content accurately reflects the implementation and
   technical behavior.
 2.  **Self-review:** Re-read changes for formatting, correctness, and flow.
-3.  **Link check:** Verify all new and existing links leading to or from
-    modified pages. If you changed a header, ensure that any links that lead to
-    it are updated.
-4.  **Format:** If `npm run format` fails, it may be necessary to run `npm
-    install` first to ensure all formatting dependencies are available. Once all
-    changes are complete, ask to execute `npm run format` to ensure consistent
-    formatting across the project. If the user confirms, execute the command.
+3.  **Link check:** Verify all new and existing links leading to or from modified
+    pages. If you changed a header, ensure that any links that lead to it are
+    updated.
+4.  **Format:** Once all changes are complete, ask to execute `npm run format`
+    to ensure consistent formatting across the project. If the user confirms,
+    execute the command.

.gemini/skills/docs-writer/references/docs-auditing.md

@@ -1,195 +0,0 @@
-# Procedural Guide: Auditing the Docset
-
-This guide outlines the process for auditing the Gemini CLI documentation for
-correctness and adherence to style guidelines. This process involves both an
-"Editor" and "Technical Writer" phase.
-
-## Objective
-
-To ensure all public-facing documentation is accurate, up-to-date, adheres to
-the Gemini CLI documentation style guide, and reflects the current state of the
-codebase.
-
-## Phase 1: Editor Audit
-
-**Role:** The editor is responsible for identifying potential issues based on
-style guide violations and technical inaccuracies.
-
-### Steps
-
-1.  **Identify Documentation Scope:**
-    - Read `docs/sidebar.json` to get a list of all viewable documentation
-      pages.
-    - For each entry with a `slug`, convert it into a file path (e.g., `docs` ->
-      `docs/index.md`, `docs/get-started` -> `docs/get-started.md`). Ignore
-      entries with `link` properties.
-
-2.  **Prepare Audit Results File:**
-    - Create a new Markdown file named `audit-results-[YYYY-MM-DD].md` (e.g.,
-      `audit-results-2026-03-13.md`). This file will contain all identified
-      violations and recommendations.
-
-3.  **Retrieve Style Guidelines:**
-    - Familiarize yourself with the `docs-writer` skill instructions and the
-      included style guidelines.
-
-4.  **Audit Each Document:**
-    - For each documentation file identified in Step 1, read its content.
-    - **Review against Style Guide:**
-      - **Voice and Tone Violations:**
-        - **Unprofessional Tone:** Identify phrasing that is overly casual,
-          defensive, or lacks a professional and friendly demeanor.
-        - **Indirectness or Vagueness:** Identify sentences that are
-          unnecessarily wordy or fail to be concise and direct.
-        - **Incorrect Pronoun:** Identify any use of third-person pronouns
-          (e.g., "we," "they," "the user") when referring to the reader, instead
-          of the second-person pronoun **"you"**.
-        - **Passive Voice:** Identify sentences written in the passive voice.
-        - **Incorrect Tense:** Identify the use of past or future tense verbs,
-          instead of the **present tense**.
-        - **Poor Vocabulary:** Identify the use of jargon, slang, or overly
-          informal language.
-      - **Language and Grammar Violations:**
-        - **Lack of Conciseness:** Identify unnecessarily long phrases or
-          sentences.
-        - **Punctuation Errors:** Identify incorrect or missing punctuation.
-        - **Ambiguous Dates:** Identify dates that could be misinterpreted
-          (e.g., "next Monday" instead of "April 15, 2026").
-        - **Abbreviation Usage:** Identify the use of abbreviations that should
-          be spelled out (e.g., "e.g." instead of "for example").
-        - **Terminology:** Check for incorrect or inconsistent use of
-          product-specific terms (e.g., "quota" vs. "limit").
-      - **Formatting and Syntax Violations:**
-        - **Missing Overview:** Check for the absence of a brief overview
-          paragraph at the start of the document.
-        - **Line Length:** Identify any lines of text that exceed **80
-          characters** (text wrap violation).
-        - **Casing:** Identify incorrect casing for headings, titles, or named
-          entities (e.g., product names like `Gemini CLI`).
-        - **List Formatting:** Identify incorrectly formatted lists (e.g.,
-          inconsistent indentation or numbering).
-        - **Incorrect Emphasis:** Identify incorrect use of bold text (should
-          only be used for UI elements) or code font (should be used for code,
-          file names, or command-line input).
-        - **Link Quality:** Identify links with non-descriptive anchor text
-          (e.g., "click here").
-        - **Image Alt Text:** Identify images with missing or poor-quality
-          (non-descriptive) alt text.
-      - **Structure Violations:**
-        - **Missing BLUF:** Check for the absence of a "Bottom Line Up Front"
-          summary at the start of complex sections or documents.
-        - **Experimental Feature Notes:** Identify experimental features that
-          are not clearly labeled with a standard note.
-        - **Heading Hierarchy:** Check for skipped heading levels (e.g., going
-          from `##` to `####`).
-        - **Procedure Clarity:** Check for procedural steps that do not start
-          with an imperative verb or where a condition is placed _after_ the
-          instruction.
-        - **Element Misuse:** Identify the incorrect or inappropriate use of
-          special elements (e.g., Notes, Warnings, Cautions).
-        - **Table of Contents:** Identify the presence of a dynamically
-          generated or manually included table of contents.
-        - **Missing Next Steps:** Check for procedural documents that lack a
-          "Next steps" section (if applicable).
-    - **Verify Code Accuracy (if applicable):**
-      - If the document contains code snippets (e.g., shell commands, API calls,
-        file paths, Docker image versions), use `grep_search` and `read_file`
-        within the `packages/` directory (or other relevant parts of the
-        codebase) to ensure the code is still accurate and up-to-date. Pay close
-        attention to version numbers, package names, and command syntax.
-    - **Record Findings:** For each **violation** or inaccuracy found:
-      - Note the file path.
-      - Describe the violation (e.g., "Violation (Language and Grammar): Uses
-        'e.g.'").
-      - Provide a clear and actionable recommendation to correct the issue.
-        (e.g., "Recommendation: Replace 'e.g.' with 'for example'." or
-        "Recommendation: Replace '...' with '...' in active voice.).
-      - Append these findings to `audit-results-[YYYY-MM-DD].md`.
-
-## Phase 2: Software Engineer Audit
-
-**Role:** The software engineer is responsible for finding undocumented features
-by auditing the codebase and recent changelogs, and passing these findings to
-the technical writer.
-
-### Steps
-
-1.  **Proactive Codebase Audit:**
-    - Audit high-signal areas of the codebase to identify undocumented features.
-      You MUST review:
-      - `packages/cli/src/commands/`
-      - `packages/core/src/tools/`
-      - `packages/cli/src/config/settings.ts`
-
-2.  **Review Recent Updates:**
-    - Check recent changelogs in stable and announcements within the
-      documentation to see if newly introduced features are documented properly.
-
-3.  **Evaluate and Record Findings:**
-    - Determine if these features are adequately covered in the docs. They do
-      not need to be documented word for word, but major features that customers
-      should care about probably should have an article.
-    - Append your findings to the `audit-results-[YYYY-MM-DD].md` file,
-      providing a brief description of the feature and where it should be
-      documented.
-
-## Phase 3: Technical Writer Implementation
-
-**Role:** The technical writer handles input from both the editor and the
-software engineer, makes appropriate decisions about what to change, and
-implements the approved changes.
-
-### Steps
-
-1.  **Review Audit Results:**
-    - Read `audit-results-[YYYY-MM-DD].md` to understand all identified issues,
-      undocumented features, and recommendations from both the Editor and
-      Software Engineer phases.
-
-2.  **Make Decisions and Log Reasoning:**
-    - Create or update an implementation log (e.g.,
-      `audit-implementation-log-[YYYY-MM-DD].md`).
-    - Make sure the logs are updated for all steps, documenting your reasoning
-      for each recommendation (why it was accepted, modified, or rejected). This
-      is required for a final check by a human in the PR.
-
-3.  **Implement Changes:**
-    - For each approved recommendation:
-      - Read the target documentation file.
-      - Apply the recommended change using the `replace` tool. Pay close
-        attention to `old_string` for exact matches, including whitespace and
-        newlines. For multiple occurrences of the same simple string (e.g.,
-        "e.g."), use `allow_multiple: true`.
-      - **String replacement safeguards:** When applying these fixes across the
-        docset, you must verify the following:
-        - **Preserve Code Blocks:** Explicitly verify that no code blocks,
-          inline code snippets, terminal commands, or file paths have been
-          erroneously capitalized or modified.
-        - **Preserve Literal Strings:** Never alter the wording of literal error
-          messages, UI quotes, or system logs. For example, if a style rule says
-          to remove the word "please", you must NOT remove it if it appears
-          inside a quoted error message (e.g.,
-          `Error: Please contact your administrator`).
-        - **Verify Sentence Casing:** When removing filler words (like "please")
-          from the beginning of a sentence or list item, always verify that the
-          new first word of the sentence is properly capitalized.
-      - For structural changes (e.g., adding an overview paragraph), use
-        `replace` or `write_file` as appropriate.
-      - For broken links, determine the correct new path or update the link
-        text.
-      - For creating new files (e.g., `docs/get-started.md` to fix a broken
-        link, or a new feature article), use `write_file`.
-
-4.  **Execute Auto-Generation Scripts:**
-    - Some documentation pages are auto-generated from the codebase and should
-      be updated using npm scripts rather than manual edits. After implementing
-      manual changes (especially if you edited settings or configurations based
-      on SWE recommendations), ensure you run:
-      - `npm run docs:settings` to generate/update the configuration reference.
-      - `npm run docs:keybindings` to generate/update the keybindings reference.
-
-5.  **Format Code:**
-    - **Dependencies:** If `npm run format` fails, it may be necessary to run
-      `npm install` first to ensure all formatting dependencies are available.
-    - After all changes have been implemented, run `npm run format` to ensure
-      consistent formatting across the project.

.gemini/skills/tui-tester/SKILL.md

@@ -1,65 +0,0 @@
----
-name: tui-tester
-description: Expert guidance for testing Gemini CLI behavior and visual output using terminal automation.
----
-
-# TUI Tester Skill
-
-This skill provides the operational manual for verifying Gemini CLI behavioral changes and visual output using terminal automation.
-
-## Core Responsibilities
-
-- **Verify Behavior**: Confirm that code changes result in the expected terminal interactions.
-- **Visual Validation**: Ensure the TUI renders correctly across different terminal sizes and states.
-- **Regression Testing**: Use automation to prevent breaking existing interactive workflows.
-
-## Critical Protocol
-
-When performing TUI testing, you must adhere to these strict rules:
-
-### 1. Initialization
-**YOUR ABSOLUTE FIRST ACTION MUST BE:**
-Activate the `agent-tui` skill. This provides the underlying tools needed for terminal automation.
-
-### 2. Environment Setup (macOS / Parallel Safe)
-Ensure the global daemon is running and the live preview is open:
-```bash
-if ! agent-tui sessions >/dev/null 2>&1; then
-  tmux kill-session -t agent-tui 2>/dev/null || true
-  agent-tui daemon stop 2>/dev/null || true
-  rm -f /tmp/agent-tui*
-  tmux new-session -d -s agent-tui 'agent-tui daemon start --foreground > /tmp/agent-tui-daemon.log 2>&1'
-  sleep 1
-fi
-agent-tui live start --open
-```
-
-### 3. Session Management
-- **Session IDs**: Always use the `session_id` returned by `agent-tui run` for subsequent interactions.
-- **Atomic Execution**: Execute exactly one command per turn. Do not pipeline actions.
-- **The Loop**: Action -> Wait -> Screenshot -> Verify -> Next Action.
-
-### 4. Gemini CLI Specifics
-- **Build First**: Always run `npm run build` or `npm run build:all` before testing local changes.
-- **Bypass Trust**: Set `GEMINI_CLI_TRUST_WORKSPACE=true` to avoid focus-stealing modals.
-- **Isolate Config**: Use `GEMINI_CLI_HOME` to prevent interference with your personal settings.
-
-## Workflow Example
-
-```bash
-# Start the CLI
-env GEMINI_CLI_TRUST_WORKSPACE=true agent-tui run node packages/cli/dist/index.js
-
-# Wait for the prompt
-agent-tui wait "│" --assert
-
-# Send a command
-agent-tui type "/help"
-agent-tui press Enter
-
-# Verify output
-agent-tui wait "Available Commands" --assert
-```
-
-## Error Recovery
-If a wait times out, take a fresh screenshot to diagnose the state. If you see `os error 61`, restart the daemon using the tmux method.

.geminiignore

@@ -1,2 +1 @@
 packages/core/src/services/scripts/*.exe
-gha-creds-*.json

.github/actions/calculate-vars/action.yml

@@ -14,6 +14,12 @@ outputs:
 runs:
   using: 'composite'
   steps:
+    - name: 'Print inputs'
+      shell: 'bash'
+      env:
+        JSON_INPUTS: '${{ toJSON(inputs) }}'
+      run: 'echo "$JSON_INPUTS"'
+
     - name: 'Set vars for simplified logic'
       id: 'set_vars'
       shell: 'bash'

.github/actions/create-pull-request/action.yml

@@ -30,6 +30,11 @@ inputs:
 runs:
   using: 'composite'
   steps:
+    - name: '📝 Print Inputs'
+      shell: 'bash'
+      env:
+        JSON_INPUTS: '${{ toJSON(inputs) }}'
+      run: 'echo "$JSON_INPUTS"'
     - name: 'Creates a Pull Request'
       if: "inputs.dry-run != 'true'"
       env:

.github/actions/download-mac-binaries/action.yml

@@ -1,23 +0,0 @@
-name: 'Download Mac Binaries'
-description: 'Downloads the unsigned macOS binaries (x64 and arm64)'
-inputs:
-  path:
-    description: 'The base path to download the binaries to'
-    required: true
-    default: 'dist'
-runs:
-  using: 'composite'
-  steps:
-    - name: 'Download macOS arm64 binary'
-      uses: 'actions/download-artifact@cc203385981b70ca67e1cc392babf9cc229d5806' # ratchet:actions/download-artifact@v4
-      continue-on-error: true
-      with:
-        name: 'gemini-darwin-arm64-unsigned'
-        path: '${{ inputs.path }}/darwin-arm64'
-
-    - name: 'Download macOS x64 binary'
-      uses: 'actions/download-artifact@cc203385981b70ca67e1cc392babf9cc229d5806' # ratchet:actions/download-artifact@v4
-      continue-on-error: true
-      with:
-        name: 'gemini-darwin-x64-unsigned'
-        path: '${{ inputs.path }}/darwin-x64'

.github/actions/post-coverage-comment/action.yml

@@ -27,6 +27,11 @@ inputs:
 runs:
   using: 'composite'
   steps:
+    - name: '📝 Print Inputs'
+      shell: 'bash'
+      env:
+        JSON_INPUTS: '${{ toJSON(inputs) }}'
+      run: 'echo "$JSON_INPUTS"'
     - name: 'Prepare Coverage Comment'
       id: 'prep_coverage_comment'
       shell: 'bash'

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

@@ -75,6 +75,12 @@ inputs:
 runs:
   using: 'composite'
   steps:
+    - name: '📝 Print Inputs'
+      shell: 'bash'
+      env:
+        JSON_INPUTS: '${{ toJSON(inputs) }}'
+      run: 'echo "$JSON_INPUTS"'
+
     - name: '👤 Configure Git User'
       working-directory: '${{ inputs.working-directory }}'
       shell: 'bash'
@@ -108,14 +114,13 @@ runs:
         BRANCH_NAME: '${{ steps.release_branch.outputs.BRANCH_NAME }}'
         DRY_RUN: '${{ inputs.dry-run }}'
         RELEASE_TAG: '${{ inputs.release-tag }}'
-        GIT_PUSH_TOKEN: '${{ inputs.github-release-token || inputs.github-token }}'
       run: |-
         set -e
         git add package.json package-lock.json packages/*/package.json
         git commit -m "chore(release): ${RELEASE_TAG}"
         if [[ "${DRY_RUN}" == "false" ]]; then
           echo "Pushing release branch to remote..."
-          git push "https://x-access-token:${GIT_PUSH_TOKEN}@github.com/${{ github.repository }}.git" "HEAD:${BRANCH_NAME}" --follow-tags
+          git push --set-upstream origin "${BRANCH_NAME}" --follow-tags
         else
           echo "Dry run enabled. Skipping push."
         fi
@@ -167,12 +172,11 @@ runs:
       shell: 'bash'
       run: |
         npm publish \
-          --ignore-scripts \
           --dry-run="${INPUTS_DRY_RUN}" \
           --workspace="${INPUTS_CORE_PACKAGE_NAME}" \
-          --tag staging-tmp
+          --no-tag
         if [[ "${INPUTS_DRY_RUN}" == "false" ]]; then
-          npm dist-tag rm ${INPUTS_CORE_PACKAGE_NAME} staging-tmp
+          npm dist-tag rm ${INPUTS_CORE_PACKAGE_NAME} false
         fi
 
     - name: '🔗 Install latest core package'
@@ -216,12 +220,11 @@ runs:
       shell: 'bash'
       run: |
         npm publish \
-          --ignore-scripts \
           --dry-run="${INPUTS_DRY_RUN}" \
           --workspace="${INPUTS_CLI_PACKAGE_NAME}" \
-          --tag staging-tmp
+          --no-tag
         if [[ "${INPUTS_DRY_RUN}" == "false" ]]; then
-          npm dist-tag rm ${INPUTS_CLI_PACKAGE_NAME} staging-tmp
+          npm dist-tag rm ${INPUTS_CLI_PACKAGE_NAME} false
         fi
 
     - name: 'Get a2a-server Token'
@@ -244,12 +247,11 @@ runs:
       # Tag staging for initial release
       run: |
         npm publish \
-          --ignore-scripts \
           --dry-run="${INPUTS_DRY_RUN}" \
           --workspace="${INPUTS_A2A_PACKAGE_NAME}" \
-          --tag staging-tmp
+          --no-tag
           if [[ "${INPUTS_DRY_RUN}" == "false" ]]; then
-            npm dist-tag rm ${INPUTS_A2A_PACKAGE_NAME} staging-tmp
+            npm dist-tag rm ${INPUTS_A2A_PACKAGE_NAME} false
           fi
 
     - name: '🔬 Verify NPM release by version'
@@ -306,21 +308,8 @@ runs:
         fi
         rm -rf test-bundle
 
-        RELEASE_ASSETS=("gemini-cli-bundle.zip")
-
-        # Check for and prepare macOS binaries if they exist
-        for arch in arm64 x64; do
-          BINARY_PATH="dist/darwin-${arch}/gemini"
-          if [[ -f "$BINARY_PATH" ]]; then
-            chmod +x "$BINARY_PATH"
-            ZIP_NAME="gemini-darwin-${arch}-unsigned.zip"
-            zip -j "$ZIP_NAME" "$BINARY_PATH"
-            RELEASE_ASSETS+=("$ZIP_NAME")
-          fi
-        done
-
         gh release create "${INPUTS_RELEASE_TAG}" \
-          "${RELEASE_ASSETS[@]}" \
+          gemini-cli-bundle.zip \
           --target "${STEPS_RELEASE_BRANCH_OUTPUTS_BRANCH_NAME}" \
           --title "Release ${INPUTS_RELEASE_TAG}" \
           --notes-start-tag "${INPUTS_PREVIOUS_TAG}" \
@@ -334,8 +323,7 @@ runs:
       shell: 'bash'
       run: |
         echo "Cleaning up release branch ${STEPS_RELEASE_BRANCH_OUTPUTS_BRANCH_NAME}..."
-        git push "https://x-access-token:${GIT_PUSH_TOKEN}@github.com/${{ github.repository }}.git" --delete "${STEPS_RELEASE_BRANCH_OUTPUTS_BRANCH_NAME}"
+        git push origin --delete "${STEPS_RELEASE_BRANCH_OUTPUTS_BRANCH_NAME}"
 
       env:
-        GIT_PUSH_TOKEN: '${{ inputs.github-release-token || inputs.github-token }}'
         STEPS_RELEASE_BRANCH_OUTPUTS_BRANCH_NAME: '${{ steps.release_branch.outputs.BRANCH_NAME }}'

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

@@ -18,6 +18,11 @@ inputs:
 runs:
   using: 'composite'
   steps:
+    - name: '📝 Print Inputs'
+      shell: 'bash'
+      env:
+        JSON_INPUTS: '${{ toJSON(inputs) }}'
+      run: 'echo "$JSON_INPUTS"'
     - name: 'Checkout'
       uses: 'actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955' # ratchet:actions/checkout@v4
       with:

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

@@ -28,6 +28,11 @@ inputs:
 runs:
   using: 'composite'
   steps:
+    - name: '📝 Print Inputs'
+      shell: 'bash'
+      env:
+        JSON_INPUTS: '${{ toJSON(inputs) }}'
+      run: 'echo "$JSON_INPUTS"'
     - name: 'Checkout'
       uses: 'actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5' # ratchet:actions/checkout@v4
       with:

.github/actions/run-tests/action.yml

@@ -13,6 +13,11 @@ inputs:
 runs:
   using: 'composite'
   steps:
+    - name: '📝 Print Inputs'
+      shell: 'bash'
+      env:
+        JSON_INPUTS: '${{ toJSON(inputs) }}'
+      run: 'echo "$JSON_INPUTS"'
     - name: 'Install system dependencies'
       if: "runner.os == 'Linux'"
       run: |
@@ -23,7 +28,6 @@ runs:
     - name: 'Run Tests'
       env:
         GEMINI_API_KEY: '${{ inputs.gemini_api_key }}'
-        GEMINI_CLI_TRUST_WORKSPACE: true
       working-directory: '${{ inputs.working-directory }}'
       run: |-
         echo "::group::Build"

.github/actions/tag-npm-release/action.yml

@@ -40,6 +40,12 @@ inputs:
 runs:
   using: 'composite'
   steps:
+    - name: '📝 Print Inputs'
+      shell: 'bash'
+      env:
+        JSON_INPUTS: '${{ toJSON(inputs) }}'
+      run: 'echo "$JSON_INPUTS"'
+
     - name: 'Setup Node.js'
       uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020'
       with:

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

@@ -29,6 +29,12 @@ inputs:
 runs:
   using: 'composite'
   steps:
+    - name: '📝 Print Inputs'
+      shell: 'bash'
+      env:
+        JSON_INPUTS: '${{ toJSON(inputs) }}'
+      run: 'echo "$JSON_INPUTS"'
+
     - name: 'setup node'
       uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020' # ratchet:actions/setup-node@v4
       with:
@@ -86,13 +92,12 @@ runs:
     - name: 'Install dependencies for integration tests'
       shell: 'bash'
       working-directory: '${{ inputs.working-directory }}'
-      run: 'npm ci --ignore-scripts'
+      run: 'npm ci'
 
     - name: '🔬 Run integration tests against NPM release'
       working-directory: '${{ inputs.working-directory }}'
       env:
         GEMINI_API_KEY: '${{ inputs.gemini_api_key }}'
-        GEMINI_CLI_TRUST_WORKSPACE: true
         INTEGRATION_TEST_USE_INSTALLED_GEMINI: 'true'
         # We must diable CI mode here because it interferes with interactive tests.
         # See https://github.com/google-gemini/gemini-cli/issues/10517

.github/dependabot.yml

@@ -8,10 +8,6 @@ updates:
     open-pull-requests-limit: 10
     reviewers:
       - 'joshualitt'
-    cooldown:
-      semver-major-days: 14
-      semver-minor-days: 14
-      semver-patch-days: 14
     groups:
       npm-dependencies:
         patterns:
@@ -28,10 +24,6 @@ updates:
     open-pull-requests-limit: 10
     reviewers:
       - 'joshualitt'
-    cooldown:
-      semver-major-days: 14
-      semver-minor-days: 14
-      semver-patch-days: 14
     groups:
       actions-dependencies:
         patterns:

.github/scripts/apply-issue-labels.cjs

@@ -1,278 +0,0 @@
-/**
- * @license
- * Copyright 2026 Google LLC
- * SPDX-License-Identifier: Apache-2.0
- */
-
-module.exports = async ({ github, context, core }) => {
-  const extractJson = (raw) => {
-    if (!raw || raw === '[]' || raw === '') return [];
-    try {
-      // First, try to parse the raw output as JSON.
-      return JSON.parse(raw);
-    } catch {
-      // If that fails, check for a markdown code block.
-      core.info(
-        'Direct JSON parsing failed. Trying to extract from a markdown block.',
-      );
-      const jsonMatch = raw.match(/```json\s*([\s\S]*?)\s*```/);
-      if (jsonMatch && jsonMatch[1]) {
-        try {
-          return JSON.parse(jsonMatch[1].trim());
-        } catch (markdownError) {
-          core.warning(
-            `Failed to parse extracted JSON from markdown block: ${markdownError.message}`,
-          );
-        }
-      }
-
-      // Try to find a raw JSON array in the output.
-      const jsonArrayMatch = raw.match(
-        /\[\s*\{\s*"issue_number"[\s\S]*\}\s*\]/,
-      );
-      if (jsonArrayMatch) {
-        try {
-          return JSON.parse(jsonArrayMatch[0]);
-        } catch {
-          const fallbackMatch = raw.match(/(\[\s*\{\s*"issue_number"[\s\S]*)/);
-          if (fallbackMatch) {
-            try {
-              const cleaned = fallbackMatch[0].substring(
-                0,
-                fallbackMatch[0].lastIndexOf(']') + 1,
-              );
-              return JSON.parse(cleaned);
-            } catch (fallbackError) {
-              core.warning(
-                `Failed to parse extracted JSON using fallback regex: ${fallbackError.message}`,
-              );
-            }
-          }
-        }
-      }
-    }
-    core.warning('No valid JSON could be extracted from input.');
-    return [];
-  };
-
-  // Collect all outputs from environment variables
-  // Prioritize EFFORT results over STANDARD results by processing Effort FIRST
-  // so that its labels appear first in the merged arrays (and thus win in mutually exclusive logic)
-  const effortRaw = process.env.LABELS_OUTPUT_EFFORT;
-  const standardRaw = process.env.LABELS_OUTPUT_STANDARD;
-  const genericRaw = process.env.LABELS_OUTPUT;
-
-  const resultsByIssue = new Map();
-
-  const processResults = (results, _sourceName) => {
-    for (const entry of results) {
-      const issueNumber = entry.issue_number;
-      if (!issueNumber) continue;
-
-      if (!resultsByIssue.has(issueNumber)) {
-        resultsByIssue.set(issueNumber, {
-          issue_number: issueNumber,
-          labels_to_add: [...(entry.labels_to_add || [])],
-          labels_to_remove: [...(entry.labels_to_remove || [])],
-          explanation: entry.explanation || '',
-          effort_analysis: entry.effort_analysis || '',
-        });
-      } else {
-        const existing = resultsByIssue.get(issueNumber);
-        // Combine labels
-        existing.labels_to_add = [
-          ...new Set([
-            ...existing.labels_to_add,
-            ...(entry.labels_to_add || []),
-          ]),
-        ];
-        existing.labels_to_remove = [
-          ...new Set([
-            ...existing.labels_to_remove,
-            ...(entry.labels_to_remove || []),
-          ]),
-        ];
-
-        // Combine explanations (if different)
-        if (
-          entry.explanation &&
-          !existing.explanation.includes(entry.explanation)
-        ) {
-          existing.explanation = existing.explanation
-            ? `${existing.explanation}\n\n${entry.explanation}`
-            : entry.explanation;
-        }
-
-        // Take effort analysis if present
-        if (entry.effort_analysis && !existing.effort_analysis) {
-          existing.effort_analysis = entry.effort_analysis;
-        }
-      }
-    }
-  };
-
-  // Order matters: Effort first so its labels win in conflict resolution
-  processResults(extractJson(effortRaw), 'EFFORT');
-  processResults(extractJson(standardRaw), 'STANDARD');
-  processResults(extractJson(genericRaw), 'GENERIC');
-
-  const finalResults = Array.from(resultsByIssue.values());
-  core.info(`Aggregated triage results for ${finalResults.length} issues.`);
-
-  for (const entry of finalResults) {
-    const issueNumber = entry.issue_number;
-    let labelsToAdd = entry.labels_to_add || [];
-    let labelsToRemove = entry.labels_to_remove || [];
-    let existingLabels = [];
-
-    // Fetch existing labels early
-    try {
-      const { data: issueData } = await github.rest.issues.get({
-        owner: context.repo.owner,
-        repo: context.repo.repo,
-        issue_number: issueNumber,
-      });
-      existingLabels = issueData.labels.map((l) =>
-        typeof l === 'string' ? l : l.name,
-      );
-    } catch (e) {
-      core.warning(
-        `Failed to fetch existing labels for #${issueNumber}: ${e.message}`,
-      );
-    }
-
-    // Programmatic Priority Downgrade Logic
-    if (labelsToAdd.includes('status/need-information')) {
-      const targetPriority = labelsToAdd.find((l) => l.startsWith('priority/'));
-      if (targetPriority) {
-        let downgradedPriority = null;
-        if (targetPriority === 'priority/p0')
-          downgradedPriority = 'priority/p1';
-        if (targetPriority === 'priority/p1')
-          downgradedPriority = 'priority/p2';
-
-        if (downgradedPriority) {
-          core.info(
-            `Programmatically downgrading ${targetPriority} to ${downgradedPriority} due to status/need-information`,
-          );
-          labelsToAdd = labelsToAdd.filter((l) => l !== targetPriority);
-          labelsToAdd.push(downgradedPriority);
-        }
-      }
-    }
-
-    labelsToRemove.push('status/need-triage');
-
-    if (
-      labelsToAdd.includes('status/manual-triage') ||
-      existingLabels.includes('status/manual-triage')
-    ) {
-      labelsToRemove.push('status/bot-triaged');
-      labelsToAdd = labelsToAdd.filter((l) => l !== 'status/bot-triaged');
-    } else {
-      labelsToAdd.push('status/bot-triaged');
-    }
-
-    // Resolve internal conflicts (e.g., adding P1 and P2)
-    // We already resolved these by putting Effort first in the combined list
-
-    // Resolve external conflicts with existing labels
-    if (labelsToAdd.some((l) => l.startsWith('area/'))) {
-      labelsToRemove.push(
-        ...existingLabels.filter((l) => l.startsWith('area/')),
-      );
-    }
-    if (labelsToAdd.some((l) => l.startsWith('priority/'))) {
-      labelsToRemove.push(
-        ...existingLabels.filter((l) => l.startsWith('priority/')),
-      );
-    }
-    if (labelsToAdd.some((l) => l.startsWith('kind/'))) {
-      labelsToRemove.push(
-        ...existingLabels.filter((l) => l.startsWith('kind/')),
-      );
-    }
-
-    // Enforce mutual exclusivity in the TO-ADD list (Architect wins)
-    const exclusivePrefixes = ['area/', 'priority/', 'kind/'];
-    for (const prefix of exclusivePrefixes) {
-      const filtered = labelsToAdd.filter((l) => l.startsWith(prefix));
-      if (filtered.length > 1) {
-        const winner = filtered[0]; // First one wins
-        core.info(
-          `Issue #${issueNumber} has multiple ${prefix} labels suggested. Keeping "${winner}" and discarding others.`,
-        );
-        labelsToAdd = labelsToAdd.filter(
-          (l) => !l.startsWith(prefix) || l === winner,
-        );
-      }
-    }
-
-    // Final deduplication and cleanup
-    labelsToRemove = [...new Set(labelsToRemove)].filter(
-      (l) => !labelsToAdd.includes(l) && existingLabels.includes(l),
-    );
-    labelsToAdd = [...new Set(labelsToAdd)].filter(
-      (l) => !existingLabels.includes(l),
-    );
-
-    // Batch label operations
-    if (labelsToAdd.length > 0) {
-      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(', ')}`,
-      );
-    }
-
-    if (labelsToRemove.length > 0) {
-      for (const label of labelsToRemove) {
-        try {
-          await github.rest.issues.removeLabel({
-            owner: context.repo.owner,
-            repo: context.repo.repo,
-            issue_number: issueNumber,
-            name: label,
-          });
-        } catch (e) {
-          if (e.status !== 404)
-            core.warning(
-              `Failed to remove label ${label} from #${issueNumber}: ${e.message}`,
-            );
-        }
-      }
-      core.info(
-        `Successfully removed labels for #${issueNumber}: ${labelsToRemove.join(', ')}`,
-      );
-    }
-
-    // Post comment if needed
-    const needsInfoAdded =
-      labelsToAdd.includes('status/need-information') &&
-      !existingLabels.includes('status/need-information');
-    const hasEffortAnalysis = !!entry.effort_analysis;
-
-    if (needsInfoAdded || hasEffortAnalysis) {
-      let commentBody = '';
-      if (needsInfoAdded && entry.explanation) commentBody += entry.explanation;
-      if (hasEffortAnalysis) {
-        if (commentBody) commentBody += '\n\n';
-        commentBody += `**Effort Analysis:**\n${entry.effort_analysis}`;
-      }
-
-      if (commentBody) {
-        await github.rest.issues.createComment({
-          owner: context.repo.owner,
-          repo: context.repo.repo,
-          issue_number: issueNumber,
-          body: commentBody,
-        });
-        core.info(`Posted required comment for #${issueNumber}`);
-      }
-    }
-  }
-};

.github/scripts/cleanup-triage-labels.cjs

@@ -1,74 +0,0 @@
-/**
- * @license
- * Copyright 2026 Google LLC
- * SPDX-License-Identifier: Apache-2.0
- */
-
-const fs = require('node:fs');
-
-module.exports = async ({ github, context, core }) => {
-  let issuesToCleanup = [];
-  try {
-    const fileContent = fs.readFileSync('issues_to_cleanup.json', 'utf8');
-    issuesToCleanup = JSON.parse(fileContent);
-  } catch (error) {
-    if (error.code === 'ENOENT') {
-      core.info('No issues found to clean up.');
-      return;
-    }
-    core.setFailed(`Failed to read issues_to_cleanup.json: ${error.message}`);
-    return;
-  }
-
-  for (const issue of issuesToCleanup) {
-    try {
-      const { data: issueData } = await github.rest.issues.get({
-        owner: context.repo.owner,
-        repo: context.repo.repo,
-        issue_number: issue.number,
-      });
-
-      const labels = issueData.labels.map((l) =>
-        typeof l === 'string' ? l : l.name,
-      );
-
-      if (
-        labels.includes('status/bot-triaged') &&
-        labels.includes('status/need-triage')
-      ) {
-        await github.rest.issues.removeLabel({
-          owner: context.repo.owner,
-          repo: context.repo.repo,
-          issue_number: issue.number,
-          name: 'status/need-triage',
-        });
-        core.info(
-          `Successfully removed status/need-triage from #${issue.number}`,
-        );
-      }
-
-      if (
-        labels.includes('status/bot-triaged') &&
-        labels.includes('status/manual-triage')
-      ) {
-        await github.rest.issues.removeLabel({
-          owner: context.repo.owner,
-          repo: context.repo.repo,
-          issue_number: issue.number,
-          name: 'status/bot-triaged',
-        });
-        core.info(
-          `Successfully removed status/bot-triaged from #${issue.number} because it requires manual triage`,
-        );
-      }
-    } catch (error) {
-      core.warning(
-        `Failed to clean up labels for #${issue.number}: ${error.message}`,
-      );
-    }
-  }
-
-  core.info(
-    `Cleaned up conflicting labels from ${issuesToCleanup.length} issues.`,
-  );
-};

.github/scripts/gemini-lifecycle-manager.cjs

@@ -1,380 +0,0 @@
-/**
- * @license
- * Copyright 2026 Google LLC
- * SPDX-License-Identifier: Apache-2.0
- */
-
-/**
- * Gemini Scheduled Lifecycle Manager Script
- * @param {object} param0
- * @param {import('@octokit/rest').Octokit} param0.github
- * @param {import('@actions/github/lib/context').Context} param0.context
- * @param {import('@actions/core')} param0.core
- */
-module.exports = async ({ github, context, core }) => {
-  const dryRun = process.env.DRY_RUN === 'true';
-  const owner = context.repo.owner;
-  const repo = context.repo.repo;
-
-  core.info(`Running in ${dryRun ? 'DRY RUN' : 'PRODUCTION'} mode.`);
-
-  const STALE_LABEL = 'stale';
-  const NEED_INFO_LABEL = 'status/need-information';
-  const EXEMPT_LABELS = [
-    'pinned',
-    'security',
-    '🔒 maintainer only',
-    'help wanted',
-    '🗓️ Public Roadmap',
-  ];
-
-  const STALE_DAYS = 60;
-  const CLOSE_DAYS = 14;
-  const NO_RESPONSE_DAYS = 14;
-
-  const now = new Date();
-  const staleThreshold = new Date(
-    now.getTime() - STALE_DAYS * 24 * 60 * 60 * 1000,
-  );
-  const closeThreshold = new Date(
-    now.getTime() - CLOSE_DAYS * 24 * 60 * 60 * 1000,
-  );
-  const noResponseThreshold = new Date(
-    now.getTime() - NO_RESPONSE_DAYS * 24 * 60 * 60 * 1000,
-  );
-
-  const maintainerCache = new Map();
-  async function isMaintainer(user, association) {
-    if (user?.type === 'Bot') return true;
-    if (['OWNER', 'MEMBER', 'COLLABORATOR'].includes(association)) return true;
-
-    const username = user?.login;
-    if (!username) return false;
-
-    if (maintainerCache.has(username)) {
-      return maintainerCache.get(username);
-    }
-
-    try {
-      const { data } = await github.rest.repos.getCollaboratorPermissionLevel({
-        owner,
-        repo,
-        username,
-      });
-      // Permission can be admin, write, read, none.
-      // Roles like 'maintain' or 'triage' often map to 'write' or 'read' in the top-level field.
-      const isM =
-        ['admin', 'write'].includes(data.permission) ||
-        ['admin', 'maintain', 'write'].includes(data.role_name);
-
-      maintainerCache.set(username, isM);
-      return isM;
-    } catch (err) {
-      core.warning(
-        `Could not check permissions for ${username}: ${err.message}`,
-      );
-      maintainerCache.set(username, false);
-      return false;
-    }
-  }
-
-  async function processItems(query, callback) {
-    core.info(`Searching: ${query}`);
-    try {
-      let items = await github.paginate(
-        github.rest.search.issuesAndPullRequests,
-        {
-          q: query,
-          per_page: 100,
-          sort: 'updated',
-          order: 'asc',
-        },
-      );
-      core.info(`Found ${items.length} items.`);
-      for (const item of items) {
-        try {
-          await callback(item);
-        } catch (err) {
-          core.error(`Error processing #${item.number}: ${err.message}`);
-        }
-      }
-    } catch (err) {
-      core.error(`Search failed: ${err.message}`);
-    }
-  }
-
-  // 1. Handle No-Response (status/need-information)
-  // Removal: Check issues updated in the last 48h that have the label
-  const twoDaysAgo = new Date(now.getTime() - 2 * 24 * 60 * 60 * 1000);
-  await processItems(
-    `repo:${owner}/${repo} is:open label:"${NEED_INFO_LABEL}" updated:>${twoDaysAgo.toISOString()}`,
-    async (item) => {
-      const { data: comments } = await github.rest.issues.listComments({
-        owner,
-        repo,
-        issue_number: item.number,
-        sort: 'created',
-        direction: 'desc',
-        per_page: 5,
-      });
-
-      // Check if the last comment is from a non-maintainer and not a bot
-      const lastComment = comments[0];
-      if (
-        lastComment &&
-        lastComment.user?.type !== 'Bot' &&
-        !(await isMaintainer(lastComment.user, lastComment.author_association))
-      ) {
-        if (dryRun) {
-          core.info(
-            `[DRY RUN] Would remove ${NEED_INFO_LABEL} from #${item.number} due to contributor response.`,
-          );
-        } else {
-          core.info(
-            `Removing ${NEED_INFO_LABEL} from #${item.number} due to contributor response.`,
-          );
-          await github.rest.issues
-            .removeLabel({
-              owner,
-              repo,
-              issue_number: item.number,
-              name: NEED_INFO_LABEL,
-            })
-            .catch(() => {});
-        }
-      }
-    },
-  );
-
-  // Closure: Check issues with the label that haven't been updated in 14 days
-  await processItems(
-    `repo:${owner}/${repo} is:open label:"${NEED_INFO_LABEL}" updated:<${noResponseThreshold.toISOString()}`,
-    async (item) => {
-      if (dryRun) {
-        core.info(
-          `[DRY RUN] Would close #${item.number} due to no response for ${NO_RESPONSE_DAYS} days.`,
-        );
-      } else {
-        core.info(
-          `Closing #${item.number} due to no response for ${NO_RESPONSE_DAYS} days.`,
-        );
-        await github.rest.issues.createComment({
-          owner,
-          repo,
-          issue_number: item.number,
-          body: `This item was marked as needing more information and has not received a response in ${NO_RESPONSE_DAYS} days. Closing it for now. If you still face this problem, feel free to reopen with more details. Thank you!`,
-        });
-        await github.rest.issues.update({
-          owner,
-          repo,
-          issue_number: item.number,
-          state: 'closed',
-          state_reason: 'not_planned',
-        });
-      }
-    },
-  );
-
-  // 2. Handle Stale Mark (60 days inactivity, no stale label)
-  const exemptQuery = EXEMPT_LABELS.map((l) => `-label:"${l}"`).join(' ');
-
-  await processItems(
-    `repo:${owner}/${repo} is:open -label:"${STALE_LABEL}" ${exemptQuery} updated:<${staleThreshold.toISOString()}`,
-    async (item) => {
-      const isBug = item.labels.some((l) =>
-        (typeof l === 'string' ? l : l.name).toLowerCase().includes('bug'),
-      );
-      const bodyText = isBug
-        ? `This bug report has been automatically marked as stale due to ${STALE_DAYS} days of inactivity. Many issues are resolved in newer releases. Please verify if the issue persists in the latest Gemini CLI version. If it does, please leave a comment to keep this open. It will be closed in ${CLOSE_DAYS} days if no further activity occurs. Thank you!`
-        : `This item has been automatically marked as stale due to ${STALE_DAYS} days of inactivity. It will be closed in ${CLOSE_DAYS} days if no further activity occurs. Thank you!`;
-
-      if (dryRun) {
-        core.info(`[DRY RUN] Would mark #${item.number} as stale.`);
-      } else {
-        core.info(`Marking #${item.number} as stale.`);
-        await github.rest.issues.addLabels({
-          owner,
-          repo,
-          issue_number: item.number,
-          labels: [STALE_LABEL],
-        });
-        await github.rest.issues.createComment({
-          owner,
-          repo,
-          issue_number: item.number,
-          body: bodyText,
-        });
-      }
-    },
-  );
-
-  // 3. Handle Stale Removal & Close
-  await processItems(
-    `repo:${owner}/${repo} is:open label:"${STALE_LABEL}" ${exemptQuery}`,
-    async (item) => {
-      // Fetch full timeline to see events and comments
-      const timeline = await github.paginate(
-        github.rest.issues.listEventsForTimeline,
-        {
-          owner,
-          repo,
-          issue_number: item.number,
-          per_page: 100,
-        },
-      );
-
-      // Find exactly when the Stale label was added
-      // We look for the last 'labeled' event for STALE_LABEL
-      const staleEventIndex = timeline.findLastIndex(
-        (e) =>
-          e.event === 'labeled' &&
-          e.label?.name?.toLowerCase() === STALE_LABEL.toLowerCase(),
-      );
-
-      if (staleEventIndex === -1) return; // Fallback if no event found
-
-      const staleEvent = timeline[staleEventIndex];
-      const eventsAfterStale = timeline.slice(staleEventIndex + 1);
-
-      // Check for meaningful activity after the Stale label was applied
-      const meaningfulEvents = eventsAfterStale.filter((e) => {
-        const actor = e.actor?.login || '';
-        const isBot =
-          actor.includes('[bot]') || actor.includes('github-actions');
-
-        if (isBot) return false;
-
-        // Explicit whitelist of meaningful events for humans
-        if (
-          [
-            'commented',
-            'cross-referenced',
-            'connected',
-            'reopened',
-            'assigned',
-          ].includes(e.event)
-        ) {
-          return true;
-        }
-
-        return false;
-      });
-
-      if (meaningfulEvents.length > 0) {
-        // Activity detected, remove Stale label
-        if (dryRun) {
-          core.info(
-            `[DRY RUN] Would remove ${STALE_LABEL} from #${item.number} due to meaningful activity (e.g., comment or PR).`,
-          );
-        } else {
-          core.info(
-            `Removing ${STALE_LABEL} from #${item.number} due to meaningful activity (e.g., comment or PR).`,
-          );
-          await github.rest.issues
-            .removeLabel({
-              owner,
-              repo,
-              issue_number: item.number,
-              name: STALE_LABEL,
-            })
-            .catch(() => {});
-        }
-        return;
-      }
-
-      // No meaningful activity. Check if 14 days have passed.
-      const labeledDate = new Date(staleEvent.created_at);
-      if (labeledDate > closeThreshold) {
-        // Has not been 14 days since it was ACTUALLY marked stale
-        return;
-      }
-
-      if (dryRun) {
-        core.info(`[DRY RUN] Would close stale item #${item.number}.`);
-      } else {
-        core.info(`Closing stale item #${item.number}.`);
-        await github.rest.issues.createComment({
-          owner,
-          repo,
-          issue_number: item.number,
-          body: `This item has been closed due to ${CLOSE_DAYS} additional days of inactivity after being marked as stale. If you believe this is still relevant, feel free to comment or reopen. Thank you!`,
-        });
-        await github.rest.issues.update({
-          owner,
-          repo,
-          issue_number: item.number,
-          state: 'closed',
-          state_reason: 'not_planned',
-        });
-      }
-    },
-  );
-
-  // 4. Handle PR Contribution Policy (Nudge at 7d, Close at 14d)
-  const PR_NUDGE_DAYS = 7;
-  const PR_CLOSE_DAYS = 14;
-  const nudgeThreshold = new Date(
-    now.getTime() - PR_NUDGE_DAYS * 24 * 60 * 60 * 1000,
-  );
-  const prCloseThreshold = new Date(
-    now.getTime() - PR_CLOSE_DAYS * 24 * 60 * 60 * 1000,
-  );
-
-  // Nudge
-  await processItems(
-    `repo:${owner}/${repo} is:open is:pr -label:"help wanted" -label:"🔒 maintainer only" -label:"status/pr-nudge-sent" created:${prCloseThreshold.toISOString()}..${nudgeThreshold.toISOString()}`,
-    async (pr) => {
-      if (await isMaintainer(pr.user, pr.author_association)) return;
-
-      if (dryRun) {
-        core.info(
-          `[DRY RUN] Would nudge PR #${pr.number} for contribution policy.`,
-        );
-      } else {
-        core.info(`Nudging PR #${pr.number} for contribution policy.`);
-        await github.rest.issues.addLabels({
-          owner,
-          repo,
-          issue_number: pr.number,
-          labels: ['status/pr-nudge-sent'],
-        });
-        await github.rest.issues.createComment({
-          owner,
-          repo,
-          issue_number: pr.number,
-          body: "Hi there! Thank you for your interest in contributing to Gemini CLI. \n\nTo ensure we maintain high code quality and focus on our prioritized roadmap, we only guarantee review and consideration of pull requests for issues that are explicitly labeled as 'help wanted'. \n\nThis PR will be closed in 7 days if it remains without that designation. We encourage you to find and contribute to existing 'help wanted' issues in our backlog! Thank you for your understanding.",
-        });
-      }
-    },
-  );
-
-  // Close
-  await processItems(
-    `repo:${owner}/${repo} is:open is:pr -label:"help wanted" -label:"🔒 maintainer only" created:<${prCloseThreshold.toISOString()}`,
-    async (pr) => {
-      if (await isMaintainer(pr.user, pr.author_association)) return;
-
-      if (dryRun) {
-        core.info(
-          `[DRY RUN] Would close PR #${pr.number} per contribution policy (no 'help wanted').`,
-        );
-      } else {
-        core.info(
-          `Closing PR #${pr.number} per contribution policy (no 'help wanted').`,
-        );
-        await github.rest.issues.createComment({
-          owner,
-          repo,
-          issue_number: pr.number,
-          body: "This pull request is being closed as it has been open for 14 days without a 'help wanted' designation. We encourage you to find and contribute to existing 'help wanted' issues in our backlog! Thank you for your understanding.",
-        });
-        await github.rest.pulls.update({
-          owner,
-          repo,
-          pull_number: pr.number,
-          state: 'closed',
-        });
-      }
-    },
-  );
-};

.github/scripts/sync-issue-types.cjs

@@ -1,99 +0,0 @@
-/**
- * @license
- * Copyright 2026 Google LLC
- * SPDX-License-Identifier: Apache-2.0
- */
-
-const fs = require('node:fs');
-
-module.exports = async ({ github, context, core }) => {
-  const query = `
-    query($owner: String!, $repo: String!) {
-      repository(owner: $owner, name: $repo) {
-        issues(first: 50, states: OPEN, orderBy: {field: UPDATED_AT, direction: DESC}) {
-          nodes {
-            id
-            number
-            title
-            body
-            issueType {
-              name
-            }
-            labels(first: 20) {
-              nodes {
-                name
-              }
-            }
-          }
-        }
-      }
-    }
-  `;
-
-  try {
-    const result = await github.graphql(query, {
-      owner: context.repo.owner,
-      repo: context.repo.repo,
-    });
-
-    const issues = result.repository.issues.nodes;
-    const issuesNeedingAnalysis = [];
-    let syncedCount = 0;
-
-    for (const issue of issues) {
-      if (issue.issueType === null) {
-        const labelNames = issue.labels.nodes.map((l) => l.name);
-        const hasBug = labelNames.includes('kind/bug');
-        const hasFeature =
-          labelNames.includes('kind/feature') ||
-          labelNames.includes('kind/enhancement');
-
-        let issueTypeId = null;
-        if (hasBug) {
-          issueTypeId = 'IT_kwDOCaSVvs4BR7vP'; // Bug
-        } else if (hasFeature) {
-          issueTypeId = 'IT_kwDOCaSVvs4BR7vQ'; // Feature
-        }
-
-        if (issueTypeId) {
-          await github.graphql(
-            `
-            mutation($issueId: ID!, $issueTypeId: ID!) {
-              updateIssue(input: {id: $issueId, issueTypeId: $issueTypeId}) {
-                issue {
-                  id
-                }
-              }
-            }
-          `,
-            {
-              issueId: issue.id,
-              issueTypeId: issueTypeId,
-            },
-          );
-          core.info(`Successfully synced Issue Type for #${issue.number}`);
-          syncedCount++;
-        } else {
-          // Needs analysis to determine kind/type
-          issuesNeedingAnalysis.push({
-            number: issue.number,
-            title: issue.title,
-            body: issue.body,
-          });
-        }
-      }
-    }
-
-    // Write issues needing analysis to a file so the AI can process them
-    fs.writeFileSync(
-      'no_type_issues.json',
-      JSON.stringify(issuesNeedingAnalysis),
-    );
-    core.info(`Synced ${syncedCount} issues from labels.`);
-    core.info(
-      `Found ${issuesNeedingAnalysis.length} issues missing both type and kind label to be analyzed.`,
-    );
-  } catch (error) {
-    core.setFailed(`Failed to sync issue types: ${error.message}`);
-  }
-};

.github/workflows/agent-session-drift-check.yml

@@ -1,132 +0,0 @@
-# yaml-language-server: $schema=https://json.schemastore.org/github-workflow.json
-
-name: 'Agent Session Drift Check'
-
-on:
-  pull_request:
-    branches:
-      - 'main'
-      - 'release/**'
-    paths:
-      - 'packages/cli/src/nonInteractiveCli.ts'
-      - 'packages/cli/src/nonInteractiveCliAgentSession.ts'
-
-concurrency:
-  group: '${{ github.workflow }}-${{ github.head_ref || github.ref }}'
-  cancel-in-progress: true
-
-jobs:
-  check-drift:
-    name: 'Check Agent Session Drift'
-    runs-on: 'ubuntu-latest'
-    if: "github.repository == 'google-gemini/gemini-cli'"
-    permissions:
-      contents: 'read'
-      pull-requests: 'write'
-    steps:
-      - name: 'Detect drift and comment'
-        uses: 'actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea' # ratchet:actions/github-script@v8
-        with:
-          script: |-
-            // === Pair configuration — append here to cover more pairs ===
-            const PAIRS = [
-              {
-                legacy: 'packages/cli/src/nonInteractiveCli.ts',
-                session: 'packages/cli/src/nonInteractiveCliAgentSession.ts',
-                label: 'non-interactive CLI',
-              },
-              // Future pairs can be added here. Remember to also add both
-              // paths to the `paths:` filter at the top of this workflow.
-              // Example:
-              // {
-              //   legacy: 'packages/core/src/agents/local-invocation.ts',
-              //   session: 'packages/core/src/agents/local-session-invocation.ts',
-              //   label: 'local subagent invocation',
-              // },
-            ];
-            // ============================================================
-
-            const prNumber = context.payload.pull_request.number;
-            const { owner, repo } = context.repo;
-
-            // Use the API to list changed files — no checkout/git diff needed.
-            const files = await github.paginate(github.rest.pulls.listFiles, {
-              owner,
-              repo,
-              pull_number: prNumber,
-              per_page: 100,
-            });
-            const changed = new Set(files.map((f) => f.filename));
-
-            const warnings = [];
-            for (const { legacy, session, label } of PAIRS) {
-              const legacyChanged = changed.has(legacy);
-              const sessionChanged = changed.has(session);
-              if (legacyChanged && !sessionChanged) {
-                warnings.push(
-                  `**${label}**: \`${legacy}\` was modified but \`${session}\` was not.`,
-                );
-              } else if (!legacyChanged && sessionChanged) {
-                warnings.push(
-                  `**${label}**: \`${session}\` was modified but \`${legacy}\` was not.`,
-                );
-              }
-            }
-
-            const MARKER = '<!-- agent-session-drift-check -->';
-
-            // Look up our existing drift comment (for upsert/cleanup).
-            const comments = await github.paginate(github.rest.issues.listComments, {
-              owner,
-              repo,
-              issue_number: prNumber,
-              per_page: 100,
-            });
-            const existing = comments.find(
-              (c) => c.user?.type === 'Bot' && c.body?.includes(MARKER),
-            );
-
-            if (warnings.length === 0) {
-              core.info('No drift detected.');
-              // If drift was previously flagged and is now resolved, remove the comment.
-              if (existing) {
-                await github.rest.issues.deleteComment({
-                  owner,
-                  repo,
-                  comment_id: existing.id,
-                });
-                core.info(`Deleted stale drift comment ${existing.id}.`);
-              }
-              return;
-            }
-
-            const body = [
-              MARKER,
-              '### ⚠️ Invocation Drift Warning',
-              '',
-              'The following file pairs should generally be kept in sync during the AgentSession migration:',
-              '',
-              ...warnings.map((w) => `- ${w}`),
-              '',
-              'If this is intentional (e.g., a bug fix specific to one implementation), you can ignore this comment.',
-              '',
-              '_This check will be removed once the legacy implementations are deleted._',
-            ].join('\n');
-
-            if (existing) {
-              core.info(`Updating existing drift comment ${existing.id}.`);
-              await github.rest.issues.updateComment({
-                owner,
-                repo,
-                comment_id: existing.id,
-                body,
-              });
-            } else {
-              core.info('Creating new drift comment.');
-              await github.rest.issues.createComment({
-                owner,
-                repo,
-                issue_number: prNumber,
-                body,
-              });
-            }

.github/workflows/build-unsigned-mac-binaries.yml

@@ -1,65 +0,0 @@
-name: 'Build Unsigned Mac Binaries'
-
-on:
-  workflow_dispatch:
-  workflow_call:
-    inputs:
-      ref:
-        description: 'The branch, tag, or SHA to build from.'
-        required: true
-        type: 'string'
-
-permissions:
-  contents: 'read'
-
-defaults:
-  run:
-    shell: 'bash'
-
-jobs:
-  build-mac:
-    name: 'Build Unsigned (${{ matrix.arch }})'
-    runs-on: 'macos-latest'
-    strategy:
-      fail-fast: false
-      matrix:
-        arch: ['x64', 'arm64']
-
-    steps:
-      - name: 'Checkout'
-        uses: 'actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5' # ratchet:actions/checkout@v4
-        with:
-          ref: '${{ inputs.ref || github.ref }}'
-          persist-credentials: false
-
-      - name: 'Set up Node.js'
-        uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020' # ratchet:actions/setup-node@v4
-        with:
-          node-version-file: '.nvmrc'
-          architecture: '${{ matrix.arch }}'
-          cache: 'npm'
-
-      - name: 'Install dependencies'
-        run: 'npm ci'
-
-      - name: 'Build Binary'
-        env:
-          SKIP_SIGNING: 'true'
-        run: 'npm run build:binary'
-
-      - name: 'Verify Output Exists'
-        run: |
-          if [ -f "dist/darwin-${{ matrix.arch }}/gemini" ]; then
-            echo "Binary found at dist/darwin-${{ matrix.arch }}/gemini"
-          else
-            echo "Error: Binary not found in dist/darwin-${{ matrix.arch }}/"
-            ls -R dist/
-            exit 1
-          fi
-
-      - name: 'Upload Artifact'
-        uses: 'actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02' # ratchet:actions/upload-artifact@v4
-        with:
-          name: 'gemini-darwin-${{ matrix.arch }}-unsigned'
-          path: 'dist/darwin-${{ matrix.arch }}/gemini'
-          retention-days: 14

.github/workflows/chained_e2e.yml

@@ -148,7 +148,6 @@ jobs:
         with:
           ref: '${{ needs.parse_run_context.outputs.sha }}'
           repository: '${{ needs.parse_run_context.outputs.repository }}'
-          persist-credentials: false
 
       - name: 'Set up Node.js ${{ matrix.node-version }}'
         uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020' # ratchet:actions-node@v4
@@ -168,7 +167,6 @@ jobs:
       - name: 'Run E2E tests'
         env:
           GEMINI_API_KEY: '${{ secrets.GEMINI_API_KEY }}'
-          GEMINI_CLI_TRUST_WORKSPACE: true
           KEEP_OUTPUT: 'true'
           VERBOSE: 'true'
           BUILD_SANDBOX_FLAGS: '--cache-from type=gha --cache-to type=gha,mode=max'
@@ -185,7 +183,7 @@ jobs:
     needs:
       - 'merge_queue_skipper'
       - 'parse_run_context'
-    runs-on: 'macos-latest-large'
+    runs-on: 'macos-latest'
     if: |
       github.repository == 'google-gemini/gemini-cli' && always() && (needs.merge_queue_skipper.result !='success' || needs.merge_queue_skipper.outputs.skip != 'true')
     steps:
@@ -194,7 +192,6 @@ jobs:
         with:
           ref: '${{ needs.parse_run_context.outputs.sha }}'
           repository: '${{ needs.parse_run_context.outputs.repository }}'
-          persist-credentials: false
 
       - name: 'Set up Node.js 20.x'
         uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020' # ratchet:actions-node@v4
@@ -215,7 +212,6 @@ jobs:
         if: "${{runner.os != 'Windows'}}"
         env:
           GEMINI_API_KEY: '${{ secrets.GEMINI_API_KEY }}'
-          GEMINI_CLI_TRUST_WORKSPACE: true
           KEEP_OUTPUT: 'true'
           SANDBOX: 'sandbox:none'
           VERBOSE: 'true'
@@ -235,7 +231,6 @@ jobs:
         with:
           ref: '${{ needs.parse_run_context.outputs.sha }}'
           repository: '${{ needs.parse_run_context.outputs.repository }}'
-          persist-credentials: false
 
       - name: 'Set up Node.js 20.x'
         uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020' # ratchet:actions-node@v4
@@ -293,7 +288,6 @@ jobs:
       - name: 'Run E2E tests'
         env:
           GEMINI_API_KEY: '${{ secrets.GEMINI_API_KEY }}'
-          GEMINI_CLI_TRUST_WORKSPACE: true
           KEEP_OUTPUT: 'true'
           SANDBOX: 'sandbox:none'
           VERBOSE: 'true'
@@ -317,7 +311,6 @@ jobs:
         with:
           ref: '${{ needs.parse_run_context.outputs.sha }}'
           repository: '${{ needs.parse_run_context.outputs.repository }}'
-          persist-credentials: false
           fetch-depth: 0
 
       - name: 'Set up Node.js 20.x'
@@ -341,7 +334,6 @@ jobs:
         if: "${{ steps.check_evals.outputs.should_run == 'true' }}"
         env:
           GEMINI_API_KEY: '${{ secrets.GEMINI_API_KEY }}'
-          GEMINI_CLI_TRUST_WORKSPACE: true
           GEMINI_MODEL: 'gemini-3-pro-preview'
           # Only run always passes behavioral tests.
           EVAL_SUITE_TYPE: 'behavioral'

.github/workflows/ci.yml

@@ -57,7 +57,6 @@ jobs:
       - name: 'Checkout'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8' # ratchet:actions/checkout@v5
         with:
-          persist-credentials: false
           ref: '${{ github.event.inputs.branch_ref || github.ref }}'
           fetch-depth: 0
 
@@ -103,12 +102,6 @@ jobs:
       - name: 'Run yamllint'
         run: 'node scripts/lint.js --yamllint'
 
-      - name: 'Build project for typecheck'
-        run: 'npm run build'
-
-      - name: 'Run typecheck'
-        run: 'npm run typecheck'
-
       - name: 'Run Prettier'
         run: 'node scripts/lint.js --prettier'
 
@@ -131,8 +124,6 @@ jobs:
     steps:
       - name: 'Checkout'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8' # ratchet:actions/checkout@v5
-        with:
-          persist-credentials: false
       - name: 'Link Checker'
         uses: 'lycheeverse/lychee-action@885c65f3dc543b57c898c8099f4e08c8afd178a2' # ratchet: lycheeverse/lychee-action@v2.6.1
         with:
@@ -160,8 +151,6 @@ jobs:
     steps:
       - name: 'Checkout'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8' # ratchet:actions/checkout@v5
-        with:
-          persist-credentials: false
 
       - name: 'Set up Node.js ${{ matrix.node-version }}'
         uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020' # ratchet:actions/setup-node@v4
@@ -184,7 +173,6 @@ jobs:
       - name: 'Run tests and generate reports'
         env:
           NO_COLOR: true
-          GEMINI_CLI_TRUST_WORKSPACE: true
         run: |
           if [[ "${{ matrix.shard }}" == "cli" ]]; then
             npm run test:ci --workspace "@google/gemini-cli"
@@ -236,7 +224,7 @@ jobs:
 
   test_mac:
     name: 'Test (Mac) - ${{ matrix.node-version }}, ${{ matrix.shard }}'
-    runs-on: 'macos-latest-large'
+    runs-on: 'macos-latest'
     needs:
       - 'merge_queue_skipper'
     if: "github.repository == 'google-gemini/gemini-cli' && needs.merge_queue_skipper.outputs.skip == 'false'"
@@ -257,8 +245,6 @@ jobs:
     steps:
       - name: 'Checkout'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8' # ratchet:actions/checkout@v5
-        with:
-          persist-credentials: false
 
       - name: 'Set up Node.js ${{ matrix.node-version }}'
         uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020' # ratchet:actions/setup-node@v4
@@ -275,7 +261,6 @@ jobs:
       - name: 'Run tests and generate reports'
         env:
           NO_COLOR: true
-          GEMINI_CLI_TRUST_WORKSPACE: true
         run: |
           if [[ "${{ matrix.shard }}" == "cli" ]]; then
             npm run test:ci --workspace "@google/gemini-cli" -- --coverage.enabled=false
@@ -346,7 +331,6 @@ jobs:
       - name: 'Checkout'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8' # ratchet:actions/checkout@v5
         with:
-          persist-credentials: false
           ref: '${{ github.event.inputs.branch_ref || github.ref }}'
 
       - name: 'Initialize CodeQL'
@@ -371,7 +355,6 @@ jobs:
       - name: 'Checkout'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8' # ratchet:actions/checkout@v5
         with:
-          persist-credentials: false
           ref: '${{ github.event.inputs.branch_ref || github.ref }}'
           fetch-depth: 1
 
@@ -399,7 +382,6 @@ jobs:
       - name: 'Checkout'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8' # ratchet:actions/checkout@v5
         with:
-          persist-credentials: false
           ref: '${{ github.event.inputs.branch_ref || github.ref }}'
 
       - name: 'Set up Node.js 20.x'
@@ -442,7 +424,6 @@ jobs:
         env:
           GEMINI_API_KEY: '${{ secrets.GEMINI_API_KEY }}'
           NO_COLOR: true
-          GEMINI_CLI_TRUST_WORKSPACE: true
           NODE_OPTIONS: '--max-old-space-size=32768 --max-semi-space-size=256'
           UV_THREADPOOL_SIZE: '32'
           NODE_ENV: 'test'

.github/workflows/community-report.yml

@@ -173,7 +173,6 @@ jobs:
           GITHUB_TOKEN: '${{ steps.generate_token.outputs.token }}'
           REPOSITORY: '${{ github.repository }}'
         with:
-          upload_artifacts: 'true'
           gcp_workload_identity_provider: '${{ vars.GCP_WIF_PROVIDER }}'
           gcp_project_id: '${{ vars.GOOGLE_CLOUD_PROJECT }}'
           gcp_location: '${{ vars.GOOGLE_CLOUD_LOCATION }}'
@@ -183,14 +182,12 @@ jobs:
           use_gemini_code_assist: '${{ vars.GOOGLE_GENAI_USE_GCA }}'
           settings: |-
             {
-              "tools": {
-                "core": [
-                  "run_shell_command(gh issue list)",
-                  "run_shell_command(gh pr list)",
-                  "run_shell_command(gh search issues)",
-                  "run_shell_command(gh search prs)"
-                ]
-              }
+              "coreTools": [
+                "run_shell_command(gh issue list)",
+                "run_shell_command(gh pr list)",
+                "run_shell_command(gh search issues)",
+                "run_shell_command(gh search prs)"
+              ]
             }
           prompt: |-
             You are a helpful assistant that analyzes community contribution reports.

.github/workflows/deflake.yml

@@ -43,7 +43,6 @@ jobs:
         with:
           ref: '${{ github.event.pull_request.head.sha }}'
           repository: '${{ github.repository }}'
-          persist-credentials: false
 
       - name: 'Set up Node.js ${{ matrix.node-version }}'
         uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020' # ratchet:actions-node@v4
@@ -63,7 +62,6 @@ jobs:
       - name: 'Run E2E tests'
         env:
           GEMINI_API_KEY: '${{ secrets.GEMINI_API_KEY }}'
-          GEMINI_CLI_TRUST_WORKSPACE: true
           IS_DOCKER: "${{ matrix.sandbox == 'sandbox:docker' }}"
           KEEP_OUTPUT: 'true'
           RUNS: '${{ github.event.inputs.runs }}'
@@ -79,7 +77,7 @@ jobs:
 
   deflake_e2e_mac:
     name: 'E2E Test (macOS)'
-    runs-on: 'macos-latest-large'
+    runs-on: 'macos-latest'
     if: "github.repository == 'google-gemini/gemini-cli'"
     steps:
       - name: 'Checkout'
@@ -87,7 +85,6 @@ jobs:
         with:
           ref: '${{ github.event.pull_request.head.sha }}'
           repository: '${{ github.repository }}'
-          persist-credentials: false
 
       - name: 'Set up Node.js 20.x'
         uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020' # ratchet:actions-node@v4
@@ -108,7 +105,6 @@ jobs:
         if: "runner.os != 'Windows'"
         env:
           GEMINI_API_KEY: '${{ secrets.GEMINI_API_KEY }}'
-          GEMINI_CLI_TRUST_WORKSPACE: true
           KEEP_OUTPUT: 'true'
           RUNS: '${{ github.event.inputs.runs }}'
           SANDBOX: 'sandbox:none'
@@ -127,7 +123,6 @@ jobs:
         with:
           ref: '${{ github.event.pull_request.head.sha }}'
           repository: '${{ github.repository }}'
-          persist-credentials: false
 
       - name: 'Set up Node.js 20.x'
         uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020' # ratchet:actions-node@v4
@@ -164,7 +159,6 @@ jobs:
       - name: 'Run E2E tests'
         env:
           GEMINI_API_KEY: '${{ secrets.GEMINI_API_KEY }}'
-          GEMINI_CLI_TRUST_WORKSPACE: true
           KEEP_OUTPUT: 'true'
           SANDBOX: 'sandbox:none'
           VERBOSE: 'true'

.github/workflows/docs-audit.yml

@@ -1,66 +0,0 @@
-name: 'Automated Documentation Audit'
-
-on:
-  schedule:
-    # Runs every Monday at 00:00 UTC
-    - cron: '0 0 * * MON'
-  workflow_dispatch:
-
-jobs:
-  audit-docs:
-    runs-on: 'ubuntu-latest'
-    permissions:
-      contents: 'write'
-      pull-requests: 'write'
-
-    steps:
-      - name: 'Checkout repository'
-        uses: 'actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5'
-        with:
-          fetch-depth: 0
-          ref: 'main'
-          persist-credentials: false
-
-      - name: 'Set up Node.js'
-        uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020'
-        with:
-          node-version: '20'
-
-      - name: 'Run Docs Audit with Gemini'
-        id: 'run_gemini'
-        uses: 'google-github-actions/run-gemini-cli@a3bf79042542528e91937b3a3a6fbc4967ee3c31'
-        env:
-          GEMINI_CLI_TRUST_WORKSPACE: true
-        with:
-          upload_artifacts: 'true'
-          gemini_api_key: '${{ secrets.GEMINI_API_KEY }}'
-          prompt: |
-            Activate the 'docs-writer' skill.
-
-            **Task:** Execute the docs audit procedure, as defined in your 'docs-auditing.md' reference.
-            Provide a detailed summary of the changes you make.
-
-      - name: 'Get current date'
-        id: 'date'
-        run: |
-          echo "date=$(date +'%Y-%m-%d')" >> "$GITHUB_OUTPUT"
-
-      - name: 'Create Pull Request with Audit Results'
-        uses: 'peter-evans/create-pull-request@c5a7806660adbe173f04e3e038b0ccdcd758773c'
-        with:
-          token: '${{ secrets.GEMINI_CLI_ROBOT_GITHUB_PAT }}'
-          commit-message: 'docs: weekly audit results for ${{ github.run_id }}'
-          title: 'Docs audit: ${{ steps.date.outputs.date }}'
-          body: |
-            This PR contains the auto-generated documentation audit for the week. It includes a new `audit-results-*.md` file with findings and any direct fixes applied by the agent.
-
-            ### Audit Summary:
-            ${{ steps.run_gemini.outputs.summary || 'No summary provided.' }}
-
-            Please review the suggestions and merge.
-
-            Related to #25152
-          branch: 'docs-audit-${{ github.run_id }}'
-          base: 'main'
-          team-reviewers: 'gemini-cli-docs, gemini-cli-maintainers'
-          delete-branch: true

.github/workflows/docs-page-action.yml

@@ -24,8 +24,6 @@ jobs:
     steps:
       - name: 'Checkout'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8' # ratchet:actions/checkout@v5
-        with:
-          persist-credentials: false
 
       - name: 'Setup Pages'
         uses: 'actions/configure-pages@983d7736d9b0ae728b81ab479565c72886d7745b' # ratchet:actions/configure-pages@v5

.github/workflows/eval-pr.yml

@@ -38,7 +38,6 @@ jobs:
         with:
           # Check out the trusted code from main for detection
           fetch-depth: 0
-          persist-credentials: false
 
       - name: 'Detect Steering Changes'
         id: 'detect'
@@ -103,7 +102,6 @@ jobs:
           # This only runs AFTER manual approval
           ref: '${{ github.event.pull_request.head.sha }}'
           fetch-depth: 0
-          persist-credentials: false
 
       - name: 'Remove Approval Notification'
         # Run even if other steps fail, to ensure we clean up the "Action Required" message

.github/workflows/evals-nightly.yml

@@ -46,8 +46,6 @@ jobs:
     steps:
       - name: 'Checkout'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8' # ratchet:actions/checkout@v5
-        with:
-          persist-credentials: false
 
       - name: 'Set up Node.js'
         uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020' # ratchet:actions/setup-node@v4
@@ -68,7 +66,6 @@ jobs:
         continue-on-error: true
         env:
           GEMINI_API_KEY: '${{ secrets.GEMINI_API_KEY }}'
-          GEMINI_CLI_TRUST_WORKSPACE: true
           GEMINI_MODEL: '${{ matrix.model }}'
           RUN_EVALS: 'true'
           EVAL_SUITE_TYPE: "${{ github.event.inputs.suite_type || 'behavioral' }}"
@@ -107,8 +104,6 @@ jobs:
     steps:
       - name: 'Checkout'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8' # ratchet:actions/checkout@v5
-        with:
-          persist-credentials: false
 
       - name: 'Download Logs'
         uses: 'actions/download-artifact@cc203385981b70ca67e1cc392babf9cc229d5806' # ratchet:actions/download-artifact@v4

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

@@ -48,8 +48,6 @@ jobs:
     steps:
       - name: 'Checkout'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8' # ratchet:actions/checkout@v5
-        with:
-          persist-credentials: false
 
       - name: 'Log in to GitHub Container Registry'
         uses: 'docker/login-action@184bdaa0721073962dff0199f1fb9940f07167d1' # ratchet:docker/login-action@v3
@@ -68,9 +66,7 @@ jobs:
           ISSUE_NUMBER: '${{ github.event.issue.number }}'
           REPOSITORY: '${{ github.repository }}'
           FIRESTORE_PROJECT: '${{ vars.FIRESTORE_PROJECT }}'
-          GEMINI_CLI_TRUST_WORKSPACE: 'true'
         with:
-          upload_artifacts: 'true'
           gcp_workload_identity_provider: '${{ vars.GCP_WIF_PROVIDER }}'
           gcp_project_id: '${{ vars.GOOGLE_CLOUD_PROJECT }}'
           gcp_location: '${{ vars.GOOGLE_CLOUD_LOCATION }}'
@@ -109,12 +105,10 @@ jobs:
                 }
               },
               "maxSessionTurns": 25,
-              "tools": {
-                "core": [
-                  "run_shell_command(echo)",
-                  "run_shell_command(gh issue view)"
-                ]
-              },
+              "coreTools": [
+                "run_shell_command(echo)",
+                "run_shell_command(gh issue view)"
+              ],
               "telemetry": {
                 "enabled": true,
                 "target": "gcp"

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

@@ -90,8 +90,6 @@ jobs:
 
       - name: 'Checkout'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8' # ratchet:actions/checkout@v5
-        with:
-          persist-credentials: false
 
       - name: 'Generate GitHub App Token'
         id: 'generate_token'
@@ -131,31 +129,20 @@ jobs:
             core.info(`Found ${labelNames.length} labels: ${labelNames.join(', ')}`);
             return labelNames;
 
-      - name: 'Prepare Issue Data'
-        id: 'prepare_issue_data'
-        env:
-          ISSUE_TITLE: >-
-            ${{ github.event_name == 'workflow_dispatch' && steps.get_issue_data.outputs.title || github.event.issue.title }}
-          ISSUE_BODY: >-
-            ${{ github.event_name == 'workflow_dispatch' && steps.get_issue_data.outputs.body || github.event.issue.body }}
-        run: |
-          set -euo pipefail
-          echo "Title: ${ISSUE_TITLE}" > issue_context.md
-          echo "Body:" >> issue_context.md
-          echo "${ISSUE_BODY}" >> issue_context.md
-
       - name: 'Run Gemini Issue Analysis'
         uses: 'google-github-actions/run-gemini-cli@a3bf79042542528e91937b3a3a6fbc4967ee3c31' # ratchet:google-github-actions/run-gemini-cli@v0
         id: 'gemini_issue_analysis'
         env:
           GITHUB_TOKEN: '' # Do not pass any auth token here since this runs on untrusted inputs
+          ISSUE_TITLE: >-
+            ${{ github.event_name == 'workflow_dispatch' && steps.get_issue_data.outputs.title || github.event.issue.title }}
+          ISSUE_BODY: >-
+            ${{ github.event_name == 'workflow_dispatch' && steps.get_issue_data.outputs.body || github.event.issue.body }}
           ISSUE_NUMBER: >-
             ${{ github.event_name == 'workflow_dispatch' && (github.event.inputs.issue_number || inputs.issue_number) || github.event.issue.number }}
           REPOSITORY: '${{ github.repository }}'
           AVAILABLE_LABELS: '${{ steps.get_labels.outputs.available_labels }}'
-          GEMINI_CLI_TRUST_WORKSPACE: 'true'
         with:
-          upload_artifacts: 'true'
           gcp_workload_identity_provider: '${{ vars.GCP_WIF_PROVIDER }}'
           gcp_project_id: '${{ vars.GOOGLE_CLOUD_PROJECT }}'
           gcp_location: '${{ vars.GOOGLE_CLOUD_LOCATION }}'
@@ -170,12 +157,9 @@ jobs:
                 "enabled": true,
                 "target": "gcp"
               },
-              "tools": {
-                "core": [
-                  "run_shell_command(echo)",
-                  "read_file"
-                ]
-              }
+              "coreTools": [
+                "run_shell_command(echo)"
+              ]
             }
           prompt: |-
             ## Role
@@ -183,7 +167,7 @@ jobs:
             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.
 
             ## Steps
-            1. Use the read_file tool to read the file "issue_context.md" which contains the issue title and body.
+            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:
@@ -338,41 +322,14 @@ jobs:
               return;
             }
 
-            const newAreaLabel = labelsToAdd[0];
-
-            // Get current labels to resolve conflicts
-            const { data: currentLabels } = await github.rest.issues.listLabelsOnIssue({
-              owner: context.repo.owner,
-              repo: context.repo.repo,
-              issue_number: issueNumber,
-            });
-            const currentLabelNames = currentLabels.map(l => l.name);
-            const currentAreaLabels = currentLabelNames.filter(name => name.startsWith('area/'));
-
-            const labelsToRemove = currentAreaLabels.filter(name => name !== newAreaLabel);
-
-            for (const label of labelsToRemove) {
-              try {
-                await github.rest.issues.removeLabel({
-                  owner: context.repo.owner,
-                  repo: context.repo.repo,
-                  issue_number: issueNumber,
-                  name: label
-                });
-                core.info(`Removed conflicting area label: ${label}`);
-              } catch (e) {
-                core.warning(`Failed to remove label ${label}: ${e.message}`);
-              }
-            }
-
             // Set labels based on triage result
             await github.rest.issues.addLabels({
               owner: context.repo.owner,
               repo: context.repo.repo,
               issue_number: issueNumber,
-              labels: [newAreaLabel]
+              labels: labelsToAdd
             });
-            core.info(`Successfully added labels for #${issueNumber}: ${newAreaLabel}`);
+            core.info(`Successfully added labels for #${issueNumber}: ${labelsToAdd.join(', ')}`);
 
       - name: 'Post Issue Analysis Failure Comment'
         if: |-

.github/workflows/gemini-cli-bot-brain.yml

@@ -1,350 +0,0 @@
-name: '🧠 Gemini CLI Bot: Brain'
-
-on:
-  schedule:
-    - cron: '0 0 * * *' # Every 24 hours
-  issue_comment:
-    types: ['created']
-  workflow_dispatch:
-    inputs:
-      run_interactive:
-        description: 'Run interactive flow (requires issue_number)'
-        type: 'boolean'
-        default: false
-      issue_number:
-        description: 'Issue/PR number to simulate context from'
-        type: 'string'
-        required: false
-      comment_id:
-        description: 'Specific comment ID to simulate'
-        type: 'string'
-        required: false
-      clear_memory:
-        description: 'Clear memory (drops learnings from previous runs)'
-        type: 'boolean'
-        default: false
-      enable_prs:
-        description: 'Enable PRs (automatically promote changes to PRs)'
-        type: 'boolean'
-        default: false
-
-concurrency:
-  group: '${{ github.workflow }}-${{ github.event.issue.number || github.event.inputs.issue_number || github.ref }}'
-  cancel-in-progress: true
-
-jobs:
-  reasoning:
-    name: 'Brain (Reasoning Layer)'
-    runs-on: 'ubuntu-latest'
-    if: |
-      github.repository == 'google-gemini/gemini-cli' && (
-        github.event_name == 'schedule' ||
-        (github.event_name == 'workflow_dispatch' && github.event.inputs.run_interactive != 'true') ||
-        (github.event_name == 'workflow_dispatch' && github.event.inputs.run_interactive == 'true') ||
-        (github.event_name == 'issue_comment' && github.event.comment.user.login != 'gemini-cli[bot]' && contains(github.event.comment.body, '@gemini-cli') && contains(fromJSON('["COLLABORATOR", "MEMBER", "OWNER"]'), github.event.comment.author_association))
-      )
-    # The reasoning phase is strictly readonly.
-    permissions:
-      contents: 'read'
-      issues: 'read'
-      actions: 'read'
-    env:
-      GEMINI_CLI_TRUST_WORKSPACE: 'true'
-    steps:
-      - name: 'Determine Checkout Ref'
-        id: 'determine_ref'
-        env:
-          GITHUB_TOKEN: '${{ secrets.GITHUB_TOKEN }}'
-          ISSUE_NUMBER: '${{ github.event.issue.number || github.event.inputs.issue_number }}'
-        run: |
-          REF="${{ github.ref }}"
-          if [ -n "$ISSUE_NUMBER" ]; then
-            PR_HEAD=$(gh pr view "$ISSUE_NUMBER" --repo "${{ github.repository }}" --json headRefName --jq .headRefName 2>/dev/null || echo "")
-            if [ -n "$PR_HEAD" ]; then
-              REF="$PR_HEAD"
-            fi
-          fi
-          echo "ref=$REF" >> "$GITHUB_OUTPUT"
-
-      - name: 'Checkout'
-        uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8' # ratchet:actions/checkout@v5
-        with:
-          ref: '${{ steps.determine_ref.outputs.ref }}'
-          fetch-depth: 0
-          persist-credentials: false
-
-      - name: 'Setup Node.js'
-        uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020' # ratchet:actions/setup-node@v4
-        with:
-          node-version: '20'
-          cache: 'npm'
-
-      - name: 'Install dependencies'
-        run: 'npm ci'
-
-      - name: 'Build Gemini CLI'
-        run: 'npm run bundle'
-
-      - name: 'Download Previous State'
-        env:
-          GITHUB_TOKEN: '${{ secrets.GITHUB_TOKEN }}'
-        run: |
-          if [ "${{ github.event.inputs.clear_memory }}" = "true" ]; then
-            echo "Memory clear requested. Skipping previous state download."
-            exit 0
-          fi
-
-          # Find the last successful run of this workflow
-          LAST_RUN_ID=$(gh run list --workflow "${{ github.workflow }}" --status success --limit 1 --json databaseId --jq '.[0].databaseId')
-
-          if [ -n "$LAST_RUN_ID" ]; then
-            echo "Found previous successful run: $LAST_RUN_ID"
-
-            # Download brain memory to a temp dir so we can selectively restore only persistent state
-            mkdir -p .temp_brain_data
-            gh run download "$LAST_RUN_ID" -n brain-data -D .temp_brain_data || echo "brain-data not found"
-
-            # Restore only persistent memory files
-            cp .temp_brain_data/tools/gemini-cli-bot/lessons-learned.md tools/gemini-cli-bot/lessons-learned.md 2>/dev/null || true
-            mkdir -p tools/gemini-cli-bot/history/
-            cp .temp_brain_data/tools/gemini-cli-bot/history/*.csv tools/gemini-cli-bot/history/ 2>/dev/null || true
-            rm -rf .temp_brain_data
-          else
-            echo "No previous successful run found."
-          fi
-
-      - name: 'Collect Current Metrics'
-        env:
-          GITHUB_TOKEN: '${{ secrets.GITHUB_TOKEN }}'
-        run: 'npx tsx tools/gemini-cli-bot/metrics/index.ts'
-
-      - name: 'Run Brain Phases'
-        env:
-          GEMINI_API_KEY: '${{ secrets.GEMINI_API_KEY }}'
-          GITHUB_TOKEN: '${{ secrets.GITHUB_TOKEN }}'
-          GEMINI_MODEL: 'gemini-3-flash-preview'
-          GEMINI_CLI_HOME: 'tools/gemini-cli-bot'
-          ENABLE_PRS: "${{ github.event.inputs.enable_prs || 'false' }}"
-          TRIGGER_ISSUE_NUMBER: '${{ github.event.issue.number || github.event.inputs.issue_number }}'
-          TRIGGER_COMMENT_ID: '${{ github.event.comment.id || github.event.inputs.comment_id }}'
-        run: |
-          PROMPT_PATH="tools/gemini-cli-bot/brain/scheduled.md"
-          if [ "${{ github.event_name }}" = "issue_comment" ] || [ "${{ github.event.inputs.run_interactive }}" = "true" ]; then
-            PROMPT_PATH="tools/gemini-cli-bot/brain/interactive.md"
-            export ENABLE_PRS="true"
-          fi
-
-          touch trigger_context.md
-          if [ -n "$TRIGGER_ISSUE_NUMBER" ]; then
-            echo "<untrusted_context>" > trigger_context.md
-            echo "# Interactive Trigger Context" >> trigger_context.md
-            echo "You were invoked by a user in issue/PR #$TRIGGER_ISSUE_NUMBER." >> trigger_context.md
-
-            if [ -n "$TRIGGER_COMMENT_ID" ]; then
-              echo "## User Comment" >> trigger_context.md
-              gh api "repos/${{ github.repository }}/issues/comments/$TRIGGER_COMMENT_ID" -q '.body' >> trigger_context.md 2>/dev/null || gh api "repos/${{ github.repository }}/pulls/comments/$TRIGGER_COMMENT_ID" -q '.body' >> trigger_context.md
-              echo "" >> trigger_context.md
-            fi
-
-            echo "## Issue/PR Context" >> trigger_context.md
-            gh issue view "$TRIGGER_ISSUE_NUMBER" >> trigger_context.md 2>/dev/null || gh pr view "$TRIGGER_ISSUE_NUMBER" >> trigger_context.md
-            echo "</untrusted_context>" >> trigger_context.md
-          fi
-
-          if [ "$ENABLE_PRS" = "true" ]; then
-            echo "**System Directive**: PR creation is ENABLED for this run. You MUST activate the **'prs' skill** to stage your changes and generate a \`pr-description.md\` file if you are proposing fixes." >> trigger_context.md
-            echo "**CRITICAL System Directive**: You MUST ONLY propose and implement a **SINGLE** improvement or fix per run. Bundling unrelated changes (e.g., a documentation update and a script fix, or a metrics update and a logic fix) into a single PR is STRICTLY FORBIDDEN and will result in immediate rejection during the critique phase. If you identify multiple issues, pick the most impactful one and ignore the others for now." >> trigger_context.md
-          else
-            echo "**System Directive**: PR creation is DISABLED for this run. You MUST NOT stage files or attempt to create a PR description." >> trigger_context.md
-          fi
-          echo "" >> trigger_context.md
-
-          cat trigger_context.md "$PROMPT_PATH" > combined_prompt.md
-          node bundle/gemini.js --policy tools/gemini-cli-bot/ci-policy.toml --prompt="$(cat combined_prompt.md)"
-
-          if [ -n "$TRIGGER_ISSUE_NUMBER" ] && [ ! -s "issue-comment.md" ] && [ ! -s "pr-comment.md" ]; then
-            echo "Agent failed to respond. Generating fallback error message."
-            echo "⚠️ **Gemini CLI Bot failed to generate a response.**" > "issue-comment.md"
-            echo "" >> "issue-comment.md"
-            echo "I encountered an error or failed to generate a complete response to your request. You can check the [GitHub Actions Run Log](https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}) for more details on what went wrong." >> "issue-comment.md"
-          fi
-
-      - name: 'Run Critique Phase'
-        if: "${{ github.event.inputs.enable_prs == 'true' || github.event_name == 'issue_comment' || github.event.inputs.run_interactive == 'true' }}"
-        env:
-          GEMINI_API_KEY: '${{ secrets.GEMINI_API_KEY }}'
-          GITHUB_TOKEN: '${{ secrets.GITHUB_TOKEN }}'
-          GEMINI_MODEL: 'gemini-3-flash-preview'
-          GEMINI_CLI_HOME: 'tools/gemini-cli-bot'
-        run: |
-          if git diff --staged --quiet; then
-             echo "No changes staged. Skipping critique."
-             echo "[APPROVED]" > critique_result.txt
-          else
-             node bundle/gemini.js --policy tools/gemini-cli-bot/ci-policy.toml --prompt="$(cat tools/gemini-cli-bot/.gemini/skills/critique/SKILL.md)" 2>&1 | tee critique_output.log
-
-             if [ "${PIPESTATUS[0]}" -eq 0 ] && grep -q "\[APPROVED\]" critique_output.log && ! grep -q "\[REJECTED\]" critique_output.log; then
-               echo "[APPROVED]" > critique_result.txt
-             else
-               echo "Critique failed, rejected, or did not explicitly approve changes. Skipping PR creation."
-               echo "[REJECTED]" > critique_result.txt
-             fi
-          fi
-
-      - name: 'Generate Patch'
-        if: "${{ github.event.inputs.enable_prs == 'true' || github.event_name == 'issue_comment' || github.event.inputs.run_interactive == 'true' }}"
-        run: |
-          touch bot-changes.patch
-          touch pr-description.md
-          if [ -f critique_result.txt ] && grep -q "\[APPROVED\]" critique_result.txt && ! grep -q "\[REJECTED\]" critique_result.txt; then
-             git diff --staged > bot-changes.patch
-          else
-             echo "Critique did not approve. Skipping patch generation."
-          fi
-
-      - name: 'Archive Brain Data'
-        uses: 'actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02' # ratchet:actions/upload-artifact@v4
-        with:
-          name: 'brain-data'
-          path: |
-            tools/gemini-cli-bot/lessons-learned.md
-            tools/gemini-cli-bot/history/*.csv
-            bot-changes.patch
-            pr-description.md
-            branch-name.txt
-            pr-comment.md
-            pr-number.txt
-            issue-comment.md
-          retention-days: 90
-
-  publish:
-    name: 'Publish Artifacts (Archive Layer)'
-    needs: 'reasoning'
-    runs-on: 'ubuntu-latest'
-    if: "github.repository == 'google-gemini/gemini-cli'"
-    # The publish phase is for archiving artifacts and optionally creating PRs.
-    permissions:
-      contents: 'write'
-      pull-requests: 'write'
-      actions: 'write'
-    steps:
-      - name: 'Generate GitHub App Token 🔑'
-        id: 'generate_token'
-        if: "${{ github.event.inputs.enable_prs == 'true' || github.event_name == 'issue_comment' || github.event.inputs.run_interactive == 'true' }}"
-        uses: 'actions/create-github-app-token@a8d616148505b5069dccd32f177bb87d7f39123b' # ratchet:actions/create-github-app-token@v2
-        with:
-          app-id: '${{ secrets.APP_ID }}'
-          private-key: '${{ secrets.PRIVATE_KEY }}'
-          owner: '${{ github.repository_owner }}'
-          repositories: '${{ github.event.repository.name }}'
-          permission-contents: 'write'
-          permission-pull-requests: 'write'
-          permission-issues: 'write'
-
-      - name: 'Determine Checkout Ref'
-        id: 'determine_ref'
-        env:
-          GITHUB_TOKEN: '${{ secrets.GITHUB_TOKEN }}'
-          ISSUE_NUMBER: '${{ github.event.issue.number || github.event.inputs.issue_number }}'
-        run: |
-          REF="main"
-          if [ -n "$ISSUE_NUMBER" ]; then
-            PR_HEAD=$(gh pr view "$ISSUE_NUMBER" --repo "${{ github.repository }}" --json headRefName --jq .headRefName 2>/dev/null || echo "")
-            if [ -n "$PR_HEAD" ]; then
-              REF="$PR_HEAD"
-            fi
-          fi
-          echo "ref=$REF" >> "$GITHUB_OUTPUT"
-
-      - name: 'Checkout'
-        uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8' # ratchet:actions/checkout@v5
-        with:
-          ref: '${{ steps.determine_ref.outputs.ref }}'
-          fetch-depth: 0
-          persist-credentials: false
-
-      - name: 'Download Brain Data'
-        uses: 'actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093' # ratchet:actions/download-artifact@v4
-        with:
-          name: 'brain-data'
-          path: '${{ runner.temp }}/brain-data/'
-
-      - name: 'Create or Update PR'
-        if: "${{ github.event.inputs.enable_prs == 'true' || github.event_name == 'issue_comment' || github.event.inputs.run_interactive == 'true' }}"
-        env:
-          GH_TOKEN: '${{ steps.generate_token.outputs.token }}'
-          FALLBACK_PAT: '${{ secrets.GEMINI_CLI_ROBOT_GITHUB_PAT }}'
-        run: |
-          if [ -s "${{ runner.temp }}/brain-data/bot-changes.patch" ]; then
-            git config user.name "gemini-cli[bot]"
-            git config user.email "gemini-cli[bot]@users.noreply.github.com"
-            git remote set-url origin "https://x-access-token:${GH_TOKEN}@github.com/${{ github.repository }}.git"
-
-            BRANCH_NAME="bot/productivity-updates-$(date +'%Y%m%d%H%M%S')-${{ github.run_id }}"
-            if [ -f "${{ runner.temp }}/brain-data/branch-name.txt" ]; then
-              BRANCH_NAME=$(cat "${{ runner.temp }}/brain-data/branch-name.txt")
-            fi
-
-            if [[ ! "$BRANCH_NAME" =~ ^bot/ ]]; then
-              echo "Error: Branch name '$BRANCH_NAME' does not start with 'bot/'. Safety abort."
-              exit 1
-            fi
-
-            git checkout -B "$BRANCH_NAME"
-            git apply "${{ runner.temp }}/brain-data/bot-changes.patch"
-            git add .
-
-            if [ -s "${{ runner.temp }}/brain-data/pr-description.md" ]; then
-              git commit -F "${{ runner.temp }}/brain-data/pr-description.md"
-            else
-              git commit -m "🤖 Gemini Bot Productivity Optimizations"
-            fi
-
-            PR_TITLE="🤖 Gemini Bot Productivity Optimizations"
-            if [ -s "${{ runner.temp }}/brain-data/pr-description.md" ]; then
-              PR_TITLE=$(head -n 1 "${{ runner.temp }}/brain-data/pr-description.md")
-            fi
-
-            if ! git push origin "$BRANCH_NAME" --force; then
-              echo "Push failed. Retrying with FALLBACK_PAT..."
-              export GH_TOKEN="$FALLBACK_PAT"
-              git remote set-url origin "https://x-access-token:${FALLBACK_PAT}@github.com/${{ github.repository }}.git"
-              git push origin "$BRANCH_NAME" --force
-            fi
-
-            if ! gh pr view "$BRANCH_NAME" > /dev/null 2>&1; then
-              gh pr create --draft --title "$PR_TITLE" --body-file "${{ runner.temp }}/brain-data/pr-description.md" --head "$BRANCH_NAME" --base main || \
-              gh pr create --draft --title "🤖 Gemini Bot Productivity Optimizations" --body "Automated changes generated by Gemini CLI Bot." --head "$BRANCH_NAME" --base main
-            else
-              PR_STATE=$(gh pr view "$BRANCH_NAME" --json state --jq .state)
-              if [ "$PR_STATE" = "CLOSED" ]; then
-                NEW_BRANCH_NAME="${BRANCH_NAME}-retry-${{ github.run_id }}"
-                git checkout -b "$NEW_BRANCH_NAME"
-                git push origin "$NEW_BRANCH_NAME" --force
-                gh pr create --draft --title "$PR_TITLE" --body-file "${{ runner.temp }}/brain-data/pr-description.md" --head "$NEW_BRANCH_NAME" --base main || \
-                gh pr create --draft --title "🤖 Gemini Bot Productivity Optimizations" --body "Automated changes generated by Gemini CLI Bot." --head "$NEW_BRANCH_NAME" --base main
-              fi
-            fi
-          fi
-
-      - name: 'Post PR/Issue Comment'
-        env:
-          GH_TOKEN: '${{ steps.generate_token.outputs.token }}'
-          TRIGGER_ISSUE_NUMBER: '${{ github.event.issue.number || github.event.inputs.issue_number }}'
-        run: |
-          if [ -s "${{ runner.temp }}/brain-data/issue-comment.md" ] && [ -n "$TRIGGER_ISSUE_NUMBER" ]; then
-            echo "Posting comment to triggering issue #$TRIGGER_ISSUE_NUMBER"
-            # Use REST API (gh api) instead of GraphQL (gh issue comment) to ensure robot identity
-            # while avoiding potential GraphQL-specific authorization hurdles with PATs.
-            gh api "repos/${{ github.repository }}/issues/$TRIGGER_ISSUE_NUMBER/comments" -F body=@"${{ runner.temp }}/brain-data/issue-comment.md"
-          fi
-
-          if [ -s "${{ runner.temp }}/brain-data/pr-comment.md" ] && [ -f "${{ runner.temp }}/brain-data/pr-number.txt" ]; then
-            PR_NUM=$(cat "${{ runner.temp }}/brain-data/pr-number.txt")
-
-            # Using GitHub App, so author check is no longer valid against gemini-cli-robot
-            # Skipping author validation here to let the app post.
-
-            # Use REST API (gh api) for consistency and robot identity
-            gh api "repos/${{ github.repository }}/issues/$PR_NUM/comments" -F body=@"${{ runner.temp }}/brain-data/pr-comment.md"
-          fi

.github/workflows/gemini-cli-bot-pulse.yml

@@ -1,49 +0,0 @@
-name: '🔄 Gemini CLI Bot: Pulse'
-
-on:
-  schedule:
-    - cron: '*/30 * * * *' # Every 30 minutes
-  workflow_dispatch:
-
-concurrency:
-  group: '${{ github.workflow }}-${{ github.ref }}'
-  cancel-in-progress: true
-
-permissions:
-  contents: 'write'
-  issues: 'write'
-  pull-requests: 'write'
-
-jobs:
-  pulse:
-    name: 'Pulse (Reflex Layer)'
-    runs-on: 'ubuntu-latest'
-    if: "github.repository == 'google-gemini/gemini-cli'"
-    steps:
-      - name: 'Checkout'
-        uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8' # ratchet:actions/checkout@v5
-        with:
-          persist-credentials: false
-          fetch-depth: 0
-
-      - name: 'Setup Node.js'
-        uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020' # ratchet:actions/setup-node@v4
-        with:
-          node-version: '20'
-          cache: 'npm'
-
-      - name: 'Install dependencies'
-        run: 'npm ci'
-
-      - name: 'Run Reflex Processes'
-        env:
-          GITHUB_TOKEN: '${{ secrets.GITHUB_TOKEN }}'
-        run: |
-          if [ -d "tools/gemini-cli-bot/reflexes/scripts" ] && [ "$(ls -A tools/gemini-cli-bot/reflexes/scripts)" ]; then
-            for script in tools/gemini-cli-bot/reflexes/scripts/*.ts; do
-              echo "Running reflex script: $script"
-              npx tsx "$script"
-            done
-          else
-            echo "No reflex scripts found."
-          fi

.github/workflows/gemini-lifecycle-manager.yml

@@ -1,47 +0,0 @@
-name: '🔄 Gemini Scheduled Lifecycle Manager'
-
-on:
-  schedule:
-    - cron: '30 1 * * *' # Once a day
-  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
-
-permissions:
-  issues: 'write'
-  pull-requests: 'write'
-
-jobs:
-  manage-lifecycle:
-    if: "github.repository == 'google-gemini/gemini-cli'"
-    runs-on: 'ubuntu-latest'
-    steps:
-      - name: 'Generate GitHub App Token'
-        id: 'generate_token'
-        uses: 'actions/create-github-app-token@fee1f7d63c2ff003460e3d139729b119787bc349' # ratchet:actions/create-github-app-token@v2
-        with:
-          app-id: '${{ secrets.APP_ID }}'
-          private-key: '${{ secrets.PRIVATE_KEY }}'
-
-      - name: 'Checkout repository'
-        uses: 'actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683' # ratchet:actions/checkout@v4
-        with:
-          persist-credentials: false
-
-      - name: 'Lifecycle Management'
-        uses: 'actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea'
-        env:
-          DRY_RUN: '${{ inputs.dry_run }}'
-        with:
-          github-token: '${{ steps.generate_token.outputs.token }}'
-          script: |
-            const script = require('./.github/scripts/gemini-lifecycle-manager.cjs');
-            await script({github, context, core});

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

@@ -28,8 +28,6 @@ jobs:
     steps:
       - name: 'Checkout'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8' # ratchet:actions/checkout@v5
-        with:
-          persist-credentials: false
 
       - name: 'Log in to GitHub Container Registry'
         uses: 'docker/login-action@184bdaa0721073962dff0199f1fb9940f07167d1' # ratchet:docker/login-action@v3
@@ -49,7 +47,6 @@ jobs:
           REPOSITORY: '${{ github.repository }}'
           FIRESTORE_PROJECT: '${{ vars.FIRESTORE_PROJECT }}'
         with:
-          upload_artifacts: 'true'
           gcp_workload_identity_provider: '${{ vars.GCP_WIF_PROVIDER }}'
           gcp_project_id: '${{ vars.GOOGLE_CLOUD_PROJECT }}'
           gcp_location: '${{ vars.GOOGLE_CLOUD_LOCATION }}'
@@ -88,11 +85,9 @@ jobs:
                 }
               },
               "maxSessionTurns": 25,
-              "tools": {
-                "core": [
-                  "run_shell_command(echo)"
-                ]
-              },
+              "coreTools": [
+                "run_shell_command(echo)"
+              ],
               "telemetry": {
                 "enabled": true,
                 "target": "gcp"

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

@@ -1,6 +1,10 @@
 name: '📋 Gemini Scheduled Issue Triage'
 
 on:
+  issues:
+    types:
+      - 'opened'
+      - 'reopened'
   schedule:
     - cron: '0 * * * *' # Runs every hour
   workflow_dispatch:
@@ -19,27 +23,13 @@ permissions:
 
 jobs:
   triage-issues:
-    timeout-minutes: 60
+    timeout-minutes: 10
     if: |-
       ${{ github.repository == 'google-gemini/gemini-cli' }}
     runs-on: 'ubuntu-latest'
     steps:
       - name: 'Checkout'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8' # ratchet:actions/checkout@v5
-        with:
-          persist-credentials: false
-
-      - name: 'Install Utilities'
-        run: |
-          sudo apt-get update
-          sudo apt-get install -y ripgrep
-
-      - name: 'Get Current Version'
-        id: 'get_version'
-        run: |
-          VERSION=$(jq -r .version package.json | cut -d'-' -f1)
-          echo "version=${VERSION}" >> "${GITHUB_OUTPUT}"
-          echo "🚀 Current CLI Version: ${VERSION}"
 
       - name: 'Generate GitHub App Token'
         id: 'generate_token'
@@ -57,38 +47,10 @@ jobs:
           ISSUE_EVENT: '${{ toJSON(github.event.issue) }}'
         run: |
           set -euo pipefail
-          echo "$ISSUE_EVENT" | jq -c '[{number: .number, title: .title, body: .body}]' > issues_to_triage.json
-          echo "has_issues=true" >> "${GITHUB_OUTPUT}"
+          ISSUE_JSON=$(echo "$ISSUE_EVENT" | jq -c '[{number: .number, title: .title, body: .body}]')
+          echo "issues_to_triage=${ISSUE_JSON}" >> "${GITHUB_OUTPUT}"
           echo "✅ Found issue #${{ github.event.issue.number }} from event to triage! 🎯"
 
-      - name: 'Sync Issue Types'
-        if: |-
-          ${{ github.event_name == 'schedule' || github.event_name == 'workflow_dispatch' }}
-        uses: 'actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea'
-        with:
-          github-token: '${{ steps.generate_token.outputs.token }}'
-          script: |-
-            const syncIssueTypes = require('./.github/scripts/sync-issue-types.cjs');
-            await syncIssueTypes({ github, context, core });
-
-      - name: 'Find Issues with Conflicting Labels'
-        if: |-
-          ${{ github.event_name == 'schedule' || github.event_name == 'workflow_dispatch' }}
-        env:
-          GITHUB_TOKEN: '${{ steps.generate_token.outputs.token }}'
-          GITHUB_REPOSITORY: '${{ github.repository }}'
-        run: |-
-          set -euo pipefail
-          echo '🔍 Fetching open issues to find conflicts...'
-          # Fetch up to 2000 open issues in one quick GraphQL-backed query
-          gh issue list --repo "${GITHUB_REPOSITORY}" --search "is:issue is:open" --limit 2000 --json number,title,body,labels > all_open_issues.json
-
-          echo '🧹 Filtering issues with multiple area/ or priority/ labels...'
-          jq -c '[ .[] | select( (.labels | map(select(.name | startswith("area/"))) | length) > 1 or (.labels | map(select(.name | startswith("priority/"))) | length) > 1 ) ] | .[0:50]' all_open_issues.json > conflicting_labels_issues.json
-
-          CONFLICT_COUNT=$(jq 'length' conflicting_labels_issues.json)
-          echo "Found ${CONFLICT_COUNT} issues with conflicting labels (capped at 50 for processing)."
-
       - name: 'Find untriaged issues'
         if: |-
           ${{ github.event_name == 'schedule' || github.event_name == 'workflow_dispatch' }}
@@ -100,56 +62,25 @@ jobs:
           set -euo pipefail
 
           echo '🔍 Finding issues missing area labels...'
-          gh issue list --repo "${GITHUB_REPOSITORY}" \
-            --search 'is:open is:issue -label:area/core -label:area/agent -label:area/enterprise -label:area/non-interactive -label:area/security -label:area/platform -label:area/extensions -label:area/documentation -label:area/unknown' --limit 50 --json number,title,body,labels > no_area_issues.json
+          NO_AREA_ISSUES="$(gh issue list --repo "${GITHUB_REPOSITORY}" \
+            --search 'is:open is:issue -label:area/core -label:area/agent -label:area/enterprise -label:area/non-interactive -label:area/security -label:area/platform -label:area/extensions -label:area/documentation -label:area/unknown' --limit 100 --json number,title,body)"
 
           echo '🔍 Finding issues missing kind labels...'
-          gh issue list --repo "${GITHUB_REPOSITORY}" \
-            --search 'is:open is:issue -label:kind/bug -label:kind/enhancement -label:kind/customer-issue -label:kind/question' --limit 50 --json number,title,body,labels > no_kind_issues.json
+          NO_KIND_ISSUES="$(gh issue list --repo "${GITHUB_REPOSITORY}" \
+            --search 'is:open is:issue -label:kind/bug -label:kind/enhancement -label:kind/customer-issue -label:kind/question' --limit 100 --json number,title,body)"
 
           echo '🏷️ Finding issues missing priority labels...'
-          gh issue list --repo "${GITHUB_REPOSITORY}" \
-            --search 'is:open is:issue -label:priority/p0 -label:priority/p1 -label:priority/p2 -label:priority/p3 -label:priority/unknown' --limit 50 --json number,title,body,labels > no_priority_issues.json
+          NO_PRIORITY_ISSUES="$(gh issue list --repo "${GITHUB_REPOSITORY}" \
+            --search 'is:open is:issue -label:priority/p0 -label:priority/p1 -label:priority/p2 -label:priority/p3 -label:priority/unknown' --limit 100 --json number,title,body)"
 
-          echo '📏 Finding issues missing effort labels...'
-          gh issue list --repo "${GITHUB_REPOSITORY}" \
-            --search 'is:open is:issue -label:effort/small -label:effort/medium -label:effort/large label:area/core,area/extensions,area/site,area/non-interactive' --limit 20 --json number,title,body,labels > no_effort_issues.json
+          echo '🔄 Merging and deduplicating issues...'
+          ISSUES="$(echo "${NO_AREA_ISSUES}" "${NO_KIND_ISSUES}" "${NO_PRIORITY_ISSUES}" | jq -c -s 'add | unique_by(.number)')"
 
-          echo '🔄 Merging and deduplicating standard triage issues...'
-          if [ ! -f conflicting_labels_issues.json ]; then echo "[]" > conflicting_labels_issues.json; fi
-          jq -c -s 'add | unique_by(.number)' no_area_issues.json no_kind_issues.json no_priority_issues.json conflicting_labels_issues.json > standard_issues_to_triage.json
+          echo '📝 Setting output for GitHub Actions...'
+          echo "issues_to_triage=${ISSUES}" >> "${GITHUB_OUTPUT}"
 
-          echo '📏 Deduplicating effort issues...'
-          jq -c -s 'add | unique_by(.number)' no_effort_issues.json > effort_issues_to_triage.json
-
-          STANDARD_COUNT="$(jq 'length' standard_issues_to_triage.json)"
-          EFFORT_COUNT="$(jq 'length' effort_issues_to_triage.json)"
-          if [ "$STANDARD_COUNT" -gt 0 ] || [ "$EFFORT_COUNT" -gt 0 ]; then
-            echo "has_issues=true" >> "${GITHUB_OUTPUT}"
-            echo "has_standard_issues=$([ "$STANDARD_COUNT" -gt 0 ] && echo 'true' || echo 'false')" >> "${GITHUB_OUTPUT}"
-            echo "has_effort_issues=$([ "$EFFORT_COUNT" -gt 0 ] && echo 'true' || echo 'false')" >> "${GITHUB_OUTPUT}"
-          else
-            echo "has_issues=false" >> "${GITHUB_OUTPUT}"
-            echo "has_standard_issues=false" >> "${GITHUB_OUTPUT}"
-            echo "has_effort_issues=false" >> "${GITHUB_OUTPUT}"
-          fi
-          echo "✅ Found ${STANDARD_COUNT} standard issues and ${EFFORT_COUNT} effort issues to triage! 🎯"
-
-      - name: 'Create Gemini CLI Experiments Override'
-        if: |-
-          steps.get_issue_from_event.outputs.has_issues == 'true' || steps.find_issues.outputs.has_issues == 'true'
-        run: |
-          cat << 'EOF' > gemini_exp.json
-          {
-            "flags": [
-              {
-                "flagId": 45750526,
-                "boolValue": false
-              }
-            ],
-            "experimentIds": []
-          }
-          EOF
+          ISSUE_COUNT="$(echo "${ISSUES}" | jq 'length')"
+          echo "✅ Found ${ISSUE_COUNT} unique issues to triage! 🎯"
 
       - name: 'Get Repository Labels'
         id: 'get_labels'
@@ -166,22 +97,18 @@ jobs:
             core.info(`Found ${labelNames.length} labels: ${labelNames.join(', ')}`);
             return labelNames;
 
-      - name: 'Run Standard Triage Analysis'
+      - name: 'Run Gemini Issue Analysis'
         if: |-
-          steps.get_issue_from_event.outputs.has_issues == 'true' || steps.find_issues.outputs.has_standard_issues == 'true'
+          (steps.get_issue_from_event.outputs.issues_to_triage != '' && steps.get_issue_from_event.outputs.issues_to_triage != '[]') ||
+          (steps.find_issues.outputs.issues_to_triage != '' && steps.find_issues.outputs.issues_to_triage != '[]')
         uses: 'google-github-actions/run-gemini-cli@a3bf79042542528e91937b3a3a6fbc4967ee3c31' # ratchet:google-github-actions/run-gemini-cli@v0
-        id: 'gemini_standard_issue_analysis'
+        id: 'gemini_issue_analysis'
         env:
           GITHUB_TOKEN: '' # Do not pass any auth token here since this runs on untrusted inputs
+          ISSUES_TO_TRIAGE: '${{ steps.get_issue_from_event.outputs.issues_to_triage || steps.find_issues.outputs.issues_to_triage }}'
           REPOSITORY: '${{ github.repository }}'
           AVAILABLE_LABELS: '${{ steps.get_labels.outputs.available_labels }}'
-          CLI_VERSION: '${{ steps.get_version.outputs.version }}'
-          GEMINI_CLI_TRUST_WORKSPACE: 'true'
-          GEMINI_EXP: 'gemini_exp.json'
-          GEMINI_STRICT_TELEMETRY_LIMITS: 'true'
-          GEMINI_MODEL: 'gemini-3-flash-preview'
         with:
-          upload_artifacts: 'true'
           gcp_workload_identity_provider: '${{ vars.GCP_WIF_PROVIDER }}'
           gcp_project_id: '${{ vars.GOOGLE_CLOUD_PROJECT }}'
           gcp_location: '${{ vars.GOOGLE_CLOUD_LOCATION }}'
@@ -192,14 +119,11 @@ jobs:
           settings: |-
             {
               "maxSessionTurns": 25,
-              "tools": {
-                "core": [
-                  "run_shell_command(echo)",
-                  "read_file"
-                ]
-              },
+              "coreTools": [
+                "run_shell_command(echo)"
+              ],
               "telemetry": {
-                "enabled": false,
+                "enabled": true,
                 "target": "gcp"
               }
             }
@@ -212,16 +136,14 @@ jobs:
 
             ## Steps
 
-            1. You are only able to use the echo and read_file commands. Review the available labels in the environment variable: "${AVAILABLE_LABELS}".
-            2. Use the read_file tool to read the file "standard_issues_to_triage.json" which contains the JSON array of issues to triage (including their current labels).
-            3. Review the issue title, body, current labels, and any comments provided in the JSON file.
-            4. Identify the most relevant labels from the existing labels, specifically focusing on area/*, kind/*, and priority/*.
+            1. You are only able to use the echo command. Review the available labels in the environment variable: "${AVAILABLE_LABELS}".
+            2. Check environment variable for issues to triage: $ISSUES_TO_TRIAGE (JSON array of issues)
+            3. Review the issue title, body and any comments provided in the environment variables.
+            4. Identify the most relevant labels from the existing labels, specifically focusing on area/*, kind/* and priority/*.
             5. Label Policy:
                - If the issue already has a kind/ label, do not change it.
-               - If the issue has exactly ONE priority/ label, do not change it (unless you are explicitly re-evaluating an ambiguous priority).
-               - If the issue is missing a priority/ label, OR if the issue currently has MULTIPLE priority/ labels, you must evaluate the issue's impact to determine exactly ONE priority level (priority/p0, priority/p1, priority/p2, priority/p3, or priority/unknown) based the guidelines. If you are fixing an issue with multiple priority/ labels, put the correct one in `labels_to_add` and put all the incorrect ones in `labels_to_remove`.
-               - If the issue has exactly ONE area/ label, do not change it.
-               - If the issue is missing an area/ label, OR if the issue currently has MULTIPLE area/ labels, select exactly ONE area/ label that best fits the issue. Issues MUST NOT have multiple area/ labels. If you are fixing an issue with multiple area/ labels, put the correct one in `labels_to_add` and put all the incorrect ones in `labels_to_remove`.
+               - If the issue already has a priority/ label, do not change it.
+               - If the issue already has an area/ label, do not change it.
                - If any of these are missing, select exactly ONE appropriate label for the missing category.
             6. Identify other applicable labels based on the issue content, such as status/*, help wanted, good first issue, etc.
             7. Give me a single short explanation about why you are selecting each label in the process.
@@ -238,12 +160,11 @@ jobs:
                ]
                ```
               If an issue cannot be classified, do not include it in the output array.
-            9. For each issue, carefully check if the CLI version is present. It is usually found under the "### Client information" header, as a bullet point (e.g., "• CLI Version: 0.33.1", "* **CLI Version:** 0.42.0"), or in the output of the `/about` command.
-              - **Only for issues classified as kind/bug:** If the version is provided but is more than 6 minor versions older than the most recent release (current version is ${{ steps.get_version.outputs.version }}), apply the status/need-information label and leave a comment politely asking the user to verify if the issue persists in the latest version.
-            10. **Only for issues classified as kind/bug:** If the issue does not have sufficient information, recommend the status/need-information label and leave a comment politely requesting the missing details. For example, if repro steps are missing, ask for them; if the CLI version is completely missing, ask for the version information in the explanation section below. Do not ask for version info if it is already in the issue body. (Check both bullet points and bold text). For features and enhancements, the CLI version is NOT required.
-            11. If you think an issue is a Priority/P0, you MUST apply the priority/p1 label AND the status/manual-triage label, and include a note in your explanation that it likely requires P0 escalation.
-            12. If the issue is highly ambiguous, completely lacks a description, or you are torn between two lower priorities (like P2 vs P3), you MUST retain the existing priority label if one is already present. Do not toggle the priority if you do not have enough information to make a definitive change.
-            13. If you are uncertain about a category, use the area/unknown, kind/question, or priority/unknown labels as appropriate. If you are extremely uncertain, apply the status/manual-triage label.
+            9. 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
+              - Anything more than 6 versions older than the most recent should add the status/need-retesting label
+            10. 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.
+            11. 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.
+            12. If you are uncertain about a category, use the area/unknown, kind/question, or priority/unknown labels as appropriate. If you are extremely uncertain, apply the status/manual-triage label.
 
             ## Guidelines
 
@@ -253,127 +174,10 @@ jobs:
               - Do not add comments or modify the issue content.
               - Do not remove the following labels maintainer, help wanted or good first issue.
               - Triage only the current issue.
-              - Identify exactly ONE area/ label. Do NOT assign multiple area/ labels to a single issue.
+              - Identify only one area/ label.
               - Identify only one kind/ label (Do not apply kind/duplicate or kind/parent-issue)
-              - Identify exactly ONE priority/ label. Do NOT assign multiple priority/ labels to a single issue.
-              - **Do not manually downgrade the priority.** Always assign the true priority based on the guidelines. The system will handle downgrades programmatically if information is missing.
-              - **NEVER mention label names, label removals, or label additions in your `explanation`.** The explanation must be purely written for the user (e.g., "Please provide your CLI version.") without exposing internal triage mechanics (e.g., do NOT say "Removing area/unknown to leave only area/core").
-
-            Categorization Guidelines (Priority):
-            P0 - Urgent Blocking Issues:
-              - DO NOT APPLY THE priority/p0 LABEL AUTOMATICALLY. Instead apply priority/p1 and status/manual-triage.
-              - Definition: Critical failures breaking core functionality for a large portion of users. Examples: CLI fails to launch globally, core commands (gemini run) crash on valid input, unhandled promise rejections on boot, critical security vulnerability.
-              - Note: You must apply priority/p1 and status/manual-triage instead of priority/p0.
-            P1 - Critical but Workable:
-              - Definition: Severe issues without a reasonable workaround, significantly degrading the developer experience but not globally blocking. Examples: Specific tools failing consistently (e.g., `web_search` returns 500s), persistent PTY streaming hangs, memory leaks leading to OOM after short use.
-            P2 - Significant Issues:
-              - Definition: Affect some workflows but a clear workaround exists, or non-critical bugs. Examples: Theme flickering, confusing error messages, minor UI misalignment, failing to read deeply nested config files correctly.
-            P3 - Minor/Enhancements:
-              - Definition: Trivial bugs, typos, documentation requests, or feature requests.
-
-            Categorization Guidelines (Kind):
-            kind/bug: The issue is describing an unexpected behavior or failure in the application.
-            kind/enhancement: The issue is describing a feature request or an improvement to an existing feature.
-            kind/question: The issue is asking a question about how to use the CLI or about a specific feature.
-
-            Categorization Guidelines (Area):
-            area/agent: The "brain" of the CLI. Core agent logic, model quality, tool/function calling, memory, web search, generated code quality, sub-agents.
-            area/core: The fundamental CLI app. UI/UX, installation, OS compatibility, performance, command parsing, theming, flickering.
-            area/documentation: Website docs, READMEs, inline help text.
-            area/enterprise: Telemetry, Policy, Quota / Licensing
-            area/extensions: Gemini CLI extensions capability
-            area/non-interactive: GitHub Actions, SDK, 3P Integrations, Shell Scripting, Command line automation
-            area/platform: Platform specific behavior
-            area/security: Authentication, authorization, privacy, data leaks, credential storage.
-
-      - name: 'Stop Telemetry Collector'
-        if: |-
-          steps.find_issues.outputs.has_effort_issues == 'true'
-        run: 'docker rm -f gemini-telemetry-collector || true'
-
-      - name: 'Run Effort Triage Analysis'
-        if: |-
-          steps.find_issues.outputs.has_effort_issues == 'true'
-        uses: 'google-github-actions/run-gemini-cli@a3bf79042542528e91937b3a3a6fbc4967ee3c31' # ratchet:google-github-actions/run-gemini-cli@v0
-        id: 'gemini_effort_issue_analysis'
-        env:
-          GITHUB_TOKEN: '' # Do not pass any auth token here since this runs on untrusted inputs
-          REPOSITORY: '${{ github.repository }}'
-          AVAILABLE_LABELS: '${{ steps.get_labels.outputs.available_labels }}'
-          CLI_VERSION: '${{ steps.get_version.outputs.version }}'
-          GEMINI_CLI_TRUST_WORKSPACE: 'true'
-          GEMINI_EXP: 'gemini_exp.json'
-          GEMINI_STRICT_TELEMETRY_LIMITS: 'true'
-          GEMINI_MODEL: 'gemini-3-flash-preview'
-        with:
-          upload_artifacts: 'true'
-          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: |-
-            {
-              "maxSessionTurns": 30,
-              "tools": {
-                "core": [
-                  "run_shell_command(echo)",
-                  "grep_search",
-                  "glob",
-                  "read_file"
-                ]
-              },
-              "telemetry": {
-                "enabled": false,
-                "target": "gcp"
-              }
-            }
-          prompt: |-
-            ## Role
-
-            You are an expert software architect. Analyze the provided GitHub issues and assign the correct `effort/*` label based on the codebase complexity.
-
-            ## Steps
-
-            1. Use the read_file tool to read "effort_issues_to_triage.json".
-            2. For each issue in the array:
-               - You must evaluate the architectural complexity to determine the effort level. You MUST NOT guess the root cause. You MUST actively use your codebase search tools (grep_search and glob) to search for keywords from the issue and explore the codebase. You must identify the specific files and components involved before deciding the effort.
-            3. Output a JSON array of objects, each containing the issue number and the effort label to add, along with an explanation and an effort_analysis field. This effort_analysis must be highly detailed, technical, and empirical. It MUST NOT contain vague guesses (e.g., avoid words like "likely points to" or "possibly"). You must explicitly cite the specific file paths and architectural mechanisms you discovered using your search tools, explain the root cause, and then explicitly state how that complexity maps to the chosen effort level guidelines. For example:
-               ```
-               [
-                 {
-                   "issue_number": 123,
-                   "labels_to_add": ["effort/small"],
-                   "explanation": "This is a simple logic fix.",
-                   "effort_analysis": "The `vscode-ide-companion` extension indiscriminately tracks active text editors via `vscode.window.onDidChangeActiveTextEditor` in `open-files-manager.ts`. When a user opens `.vscode/settings.json`, its content is sent to the CLI's context. The fix is highly localized to the VS Code companion extension's event listener. It involves adding a simple conditional check to exclude specific configuration files from the active editor tracking logic, which is a trivial logic adjustment with a clear root cause."
-                 }
-               ]
-               ```
-
-            ## Guidelines
-
-            - Output only valid JSON format
-            - Do not include any explanation or additional text, just the JSON
-            - Triage only the current issue.
-
-            Categorization Guidelines (Effort):
-            effort/small (1 day or less):
-              - Trivial Logic & Config: Schema updates (Zod), feature flag toggles, adding missing fields to package.json or settings.json.
-              - UI/Aesthetic Adjustments: Fixing minor layout bugs in Ink components (e.g., adding flexShrink, correcting padding in a single Box), text color changes.
-              - Documentation & Strings: Typos, log message updates, CLI argument descriptions.
-              - Localized Bug Fixes: Single-file logic errors, straightforward promise rejections (e.g., wrapping a known failure in a try/catch), simple regex or string parsing fixes.
-            effort/medium (2-3 days):
-              - React/Ink State Management: Debugging useState/useEffect/useReducer bugs, component lifecycle issues (memory leaks in the UI), terminal redraw flickering, or state synchronization between the CLI's internal input buffer and the interactive React components.
-              - Asynchronous Flow & Integration: Resolving complex Promise chains, ERR_STREAM_PREMATURE_CLOSE, debugging IDE companion extensions (VS Code, Android Studio) or resolving hanging HTTP requests/IPC between the CLI and external plugins, timeouts in non-interactive/ACP modes.
-              - Tooling & Output Parsers: Modifying how tools parse streaming stdout/stderr buffers, adding new built-in tools that don't require native bindings.
-              - Cross-Component Refactors: Changes that span across packages/cli and packages/core to pass new data models or telemetry state.
-            effort/large (3+ days):
-              - Platform-Specific Complexities (PTY/Signals): Any issue involving node-pty, child_process.spawn, OS-level shell behavior (Windows vs Linux vs macOS), pseudo-terminal exhaustion (ENXIO), raw mode terminal desyncs, or POSIX signal forwarding (SIGINT/SIGTERM).
-              - Core Architecture & Protocols: Refactoring the Scheduler, Agent-to-Agent (A2A) protocol implementation, low-level MCP (Model Context Protocol) transport mechanisms.
-              - Performance & Memory: Diagnosing massive disk/memory leaks, severe boot time regressions, high-throughput streaming optimizations (e.g., voice streaming pipelines).
-            Note: Any bug that is described as intermittent, flickering, difficult to reproduce, platform-specific, or requiring cross-environment setups (e.g., involving the VS Code IDE companion, GCA plugin, or Android Studio) MUST NOT be rated as effort/small because of the increased overhead of testing and reproducing.
+              - Identify only one priority/ label.
+              - 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.
 
             Categorization Guidelines (Priority):
             P0 - Urgent Blocking Issues:
@@ -412,52 +216,64 @@ jobs:
             - 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.
 
-      - name: 'Apply Triaged Labels'
+      - name: 'Apply Labels to Issues'
         if: |-
-          always() &&
-          ( (steps.gemini_standard_issue_analysis.outcome == 'success' && steps.gemini_standard_issue_analysis.outputs.summary != '[]' && steps.gemini_standard_issue_analysis.outputs.summary != '') ||
-            (steps.gemini_effort_issue_analysis.outcome == 'success' && steps.gemini_effort_issue_analysis.outputs.summary != '[]' && steps.gemini_effort_issue_analysis.outputs.summary != '') )
+          ${{ steps.gemini_issue_analysis.outcome == 'success' &&
+              steps.gemini_issue_analysis.outputs.summary != '[]' }}
         env:
-          LABELS_OUTPUT_STANDARD: '${{ steps.gemini_standard_issue_analysis.outputs.summary }}'
-          LABELS_OUTPUT_EFFORT: '${{ steps.gemini_effort_issue_analysis.outputs.summary }}'
+          REPOSITORY: '${{ github.repository }}'
+          LABELS_OUTPUT: '${{ steps.gemini_issue_analysis.outputs.summary }}'
         uses: 'actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea'
         with:
           github-token: '${{ steps.generate_token.outputs.token }}'
           script: |-
-            const applyLabels = require('./.github/scripts/apply-issue-labels.cjs');
-            await applyLabels({ github, context, core });
+            const rawLabels = process.env.LABELS_OUTPUT;
+            core.info(`Raw labels JSON: ${rawLabels}`);
+            let parsedLabels;
+            try {
+              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 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;
+            }
 
-      - name: 'Sync Issue Types (Post-Analysis)'
-        if: |-
-          always() && (github.event_name == 'schedule' || github.event_name == 'workflow_dispatch')
-        uses: 'actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea'
-        with:
-          github-token: '${{ steps.generate_token.outputs.token }}'
-          script: |-
-            const syncIssueTypes = require('./.github/scripts/sync-issue-types.cjs');
-            await syncIssueTypes({ github, context, core });
+            for (const entry of parsedLabels) {
+              const issueNumber = entry.issue_number;
+              if (!issueNumber) {
+                core.info(`Skipping entry with no issue number: ${JSON.stringify(entry)}`);
+                continue;
+              }
 
-      - name: 'Find Triaged Issues to Clean Up'
-        if: |-
-          always() && (github.event_name == 'schedule' || github.event_name == 'workflow_dispatch')
-        env:
-          GITHUB_TOKEN: '${{ steps.generate_token.outputs.token }}'
-          GITHUB_REPOSITORY: '${{ github.repository }}'
-        run: |-
-          set -euo pipefail
-          echo '🧹 Finding issues that have conflicting status labels...'
-          gh issue list --repo "${GITHUB_REPOSITORY}" \
-            --search 'is:open is:issue label:status/bot-triaged label:status/need-triage' --limit 50 --json number > cleanup_1.json
-          gh issue list --repo "${GITHUB_REPOSITORY}" \
-            --search 'is:open is:issue label:status/bot-triaged label:status/manual-triage' --limit 50 --json number > cleanup_2.json
-          jq -c -s 'add | unique_by(.number)' cleanup_1.json cleanup_2.json > issues_to_cleanup.json
+              const labelsToAdd = entry.labels_to_add || [];
+              labelsToAdd.push('status/bot-triaged');
 
-      - name: 'Clean Up Triage Labels'
-        if: |-
-          always() && (github.event_name == 'schedule' || github.event_name == 'workflow_dispatch')
-        uses: 'actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea'
-        with:
-          github-token: '${{ steps.generate_token.outputs.token }}'
-          script: |-
-            const cleanupLabels = require('./.github/scripts/cleanup-triage-labels.cjs');
-            await cleanupLabels({ github, context, core });
+              if (labelsToAdd.length > 0) {
+                await github.rest.issues.addLabels({
+                  owner: context.repo.owner,
+                  repo: context.repo.repo,
+                  issue_number: issueNumber,
+                  labels: labelsToAdd
+                });
+                const explanation = entry.explanation ? ` - ${entry.explanation}` : '';
+                core.info(`Successfully added labels for #${issueNumber}: ${labelsToAdd.join(', ')}${explanation}`);
+              }
+
+              if (entry.explanation) {
+                await github.rest.issues.createComment({
+                  owner: context.repo.owner,
+                  repo: context.repo.repo,
+                  issue_number: issueNumber,
+                  body: entry.explanation,
+                });
+              }
+
+              if ((!entry.labels_to_add || entry.labels_to_add.length === 0) && (!entry.labels_to_remove || entry.labels_to_remove.length === 0)) {
+                core.info(`No labels to add or remove for #${issueNumber}, leaving as is`);
+              }
+            }

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

@@ -21,8 +21,6 @@ jobs:
     steps:
       - name: 'Checkout'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8' # ratchet:actions/checkout@v5
-        with:
-          persist-credentials: false
 
       - name: 'Generate GitHub App Token'
         id: 'generate_token'

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

@@ -0,0 +1,159 @@
+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:
+    if: "github.repository == 'google-gemini/gemini-cli'"
+    runs-on: 'ubuntu-latest'
+    permissions:
+      issues: 'write'
+    steps:
+      - name: 'Generate GitHub App Token'
+        id: 'generate_token'
+        uses: 'actions/create-github-app-token@fee1f7d63c2ff003460e3d139729b119787bc349' # ratchet:actions/create-github-app-token@v2
+        with:
+          app-id: '${{ secrets.APP_ID }}'
+          private-key: '${{ secrets.PRIVATE_KEY }}'
+          permission-issues: 'write'
+
+      - name: 'Process Stale Issues'
+        uses: 'actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b' # ratchet: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, help wanted, or Public Roadmap label
+              const rawLabels = issue.labels.map((l) => l.name);
+              const lowercaseLabels = rawLabels.map((l) => l.toLowerCase());
+              if (
+                lowercaseLabels.some((l) => l.includes('maintainer')) ||
+                lowercaseLabels.includes('help wanted') ||
+                rawLabels.includes('🗓️ Public Roadmap')
+              ) {
+                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/gemini-scheduled-stale-pr-closer.yml

@@ -0,0 +1,254 @@
+name: 'Gemini Scheduled Stale PR Closer'
+
+on:
+  schedule:
+    - cron: '0 2 * * *' # Every day at 2 AM UTC
+  pull_request:
+    types: ['opened', 'edited']
+  workflow_dispatch:
+    inputs:
+      dry_run:
+        description: 'Run in dry-run mode'
+        required: false
+        default: false
+        type: 'boolean'
+
+jobs:
+  close-stale-prs:
+    if: "github.repository == 'google-gemini/gemini-cli'"
+    runs-on: 'ubuntu-latest'
+    permissions:
+      pull-requests: 'write'
+      issues: 'write'
+    steps:
+      - name: 'Generate GitHub App Token'
+        id: 'generate_token'
+        env:
+          APP_ID: '${{ secrets.APP_ID }}'
+        if: |-
+          ${{ env.APP_ID != '' }}
+        uses: 'actions/create-github-app-token@fee1f7d63c2ff003460e3d139729b119787bc349' # ratchet:actions/create-github-app-token@v2
+        with:
+          app-id: '${{ secrets.APP_ID }}'
+          private-key: '${{ secrets.PRIVATE_KEY }}'
+
+      - name: 'Process Stale PRs'
+        uses: 'actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b' # ratchet:actions/github-script@v7
+        env:
+          DRY_RUN: '${{ inputs.dry_run }}'
+        with:
+          github-token: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}'
+          script: |
+            const dryRun = process.env.DRY_RUN === 'true';
+            const fourteenDaysAgo = new Date();
+            fourteenDaysAgo.setDate(fourteenDaysAgo.getDate() - 14);
+            const thirtyDaysAgo = new Date();
+            thirtyDaysAgo.setDate(thirtyDaysAgo.getDate() - 30);
+
+            // 1. Fetch maintainers for verification
+            let maintainerLogins = new Set();
+            const teams = ['gemini-cli-maintainers', 'gemini-cli-askmode-approvers', 'gemini-cli-docs'];
+
+            for (const team_slug of teams) {
+              try {
+                const members = await github.paginate(github.rest.teams.listMembersInOrg, {
+                  org: context.repo.owner,
+                  team_slug: team_slug
+                });
+                for (const m of members) maintainerLogins.add(m.login.toLowerCase());
+                core.info(`Successfully fetched ${members.length} team members from ${team_slug}`);
+              } catch (e) {
+                // Silently skip if permissions are insufficient; we will rely on author_association
+                core.debug(`Skipped team fetch for ${team_slug}: ${e.message}`);
+              }
+            }
+
+            const isMaintainer = async (login, assoc) => {
+              // Reliably identify maintainers using authorAssociation (provided by GitHub)
+              // and organization membership (if available).
+              const isTeamMember = maintainerLogins.has(login.toLowerCase());
+              const isRepoMaintainer = ['OWNER', 'MEMBER', 'COLLABORATOR'].includes(assoc);
+
+              if (isTeamMember || isRepoMaintainer) return true;
+
+              // Fallback: Check if user belongs to the 'google' or 'googlers' orgs (requires permission)
+              try {
+                const orgs = ['googlers', 'google'];
+                for (const org of orgs) {
+                  try {
+                    await github.rest.orgs.checkMembershipForUser({ org: org, username: login });
+                    return true;
+                  } catch (e) {
+                    if (e.status !== 404) throw e;
+                  }
+                }
+              } catch (e) {
+                // Gracefully ignore failures here
+              }
+
+              return false;
+            };
+
+            // 2. Fetch all open PRs
+            let prs = [];
+            if (context.eventName === 'pull_request') {
+              const { data: pr } = await github.rest.pulls.get({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                pull_number: context.payload.pull_request.number
+              });
+              prs = [pr];
+            } else {
+              prs = await github.paginate(github.rest.pulls.list, {
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                state: 'open',
+                per_page: 100
+              });
+            }
+
+            for (const pr of prs) {
+              const maintainerPr = await isMaintainer(pr.user.login, pr.author_association);
+              const isBot = pr.user.type === 'Bot' || pr.user.login.endsWith('[bot]');
+              if (maintainerPr || isBot) continue;
+
+              // Helper: Fetch labels and linked issues via GraphQL
+              const prDetailsQuery = `query($owner:String!, $repo:String!, $number:Int!) {
+                repository(owner:$owner, name:$repo) {
+                  pullRequest(number:$number) {
+                    closingIssuesReferences(first: 10) {
+                      nodes {
+                        number
+                        labels(first: 20) {
+                          nodes { name }
+                        }
+                      }
+                    }
+                  }
+                }
+              }`;
+
+              let linkedIssues = [];
+              try {
+                const res = await github.graphql(prDetailsQuery, {
+                  owner: context.repo.owner, repo: context.repo.repo, number: pr.number
+                });
+                linkedIssues = res.repository.pullRequest.closingIssuesReferences.nodes;
+              } catch (e) {
+                core.warning(`GraphQL fetch failed for PR #${pr.number}: ${e.message}`);
+              }
+
+              // Check for mentions in body as fallback (regex)
+              const body = pr.body || '';
+              const mentionRegex = /(?:#|https:\/\/github\.com\/[^\/]+\/[^\/]+\/issues\/)(\d+)/i;
+              const matches = body.match(mentionRegex);
+              if (matches && linkedIssues.length === 0) {
+                const issueNumber = parseInt(matches[1]);
+                try {
+                  const { data: issue } = await github.rest.issues.get({
+                    owner: context.repo.owner,
+                    repo: context.repo.repo,
+                    issue_number: issueNumber
+                  });
+                  linkedIssues = [{ number: issueNumber, labels: { nodes: issue.labels.map(l => ({ name: l.name })) } }];
+                } catch (e) {}
+              }
+
+              // 3. Enforcement Logic
+              const prLabels = pr.labels.map(l => l.name.toLowerCase());
+              const hasHelpWanted = prLabels.includes('help wanted') ||
+                                    linkedIssues.some(issue => issue.labels.nodes.some(l => l.name.toLowerCase() === 'help wanted'));
+
+              const hasMaintainerOnly = prLabels.includes('🔒 maintainer only') ||
+                                        linkedIssues.some(issue => issue.labels.nodes.some(l => l.name.toLowerCase() === '🔒 maintainer only'));
+
+              const hasLinkedIssue = linkedIssues.length > 0;
+
+              // Closure Policy: No help-wanted label = Close after 14 days
+              if (pr.state === 'open' && !hasHelpWanted && !hasMaintainerOnly) {
+                const prCreatedAt = new Date(pr.created_at);
+
+                // We give a 14-day grace period for non-help-wanted PRs to be manually reviewed/labeled by an EM
+                if (prCreatedAt > fourteenDaysAgo) {
+                  core.info(`PR #${pr.number} is new and lacks 'help wanted'. Giving 14-day grace period for EM review.`);
+                  continue;
+                }
+
+                core.info(`PR #${pr.number} is older than 14 days and lacks 'help wanted' association. Closing.`);
+                if (!dryRun) {
+                  await github.rest.issues.createComment({
+                    owner: context.repo.owner,
+                    repo: context.repo.repo,
+                    issue_number: pr.number,
+                    body: "Hi there! Thank you for your interest in contributing to Gemini CLI. \n\nTo ensure we maintain high code quality and focus on our prioritized roadmap, we have updated our contribution policy (see [Discussion #17383](https://github.com/google-gemini/gemini-cli/discussions/17383)). \n\n**We only *guarantee* review and consideration of pull requests for issues that are explicitly labeled as 'help wanted'.** All other community pull requests are subject to closure after 14 days if they do not align with our current focus areas. For this reason, we strongly recommend that contributors only submit pull requests against issues explicitly labeled as **'help-wanted'**. \n\nThis pull request is being closed as it has been open for 14 days without a 'help wanted' designation. We encourage you to find and contribute to existing 'help wanted' issues in our backlog! Thank you for your understanding and for being part of our community!"
+                  });
+                  await github.rest.pulls.update({
+                    owner: context.repo.owner,
+                    repo: context.repo.repo,
+                    pull_number: pr.number,
+                    state: 'closed'
+                  });
+                }
+                continue;
+              }
+
+              // Also check for linked issue even if it has help wanted (redundant but safe)
+              if (pr.state === 'open' && !hasLinkedIssue) {
+                 // Already covered by hasHelpWanted check above, but good for future-proofing
+                 continue;
+              }
+
+              // 4. Staleness Check (Scheduled only)
+              if (pr.state === 'open' && context.eventName !== 'pull_request') {
+                // Skip PRs that were created less than 30 days ago - they cannot be stale yet
+                const prCreatedAt = new Date(pr.created_at);
+                if (prCreatedAt > thirtyDaysAgo) continue;
+
+                let lastActivity = new Date(pr.created_at);
+                try {
+                  const reviews = await github.paginate(github.rest.pulls.listReviews, {
+                    owner: context.repo.owner, repo: context.repo.repo, pull_number: pr.number
+                  });
+                  for (const r of reviews) {
+                    if (await isMaintainer(r.user.login, r.author_association)) {
+                      const d = new Date(r.submitted_at || r.updated_at);
+                      if (d > lastActivity) lastActivity = d;
+                    }
+                  }
+                  const comments = await github.paginate(github.rest.issues.listComments, {
+                    owner: context.repo.owner, repo: context.repo.repo, issue_number: pr.number
+                  });
+                  for (const c of comments) {
+                    if (await isMaintainer(c.user.login, c.author_association)) {
+                      const d = new Date(c.updated_at);
+                      if (d > lastActivity) lastActivity = d;
+                    }
+                  }
+                } catch (e) {}
+
+                if (lastActivity < thirtyDaysAgo) {
+                  const labels = pr.labels.map(l => l.name.toLowerCase());
+                  const isProtected = labels.includes('help wanted') || labels.includes('🔒 maintainer only');
+                  if (isProtected) {
+                    core.info(`PR #${pr.number} is stale but has a protected label. Skipping closure.`);
+                    continue;
+                  }
+
+                  core.info(`PR #${pr.number} is stale (no maintainer activity for 30+ days). Closing.`);
+                  if (!dryRun) {
+                    await github.rest.issues.createComment({
+                      owner: context.repo.owner,
+                      repo: context.repo.repo,
+                      issue_number: pr.number,
+                      body: "Hi there! Thank you for your contribution. To keep our backlog manageable, we are closing pull requests that haven't seen maintainer activity for 30 days. If you're still working on this, please let us know!"
+                    });
+                    await github.rest.pulls.update({
+                      owner: context.repo.owner,
+                      repo: context.repo.repo,
+                      pull_number: pr.number,
+                      state: 'closed'
+                    });
+                  }
+                }
+              }
+            }

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

@@ -19,8 +19,6 @@ jobs:
     steps:
       - name: 'Checkout'
         uses: 'actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5' # ratchet:actions/checkout@v4
-        with:
-          persist-credentials: false
 
       - name: 'Setup Node.js'
         uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020' # ratchet:actions/setup-node@v4
@@ -43,8 +41,6 @@ jobs:
     steps:
       - name: 'Checkout'
         uses: 'actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5' # ratchet:actions/checkout@v4
-        with:
-          persist-credentials: false
 
       - name: 'Setup Node.js'
         uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020' # ratchet:actions/setup-node@v4

.github/workflows/links.yml

@@ -17,8 +17,6 @@ jobs:
     runs-on: 'ubuntu-latest'
     steps:
       - uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8' # ratchet:actions/checkout@v5
-        with:
-          persist-credentials: false
 
       - name: 'Link Checker'
         id: 'lychee'

.github/workflows/memory-nightly.yml

@@ -16,8 +16,6 @@ jobs:
     steps:
       - name: 'Checkout'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8' # ratchet:actions/checkout@v5
-        with:
-          persist-credentials: false
 
       - name: 'Set up Node.js'
         uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020' # ratchet:actions/setup-node@v4

.github/workflows/no-response.yml

@@ -0,0 +1,33 @@
+name: 'No Response'
+
+# Run as a daily cron at 1:45 AM
+on:
+  schedule:
+    - cron: '45 1 * * *'
+  workflow_dispatch:
+
+jobs:
+  no-response:
+    runs-on: 'ubuntu-latest'
+    if: |-
+      ${{ github.repository == 'google-gemini/gemini-cli' }}
+    permissions:
+      issues: 'write'
+      pull-requests: 'write'
+    concurrency:
+      group: '${{ github.workflow }}-no-response'
+      cancel-in-progress: true
+    steps:
+      - uses: 'actions/stale@5bef64f19d7facfb25b37b414482c7164d639639' # ratchet:actions/stale@v9
+        with:
+          repo-token: '${{ secrets.GITHUB_TOKEN }}'
+          days-before-stale: -1
+          days-before-close: 14
+          stale-issue-label: 'status/need-information'
+          close-issue-message: >-
+            This issue was marked as needing more information and has not received a response in 14 days.
+            Closing it for now. If you still face this problem, feel free to reopen with more details. Thank you!
+          stale-pr-label: 'status/need-information'
+          close-pr-message: >-
+            This pull request was marked as needing more information and has had no updates in 14 days.
+            Closing it for now. You are welcome to reopen with the required info. Thanks for contributing!

.github/workflows/perf-nightly.yml

@@ -16,8 +16,6 @@ jobs:
     steps:
       - name: 'Checkout'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8' # ratchet:actions/checkout@v5
-        with:
-          persist-credentials: false
 
       - name: 'Set up Node.js'
         uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020' # ratchet:actions/setup-node@v4

.github/workflows/pr-contribution-guidelines-notifier.yml

@@ -0,0 +1,133 @@
+name: '🏷️ PR Contribution Guidelines Notifier'
+
+on:
+  pull_request:
+    types:
+      - 'opened'
+
+jobs:
+  notify-process-change:
+    runs-on: 'ubuntu-latest'
+    if: |-
+      github.repository == 'google-gemini/gemini-cli' || github.repository == 'google-gemini/maintainers-gemini-cli'
+    permissions:
+      pull-requests: 'write'
+    steps:
+      - name: 'Generate GitHub App Token'
+        id: 'generate_token'
+        env:
+          APP_ID: '${{ secrets.APP_ID }}'
+        if: |-
+          ${{ env.APP_ID != '' }}
+        uses: 'actions/create-github-app-token@fee1f7d63c2ff003460e3d139729b119787bc349' # ratchet:actions/create-github-app-token@v2
+        with:
+          app-id: '${{ secrets.APP_ID }}'
+          private-key: '${{ secrets.PRIVATE_KEY }}'
+
+      - name: 'Check membership and post comment'
+        uses: 'actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea'
+        with:
+          github-token: '${{ steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}'
+          script: |-
+            const org = context.repo.owner;
+            const repo = context.repo.repo;
+            const username = context.payload.pull_request.user.login;
+            const pr_number = context.payload.pull_request.number;
+
+            // 1. Check if the PR author is a maintainer
+            // Check team membership (most reliable for private org members)
+            let isTeamMember = false;
+            const teams = ['gemini-cli-maintainers', 'gemini-cli-askmode-approvers', 'gemini-cli-docs'];
+            for (const team_slug of teams) {
+              try {
+                const members = await github.paginate(github.rest.teams.listMembersInOrg, {
+                  org: org,
+                  team_slug: team_slug
+                });
+                if (members.some(m => m.login.toLowerCase() === username.toLowerCase())) {
+                  isTeamMember = true;
+                  core.info(`${username} is a member of ${team_slug}. No notification needed.`);
+                  break;
+                }
+              } catch (e) {
+                core.warning(`Failed to fetch team members from ${team_slug}: ${e.message}`);
+              }
+            }
+
+            if (isTeamMember) return;
+
+            // Check author_association from webhook payload
+            const authorAssociation = context.payload.pull_request.author_association;
+            const isRepoMaintainer = ['OWNER', 'MEMBER', 'COLLABORATOR'].includes(authorAssociation);
+
+            if (isRepoMaintainer) {
+              core.info(`${username} is a maintainer (author_association: ${authorAssociation}). No notification needed.`);
+              return;
+            }
+
+            // Check if author is a Googler
+            const isGoogler = async (login) => {
+              try {
+                const orgs = ['googlers', 'google'];
+                for (const org of orgs) {
+                  try {
+                    await github.rest.orgs.checkMembershipForUser({
+                      org: org,
+                      username: login
+                    });
+                    return true;
+                  } catch (e) {
+                    if (e.status !== 404) throw e;
+                  }
+                }
+              } catch (e) {
+                core.warning(`Failed to check org membership for ${login}: ${e.message}`);
+              }
+              return false;
+            };
+
+            if (await isGoogler(username)) {
+              core.info(`${username} is a Googler. No notification needed.`);
+              return;
+            }
+
+            // 2. Check if the PR is already associated with an issue
+            const query = `
+              query($owner:String!, $repo:String!, $number:Int!) {
+                repository(owner:$owner, name:$repo) {
+                  pullRequest(number:$number) {
+                    closingIssuesReferences(first: 1) {
+                      totalCount
+                    }
+                  }
+                }
+              }
+            `;
+            const variables = { owner: org, repo: repo, number: pr_number };
+            const result = await github.graphql(query, variables);
+            const issueCount = result.repository.pullRequest.closingIssuesReferences.totalCount;
+
+            if (issueCount > 0) {
+              core.info(`PR #${pr_number} is already associated with an issue. No notification needed.`);
+              return;
+            }
+
+            // 3. Post the notification comment
+            core.info(`${username} is not a maintainer and PR #${pr_number} has no linked issue. Posting notification.`);
+
+            const comment = `
+            Hi @${username}, thank you so much for your contribution to Gemini CLI! We really appreciate the time and effort you've put into this.
+
+            We're making some updates to our contribution process to improve how we track and review changes. Please take a moment to review our recent discussion post: [Improving Our Contribution Process & Introducing New Guidelines](https://github.com/google-gemini/gemini-cli/discussions/16706).
+
+            Key Update: Starting **January 26, 2026**, the Gemini CLI project will require all pull requests to be associated with an existing issue. Any pull requests not linked to an issue by that date will be automatically closed.
+
+            Thank you for your understanding and for being a part of our community!
+            `.trim().replace(/^[ ]+/gm, '');
+
+            await github.rest.issues.createComment({
+              owner: org,
+              repo: repo,
+              issue_number: pr_number,
+              body: comment
+            });

.github/workflows/pr-size-labeler-batch-run.yml

@@ -1,107 +0,0 @@
-name: 'PR Size Labeler (Batch)'
-
-on:
-  workflow_dispatch:
-    inputs:
-      process_all:
-        description: 'Process all PRs (open and closed) or open only'
-        required: true
-        default: 'false'
-        type: 'choice'
-        options:
-          - 'true'
-          - 'false'
-      limit:
-        description: 'Max number of PRs to fetch and check'
-        required: true
-        default: '100'
-        type: 'string'
-
-permissions:
-  pull-requests: 'write'
-
-jobs:
-  batch-label:
-    runs-on: 'ubuntu-latest'
-    steps:
-      - name: 'Batch label PRs'
-        env:
-          GH_TOKEN: '${{ secrets.GITHUB_TOKEN }}'
-          GH_REPO: '${{ github.repository }}'
-        run: |
-          # Determine the state filter
-          STATE="open"
-          if [ "${{ github.event.inputs.process_all }}" = "true" ]; then
-            STATE="all"
-          fi
-
-          LIMIT="${{ github.event.inputs.limit }}"
-          echo "Batch labeling up to $LIMIT $STATE PRs..."
-
-          # 1. Ensure standard premium size labels exist in the repository (self-healing)
-          gh label create "size/XS" --color "7ee081" --description "XS: <10 lines changed" 2>/dev/null || true
-          gh label create "size/S"  --color "a6d49f" --description "S: 10-49 lines changed" 2>/dev/null || true
-          gh label create "size/M"  --color "f7d070" --description "M: 50-249 lines changed" 2>/dev/null || true
-          gh label create "size/L"  --color "f48c06" --description "L: 250-999 lines changed" 2>/dev/null || true
-          gh label create "size/XL" --color "dc2f02" --description "XL: >=1000 lines changed" 2>/dev/null || true
-
-          # 2. Query PR list with all required fields in ONE call to prevent N+1 queries
-          PR_LIST=$(gh pr list --state "$STATE" --limit "$LIMIT" --json number,additions,deletions,labels)
-          if [ -z "$PR_LIST" ] || [ "$PR_LIST" = "[]" ]; then
-            echo "ℹ️ No PRs found matching the criteria."
-            exit 0
-          fi
-
-          # Parse and iterate over PRs
-          UPDATED_COUNT=0
-          SKIPPED_COUNT=0
-
-          echo "$PR_LIST" | jq -c '.[]' | while read -r PR_JSON; do
-            PR_NUMBER=$(echo "$PR_JSON" | jq '.number')
-            ADDITIONS=$(echo "$PR_JSON" | jq '.additions')
-            DELETIONS=$(echo "$PR_JSON" | jq '.deletions')
-            TOTAL=$((ADDITIONS + DELETIONS))
-
-            # Calculate target size
-            if [ $TOTAL -lt 10 ]; then
-              SIZE="size/XS"
-            elif [ $TOTAL -lt 50 ]; then
-              SIZE="size/S"
-            elif [ $TOTAL -lt 250 ]; then
-              SIZE="size/M"
-            elif [ $TOTAL -lt 1000 ]; then
-              SIZE="size/L"
-            else
-              SIZE="size/XL"
-            fi
-
-            # Inspect existing labels to detect discrepancies
-            EXISTING_LABELS=$(echo "$PR_JSON" | jq -r '.labels[].name' 2>/dev/null || echo "")
-
-            LABELS_TO_REMOVE=()
-            for L in size/XS size/S size/M size/L size/XL; do
-              if echo "$EXISTING_LABELS" | grep -Fq "$L" && [ "$L" != "$SIZE" ]; then
-                LABELS_TO_REMOVE+=("--remove-label" "$L")
-              fi
-            done
-
-            LABEL_TO_ADD=()
-            if ! echo "$EXISTING_LABELS" | grep -Fq "$SIZE"; then
-              LABEL_TO_ADD+=("--add-label" "$SIZE")
-            fi
-
-            # Update labels if there's a difference
-            if [ ${#LABELS_TO_REMOVE[@]} -gt 0 ] || [ ${#LABEL_TO_ADD[@]} -gt 0 ]; then
-              echo "🔄 PR #$PR_NUMBER (+$ADDITIONS/-$DELETIONS = $TOTAL lines): updating size to $SIZE"
-              gh pr edit "$PR_NUMBER" "${LABELS_TO_REMOVE[@]}" "${LABEL_TO_ADD[@]}" 2>/dev/null || true
-              UPDATED_COUNT=$((UPDATED_COUNT + 1))
-            else
-              echo "✅ PR #$PR_NUMBER (+$ADDITIONS/-$DELETIONS = $TOTAL lines): already has correct label ($SIZE). Skipping."
-              SKIPPED_COUNT=$((SKIPPED_COUNT + 1))
-            fi
-          done
-
-          echo "============================================"
-          echo "🎉 Batch run completed!"
-          echo "Skipped (already correct): $SKIPPED_COUNT"
-          echo "Updated: $UPDATED_COUNT"

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

@@ -1,120 +0,0 @@
-name: 'PR Size Labeler'
-
-on:
-  pull_request_target:
-    types: ['opened', 'synchronize', 'reopened']
-  workflow_dispatch:
-    inputs:
-      pr_number:
-        description: 'PR number to label manually (for workflow_dispatch)'
-        required: false
-        type: 'string'
-
-permissions:
-  pull-requests: 'write'
-  issues: 'write'
-
-jobs:
-  size-label:
-    runs-on: 'ubuntu-latest'
-    steps:
-      - name: 'Run size labeler'
-        env:
-          GH_TOKEN: '${{ secrets.GITHUB_TOKEN }}'
-          GH_REPO: '${{ github.repository }}'
-        run: |
-          # Determine the target PR number
-          if [ -n "${{ github.event.pull_request.number }}" ]; then
-            PR_NUMBER="${{ github.event.pull_request.number }}"
-          elif [ -n "${{ github.event.inputs.pr_number }}" ]; then
-            PR_NUMBER="${{ github.event.inputs.pr_number }}"
-          else
-            echo "❌ Error: No PR number provided."
-            exit 1
-          fi
-
-          echo "Checking PR #$PR_NUMBER..."
-
-          # 1. Ensure standard premium size labels exist in the repository (self-healing)
-          # size/XS: Light green (#7ee081)
-          # size/S: Yellow-green (#a6d49f)
-          # size/M: Amber/Yellow (#f7d070)
-          # size/L: Orange (#f48c06)
-          # size/XL: Red (#dc2f02)
-          gh label create "size/XS" --color "7ee081" --description "XS: <10 lines changed" 2>/dev/null || true
-          gh label create "size/S"  --color "a6d49f" --description "S: 10-49 lines changed" 2>/dev/null || true
-          gh label create "size/M"  --color "f7d070" --description "M: 50-249 lines changed" 2>/dev/null || true
-          gh label create "size/L"  --color "f48c06" --description "L: 250-999 lines changed" 2>/dev/null || true
-          gh label create "size/XL" --color "dc2f02" --description "XL: >=1000 lines changed" 2>/dev/null || true
-
-          # 2. Fetch PR details in a single efficient API call
-          PR_DATA=$(gh pr view "$PR_NUMBER" --json additions,deletions,changedFiles,labels)
-          if [ -z "$PR_DATA" ]; then
-            echo "❌ Error: Could not fetch PR details."
-            exit 1
-          fi
-
-          ADDITIONS=$(echo "$PR_DATA" | jq '.additions')
-          DELETIONS=$(echo "$PR_DATA" | jq '.deletions')
-          CHANGED_FILES=$(echo "$PR_DATA" | jq '.changedFiles')
-          TOTAL=$((ADDITIONS + DELETIONS))
-
-          echo "PR additions: $ADDITIONS, deletions: $DELETIONS, total changes: $TOTAL, files: $CHANGED_FILES"
-
-          # 3. Calculate new size label
-          if [ $TOTAL -lt 10 ]; then
-            SIZE="size/XS"
-          elif [ $TOTAL -lt 50 ]; then
-            SIZE="size/S"
-          elif [ $TOTAL -lt 250 ]; then
-            SIZE="size/M"
-          elif [ $TOTAL -lt 1000 ]; then
-            SIZE="size/L"
-          else
-            SIZE="size/XL"
-          fi
-
-          # 4. Check existing labels and update only if necessary
-          EXISTING_LABELS=$(echo "$PR_DATA" | jq -r '.labels[].name' 2>/dev/null || echo "")
-
-          LABELS_TO_REMOVE=()
-          for L in size/XS size/S size/M size/L size/XL; do
-            if echo "$EXISTING_LABELS" | grep -Fq "$L" && [ "$L" != "$SIZE" ]; then
-              LABELS_TO_REMOVE+=("--remove-label" "$L")
-            fi
-          done
-
-          LABEL_TO_ADD=()
-          if ! echo "$EXISTING_LABELS" | grep -Fq "$SIZE"; then
-            LABEL_TO_ADD+=("--add-label" "$SIZE")
-          fi
-
-          # Perform a single, highly atomic edit call if changes are needed
-          if [ ${#LABELS_TO_REMOVE[@]} -gt 0 ] || [ ${#LABEL_TO_ADD[@]} -gt 0 ]; then
-            echo "Updating labels: removing ${LABELS_TO_REMOVE[*]}, adding $SIZE"
-            gh pr edit "$PR_NUMBER" "${LABELS_TO_REMOVE[@]}" "${LABEL_TO_ADD[@]}"
-          else
-            echo "✅ PR #$PR_NUMBER already has the correct size label ($SIZE)."
-          fi
-
-          # 5. Premium, anti-spam comment logic (updates previous comment to keep thread clean)
-          COMMENT="📊 PR Size: **$SIZE**
-          - Lines changed: **$TOTAL**
-          - Additions: +$ADDITIONS
-          - Deletions: -$DELETIONS
-          - Files changed: $CHANGED_FILES"
-
-          # Find any existing size labeler comment by the github-actions bot
-          echo "Searching for existing size comment..."
-          COMMENT_ID=$(gh api "repos/${{ github.repository }}/issues/$PR_NUMBER/comments" \
-            --jq '.[] | select(.user.login == "github-actions[bot]" and (.body | startswith("📊 PR Size:"))) | .id' | head -n 1)
-
-          if [ -n "$COMMENT_ID" ]; then
-            echo "Updating existing comment (ID: $COMMENT_ID)..."
-            gh api "repos/${{ github.repository }}/issues/comments/$COMMENT_ID" -X PATCH -f body="$COMMENT" > /dev/null
-          else
-            echo "Creating new comment..."
-            gh pr comment "$PR_NUMBER" --body "$COMMENT" > /dev/null
-          fi
-
-          echo "🎉 PR size labeling completed successfully."

.github/workflows/release-change-tags.yml

@@ -44,7 +44,6 @@ jobs:
         with:
           ref: '${{ github.ref }}'
           fetch-depth: 0
-          persist-credentials: false
 
       - name: 'Setup Node.js'
         uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020'

.github/workflows/release-manual.yml

@@ -46,15 +46,8 @@ on:
         default: 'prod'
 
 jobs:
-  build-mac:
-    if: "github.repository == 'google-gemini/gemini-cli'"
-    uses: './.github/workflows/build-unsigned-mac-binaries.yml'
-    with:
-      ref: '${{ github.event.inputs.ref }}'
-
   release:
     if: "github.repository == 'google-gemini/gemini-cli'"
-    needs: ['build-mac']
     runs-on: 'ubuntu-latest'
     environment: "${{ github.event.inputs.environment || 'prod' }}"
     permissions:
@@ -65,13 +58,11 @@ jobs:
       - name: 'Checkout'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8'
         with:
-          persist-credentials: false
           fetch-depth: 0
 
       - name: 'Checkout Release Code'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8'
         with:
-          persist-credentials: false
           ref: '${{ github.event.inputs.ref }}'
           path: 'release'
           fetch-depth: 0
@@ -92,11 +83,6 @@ jobs:
         working-directory: './release'
         run: 'npm ci'
 
-      - name: 'Download macOS Binaries'
-        uses: './.github/actions/download-mac-binaries'
-        with:
-          path: 'release/dist'
-
       - name: 'Prepare Release Info'
         id: 'release_info'
         working-directory: './release'

.github/workflows/release-nightly.yml

@@ -30,16 +30,9 @@ on:
         default: 'prod'
 
 jobs:
-  build-mac:
-    if: "github.repository == 'google-gemini/gemini-cli'"
-    uses: './.github/workflows/build-unsigned-mac-binaries.yml'
-    with:
-      ref: '${{ github.event.inputs.ref }}'
-
   release:
     if: "github.repository == 'google-gemini/gemini-cli'"
-    needs: ['build-mac']
-    environment: "${{ github.event_name == 'schedule' && 'internal' || github.event.inputs.environment || 'prod' }}"
+    environment: "${{ github.event.inputs.environment || 'prod' }}"
     runs-on: 'ubuntu-latest'
     permissions:
       contents: 'write'
@@ -50,13 +43,11 @@ jobs:
       - name: 'Checkout'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8'
         with:
-          persist-credentials: false
           fetch-depth: 0
 
       - name: 'Checkout Release Code'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8'
         with:
-          persist-credentials: false
           ref: '${{ github.event.inputs.ref }}'
           path: 'release'
           fetch-depth: 0
@@ -71,11 +62,6 @@ jobs:
         working-directory: './release'
         run: 'npm ci'
 
-      - name: 'Download macOS Binaries'
-        uses: './.github/actions/download-mac-binaries'
-        with:
-          path: 'release/dist'
-
       - name: 'Print Inputs'
         shell: 'bash'
         env:
@@ -145,12 +131,12 @@ jobs:
           skip-branch-cleanup: true
           force-skip-tests: "${{ github.event_name != 'schedule' && github.event.inputs.force_skip_tests == 'true' }}"
           gemini_api_key: '${{ secrets.GEMINI_API_KEY }}'
-          npm-registry-publish-url: "${{ vars.NPM_REGISTRY_PUBLISH_URL || 'https://wombat-dressing-room.appspot.com' }}"
-          npm-registry-url: "${{ vars.NPM_REGISTRY_URL || 'https://wombat-dressing-room.appspot.com' }}"
-          npm-registry-scope: "${{ vars.NPM_REGISTRY_SCOPE || '@google' }}"
-          cli-package-name: "${{ vars.CLI_PACKAGE_NAME || '@google/gemini-cli' }}"
-          core-package-name: "${{ vars.CORE_PACKAGE_NAME || '@google/gemini-cli-core' }}"
-          a2a-package-name: "${{ vars.A2A_PACKAGE_NAME || '@google/gemini-cli-a2a-server' }}"
+          npm-registry-publish-url: '${{ vars.NPM_REGISTRY_PUBLISH_URL }}'
+          npm-registry-url: '${{ vars.NPM_REGISTRY_URL }}'
+          npm-registry-scope: '${{ vars.NPM_REGISTRY_SCOPE }}'
+          cli-package-name: '${{ vars.CLI_PACKAGE_NAME }}'
+          core-package-name: '${{ vars.CORE_PACKAGE_NAME }}'
+          a2a-package-name: '${{ vars.A2A_PACKAGE_NAME }}'
 
       - name: 'Create and Merge Pull Request'
         if: "github.event.inputs.environment != 'dev'"

.github/workflows/release-notes.yml

@@ -31,7 +31,6 @@ jobs:
       - name: 'Checkout repository'
         uses: 'actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5' # ratchet:actions/checkout@v4
         with:
-          persist-credentials: false
           # The user-level skills need to be available to the workflow
           fetch-depth: 0
           ref: 'main'
@@ -71,10 +70,7 @@ jobs:
       - name: 'Generate Changelog with Gemini'
         if: "steps.validate_version.outputs.CONTINUE == 'true'"
         uses: 'google-github-actions/run-gemini-cli@a3bf79042542528e91937b3a3a6fbc4967ee3c31' # ratchet:google-github-actions/run-gemini-cli@v0
-        env:
-          GEMINI_CLI_TRUST_WORKSPACE: true
         with:
-          upload_artifacts: 'true'
           gemini_api_key: '${{ secrets.GEMINI_API_KEY }}'
           prompt: |
             Activate the 'docs-changelog' skill.

.github/workflows/release-patch-0-from-comment.yml

@@ -17,7 +17,6 @@ jobs:
       - name: 'Checkout'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8'
         with:
-          persist-credentials: false
           fetch-depth: 1
 
       - name: 'Slash Command Dispatch'

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

@@ -54,7 +54,6 @@ jobs:
         with:
           ref: '${{ github.event.inputs.ref }}'
           fetch-depth: 0
-          persist-credentials: false
 
       - name: 'Setup Node.js'
         uses: 'actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020' # ratchet:actions/setup-node@v4

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

@@ -64,7 +64,6 @@ jobs:
       - name: 'Checkout'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8'
         with:
-          persist-credentials: false
           ref: "${{ github.event.inputs.workflow_ref || 'main' }}"
           fetch-depth: 1
 

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

@@ -53,14 +53,12 @@ jobs:
       - name: 'Checkout'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8'
         with:
-          persist-credentials: false
           fetch-depth: 0
           fetch-tags: true
 
       - name: 'Checkout Release Code'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8'
         with:
-          persist-credentials: false
           ref: '${{ github.event.inputs.release_ref }}'
           path: 'release'
           fetch-depth: 0

.github/workflows/release-promote.yml

@@ -55,7 +55,6 @@ jobs:
       - name: 'Checkout'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8'
         with:
-          persist-credentials: false
           fetch-depth: 0
           fetch-tags: true
 
@@ -172,13 +171,11 @@ jobs:
       - name: 'Checkout Ref'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8'
         with:
-          persist-credentials: false
           ref: '${{ github.event.inputs.ref }}'
 
       - name: 'Checkout correct SHA'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8'
         with:
-          persist-credentials: false
           ref: '${{ matrix.sha }}'
           path: 'release'
           fetch-depth: 0
@@ -200,15 +197,9 @@ jobs:
           gemini_api_key: '${{ secrets.GEMINI_API_KEY }}'
           working-directory: './release'
 
-  build-mac:
-    if: "github.repository == 'google-gemini/gemini-cli'"
-    uses: './.github/workflows/build-unsigned-mac-binaries.yml'
-    with:
-      ref: '${{ github.event.inputs.ref }}'
-
   publish-preview:
     name: 'Publish preview'
-    needs: ['calculate-versions', 'test', 'build-mac']
+    needs: ['calculate-versions', 'test']
     runs-on: 'ubuntu-latest'
     environment: "${{ github.event.inputs.environment || 'prod' }}"
     permissions:
@@ -219,13 +210,11 @@ jobs:
       - name: 'Checkout Ref'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8'
         with:
-          persist-credentials: false
           ref: '${{ github.event.inputs.ref }}'
 
       - name: 'Checkout correct SHA'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8'
         with:
-          persist-credentials: false
           ref: '${{ needs.calculate-versions.outputs.PREVIEW_SHA }}'
           path: 'release'
           fetch-depth: 0
@@ -240,11 +229,6 @@ jobs:
         working-directory: './release'
         run: 'npm ci'
 
-      - name: 'Download macOS Binaries'
-        uses: './.github/actions/download-mac-binaries'
-        with:
-          path: 'release/dist'
-
       - name: 'Publish Release'
         uses: './.github/actions/publish-release'
         with:
@@ -282,7 +266,7 @@ jobs:
 
   publish-stable:
     name: 'Publish stable'
-    needs: ['calculate-versions', 'test', 'publish-preview', 'build-mac']
+    needs: ['calculate-versions', 'test', 'publish-preview']
     runs-on: 'ubuntu-latest'
     environment: "${{ github.event.inputs.environment || 'prod' }}"
     permissions:
@@ -293,13 +277,11 @@ jobs:
       - name: 'Checkout Ref'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8'
         with:
-          persist-credentials: false
           ref: '${{ github.event.inputs.ref }}'
 
       - name: 'Checkout correct SHA'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8'
         with:
-          persist-credentials: false
           ref: '${{ needs.calculate-versions.outputs.STABLE_SHA }}'
           path: 'release'
           fetch-depth: 0
@@ -314,11 +296,6 @@ jobs:
         working-directory: './release'
         run: 'npm ci'
 
-      - name: 'Download macOS Binaries'
-        uses: './.github/actions/download-mac-binaries'
-        with:
-          path: 'release/dist'
-
       - name: 'Publish Release'
         uses: './.github/actions/publish-release'
         with:
@@ -367,7 +344,6 @@ jobs:
       - name: 'Checkout Ref'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8'
         with:
-          persist-credentials: false
           ref: '${{ github.event.inputs.ref }}'
 
       - name: 'Setup Node.js'
@@ -403,7 +379,6 @@ jobs:
           BRANCH_NAME: '${{ steps.release_branch.outputs.BRANCH_NAME }}'
           DRY_RUN: '${{ github.event.inputs.dry_run }}'
           NEEDS_CALCULATE_VERSIONS_OUTPUTS_NEXT_NIGHTLY_VERSION: '${{ needs.calculate-versions.outputs.NEXT_NIGHTLY_VERSION }}'
-          GIT_PUSH_TOKEN: '${{ secrets.GEMINI_CLI_ROBOT_GITHUB_PAT }}'
         run: |-
           git add package.json packages/*/package.json
           if [ -f package-lock.json ]; then
@@ -412,7 +387,7 @@ jobs:
           git commit -m "chore(release): bump version to ${NEEDS_CALCULATE_VERSIONS_OUTPUTS_NEXT_NIGHTLY_VERSION}"
           if [[ "${DRY_RUN}" == "false" ]]; then
             echo "Pushing release branch to remote..."
-            git push "https://x-access-token:${GIT_PUSH_TOKEN}@github.com/${{ github.repository }}.git" "HEAD:${BRANCH_NAME}" --follow-tags
+            git push --set-upstream origin "${BRANCH_NAME}"
           else
             echo "Dry run enabled. Skipping push."
           fi

.github/workflows/release-rollback.yml

@@ -52,7 +52,6 @@ jobs:
       - name: 'Checkout repository'
         uses: 'actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955' # ratchet:actions/checkout@v4
         with:
-          persist-credentials: false
           ref: '${{ github.event.inputs.ref }}'
           fetch-depth: 0
 
@@ -193,7 +192,7 @@ jobs:
         run: |
           echo "ROLLBACK_TAG=$ROLLBACK_TAG_NAME" >> "$GITHUB_OUTPUT"
           git tag "$ROLLBACK_TAG_NAME" "${ORIGIN_HASH}"
-          git push "https://x-access-token:${GITHUB_TOKEN}@github.com/${{ github.repository }}.git" --tags
+          git push origin --tags
 
       - name: 'Verify Rollback Tag Added'
         if: "${{ github.event.inputs.dry-run == 'false' }}"

.github/workflows/release-sandbox.yml

@@ -26,7 +26,6 @@ jobs:
       - name: 'Checkout'
         uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8'
         with:
-          persist-credentials: false
           ref: '${{ github.event.inputs.ref || github.sha }}'
           fetch-depth: 0
       - name: 'Push'

.github/workflows/smoke-test.yml

@@ -32,7 +32,6 @@ jobs:
         with:
           ref: '${{ github.event.inputs.ref || github.sha }}'
           fetch-depth: 0
-          persist-credentials: false
       - name: 'Install Dependencies'
         run: 'npm ci'
       - name: 'Build bundle'

.github/workflows/stale.yml

@@ -0,0 +1,44 @@
+name: 'Mark stale issues and pull requests'
+
+# Run as a daily cron at 1:30 AM
+on:
+  schedule:
+    - cron: '30 1 * * *'
+  workflow_dispatch:
+
+jobs:
+  stale:
+    strategy:
+      fail-fast: false
+      matrix:
+        runner:
+          - 'ubuntu-latest' # GitHub-hosted
+    runs-on: '${{ matrix.runner }}'
+    if: |-
+      ${{ github.repository == 'google-gemini/gemini-cli' }}
+    permissions:
+      issues: 'write'
+      pull-requests: 'write'
+    concurrency:
+      group: '${{ github.workflow }}-stale'
+      cancel-in-progress: true
+    steps:
+      - uses: 'actions/stale@5bef64f19d7facfb25b37b414482c7164d639639' # ratchet:actions/stale@v9
+        with:
+          repo-token: '${{ secrets.GITHUB_TOKEN }}'
+          stale-issue-message: >-
+            This issue has been automatically marked as stale due to 60 days of inactivity.
+            It will be closed in 14 days if no further activity occurs.
+          stale-pr-message: >-
+            This pull request has been automatically marked as stale due to 60 days of inactivity.
+            It will be closed in 14 days if no further activity occurs.
+          close-issue-message: >-
+            This issue has been closed due to 14 additional days of inactivity after being marked as stale.
+            If you believe this is still relevant, feel free to comment or reopen the issue. Thank you!
+          close-pr-message: >-
+            This pull request has been closed due to 14 additional days of inactivity after being marked as stale.
+            If this is still relevant, you are welcome to reopen or leave a comment. Thanks for contributing!
+          days-before-stale: 60
+          days-before-close: 14
+          exempt-issue-labels: 'pinned,security,🔒 maintainer only,help wanted,🗓️ Public Roadmap'
+          exempt-pr-labels: 'pinned,security,🔒 maintainer only,help wanted,🗓️ Public Roadmap'

.github/workflows/test-build-binary.yml

@@ -34,8 +34,6 @@ jobs:
     steps:
       - name: 'Checkout'
         uses: 'actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5' # ratchet:actions/checkout@v4
-        with:
-          persist-credentials: false
 
       - name: 'Optimize Windows Performance'
         if: "matrix.os == 'windows-latest'"
@@ -143,7 +141,6 @@ jobs:
         if: "github.event_name != 'pull_request'"
         env:
           GEMINI_API_KEY: '${{ secrets.GEMINI_API_KEY }}'
-          GEMINI_CLI_TRUST_WORKSPACE: true
         run: |
           echo "Running integration tests with binary..."
           if [[ "${{ matrix.os }}" == 'windows-latest' ]]; then

.github/workflows/verify-release.yml

@@ -44,8 +44,6 @@ jobs:
         shell: 'bash'
         run: 'echo "${{ toJSON(vars) }}"'
       - uses: 'actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8'
-        with:
-          persist-credentials: false
       - name: 'Verify release'
         uses: './.github/actions/verify-release'
         with:

.prettierignore

@@ -22,5 +22,3 @@ Thumbs.db
 .pytest_cache
 **/SKILL.md
 packages/sdk/test-data/*.json
-*.mdx
-packages/vscode-ide-companion/NOTICES.txt

.vscode/launch.json

@@ -43,13 +43,9 @@
     {
       "type": "node",
       "request": "launch",
-      "name": "CLI: Run Current File",
-      "runtimeExecutable": "node",
-      "runtimeArgs": ["--import", "tsx"],
+      "name": "Launch Program",
       "skipFiles": ["<node_internals>/**"],
       "program": "${file}",
-      "cwd": "${workspaceFolder}",
-      "console": "integratedTerminal",
       "outFiles": ["${workspaceFolder}/**/*.js"]
     },
     {

CONTRIBUTING.md

@@ -110,9 +110,7 @@ assign or unassign the issue as requested, provided the conditions are met
 (e.g., an issue must be unassigned to be assigned).
 
 Please note that you can have a maximum of 3 issues assigned to you at any given
-time and that only
-[issues labeled "help wanted"](https://github.com/google-gemini/gemini-cli/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22help%20wanted%22)
-may be self-assigned.
+time.
 
 ### Pull request guidelines
 

Dockerfile

@@ -1,44 +1,3 @@
-# ---- Stage 1: Builder ----
-FROM docker.io/library/node:20-slim AS builder
-
-# Install git (needed by generate-git-commit-info.js script)
-RUN apt-get update && apt-get install -y --no-install-recommends git \
-  && apt-get clean && rm -rf /var/lib/apt/lists/*
-
-WORKDIR /build
-
-# Copy only package.json files first for better layer caching
-# Dependencies only re-install when package files change, not source files
-COPY package*.json ./
-COPY packages/cli/package*.json ./packages/cli/
-COPY packages/core/package*.json ./packages/core/
-COPY packages/vscode-ide-companion/package*.json ./packages/vscode-ide-companion/
-COPY packages/vscode-ide-companion/scripts/ ./packages/vscode-ide-companion/scripts/
-COPY packages/devtools/package*.json ./packages/devtools/
-COPY packages/sdk/package*.json ./packages/sdk/
-COPY packages/test-utils/package*.json ./packages/test-utils/
-COPY packages/a2a-server/package*.json ./packages/a2a-server/
-
-# Use npm ci for consistent, reliable builds (respects package-lock.json)
-RUN HUSKY=0 npm ci --ignore-scripts
-
-# Now copy the rest of the source (after install for better caching)
-COPY packages/ ./packages/
-COPY tsconfig*.json ./
-COPY eslint.config.js ./
-COPY scripts/ ./scripts/
-COPY esbuild.config.js ./
-
-# Pass git commit hash as build arg instead of copying entire .git directory
-ARG GIT_COMMIT=unknown
-ENV GIT_COMMIT=$GIT_COMMIT
-
-# Build and pack artifacts
-RUN HUSKY=0 npm run build && \
-    npm pack -w packages/core --pack-destination packages/core/dist/ && \
-    npm pack -w packages/cli --pack-destination packages/cli/dist/
-
-# ---- Stage 2: Runtime ----
 FROM docker.io/library/node:20-slim
 
 ARG SANDBOX_NAME="gemini-cli-sandbox"
@@ -81,8 +40,8 @@ ENV PATH=$PATH:/usr/local/share/npm-global/bin
 USER node
 
 # install gemini-cli and clean up
-COPY --chown=node:node packages/cli/dist/google-gemini-cli-*.tgz /tmp/gemini-cli.tgz
-COPY --chown=node:node packages/core/dist/google-gemini-cli-core-*.tgz /tmp/gemini-core.tgz
+COPY packages/cli/dist/google-gemini-cli-*.tgz /tmp/gemini-cli.tgz
+COPY packages/core/dist/google-gemini-cli-core-*.tgz /tmp/gemini-core.tgz
 RUN npm install -g /tmp/gemini-core.tgz \
   && npm install -g /tmp/gemini-cli.tgz \
   && node -e "const fs=require('node:fs'); JSON.parse(fs.readFileSync('/usr/local/share/npm-global/lib/node_modules/@google/gemini-cli/package.json','utf8')); JSON.parse(fs.readFileSync('/usr/local/share/npm-global/lib/node_modules/@google/gemini-cli-core/package.json','utf8'));" \
@@ -91,4 +50,4 @@ RUN npm install -g /tmp/gemini-core.tgz \
   && rm -f /tmp/gemini-{cli,core}.tgz
 
 # default entrypoint when none specified
-ENTRYPOINT ["/usr/local/share/npm-global/bin/gemini"]
+CMD ["gemini"]

README.md

@@ -371,8 +371,6 @@ for planned features and priorities.
 
 ## 📖 Resources
 
-- **[Free Course](https://learn.deeplearning.ai/courses/gemini-cli-code-and-create-with-an-open-source-agent/information)** -
-  Learn the basics.
 - **[Official Roadmap](./ROADMAP.md)** - See what's coming next.
 - **[Changelog](https://www.geminicli.com/docs/changelogs)** - See recent
   notable updates.
@@ -395,16 +393,6 @@ for removal instructions.
   [Terms & Privacy](https://www.geminicli.com/docs/resources/tos-privacy)
 - **Security**: [Security Policy](SECURITY.md)
 
-<p align="left">
- <a href="https://www.star-history.com/google-gemini/gemini-cli">
-  <picture>
-   <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/badge?repo=google-gemini/gemini-cli&theme=dark" />
-   <source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/badge?repo=google-gemini/gemini-cli" />
-   <img alt="Star History Rank" src="https://api.star-history.com/badge?repo=google-gemini/gemini-cli" />
-  </picture>
- </a>
-</p>
-
 ---
 
 <p align="center">

docs/admin/enterprise-controls.md

@@ -72,7 +72,7 @@ organization.
 **Supported Fields:**
 
 - `url`: (Required) The full URL of the MCP server endpoint.
-- `type`: (Required) The connection type (for example, `sse` or `http`).
+- `type`: (Required) The connection type (e.g., `sse` or `http`).
 - `trust`: (Optional) If set to `true`, the server is trusted and tool execution
   will not require user approval.
 - `includeTools`: (Optional) An explicit list of tool names to allow. If

docs/changelogs/index.md

@@ -18,140 +18,6 @@ on GitHub.
 | [Preview](preview.md) | Experimental features ready for early feedback. |
 | [Stable](latest.md)   | Stable, recommended for general use.            |
 
-## Announcements: v0.45.0 - 2026-06-03
-
-- **Context Simplification:** Completed major architectural work to simplify the
-  `ContextManager`, improving system robustness and performance
-  ([#27345](https://github.com/google-gemini/gemini-cli/pull/27345) by
-  @joshualitt).
-- **A2A Usage Metadata:** Exposed critical usage metadata in the Agent-to-Agent
-  (A2A) protocol for better resource tracking
-  ([#27288](https://github.com/google-gemini/gemini-cli/pull/27288) by
-  @jvargassanchez-dot).
-- **Reliability Fixes:** Addressed Termux relaunch loops, PTY resize errors, and
-  forced sequential execution for topic updates
-  ([#27110](https://github.com/google-gemini/gemini-cli/pull/27110) by @saymanq,
-  [#27357](https://github.com/google-gemini/gemini-cli/pull/27357) by
-  @jvargassanchez-dot,
-  [#27461](https://github.com/google-gemini/gemini-cli/pull/27461) by
-  @scidomino).
-
-## Announcements: v0.44.0 - 2026-05-27
-
-- **Unified Auto Mode:** Streamlined the automation experience by merging
-  specialized Auto modes into a single, unified mode
-  ([#26714](https://github.com/google-gemini/gemini-cli/pull/26714) by
-  @DavidAPierce).
-- **New Editor Integrations:** Added native support for Sublime Text and Emacs
-  Client ([#21090](https://github.com/google-gemini/gemini-cli/pull/21090) by
-  @alberti42).
-- **Enhanced TUI Testing:** Introduced `agent-tui` and `tui-tester` skills for
-  programmatic testing and automation of terminal UI applications
-  ([#27121](https://github.com/google-gemini/gemini-cli/pull/27121) by
-  @adamfweidman).
-
-## Announcements: v0.43.0 - 2026-05-22
-
-- **Surgical Code Edits:** Steered Gemini models to prefer the `edit` tool for
-  surgical modifications, improving speed and precision
-  ([#26480](https://github.com/google-gemini/gemini-cli/pull/26480) by
-  @aishaneeshah).
-- **Session Export and Import:** Added the ability to export sessions to files
-  and import them via a new flag, facilitating session portability
-  ([#26514](https://github.com/google-gemini/gemini-cli/pull/26514) by
-  @cocosheng-g).
-- **Adaptive Token Estimation:** Introduced an adaptive token calculator for
-  more accurate content size estimation, enhancing context management efficiency
-  ([#26888](https://github.com/google-gemini/gemini-cli/pull/26888) by
-  @joshualitt).
-
-## Announcements: v0.42.0 - 2026-05-12
-
-- **Auto Memory Inbox:** Introduced a new inbox flow for Auto Memory with a
-  canonical-patch contract for seamless skill management
-  ([#26338](https://github.com/google-gemini/gemini-cli/pull/26338) by
-  @SandyTao520).
-- **Gemma 4 by Default:** Enabled Gemma 4 models by default via the Gemini API
-  for all users
-  ([#26307](https://github.com/google-gemini/gemini-cli/pull/26307) by
-  @Abhijit-2592).
-- **Voice Mode Enhancements:** Added wave animations and privacy/compliance UX
-  warnings for the Gemini Live backend
-  ([#26284](https://github.com/google-gemini/gemini-cli/pull/26284) by
-  @devr0306, [#26454](https://github.com/google-gemini/gemini-cli/pull/26454) by
-  @cocosheng-g).
-
-## Announcements: v0.41.0 - 2026-05-05
-
-- **Real-time Voice Mode:** Implemented real-time voice mode with cloud and
-  local backends
-  ([#24174](https://github.com/google-gemini/gemini-cli/pull/24174) by
-  @Abhijit-2592).
-- **Secure Environment Loading:** Enforced workspace trust and secured .env
-  loading in headless mode
-  ([#25814](https://github.com/google-gemini/gemini-cli/pull/25814) by
-  @ehedlund).
-- **Advanced Shell Validation:** Enhanced shell command validation and added
-  core tools allowlist for improved security
-  ([#25720](https://github.com/google-gemini/gemini-cli/pull/25720) by @galz10).
-
-## Announcements: v0.40.0 - 2026-04-28
-
-- **Offline Search and Themes:** Bundled ripgrep for offline search support and
-  added GitHub-style colorblind themes
-  ([#25342](https://github.com/google-gemini/gemini-cli/pull/25342) by
-  @scidomino, [#15504](https://github.com/google-gemini/gemini-cli/pull/15504)
-  by @Z1xus).
-- **Advanced Resource and Memory Management:** Introduced MCP resource tools and
-  transitioned to a prompt-driven, four-tier memory management system
-  ([#25395](https://github.com/google-gemini/gemini-cli/pull/25395) by
-  @ruomengz, [#25716](https://github.com/google-gemini/gemini-cli/pull/25716) by
-  @SandyTao520).
-- **UX and Local Models:** Enabled topic update narrations by default and
-  streamlined Gemma local model setup with `gemini gemma`
-  ([#25586](https://github.com/google-gemini/gemini-cli/pull/25586) by
-  @gundermanc, [#25498](https://github.com/google-gemini/gemini-cli/pull/25498)
-  by @Samee24).
-
-## Announcements: v0.39.0 - 2026-04-23
-
-- **Skill Management:** Added a new `/memory` inbox command for reviewing and
-  patching skills extracted during sessions
-  ([#24544](https://github.com/google-gemini/gemini-cli/pull/24544) by
-  @SandyTao520, [#25148](https://github.com/google-gemini/gemini-cli/pull/25148)
-  by @SandyTao520).
-- **Improved Transparency:** Plan Mode now requires confirmation for skill
-  activation and allows plan inspection
-  ([#24946](https://github.com/google-gemini/gemini-cli/pull/24946),
-  [#25058](https://github.com/google-gemini/gemini-cli/pull/25058) by
-  @ruomengz).
-- **Architecture & Reliability:** Introduced a decoupled `ContextManager`
-  architecture and resolved several critical memory leaks and PTY exhaustion
-  issues ([#24752](https://github.com/google-gemini/gemini-cli/pull/24752) by
-  @joshualitt, [#25079](https://github.com/google-gemini/gemini-cli/pull/25079)
-  by @spencer426).
-
-## Announcements: v0.38.0 - 2026-04-14
-
-- **Chapters Narrative Flow:** Group agent interactions into "Chapters" based on
-  intent and tool usage for better session structure
-  ([#23150](https://github.com/google-gemini/gemini-cli/pull/23150) by
-  @Abhijit-2592,
-  [#24079](https://github.com/google-gemini/gemini-cli/pull/24079) by
-  @gundermanc).
-- **Context Compression Service:** Advanced context management to efficiently
-  distill conversation history
-  ([#24483](https://github.com/google-gemini/gemini-cli/pull/24483) by
-  @joshualitt).
-- **UI Flicker & UX Enhancements:** Solved rendering flicker with "Terminal
-  Buffer" mode and introduced selective topic expansion
-  ([#24512](https://github.com/google-gemini/gemini-cli/pull/24512) by
-  @jacob314, [#24793](https://github.com/google-gemini/gemini-cli/pull/24793) by
-  @Abhijit-2592).
-- **Persistent Policy Approvals:** Implemented context-aware persistent
-  approvals for tool execution
-  ([#23257](https://github.com/google-gemini/gemini-cli/pull/23257) by @jerop).
-
 ## Announcements: v0.37.0 - 2026-04-08
 
 - **Dynamic Sandbox Expansion:** Implemented dynamic sandbox expansion and
@@ -507,7 +373,6 @@ on GitHub.
   headlessly in notebook cells or interactively in the built-in terminal
   ([pic](https://imgur.com/a/G0Tn7vi))
 - 🎉**Gemini CLI Extensions:**
-
   - **Conductor:** Planning++, Gemini works with you to build out a detailed
     plan, pull in extra details as needed, ultimately to give the LLM guardrails
     with artifacts. Measure twice, implement once!
@@ -636,7 +501,6 @@ on GitHub.
   - **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:
 
@@ -676,7 +540,6 @@ on GitHub.
 ![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))
 

docs/changelogs/latest.md

@@ -1,6 +1,6 @@
-# Latest stable release: v0.45.0
+# Latest stable release: v0.37.0
 
-Released: June 03, 2026
+Released: April 08, 2026
 
 For most users, our latest stable release is the recommended release. Install
 the latest stable version with:
@@ -11,55 +11,409 @@ npm install -g @google/gemini-cli
 
 ## Highlights
 
-- **Context Manager Simplification:** Completed a significant refactoring of the
-  context management system to improve reliability and architectural clarity.
-- **A2A Usage Metadata:** Enhanced the Agent-to-Agent protocol to expose usage
-  metadata, enabling more transparent resource monitoring.
-- **Terminal & PTY Robustness:** Resolved several critical issues related to
-  terminal interactions, including Termux relaunch loops and PTY resize errors.
-- **Routing Optimizations:** Updated default auto-routing and bypassed
-  classifiers for specific tool responses to prevent orphaned function errors.
-- **Tool Execution Control:** Forced the `update_topic` tool to execute
-  sequentially, ensuring consistent narrative flow in agent interactions.
+- **Dynamic Sandbox Expansion:** Implemented dynamic sandbox expansion and
+  worktree support for both Linux and Windows, enhancing development flexibility
+  in restricted environments.
+- **Tool-Based Topic Grouping (Chapters):** Introduced "Chapters" to logically
+  group agent interactions based on tool usage and intent, providing a clearer
+  narrative flow in long sessions.
+- **Enhanced Browser Agent:** Added persistent session management, dynamic
+  read-only tool discovery, and sandbox-aware initialization for the browser
+  agent.
+- **Security & Permission Hardening:** Implemented secret visibility lockdown
+  for environment files and integrated integrity controls for Windows
+  sandboxing.
 
 ## What's Changed
 
-- chore(release): bump version to 0.45.0-nightly.20260521.g854f811be by
+- feat(evals): centralize test agents into test-utils for reuse by @Samee24 in
+  [#23616](https://github.com/google-gemini/gemini-cli/pull/23616)
+- revert: chore(config): disable agents by default by @abhipatel12 in
+  [#23672](https://github.com/google-gemini/gemini-cli/pull/23672)
+- fix(plan): update telemetry attribute keys and add timestamp by @Adib234 in
+  [#23685](https://github.com/google-gemini/gemini-cli/pull/23685)
+- fix(core): prevent premature MCP discovery completion by @jackwotherspoon in
+  [#23637](https://github.com/google-gemini/gemini-cli/pull/23637)
+- feat(browser): add maxActionsPerTask for browser agent setting by
+  @cynthialong0-0 in
+  [#23216](https://github.com/google-gemini/gemini-cli/pull/23216)
+- fix(core): improve agent loader error formatting for empty paths by
+  @adamfweidman in
+  [#23690](https://github.com/google-gemini/gemini-cli/pull/23690)
+- fix(cli): only show updating spinner when auto-update is in progress by
+  @scidomino in [#23709](https://github.com/google-gemini/gemini-cli/pull/23709)
+- Refine onboarding metrics to log the duration explicitly and use the tier
+  name. by @yunaseoul in
+  [#23678](https://github.com/google-gemini/gemini-cli/pull/23678)
+- chore(tools): add toJSON to tools and invocations to reduce logging verbosity
+  by @alisa-alisa in
+  [#22899](https://github.com/google-gemini/gemini-cli/pull/22899)
+- fix(cli): stabilize copy mode to prevent flickering and cursor resets by
+  @mattKorwel in
+  [#22584](https://github.com/google-gemini/gemini-cli/pull/22584)
+- fix(test): move flaky ctrl-c-exit test to non-blocking suite by @mattKorwel in
+  [#23732](https://github.com/google-gemini/gemini-cli/pull/23732)
+- feat(skills): add ci skill for automated failure replication by @mattKorwel in
+  [#23720](https://github.com/google-gemini/gemini-cli/pull/23720)
+- feat(sandbox): implement forbiddenPaths for OS-specific sandbox managers by
+  @ehedlund in [#23282](https://github.com/google-gemini/gemini-cli/pull/23282)
+- fix(core): conditionally expose additional_permissions in shell tool by
+  @galz10 in [#23729](https://github.com/google-gemini/gemini-cli/pull/23729)
+- refactor(core): standardize OS-specific sandbox tests and extract linux helper
+  methods by @ehedlund in
+  [#23715](https://github.com/google-gemini/gemini-cli/pull/23715)
+- format recently added script by @scidomino in
+  [#23739](https://github.com/google-gemini/gemini-cli/pull/23739)
+- fix(ui): prevent over-eager slash subcommand completion by @keithguerin in
+  [#20136](https://github.com/google-gemini/gemini-cli/pull/20136)
+- Fix dynamic model routing for gemini 3.1 pro to customtools model by
+  @kevinjwang1 in
+  [#23641](https://github.com/google-gemini/gemini-cli/pull/23641)
+- feat(core): support inline agentCardJson for remote agents by @adamfweidman in
+  [#23743](https://github.com/google-gemini/gemini-cli/pull/23743)
+- fix(cli): skip console log/info in headless mode by @cynthialong0-0 in
+  [#22739](https://github.com/google-gemini/gemini-cli/pull/22739)
+- test(core): install bubblewrap on Linux CI for sandbox integration tests by
+  @ehedlund in [#23583](https://github.com/google-gemini/gemini-cli/pull/23583)
+- docs(reference): split tools table into category sections by @sheikhlimon in
+  [#21516](https://github.com/google-gemini/gemini-cli/pull/21516)
+- fix(browser): detect embedded URLs in query params to prevent allowedDomains
+  bypass by @tony-shi in
+  [#23225](https://github.com/google-gemini/gemini-cli/pull/23225)
+- fix(browser): add proxy bypass constraint to domain restriction system prompt
+  by @tony-shi in
+  [#23229](https://github.com/google-gemini/gemini-cli/pull/23229)
+- fix(policy): relax write_file argsPattern in plan mode to allow paths without
+  session ID by @Adib234 in
+  [#23695](https://github.com/google-gemini/gemini-cli/pull/23695)
+- docs: fix grammar in CONTRIBUTING and numbering in sandbox docs by
+  @splint-disk-8i in
+  [#23448](https://github.com/google-gemini/gemini-cli/pull/23448)
+- fix(acp): allow attachments by adding a permission prompt by @sripasg in
+  [#23680](https://github.com/google-gemini/gemini-cli/pull/23680)
+- fix(core): thread AbortSignal to chat compression requests (#20405) by
+  @SH20RAJ in [#20778](https://github.com/google-gemini/gemini-cli/pull/20778)
+- feat(core): implement Windows sandbox dynamic expansion Phase 1 and 2.1 by
+  @scidomino in [#23691](https://github.com/google-gemini/gemini-cli/pull/23691)
+- Add note about root privileges in sandbox docs by @diodesign in
+  [#23314](https://github.com/google-gemini/gemini-cli/pull/23314)
+- docs(core): document agent_card_json string literal options for remote agents
+  by @adamfweidman in
+  [#23797](https://github.com/google-gemini/gemini-cli/pull/23797)
+- fix(cli): resolve TTY hang on headless environments by unconditionally
+  resuming process.stdin before React Ink launch by @cocosheng-g in
+  [#23673](https://github.com/google-gemini/gemini-cli/pull/23673)
+- fix(ui): cleanup estimated string length hacks in composer by @keithguerin in
+  [#23694](https://github.com/google-gemini/gemini-cli/pull/23694)
+- feat(browser): dynamically discover read-only tools by @cynthialong0-0 in
+  [#23805](https://github.com/google-gemini/gemini-cli/pull/23805)
+- docs: clarify policy requirement for `general.plan.directory` in settings
+  schema by @jerop in
+  [#23784](https://github.com/google-gemini/gemini-cli/pull/23784)
+- Revert "perf(cli): optimize --version startup time (#23671)" by @scidomino in
+  [#23812](https://github.com/google-gemini/gemini-cli/pull/23812)
+- don't silence errors from wombat by @scidomino in
+  [#23822](https://github.com/google-gemini/gemini-cli/pull/23822)
+- fix(ui): prevent escape key from cancelling requests in shell mode by
+  @PrasannaPal21 in
+  [#21245](https://github.com/google-gemini/gemini-cli/pull/21245)
+- Changelog for v0.36.0-preview.0 by @gemini-cli-robot in
+  [#23702](https://github.com/google-gemini/gemini-cli/pull/23702)
+- feat(core,ui): Add experiment-gated support for gemini flash 3.1 lite by
+  @chrstnb in [#23794](https://github.com/google-gemini/gemini-cli/pull/23794)
+- Changelog for v0.36.0-preview.3 by @gemini-cli-robot in
+  [#23827](https://github.com/google-gemini/gemini-cli/pull/23827)
+- new linting check: github-actions-pinning by @alisa-alisa in
+  [#23808](https://github.com/google-gemini/gemini-cli/pull/23808)
+- fix(cli): show helpful guidance when no skills are available by @Niralisj in
+  [#23785](https://github.com/google-gemini/gemini-cli/pull/23785)
+- fix: Chat logs and errors handle tail tool calls correctly by @googlestrobe in
+  [#22460](https://github.com/google-gemini/gemini-cli/pull/22460)
+- Don't try removing a tag from a non-existent release. by @scidomino in
+  [#23830](https://github.com/google-gemini/gemini-cli/pull/23830)
+- fix(cli): allow ask question dialog to take full window height by @jacob314 in
+  [#23693](https://github.com/google-gemini/gemini-cli/pull/23693)
+- fix(core): strip leading underscores from error types in telemetry by
+  @yunaseoul in [#23824](https://github.com/google-gemini/gemini-cli/pull/23824)
+- Changelog for v0.35.0 by @gemini-cli-robot in
+  [#23819](https://github.com/google-gemini/gemini-cli/pull/23819)
+- feat(evals): add reliability harvester and 500/503 retry support by
+  @alisa-alisa in
+  [#23626](https://github.com/google-gemini/gemini-cli/pull/23626)
+- feat(sandbox): dynamic Linux sandbox expansion and worktree support by @galz10
+  in [#23692](https://github.com/google-gemini/gemini-cli/pull/23692)
+- Merge examples of use into quickstart documentation by @diodesign in
+  [#23319](https://github.com/google-gemini/gemini-cli/pull/23319)
+- fix(cli): prioritize primary name matches in slash command search by @sehoon38
+  in [#23850](https://github.com/google-gemini/gemini-cli/pull/23850)
+- Changelog for v0.35.1 by @gemini-cli-robot in
+  [#23840](https://github.com/google-gemini/gemini-cli/pull/23840)
+- fix(browser): keep input blocker active across navigations by @kunal-10-cloud
+  in [#22562](https://github.com/google-gemini/gemini-cli/pull/22562)
+- feat(core): new skill to look for duplicated code while reviewing PRs by
+  @devr0306 in [#23704](https://github.com/google-gemini/gemini-cli/pull/23704)
+- fix(core): replace hardcoded non-interactive ASK_USER denial with explicit
+  policy rules by @ruomengz in
+  [#23668](https://github.com/google-gemini/gemini-cli/pull/23668)
+- fix(plan): after exiting plan mode switches model to a flash model by @Adib234
+  in [#23885](https://github.com/google-gemini/gemini-cli/pull/23885)
+- feat(gcp): add development worker infrastructure by @mattKorwel in
+  [#23814](https://github.com/google-gemini/gemini-cli/pull/23814)
+- fix(a2a-server): A2A server should execute ask policies in interactive mode by
+  @kschaab in [#23831](https://github.com/google-gemini/gemini-cli/pull/23831)
+- feat(core): define TrajectoryProvider interface by @sehoon38 in
+  [#23050](https://github.com/google-gemini/gemini-cli/pull/23050)
+- Docs: Update quotas and pricing by @jkcinouye in
+  [#23835](https://github.com/google-gemini/gemini-cli/pull/23835)
+- fix(core): allow disabling environment variable redaction by @galz10 in
+  [#23927](https://github.com/google-gemini/gemini-cli/pull/23927)
+- feat(cli): enable notifications cross-platform via terminal bell fallback by
+  @genneth in [#21618](https://github.com/google-gemini/gemini-cli/pull/21618)
+- feat(sandbox): implement secret visibility lockdown for env files by
+  @DavidAPierce in
+  [#23712](https://github.com/google-gemini/gemini-cli/pull/23712)
+- fix(core): remove shell outputChunks buffer caching to prevent memory bloat
+  and sanitize prompt input by @spencer426 in
+  [#23751](https://github.com/google-gemini/gemini-cli/pull/23751)
+- feat(core): implement persistent browser session management by @kunal-10-cloud
+  in [#21306](https://github.com/google-gemini/gemini-cli/pull/21306)
+- refactor(core): delegate sandbox denial parsing to SandboxManager by
+  @scidomino in [#23928](https://github.com/google-gemini/gemini-cli/pull/23928)
+- dep(update) Update Ink version to 6.5.0 by @jacob314 in
+  [#23843](https://github.com/google-gemini/gemini-cli/pull/23843)
+- Docs: Update 'docs-writer' skill for relative links by @jkcinouye in
+  [#21463](https://github.com/google-gemini/gemini-cli/pull/21463)
+- Changelog for v0.36.0-preview.4 by @gemini-cli-robot in
+  [#23935](https://github.com/google-gemini/gemini-cli/pull/23935)
+- fix(acp): Update allow approval policy flow for ACP clients to fix config
+  persistence and compatible with TUI by @sripasg in
+  [#23818](https://github.com/google-gemini/gemini-cli/pull/23818)
+- Changelog for v0.35.2 by @gemini-cli-robot in
+  [#23960](https://github.com/google-gemini/gemini-cli/pull/23960)
+- ACP integration documents by @g-samroberts in
+  [#22254](https://github.com/google-gemini/gemini-cli/pull/22254)
+- fix(core): explicitly set error names to avoid bundling renaming issues by
+  @yunaseoul in [#23913](https://github.com/google-gemini/gemini-cli/pull/23913)
+- feat(core): subagent isolation and cleanup hardening by @abhipatel12 in
+  [#23903](https://github.com/google-gemini/gemini-cli/pull/23903)
+- disable extension-reload test by @scidomino in
+  [#24018](https://github.com/google-gemini/gemini-cli/pull/24018)
+- feat(core): add forbiddenPaths to GlobalSandboxOptions and refactor
+  createSandboxManager by @ehedlund in
+  [#23936](https://github.com/google-gemini/gemini-cli/pull/23936)
+- refactor(core): improve ignore resolution and fix directory-matching bug by
+  @ehedlund in [#23816](https://github.com/google-gemini/gemini-cli/pull/23816)
+- revert(core): support custom base URL via env vars by @spencer426 in
+  [#23976](https://github.com/google-gemini/gemini-cli/pull/23976)
+- Increase memory limited for eslint. by @jacob314 in
+  [#24022](https://github.com/google-gemini/gemini-cli/pull/24022)
+- fix(acp): prevent crash on empty response in ACP mode by @sripasg in
+  [#23952](https://github.com/google-gemini/gemini-cli/pull/23952)
+- feat(core): Land `AgentHistoryProvider`. by @joshualitt in
+  [#23978](https://github.com/google-gemini/gemini-cli/pull/23978)
+- fix(core): switch to subshells for shell tool wrapping to fix heredocs and
+  edge cases by @abhipatel12 in
+  [#24024](https://github.com/google-gemini/gemini-cli/pull/24024)
+- Debug command. by @jacob314 in
+  [#23851](https://github.com/google-gemini/gemini-cli/pull/23851)
+- Changelog for v0.36.0-preview.5 by @gemini-cli-robot in
+  [#24046](https://github.com/google-gemini/gemini-cli/pull/24046)
+- Fix test flakes by globally mocking ink-spinner by @jacob314 in
+  [#24044](https://github.com/google-gemini/gemini-cli/pull/24044)
+- Enable network access in sandbox configuration by @galz10 in
+  [#24055](https://github.com/google-gemini/gemini-cli/pull/24055)
+- feat(context): add configurable memoryBoundaryMarkers setting by @SandyTao520
+  in [#24020](https://github.com/google-gemini/gemini-cli/pull/24020)
+- feat(core): implement windows sandbox expansion and denial detection by
+  @scidomino in [#24027](https://github.com/google-gemini/gemini-cli/pull/24027)
+- fix(core): resolve ACP Operation Aborted Errors in grep_search by @ivanporty
+  in [#23821](https://github.com/google-gemini/gemini-cli/pull/23821)
+- fix(hooks): prevent SessionEnd from firing twice in non-interactive mode by
+  @krishdef7 in [#22139](https://github.com/google-gemini/gemini-cli/pull/22139)
+- Re-word intro to Gemini 3 page. by @g-samroberts in
+  [#24069](https://github.com/google-gemini/gemini-cli/pull/24069)
+- fix(cli): resolve layout contention and flashing loop in StatusRow by
+  @keithguerin in
+  [#24065](https://github.com/google-gemini/gemini-cli/pull/24065)
+- fix(sandbox): implement Windows Mandatory Integrity Control for GeminiSandbox
+  by @galz10 in [#24057](https://github.com/google-gemini/gemini-cli/pull/24057)
+- feat(core): implement tool-based topic grouping (Chapters) by @Abhijit-2592 in
+  [#23150](https://github.com/google-gemini/gemini-cli/pull/23150)
+- feat(cli): support 'tab to queue' for messages while generating by @gundermanc
+  in [#24052](https://github.com/google-gemini/gemini-cli/pull/24052)
+- feat(core): agnostic background task UI with CompletionBehavior by
+  @adamfweidman in
+  [#22740](https://github.com/google-gemini/gemini-cli/pull/22740)
+- UX for topic narration tool by @gundermanc in
+  [#24079](https://github.com/google-gemini/gemini-cli/pull/24079)
+- fix: shellcheck warnings in scripts by @scidomino in
+  [#24035](https://github.com/google-gemini/gemini-cli/pull/24035)
+- test(evals): add comprehensive subagent delegation evaluations by @abhipatel12
+  in [#24132](https://github.com/google-gemini/gemini-cli/pull/24132)
+- fix(a2a-server): prioritize ADC before evaluating headless constraints for
+  auth initialization by @spencer426 in
+  [#23614](https://github.com/google-gemini/gemini-cli/pull/23614)
+- Text can be added after /plan command by @rambleraptor in
+  [#22833](https://github.com/google-gemini/gemini-cli/pull/22833)
+- fix(cli): resolve missing F12 logs via global console store by @scidomino in
+  [#24235](https://github.com/google-gemini/gemini-cli/pull/24235)
+- fix broken tests by @scidomino in
+  [#24279](https://github.com/google-gemini/gemini-cli/pull/24279)
+- fix(evals): add update_topic behavioral eval by @gundermanc in
+  [#24223](https://github.com/google-gemini/gemini-cli/pull/24223)
+- feat(core): Unified Context Management and Tool Distillation. by @joshualitt
+  in [#24157](https://github.com/google-gemini/gemini-cli/pull/24157)
+- Default enable narration for the team. by @gundermanc in
+  [#24224](https://github.com/google-gemini/gemini-cli/pull/24224)
+- fix(core): ensure default agents provide tools and use model-specific schemas
+  by @abhipatel12 in
+  [#24268](https://github.com/google-gemini/gemini-cli/pull/24268)
+- feat(cli): show Flash Lite Preview model regardless of user tier by @sehoon38
+  in [#23904](https://github.com/google-gemini/gemini-cli/pull/23904)
+- feat(cli): implement compact tool output by @jwhelangoog in
+  [#20974](https://github.com/google-gemini/gemini-cli/pull/20974)
+- Add security settings for tool sandboxing by @galz10 in
+  [#23923](https://github.com/google-gemini/gemini-cli/pull/23923)
+- chore(test-utils): switch integration tests to use PREVIEW_GEMINI_MODEL by
+  @sehoon38 in [#24276](https://github.com/google-gemini/gemini-cli/pull/24276)
+- feat(core): enable topic update narration for legacy models by @Abhijit-2592
+  in [#24241](https://github.com/google-gemini/gemini-cli/pull/24241)
+- feat(core): add project-level memory scope to save_memory tool by @SandyTao520
+  in [#24161](https://github.com/google-gemini/gemini-cli/pull/24161)
+- test(integration): fix plan mode write denial test false positive by @sehoon38
+  in [#24299](https://github.com/google-gemini/gemini-cli/pull/24299)
+- feat(plan): support `Plan` mode in untrusted folders by @Adib234 in
+  [#17586](https://github.com/google-gemini/gemini-cli/pull/17586)
+- fix(core): enable mid-stream retries for all models and re-enable compression
+  test by @sehoon38 in
+  [#24302](https://github.com/google-gemini/gemini-cli/pull/24302)
+- Changelog for v0.36.0-preview.6 by @gemini-cli-robot in
+  [#24082](https://github.com/google-gemini/gemini-cli/pull/24082)
+- Changelog for v0.35.3 by @gemini-cli-robot in
+  [#24083](https://github.com/google-gemini/gemini-cli/pull/24083)
+- feat(cli): add auth info to footer by @sehoon38 in
+  [#24042](https://github.com/google-gemini/gemini-cli/pull/24042)
+- fix(browser): reset action counter for each agent session and let it ignore
+  internal actions by @cynthialong0-0 in
+  [#24228](https://github.com/google-gemini/gemini-cli/pull/24228)
+- feat(plan): promote planning feature to stable by @ruomengz in
+  [#24282](https://github.com/google-gemini/gemini-cli/pull/24282)
+- fix(browser): terminate subagent immediately on domain restriction violations
+  by @gsquared94 in
+  [#24313](https://github.com/google-gemini/gemini-cli/pull/24313)
+- feat(cli): add UI to update extensions by @ruomengz in
+  [#23682](https://github.com/google-gemini/gemini-cli/pull/23682)
+- Fix(browser): terminate immediately for "browser is already running" error by
+  @cynthialong0-0 in
+  [#24233](https://github.com/google-gemini/gemini-cli/pull/24233)
+- docs: Add 'plan' option to approval mode in CLI reference by @YifanRuan in
+  [#24134](https://github.com/google-gemini/gemini-cli/pull/24134)
+- fix(core): batch macOS seatbelt rules into a profile file to prevent ARG_MAX
+  errors by @ehedlund in
+  [#24255](https://github.com/google-gemini/gemini-cli/pull/24255)
+- fix(core): fix race condition between browser agent and main closing process
+  by @cynthialong0-0 in
+  [#24340](https://github.com/google-gemini/gemini-cli/pull/24340)
+- perf(build): optimize build scripts for parallel execution and remove
+  redundant checks by @sehoon38 in
+  [#24307](https://github.com/google-gemini/gemini-cli/pull/24307)
+- ci: install bubblewrap on Linux for release workflows by @ehedlund in
+  [#24347](https://github.com/google-gemini/gemini-cli/pull/24347)
+- chore(release): allow bundling for all builds, including stable by @sehoon38
+  in [#24305](https://github.com/google-gemini/gemini-cli/pull/24305)
+- Revert "Add security settings for tool sandboxing" by @jerop in
+  [#24357](https://github.com/google-gemini/gemini-cli/pull/24357)
+- docs: update subagents docs to not be experimental by @abhipatel12 in
+  [#24343](https://github.com/google-gemini/gemini-cli/pull/24343)
+- fix(core): implement **read and **write commands in sandbox managers by
+  @galz10 in [#24283](https://github.com/google-gemini/gemini-cli/pull/24283)
+- don't try to remove tags in dry run by @scidomino in
+  [#24356](https://github.com/google-gemini/gemini-cli/pull/24356)
+- fix(config): disable JIT context loading by default by @SandyTao520 in
+  [#24364](https://github.com/google-gemini/gemini-cli/pull/24364)
+- test(sandbox): add integration test for dynamic permission expansion by
+  @galz10 in [#24359](https://github.com/google-gemini/gemini-cli/pull/24359)
+- docs(policy): remove unsupported mcpName wildcard edge case by @abhipatel12 in
+  [#24133](https://github.com/google-gemini/gemini-cli/pull/24133)
+- docs: fix broken GEMINI.md link in CONTRIBUTING.md by @Panchal-Tirth in
+  [#24182](https://github.com/google-gemini/gemini-cli/pull/24182)
+- feat(core): infrastructure for event-driven subagent history by @abhipatel12
+  in [#23914](https://github.com/google-gemini/gemini-cli/pull/23914)
+- fix(core): resolve Plan Mode deadlock during plan file creation due to sandbox
+  restrictions by @DavidAPierce in
+  [#24047](https://github.com/google-gemini/gemini-cli/pull/24047)
+- fix(core): fix browser agent UX issues and improve E2E test reliability by
+  @gsquared94 in
+  [#24312](https://github.com/google-gemini/gemini-cli/pull/24312)
+- fix(ui): wrap topic and intent fields in TopicMessage by @jwhelangoog in
+  [#24386](https://github.com/google-gemini/gemini-cli/pull/24386)
+- refactor(core): Centralize context management logic into src/context by
+  @joshualitt in
+  [#24380](https://github.com/google-gemini/gemini-cli/pull/24380)
+- fix(core): pin AuthType.GATEWAY to use Gemini 3.1 Pro/Flash Lite by default by
+  @sripasg in [#24375](https://github.com/google-gemini/gemini-cli/pull/24375)
+- feat(ui): add Tokyo Night theme by @danrneal in
+  [#24054](https://github.com/google-gemini/gemini-cli/pull/24054)
+- fix(cli): refactor test config loading and mock debugLogger in test-setup by
+  @mattKorwel in
+  [#24389](https://github.com/google-gemini/gemini-cli/pull/24389)
+- Set memoryManager to false in settings.json by @mattKorwel in
+  [#24393](https://github.com/google-gemini/gemini-cli/pull/24393)
+- ink 6.6.3 by @jacob314 in
+  [#24372](https://github.com/google-gemini/gemini-cli/pull/24372)
+- fix(core): resolve subagent chat recording gaps and directory inheritance by
+  @abhipatel12 in
+  [#24368](https://github.com/google-gemini/gemini-cli/pull/24368)
+- fix(cli): cap shell output at 10 MB to prevent RangeError crash by @ProthamD
+  in [#24168](https://github.com/google-gemini/gemini-cli/pull/24168)
+- feat(plan): conditionally add enter/exit plan mode tools based on current mode
+  by @ruomengz in
+  [#24378](https://github.com/google-gemini/gemini-cli/pull/24378)
+- feat(core): prioritize discussion before formal plan approval by @jerop in
+  [#24423](https://github.com/google-gemini/gemini-cli/pull/24423)
+- fix(ui): add accelerated scrolling on alternate buffer mode by @devr0306 in
+  [#23940](https://github.com/google-gemini/gemini-cli/pull/23940)
+- feat(core): populate sandbox forbidden paths with project ignore file contents
+  by @ehedlund in
+  [#24038](https://github.com/google-gemini/gemini-cli/pull/24038)
+- fix(core): ensure blue border overlay and input blocker to act correctly
+  depending on browser agent activities by @cynthialong0-0 in
+  [#24385](https://github.com/google-gemini/gemini-cli/pull/24385)
+- fix(ui): removed additional vertical padding for tables by @devr0306 in
+  [#24381](https://github.com/google-gemini/gemini-cli/pull/24381)
+- fix(build): upload full bundle directory archive to GitHub releases by
+  @sehoon38 in [#24403](https://github.com/google-gemini/gemini-cli/pull/24403)
+- fix(build): wire bundle:browser-mcp into bundle pipeline by @gsquared94 in
+  [#24424](https://github.com/google-gemini/gemini-cli/pull/24424)
+- feat(browser): add sandbox-aware browser agent initialization by @gsquared94
+  in [#24419](https://github.com/google-gemini/gemini-cli/pull/24419)
+- feat(core): enhance tracker task schemas for detailed titles and descriptions
+  by @anj-s in [#23902](https://github.com/google-gemini/gemini-cli/pull/23902)
+- refactor(core): Unified context management settings schema by @joshualitt in
+  [#24391](https://github.com/google-gemini/gemini-cli/pull/24391)
+- feat(core): update browser agent prompt to check open pages first when
+  bringing up by @cynthialong0-0 in
+  [#24431](https://github.com/google-gemini/gemini-cli/pull/24431)
+- fix(acp) refactor(core,cli): centralize model discovery logic in
+  ModelConfigService by @sripasg in
+  [#24392](https://github.com/google-gemini/gemini-cli/pull/24392)
+- Changelog for v0.36.0-preview.7 by @gemini-cli-robot in
+  [#24346](https://github.com/google-gemini/gemini-cli/pull/24346)
+- fix: update task tracker storage location in system prompt by @anj-s in
+  [#24034](https://github.com/google-gemini/gemini-cli/pull/24034)
+- feat(browser): supersede stale snapshots to reclaim context-window tokens by
+  @gsquared94 in
+  [#24440](https://github.com/google-gemini/gemini-cli/pull/24440)
+- docs(core): add subagent tool isolation draft doc by @akh64bit in
+  [#23275](https://github.com/google-gemini/gemini-cli/pull/23275)
+- fix(patch): cherry-pick 64c928f to release/v0.37.0-preview.0-pr-23257 to patch
+  version v0.37.0-preview.0 and create version 0.37.0-preview.1 by
   @gemini-cli-robot in
-  [#27362](https://github.com/google-gemini/gemini-cli/pull/27362)
-- fix(cli): prevent Termux relaunch and resize remount loops by @saymanq in
-  [#27110](https://github.com/google-gemini/gemini-cli/pull/27110)
-- Feat/a2a expose usage metadata by @jvargassanchez-dot in
-  [#27288](https://github.com/google-gemini/gemini-cli/pull/27288)
-- feat(context): Complete simplification work. by @joshualitt in
-  [#27345](https://github.com/google-gemini/gemini-cli/pull/27345)
-- fix(core): force update_topic tool to execute sequentially by
-  @jvargassanchez-dot in
-  [#27357](https://github.com/google-gemini/gemini-cli/pull/27357)
-- Changelog for v0.44.0-preview.0 by @gemini-cli-robot in
-  [#27360](https://github.com/google-gemini/gemini-cli/pull/27360)
-- Changelog for v0.43.0 by @gemini-cli-robot in
-  [#27361](https://github.com/google-gemini/gemini-cli/pull/27361)
-- Revert "fix(core): prevent SIGHUP kills in PTY environments" by @bbiggs in
-  [#27401](https://github.com/google-gemini/gemini-cli/pull/27401)
-- fix(cli): filter internal session context from history during resumption by
-  @rmedranollamas in
-  [#27391](https://github.com/google-gemini/gemini-cli/pull/27391)
-- Update default auto routing by @DavidAPierce in
-  [#27071](https://github.com/google-gemini/gemini-cli/pull/27071)
-- fix(core): bypass routing classifiers to prevent orphaned function response
-  errors by @danielweis in
-  [#27389](https://github.com/google-gemini/gemini-cli/pull/27389)
-- fix(core): suppress PTY resize EBADF errors by @scidomino in
-  [#27461](https://github.com/google-gemini/gemini-cli/pull/27461)
-- fix(core): prevent blacklist bypass in mcp list by @ompatel-aiml in
-  [#27377](https://github.com/google-gemini/gemini-cli/pull/27377)
-- fix(cli): ignore unmapped vim normal keys by @MukundaKatta in
-  [#27102](https://github.com/google-gemini/gemini-cli/pull/27102)
-- fix(patch): cherry-pick bd53951 to release/v0.45.0-preview.0-pr-27496 to patch
-  version v0.45.0-preview.0 and create version 0.45.0-preview.1 by
+  [#24561](https://github.com/google-gemini/gemini-cli/pull/24561)
+- fix(patch): cherry-pick cb7f7d6 to release/v0.37.0-preview.1-pr-24342 to patch
+  version v0.37.0-preview.1 and create version 0.37.0-preview.2 by
   @gemini-cli-robot in
-  [#27535](https://github.com/google-gemini/gemini-cli/pull/27535)
+  [#24842](https://github.com/google-gemini/gemini-cli/pull/24842)
 
 **Full Changelog**:
-https://github.com/google-gemini/gemini-cli/compare/v0.44.1...v0.45.0
+https://github.com/google-gemini/gemini-cli/compare/v0.36.0...v0.37.0

docs/changelogs/preview.md

@@ -1,6 +1,6 @@
-# Preview release: v0.48.0-preview.0
+# Preview release: v0.38.0-preview.0
 
-Released: June 17, 2026
+Released: April 08, 2026
 
 Our preview release includes the latest, new, and experimental features. This
 release may not be as stable as our [latest weekly release](latest.md).
@@ -13,58 +13,256 @@ npm install -g @google/gemini-cli@preview
 
 ## Highlights
 
-- **GDC Service Identity Support**: Added support for GDC air-gapped Service
-  Identity after a major auth library update.
-- **Standardised Tool Outputs**: Standardised tool output formatting to ensure
-  consistency and readability across different CLI commands.
-- **Static Evaluation Analyzer**: Introduced a new static evaluation source
-  analyzer to improve development and testing.
-- **Vulnerability Prevention**: Hardened CLI security by preventing path
-  traversal vulnerabilities during the installation of Skills.
-- **Configuration & Error Hardening**: Migrated the `coreTools` configuration
-  setting to `tools.core` and ensured zero-quota limits fail fast to prevent
-  infinite retry loops.
+- **Context Management:** Introduced a Context Compression Service to optimize
+  context window usage and landed a background memory service for skill
+  extraction.
+- **Enhanced Security:** Implemented context-aware persistent policy approvals
+  for smarter tool permissions and enabled `web_fetch` in plan mode with user
+  confirmation.
+- **Workflow Monitoring:** Added background process monitoring and inspection
+  tools for better visibility into long-running tasks.
+- **UI/UX Refinements:** Enhanced the tool confirmation UI, selection layout,
+  and added support for selective topic expansion and click-to-expand.
+- **Core Stability:** Improved sandbox reliability on Linux and Windows,
+  resolved shebang compatibility issues, and fixed various crashes in the CLI
+  and core services.
 
 ## What's Changed
 
-- chore(release): bump version to 0.48.0-nightly.20260609.g3a13b8eeb by
-  @gemini-cli-robot in
-  [#27779](https://github.com/google-gemini/gemini-cli/pull/27779)
-- ci(dependabot): enable cooldown period for npm packages by @ruomengz in
-  [#27743](https://github.com/google-gemini/gemini-cli/pull/27743)
-- refactor(core): standardize tool output formatting by @galz10 in
-  [#27772](https://github.com/google-gemini/gemini-cli/pull/27772)
-- ci: update workflow logging and policy configurations by @galz10 in
-  [#27853](https://github.com/google-gemini/gemini-cli/pull/27853)
-- fix(core): Ensure zero-quota limits fail fast to prevent retry loop hang by
-  @luisfelipe-alt in
-  [#27698](https://github.com/google-gemini/gemini-cli/pull/27698)
-- fix(core): handle multi-line escaped quotes in stripShellWrapper by
-  @sanchezcoraspe in
-  [#27467](https://github.com/google-gemini/gemini-cli/pull/27467)
-- fix(cli): prevent path traversal vulnerabilities during skill install… by
-  @ompatel-aiml in
-  [#27767](https://github.com/google-gemini/gemini-cli/pull/27767)
-- Fix/pending tools and trust overrides by @jvargassanchez-dot in
-  [#27854](https://github.com/google-gemini/gemini-cli/pull/27854)
-- ci: use internal environment for scheduled nightly releases (#27865) by
-  @rmedranollamas in
-  [#27939](https://github.com/google-gemini/gemini-cli/pull/27939)
-- feat(core): Support GDC air-gapped Service Identity after auth library update
-  by @sidhantgoyal-droid in
-  [#27956](https://github.com/google-gemini/gemini-cli/pull/27956)
-- fix(cli): handle tmux false positive background detection by @amelidev in
-  [#27572](https://github.com/google-gemini/gemini-cli/pull/27572)
-- Add static eval source analyzer by @ved015 in
-  [#27631](https://github.com/google-gemini/gemini-cli/pull/27631)
-- fix(config): migrate coreTools setting to tools.core by @galz10 in
-  [#27947](https://github.com/google-gemini/gemini-cli/pull/27947)
-- fix(core-tools): resolve defensive path resolution for at-reference files by
-  @luisfelipe-alt in
-  [#27943](https://github.com/google-gemini/gemini-cli/pull/27943)
-- Revert "fix(core-tools): resolve defensive path resolution for at-reference
-  files" by @galz10 in
-  [#27992](https://github.com/google-gemini/gemini-cli/pull/27992)
+- fix(cli): refresh slash command list after /skills reload by @NTaylorMullen in
+  [#24454](https://github.com/google-gemini/gemini-cli/pull/24454)
+- Update README.md for links. by @g-samroberts in
+  [#22759](https://github.com/google-gemini/gemini-cli/pull/22759)
+- fix(core): ensure complete_task tool calls are recorded in chat history by
+  @abhipatel12 in
+  [#24437](https://github.com/google-gemini/gemini-cli/pull/24437)
+- feat(policy): explicitly allow web_fetch in plan mode with ask_user by
+  @Adib234 in [#24456](https://github.com/google-gemini/gemini-cli/pull/24456)
+- fix(core): refactor linux sandbox to fix ARG_MAX crashes by @ehedlund in
+  [#24286](https://github.com/google-gemini/gemini-cli/pull/24286)
+- feat(config): add experimental.adk.agentSessionNoninteractiveEnabled setting
+  by @adamfweidman in
+  [#24439](https://github.com/google-gemini/gemini-cli/pull/24439)
+- Changelog for v0.36.0-preview.8 by @gemini-cli-robot in
+  [#24453](https://github.com/google-gemini/gemini-cli/pull/24453)
+- feat(cli): change default loadingPhrases to 'off' to hide tips by @keithguerin
+  in [#24342](https://github.com/google-gemini/gemini-cli/pull/24342)
+- fix(cli): ensure agent stops when all declinable tools are cancelled by
+  @NTaylorMullen in
+  [#24479](https://github.com/google-gemini/gemini-cli/pull/24479)
+- fix(core): enhance sandbox usability and fix build error by @galz10 in
+  [#24460](https://github.com/google-gemini/gemini-cli/pull/24460)
+- Terminal Serializer Optimization by @jacob314 in
+  [#24485](https://github.com/google-gemini/gemini-cli/pull/24485)
+- Auto configure memory. by @jacob314 in
+  [#24474](https://github.com/google-gemini/gemini-cli/pull/24474)
+- Unused error variables in catch block are not allowed by @alisa-alisa in
+  [#24487](https://github.com/google-gemini/gemini-cli/pull/24487)
+- feat(core): add background memory service for skill extraction by @SandyTao520
+  in [#24274](https://github.com/google-gemini/gemini-cli/pull/24274)
+- feat: implement high-signal PR regression check for evaluations by
+  @alisa-alisa in
+  [#23937](https://github.com/google-gemini/gemini-cli/pull/23937)
+- Fix shell output display by @jacob314 in
+  [#24490](https://github.com/google-gemini/gemini-cli/pull/24490)
+- fix(ui): resolve unwanted vertical spacing around various tool output
+  treatments by @jwhelangoog in
+  [#24449](https://github.com/google-gemini/gemini-cli/pull/24449)
+- revert(cli): bring back input box and footer visibility in copy mode by
+  @sehoon38 in [#24504](https://github.com/google-gemini/gemini-cli/pull/24504)
+- fix(cli): prevent crash in AnsiOutputText when handling non-array data by
+  @sehoon38 in [#24498](https://github.com/google-gemini/gemini-cli/pull/24498)
+- feat(cli): support default values for environment variables by @ruomengz in
+  [#24469](https://github.com/google-gemini/gemini-cli/pull/24469)
+- Implement background process monitoring and inspection tools by @cocosheng-g
+  in [#23799](https://github.com/google-gemini/gemini-cli/pull/23799)
+- docs(browser-agent): update stale browser agent documentation by @gsquared94
+  in [#24463](https://github.com/google-gemini/gemini-cli/pull/24463)
+- fix: enable browser_agent in integration tests and add localhost fixture tests
+  by @gsquared94 in
+  [#24523](https://github.com/google-gemini/gemini-cli/pull/24523)
+- fix(browser): handle computer-use model detection for analyze_screenshot by
+  @gsquared94 in
+  [#24502](https://github.com/google-gemini/gemini-cli/pull/24502)
+- feat(core): Land ContextCompressionService by @joshualitt in
+  [#24483](https://github.com/google-gemini/gemini-cli/pull/24483)
+- feat(core): scope subagent workspace directories via AsyncLocalStorage by
+  @SandyTao520 in
+  [#24445](https://github.com/google-gemini/gemini-cli/pull/24445)
+- Update ink version to 6.6.7 by @jacob314 in
+  [#24514](https://github.com/google-gemini/gemini-cli/pull/24514)
+- fix(acp): handle all InvalidStreamError types gracefully in prompt by @sripasg
+  in [#24540](https://github.com/google-gemini/gemini-cli/pull/24540)
+- Fix crash when vim editor is not found in PATH on Windows by
+  @Nagajyothi-tammisetti in
+  [#22423](https://github.com/google-gemini/gemini-cli/pull/22423)
+- fix(core): move project memory dir under tmp directory by @SandyTao520 in
+  [#24542](https://github.com/google-gemini/gemini-cli/pull/24542)
+- Enable 'Other' option for yesno question type by @ruomengz in
+  [#24545](https://github.com/google-gemini/gemini-cli/pull/24545)
+- fix(cli): clear stale retry/loading state after cancellation (#21096) by
+  @Aaxhirrr in [#21960](https://github.com/google-gemini/gemini-cli/pull/21960)
+- Changelog for v0.37.0-preview.0 by @gemini-cli-robot in
+  [#24464](https://github.com/google-gemini/gemini-cli/pull/24464)
+- feat(core): implement context-aware persistent policy approvals by @jerop in
+  [#23257](https://github.com/google-gemini/gemini-cli/pull/23257)
+- docs: move agent disabling instructions and update remote agent status by
+  @jackwotherspoon in
+  [#24559](https://github.com/google-gemini/gemini-cli/pull/24559)
+- feat(cli): migrate nonInteractiveCli to LegacyAgentSession by @adamfweidman in
+  [#22987](https://github.com/google-gemini/gemini-cli/pull/22987)
+- fix(core): unsafe type assertions in Core File System #19712 by
+  @aniketsaurav18 in
+  [#19739](https://github.com/google-gemini/gemini-cli/pull/19739)
+- fix(ui): hide model quota in /stats and refactor quota display by @danzaharia1
+  in [#24206](https://github.com/google-gemini/gemini-cli/pull/24206)
+- Changelog for v0.36.0 by @gemini-cli-robot in
+  [#24558](https://github.com/google-gemini/gemini-cli/pull/24558)
+- Changelog for v0.37.0-preview.1 by @gemini-cli-robot in
+  [#24568](https://github.com/google-gemini/gemini-cli/pull/24568)
+- docs: add missing .md extensions to internal doc links by @ishaan-arora-1 in
+  [#24145](https://github.com/google-gemini/gemini-cli/pull/24145)
+- fix(ui): fixed table styling by @devr0306 in
+  [#24565](https://github.com/google-gemini/gemini-cli/pull/24565)
+- fix(core): pass includeDirectories to sandbox configuration by @galz10 in
+  [#24573](https://github.com/google-gemini/gemini-cli/pull/24573)
+- feat(ui): enable "TerminalBuffer" mode to solve flicker by @jacob314 in
+  [#24512](https://github.com/google-gemini/gemini-cli/pull/24512)
+- docs: clarify release coordination by @scidomino in
+  [#24575](https://github.com/google-gemini/gemini-cli/pull/24575)
+- fix(core): remove broken PowerShell translation and fix native \_\_write in
+  Windows sandbox by @scidomino in
+  [#24571](https://github.com/google-gemini/gemini-cli/pull/24571)
+- Add instructions for how to start react in prod and force react to prod mode
+  by @jacob314 in
+  [#24590](https://github.com/google-gemini/gemini-cli/pull/24590)
+- feat(cli): minimalist sandbox status labels by @galz10 in
+  [#24582](https://github.com/google-gemini/gemini-cli/pull/24582)
+- Feat/browser agent metrics by @kunal-10-cloud in
+  [#24210](https://github.com/google-gemini/gemini-cli/pull/24210)
+- test: fix Windows CI execution and resolve exposed platform failures by
+  @ehedlund in [#24476](https://github.com/google-gemini/gemini-cli/pull/24476)
+- feat(core,cli): prioritize summary for topics (#24608) by @Abhijit-2592 in
+  [#24609](https://github.com/google-gemini/gemini-cli/pull/24609)
+- show color by @jacob314 in
+  [#24613](https://github.com/google-gemini/gemini-cli/pull/24613)
+- feat(cli): enable compact tool output by default (#24509) by @jwhelangoog in
+  [#24510](https://github.com/google-gemini/gemini-cli/pull/24510)
+- fix(core): inject skill system instructions into subagent prompts if activated
+  by @abhipatel12 in
+  [#24620](https://github.com/google-gemini/gemini-cli/pull/24620)
+- fix(core): improve windows sandbox reliability and fix integration tests by
+  @ehedlund in [#24480](https://github.com/google-gemini/gemini-cli/pull/24480)
+- fix(core): ensure sandbox approvals are correctly persisted and matched for
+  proactive expansions by @galz10 in
+  [#24577](https://github.com/google-gemini/gemini-cli/pull/24577)
+- feat(cli) Scrollbar for input prompt by @jacob314 in
+  [#21992](https://github.com/google-gemini/gemini-cli/pull/21992)
+- Do not run pr-eval workflow when no steering changes detected by @alisa-alisa
+  in [#24621](https://github.com/google-gemini/gemini-cli/pull/24621)
+- Fix restoration of topic headers. by @gundermanc in
+  [#24650](https://github.com/google-gemini/gemini-cli/pull/24650)
+- feat(core): discourage update topic tool for simple tasks by @Samee24 in
+  [#24640](https://github.com/google-gemini/gemini-cli/pull/24640)
+- fix(core): ensure global temp directory is always in sandbox allowed paths by
+  @galz10 in [#24638](https://github.com/google-gemini/gemini-cli/pull/24638)
+- fix(core): detect uninitialized lines by @jacob314 in
+  [#24646](https://github.com/google-gemini/gemini-cli/pull/24646)
+- docs: update sandboxing documentation and toolSandboxing settings by @galz10
+  in [#24655](https://github.com/google-gemini/gemini-cli/pull/24655)
+- feat(cli): enhance tool confirmation UI and selection layout by @galz10 in
+  [#24376](https://github.com/google-gemini/gemini-cli/pull/24376)
+- feat(acp): add support for `/about` command by @sripasg in
+  [#24649](https://github.com/google-gemini/gemini-cli/pull/24649)
+- feat(cli): add role specific metrics to /stats by @cynthialong0-0 in
+  [#24659](https://github.com/google-gemini/gemini-cli/pull/24659)
+- split context by @jacob314 in
+  [#24623](https://github.com/google-gemini/gemini-cli/pull/24623)
+- fix(cli): remove -S from shebang to fix Windows and BSD execution by
+  @scidomino in [#24756](https://github.com/google-gemini/gemini-cli/pull/24756)
+- Fix issue where topic headers can be posted back to back by @gundermanc in
+  [#24759](https://github.com/google-gemini/gemini-cli/pull/24759)
+- fix(core): handle partial llm_request in BeforeModel hook override by
+  @krishdef7 in [#22326](https://github.com/google-gemini/gemini-cli/pull/22326)
+- fix(ui): improve narration suppression and reduce flicker by @gundermanc in
+  [#24635](https://github.com/google-gemini/gemini-cli/pull/24635)
+- fix(ui): fixed auth race condition causing logo to flicker by @devr0306 in
+  [#24652](https://github.com/google-gemini/gemini-cli/pull/24652)
+- fix(browser): remove premature browser cleanup after subagent invocation by
+  @gsquared94 in
+  [#24753](https://github.com/google-gemini/gemini-cli/pull/24753)
+- Revert "feat(core,cli): prioritize summary for topics (#24608)" by
+  @Abhijit-2592 in
+  [#24777](https://github.com/google-gemini/gemini-cli/pull/24777)
+- relax tool sandboxing overrides for plan mode to match defaults. by
+  @DavidAPierce in
+  [#24762](https://github.com/google-gemini/gemini-cli/pull/24762)
+- fix(cli): respect global environment variable allowlist by @scidomino in
+  [#24767](https://github.com/google-gemini/gemini-cli/pull/24767)
+- fix(cli): ensure skills list outputs to stdout in non-interactive environments
+  by @spencer426 in
+  [#24566](https://github.com/google-gemini/gemini-cli/pull/24566)
+- Add an eval for and fix unsafe cloning behavior. by @gundermanc in
+  [#24457](https://github.com/google-gemini/gemini-cli/pull/24457)
+- fix(policy): allow complete_task in plan mode by @abhipatel12 in
+  [#24771](https://github.com/google-gemini/gemini-cli/pull/24771)
+- feat(telemetry): add browser agent clearcut metrics by @gsquared94 in
+  [#24688](https://github.com/google-gemini/gemini-cli/pull/24688)
+- feat(cli): support selective topic expansion and click-to-expand by
+  @Abhijit-2592 in
+  [#24793](https://github.com/google-gemini/gemini-cli/pull/24793)
+- temporarily disable sandbox integration test on windows by @ehedlund in
+  [#24786](https://github.com/google-gemini/gemini-cli/pull/24786)
+- Remove flakey test by @scidomino in
+  [#24837](https://github.com/google-gemini/gemini-cli/pull/24837)
+- Alisa/approve button by @alisa-alisa in
+  [#24645](https://github.com/google-gemini/gemini-cli/pull/24645)
+- feat(hooks): display hook system messages in UI by @mbleigh in
+  [#24616](https://github.com/google-gemini/gemini-cli/pull/24616)
+- fix(core): propagate BeforeModel hook model override end-to-end by @krishdef7
+  in [#24784](https://github.com/google-gemini/gemini-cli/pull/24784)
+- chore: fix formatting for behavioral eval skill reference file by @abhipatel12
+  in [#24846](https://github.com/google-gemini/gemini-cli/pull/24846)
+- fix: use directory junctions on Windows for skill linking by @enjoykumawat in
+  [#24823](https://github.com/google-gemini/gemini-cli/pull/24823)
+- fix(cli): prevent multiple banner increments on remount by @sehoon38 in
+  [#24843](https://github.com/google-gemini/gemini-cli/pull/24843)
+- feat(acp): add /help command by @sripasg in
+  [#24839](https://github.com/google-gemini/gemini-cli/pull/24839)
+- fix(core): remove tmux alternate buffer warning by @jackwotherspoon in
+  [#24852](https://github.com/google-gemini/gemini-cli/pull/24852)
+- Improve sandbox error matching and caching by @DavidAPierce in
+  [#24550](https://github.com/google-gemini/gemini-cli/pull/24550)
+- feat(core): add agent protocol UI types and experimental flag by @mbleigh in
+  [#24275](https://github.com/google-gemini/gemini-cli/pull/24275)
+- feat(core): use experiment flags for default fetch timeouts by @yunaseoul in
+  [#24261](https://github.com/google-gemini/gemini-cli/pull/24261)
+- Revert "fix(ui): improve narration suppression and reduce flicker (#2… by
+  @gundermanc in
+  [#24857](https://github.com/google-gemini/gemini-cli/pull/24857)
+- refactor(cli): remove duplication in interactive shell awaiting input hint by
+  @JayadityaGit in
+  [#24801](https://github.com/google-gemini/gemini-cli/pull/24801)
+- refactor(core): make LegacyAgentSession dependencies optional by @mbleigh in
+  [#24287](https://github.com/google-gemini/gemini-cli/pull/24287)
+- Changelog for v0.37.0-preview.2 by @gemini-cli-robot in
+  [#24848](https://github.com/google-gemini/gemini-cli/pull/24848)
+- fix(cli): always show shell command description or actual command by @jacob314
+  in [#24774](https://github.com/google-gemini/gemini-cli/pull/24774)
+- Added flag for ept size and increased default size by @devr0306 in
+  [#24859](https://github.com/google-gemini/gemini-cli/pull/24859)
+- fix(core): dispose Scheduler to prevent McpProgress listener leak by
+  @Anjaligarhwal in
+  [#24870](https://github.com/google-gemini/gemini-cli/pull/24870)
+- fix(cli): switch default back to terminalBuffer=false and fix regressions
+  introduced for that mode by @jacob314 in
+  [#24873](https://github.com/google-gemini/gemini-cli/pull/24873)
+- feat(cli): switch to ctrl+g from ctrl-x by @jacob314 in
+  [#24861](https://github.com/google-gemini/gemini-cli/pull/24861)
+- fix: isolate concurrent browser agent instances by @gsquared94 in
+  [#24794](https://github.com/google-gemini/gemini-cli/pull/24794)
+- docs: update MCP server OAuth redirect port documentation by @adamfweidman in
+  [#24844](https://github.com/google-gemini/gemini-cli/pull/24844)
 
 **Full Changelog**:
-https://github.com/google-gemini/gemini-cli/compare/v0.47.0-preview.0...v0.48.0-preview.0
+https://github.com/google-gemini/gemini-cli/compare/v0.37.0-preview.2...v0.38.0-preview.0

docs/cli/acp-mode.md

@@ -44,8 +44,8 @@ and Gemini CLI (the server).
 
 - **Communication:** The entire communication happens over standard input/output
   (stdio) using the JSON-RPC 2.0 protocol.
-- **Client's role:** The client is responsible for sending requests (for
-  example, prompts) and handling responses and notifications from Gemini CLI.
+- **Client's role:** The client is responsible for sending requests (e.g.,
+  prompts) and handling responses and notifications from Gemini CLI.
 - **Gemini CLI's role:** In ACP mode, Gemini CLI listens for incoming JSON-RPC
   requests, processes them, and sends back responses.
 
@@ -72,8 +72,8 @@ leverage the IDE's capabilities to perform tasks. The MCP client logic is in
 
 ## Capabilities and supported methods
 
-The ACP protocol exposes a number of methods for ACP clients (for example IDEs)
-to control Gemini CLI.
+The ACP protocol exposes a number of methods for ACP clients (e.g. IDEs) to
+control Gemini CLI.
 
 ### Core methods
 
@@ -87,8 +87,8 @@ to control Gemini CLI.
 
 ### Session control
 
-- `setSessionMode`: Allows changing the approval level for tool calls (for
-  example, to `auto-approve`).
+- `setSessionMode`: Allows changing the approval level for tool calls (e.g., to
+  `auto-approve`).
 - `unstable_setSessionModel`: Changes the model for the current session.
 
 ### File system proxy

docs/cli/auto-memory.md

@@ -1,164 +0,0 @@
-# Auto Memory
-
-Auto Memory is an experimental feature that mines your past Gemini CLI sessions
-in the background and proposes durable memory updates and reusable
-[Agent Skills](./skills.md). You review each candidate before it becomes
-available to future sessions: apply memory updates, promote skills, or discard
-anything you do not want.
-
-<!-- prettier-ignore -->
-> [!NOTE]
-> This is an experimental feature currently under active development.
-
-## Overview
-
-Every session you run with Gemini CLI is recorded locally as a transcript. Auto
-Memory scans those transcripts for durable facts, preferences, workflow
-constraints, and procedural patterns that recur across sessions. It can draft
-memory updates as unified diff `.patch` files and draft reusable procedures as
-`SKILL.md` files. All candidates are held in a project-local inbox until you
-approve or discard them.
-
-You'll use Auto Memory when you want to:
-
-- **Capture team workflows** that you find yourself walking the agent through
-  more than once.
-- **Preserve durable project context** such as repeated verification commands,
-  local constraints, or personal project notes.
-- **Codify hard-won fixes** for project-specific landmines so future sessions
-  avoid them.
-- **Bootstrap a skills library** without writing every `SKILL.md` by hand.
-
-Auto Memory complements direct memory-file editing. The agent can still persist
-explicit user instructions by editing the appropriate Markdown memory file; Auto
-Memory infers candidates from past sessions, writes reviewable patches or skill
-drafts, and never applies them without your approval.
-
-## Prerequisites
-
-- Gemini CLI installed and authenticated.
-- At least one idle project session with 10 or more user messages. Auto Memory
-  ignores active, trivial, and sub-agent sessions.
-
-## How to enable Auto Memory
-
-Auto Memory is off by default. Enable it in your settings file:
-
-1.  Open your global settings file at `~/.gemini/settings.json`. If you only
-    want Auto Memory in one project, edit `.gemini/settings.json` in that
-    project instead.
-
-2.  Add the experimental flag:
-
-    ```json
-    {
-      "experimental": {
-        "autoMemory": true
-      }
-    }
-    ```
-
-3.  Restart Gemini CLI. The flag requires a restart because the extraction
-    service starts during session boot.
-
-## How Auto Memory works
-
-Auto Memory runs as a background task on session startup. It does not block the
-UI, consume your interactive turns, or surface tool prompts.
-
-1.  **Eligibility scan.** The service indexes recent sessions from
-    `~/.gemini/tmp/<project>/chats/`. Sessions are eligible only if they have
-    been idle for at least three hours and contain at least 10 user messages.
-2.  **Lock acquisition.** A lock file in the project's memory directory
-    coordinates across multiple CLI instances so extraction runs at most once at
-    a time. A state file records processed session versions, and extraction is
-    throttled so short back-to-back CLI launches do not repeatedly scan history.
-3.  **Candidate extraction.** A background extraction agent reviews the session
-    index, reads any sessions that look like they contain durable memory or
-    repeated procedural workflows, and drafts candidates. It defaults to
-    creating no artifacts unless the evidence is strong, so many runs produce no
-    inbox items.
-4.  **Safety boundaries.** Auto Memory writes candidates to a review inbox. It
-    cannot directly edit active memory files, settings, credentials, or project
-    `GEMINI.md` files.
-5.  **Patch validation.** Skill update patches are parsed and dry-run before
-    they are surfaced. Memory patches are parsed, target-allowlisted, and
-    applied atomically only when you approve them from the inbox.
-6.  **Notification.** When a run produces new candidates, Gemini CLI surfaces an
-    inline message telling you how many items are waiting.
-
-## How to review extracted items
-
-Use the `/memory inbox` slash command to open the inbox dialog at any time:
-
-**Command:** `/memory inbox`
-
-The dialog groups pending items into new skills, skill updates, and memory
-updates. From there you can:
-
-- **Read** the full `SKILL.md` body before deciding.
-- **Promote** a skill to your user (`~/.gemini/skills/`) or workspace
-  (`.gemini/skills/`) directory.
-- **Discard** a skill you do not want.
-- **Apply** or reject a `.patch` proposal against an existing skill.
-- **Review** memory diffs before they touch active files.
-- **Apply** or dismiss private and global memory patches. Private patches target
-  the project memory directory; global patches target only your personal
-  `~/.gemini/GEMINI.md` file.
-
-Promoted skills become discoverable in the next session and follow the standard
-[skill discovery precedence](./skills.md#skill-discovery-tiers). Applied memory
-patches update the underlying memory files and reload memory for the current
-session.
-
-## How to disable Auto Memory
-
-To turn off background extraction, set the flag back to `false` in your settings
-file and restart Gemini CLI:
-
-```json
-{
-  "experimental": {
-    "autoMemory": false
-  }
-}
-```
-
-Disabling the flag stops the background service immediately on the next session
-start. Existing inbox items remain on disk; you can either drain them with
-`/memory inbox` first or remove the project memory directory manually.
-
-## Data and privacy
-
-- Auto Memory only reads session files that already exist locally on your
-  machine.
-- Auto Memory uses model calls to analyze selected local transcript content
-  during extraction. No candidates are applied automatically, but transcript
-  excerpts may be sent to the configured model as part of those calls.
-- The extraction agent is instructed to redact secrets, tokens, and credentials
-  it encounters and to never copy large tool outputs verbatim.
-- Drafted skills and memory patches live in your project's memory directory
-  until you promote, apply, dismiss, or discard them. They are not automatically
-  loaded into any session.
-
-## Limitations
-
-- The extraction agent runs on a preview Gemini Flash model. Extraction quality
-  depends on the model's ability to recognize durable patterns versus one-off
-  incidents.
-- Auto Memory does not extract memory or skills from the current session. It
-  only considers sessions that have been idle for three hours or more.
-- Project or workspace shared instructions in project `GEMINI.md` files are not
-  auto-extractable. Auto Memory can propose private project memory, global
-  personal memory, and skills.
-- Inbox items are stored per project. Skills extracted in one workspace are not
-  visible from another until you promote them to the user-scope skills
-  directory.
-
-## Next steps
-
-- Learn how skills are discovered and activated in [Agent Skills](./skills.md).
-- Explore the [memory management tutorial](./tutorials/memory-management.md) for
-  the complementary explicit-memory and `GEMINI.md` workflows.
-- Review the experimental settings catalog in
-  [Settings](./settings.md#experimental).

docs/cli/checkpointing.md

@@ -1,9 +1,9 @@
 # Checkpointing
 
-Gemini CLI includes a Checkpointing feature that automatically saves a snapshot
-of your project's state before any file modifications are made by AI-powered
-tools. This lets you safely experiment with and apply code changes, knowing you
-can instantly revert back to the state before the tool was run.
+The Gemini CLI includes a Checkpointing feature that automatically saves a
+snapshot of your project's state before any file modifications are made by
+AI-powered tools. This lets you safely experiment with and apply code changes,
+knowing you can instantly revert back to the state before the tool was run.
 
 ## How it works
 
@@ -72,7 +72,7 @@ To see a list of all saved checkpoints for the current project, simply run:
 
 The CLI will display a list of available checkpoint files. These file names are
 typically composed of a timestamp, the name of the file being modified, and the
-name of the tool that was about to be run (for example,
+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

docs/cli/cli-reference.md

@@ -9,7 +9,7 @@ and parameters.
 | ---------------------------------- | ---------------------------------- | ------------------------------------------------------------ |
 | `gemini`                           | Start interactive REPL             | `gemini`                                                     |
 | `gemini -p "query"`                | Query non-interactively            | `gemini -p "summarize README.md"`                            |
-| gemini "query"                     | Query and continue interactively   | gemini "explain this project"                                |
+| `gemini "query"`                   | Query and continue interactively   | `gemini "explain this project"`                              |
 | `cat file \| gemini`               | Process piped content              | `cat logs.txt \| gemini`<br>`Get-Content logs.txt \| gemini` |
 | `gemini -i "query"`                | Execute and continue interactively | `gemini -i "What is the purpose of this project?"`           |
 | `gemini -r "latest"`               | Continue most recent session       | `gemini -r "latest"`                                         |
@@ -29,17 +29,16 @@ and parameters.
 
 These commands are available within the interactive REPL.
 
-| Command              | Description                                     |
-| -------------------- | ----------------------------------------------- |
-| `/skills reload`     | Reload discovered skills from disk              |
-| `/agents reload`     | Reload the agent registry                       |
-| `/commands list`     | List available custom slash commands            |
-| `/commands reload`   | Reload custom slash commands                    |
-| `/memory reload`     | Reload context files (for example, `GEMINI.md`) |
-| `/mcp reload`        | Restart and reload MCP servers                  |
-| `/extensions reload` | Reload all active extensions                    |
-| `/help`              | Show help for all commands                      |
-| `/quit`              | Exit the interactive session                    |
+| Command              | Description                              |
+| -------------------- | ---------------------------------------- |
+| `/skills reload`     | Reload discovered skills from disk       |
+| `/agents reload`     | Reload the agent registry                |
+| `/commands reload`   | Reload custom slash commands             |
+| `/memory reload`     | Reload context files (e.g., `GEMINI.md`) |
+| `/mcp reload`        | Restart and reload MCP servers           |
+| `/extensions reload` | Reload all active extensions             |
+| `/help`              | Show help for all commands               |
+| `/quit`              | Exit the interactive session             |
 
 ## CLI Options
 
@@ -53,7 +52,6 @@ These commands are available within the interactive REPL.
 | `--prompt-interactive`           | `-i`  | string  | -         | Execute prompt and continue in interactive mode                                                                                                                        |
 | `--worktree`                     | `-w`  | string  | -         | Start Gemini in a new git worktree. If no name is provided, one is generated automatically. Requires `experimental.worktrees: true` in settings.                       |
 | `--sandbox`                      | `-s`  | boolean | `false`   | Run in a sandboxed environment for safer execution                                                                                                                     |
-| `--skip-trust`                   | -     | boolean | `false`   | Trust the current workspace for this session, skipping the folder trust check.                                                                                         |
 | `--approval-mode`                | -     | string  | `default` | Approval mode for tool execution. Choices: `default`, `auto_edit`, `yolo`, `plan`                                                                                      |
 | `--yolo`                         | `-y`  | boolean | `false`   | **Deprecated.** Auto-approve all actions. Use `--approval-mode=yolo` instead.                                                                                          |
 | `--experimental-acp`             | -     | boolean | -         | Start in ACP (Agent Code Pilot) mode. **Experimental feature.**                                                                                                        |
@@ -62,7 +60,7 @@ These commands are available within the interactive REPL.
 | `--allowed-tools`                | -     | array   | -         | **Deprecated.** Use the [Policy Engine](../reference/policy-engine.md) instead. Tools that are allowed to run without confirmation (comma-separated or multiple flags) |
 | `--extensions`                   | `-e`  | array   | -         | List of extensions to use. If not provided, all extensions are enabled (comma-separated or multiple flags)                                                             |
 | `--list-extensions`              | `-l`  | boolean | -         | List all available extensions and exit                                                                                                                                 |
-| `--resume`                       | `-r`  | string  | -         | Resume a previous session. Use `"latest"` for most recent or index number (for example `--resume 5`)                                                                   |
+| `--resume`                       | `-r`  | string  | -         | Resume a previous session. Use `"latest"` for most recent or index number (e.g. `--resume 5`)                                                                          |
 | `--list-sessions`                | -     | boolean | -         | List available sessions for the current project and exit                                                                                                               |
 | `--delete-session`               | -     | string  | -         | Delete a session by index number (use `--list-sessions` to see available sessions)                                                                                     |
 | `--include-directories`          | -     | array   | -         | Additional directories to include in the workspace (comma-separated or multiple flags)                                                                                 |

docs/cli/creating-skills.md

@@ -1,138 +1,43 @@
 # Creating Agent Skills
 
-Agent Skills let you extend Gemini CLI with specialized expertise, procedural
-workflows, and task-specific resources. This guide walks you through both
-automated and manual methods for creating and organizing your skills.
+This guide provides an overview of how to create your own Agent Skills to extend
+the capabilities of Gemini CLI.
 
-## Quickstart: Create a skill with a prompt
+## Getting started: The `skill-creator` skill
 
-The fastest way to create a new skill is to use the built-in `skill-creator`.
-This meta-skill guides you through designing, scaffolding, and validating your
-expertise.
+The recommended way to create a new skill is to use the built-in `skill-creator`
+skill. To use it, ask Gemini CLI to create a new skill for you.
 
-Simply ask Gemini CLI to create a skill for you:
+**Example prompt:**
 
-> "Create a new skill called 'code-reviewer' that analyzes local files for
-> common errors and style violations."
+> "create a new skill called 'code-reviewer'"
 
-Gemini will then:
+Gemini CLI will then use the `skill-creator` to generate the skill:
 
-1.  Generate a new directory for your skill (for example, `my-new-skill/`).
+1.  Generate a new directory for your skill (e.g., `my-new-skill/`).
 2.  Create a `SKILL.md` file with the necessary YAML frontmatter (`name` and
     `description`).
 3.  Create the standard resource directories: `scripts/`, `references/`, and
     `assets/`.
 
-Once created, you can find your new skill in `.gemini/skills/code-reviewer/`.
+## Manual skill creation
 
-## Manual creation
+If you prefer to create skills manually:
 
-1.  **Create a directory** for your skill (for example, `my-new-skill/`).
+1.  **Create a directory** for your skill (e.g., `my-new-skill/`).
 2.  **Create a `SKILL.md` file** inside the new directory.
 
-### 1. Create the directory structure
+To add additional resources that support the skill, refer to the skill
+structure.
 
-The first step is to create the necessary folders for your skill and its
-scripts.
+## Skill structure
 
-**macOS/Linux**
+A skill is a directory containing a `SKILL.md` file at its root.
 
-```bash
-mkdir -p .gemini/skills/code-reviewer/scripts
-```
-
-**Windows (PowerShell)**
-
-```powershell
-New-Item -ItemType Directory -Force -Path ".gemini\skills\code-reviewer\scripts"
-```
-
-### 2. Define the skill (`SKILL.md`)
-
-The `SKILL.md` file defines the skill's purpose and instructions for the agent.
-Create a file at `.gemini/skills/code-reviewer/SKILL.md`.
-
-```markdown
----
-name: code-reviewer
-description:
-  Expertise in reviewing code changes for correctness, security, and style. Use
-  when the user asks to "review" their code or a PR.
----
-
-# Code Reviewer Instructions
-
-You act as a senior software engineer specialized in code quality. When this
-skill is active, you MUST:
-
-1.  **Analyze**: Review the provided code for logical errors, security
-    vulnerabilities, and style violations.
-2.  **Review**: Use the bundled `scripts/review.js` utility to perform an
-    automated check.
-3.  **Feedback**: Provide constructive feedback, clearly distinguishing between
-    critical issues and minor improvements.
-```
-
-### 3. Add the tool logic
-
-Skills can bundle resources like scripts to perform deterministic tasks. Create
-a file at `.gemini/skills/code-reviewer/scripts/review.js`.
-
-```javascript
-// .gemini/skills/code-reviewer/scripts/review.js
-const file = process.argv[2];
-
-if (!file) {
-  console.error('Usage: node review.js <file>');
-  process.exit(1);
-}
-
-console.log(`Reviewing ${file}...`);
-// Simple mock review logic
-setTimeout(() => {
-  console.log(`Result: Success (No major issues found in ${file})`);
-}, 500);
-```
-
-### 4. Test the skill
-
-Gemini CLI automatically discovers skills in the `.gemini/skills` directory.
-
-1.  Start a new session and ask a question that triggers the skill's
-    description: "Can you review index.js"
-2.  Gemini identifies the request matches the `code-reviewer` description and
-    asks for permission to activate it.
-3.  Once you approve, Gemini executes the bundled script:
-    `node .gemini/skills/code-reviewer/scripts/review.js index.js`
-
-To determine whether your skill has been correctly loaded, run the command:
-
-```bash
-/skills
-```
-
-### 5. Optional: Share your skill
-
-You can share your skills in several ways depending on your target audience.
-
-- **Workspace skills**: Commit your skill to a `.gemini/skills/` directory in
-  your project repository.
-- **Extensions**: Bundle your skill within a
-  [Gemini CLI extension](../extensions/writing-extensions.md).
-- **Git repositories**: Share the skill directory as a standalone Git repo and
-  install it using `gemini skills install <url>`.
-
----
-
-## Core concepts
-
-Now that you've built your first skill, let's explore the core components and
-workflows for developing more complex expertise.
-
-### Skill structure
+### Folder structure
 
 While a `SKILL.md` file is the only required component, we recommend the
-following structure for organizing your skill's resources.
+following structure for organizing your skill's resources:
 
 ```text
 my-skill/
@@ -142,66 +47,34 @@ my-skill/
 └── assets/        (Optional) Templates and other resources
 ```
 
-When a skill is activated, the model is granted access to this entire directory.
-You can instruct the model to use the tools and files found within these
-folders.
+### `SKILL.md` file
 
-### Metadata and triggers
+The `SKILL.md` file is the core of your skill. This file uses YAML frontmatter
+for metadata and Markdown for instructions. For example:
 
-The `SKILL.md` file uses YAML frontmatter for metadata.
+```markdown
+---
+name: code-reviewer
+description:
+  Use this skill to review code. It supports both local changes and remote Pull
+  Requests.
+---
+
+# Code Reviewer
+
+This skill guides the agent in conducting thorough code reviews.
+
+## Workflow
+
+### 1. Determine Review Target
+
+- **Remote PR**: If the user gives a PR number or URL, target that remote PR.
+- **Local Changes**: If changes are local... ...
+```
 
 - **`name`**: A unique identifier for the skill. This should match the directory
   name.
-- **`description`**: **CRITICAL.** This is how Gemini decides when to use the
-  skill. Be specific about the tasks it handles and the keywords that should
-  trigger it.
-
-### Discovery tiers
-
-Gemini CLI discovers skills from several locations, following a specific order
-of precedence (lowest to highest):
-
-1.  **Built-in Skills**: Included with Gemini CLI (pre-approved).
-2.  **Extension Skills**: Bundled within [extensions](../extensions/).
-3.  **User Skills**: `~/.gemini/skills/` or the `~/.agents/skills/` alias.
-4.  **Workspace Skills**: `.gemini/skills/` or the `.agents/skills/` alias.
-
-### Discovery aliases
-
-You can use `.agents/skills` as an alternative to `.gemini/skills`. This alias
-is compatible with other AI agent tools following the
-[Agent Skills](https://agentskills.io) standard.
-
-## Advanced development
-
-Once you've built a basic skill, you can use specialized scripts and workflows
-to streamline your development process.
-
-### Creation scripts
-
-If you are developing a skill and want to use the same scripts the built-in
-tools use, you can find them in the core package. These scripts help automate
-the initialization, validation, and packaging of skills.
-
-- **Initialize**: `node scripts/init_skill.cjs <name> --path <dir>`
-- **Validate**: `node scripts/validate_skill.cjs <path/to/skill>`
-- **Package**: `node scripts/package_skill.cjs <path/to/skill>` (Creates a
-  `.skill` zip file)
-
-### Linking for local development
-
-If you are developing a skill in a separate directory, you can link it to your
-user skills directory for testing:
-
-```bash
-gemini skills link .
-```
-
-## Next steps
-
-- [Skill best practices](./skills-best-practices.md): Learn strategies for
-  building reliable and effective skills.
-- [Agent Skills overview](./skills.md): Deep dive into discovery tiers and the
-  skill lifecycle.
-- [Get started with Agent Skills](./tutorials/skills-getting-started.md): A
-  quick walkthrough of triggering and using skills.
+- **`description`**: A description of what the skill does and when Gemini should
+  use it.
+- **Body**: The Markdown body of the file contains the instructions that guide
+  the agent's behavior when the skill is active.

docs/cli/custom-commands.md

@@ -34,7 +34,6 @@ separator (`/` or `\`) being converted to a colon (`:`).
 > [!TIP]
 > After creating or modifying `.toml` command files, run
 > `/commands reload` to pick up your changes without restarting the CLI.
-> To see all available command files, run `/commands list`.
 
 ## TOML file format (v1)
 
@@ -86,8 +85,8 @@ The model receives:
 **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 lets you safely
-pass arguments to shell commands, ensuring the resulting command is
+are automatically **shell-escaped** before replacement. This allows you to
+safely pass arguments to shell commands, ensuring the resulting command is
 syntactically correct and secure while preventing command injection
 vulnerabilities.
 
@@ -106,8 +105,8 @@ When you run `/grep-code It's complicated`:
 
 1. The CLI sees `{{args}}` used both outside and inside `!{...}`.
 2. Outside: The first `{{args}}` is replaced raw with `It's complicated`.
-3. Inside: The second `{{args}}` is replaced with the escaped version (for
-   example, on Linux: `"It\'s complicated"`).
+3. Inside: The second `{{args}}` is replaced with the escaped version (e.g., on
+   Linux: `"It\'s complicated"`).
 4. The command executed is `grep -r "It's complicated" .`.
 5. The CLI prompts you to confirm this exact, secure command before execution.
 6. The final prompt is sent.
@@ -117,13 +116,13 @@ When you run `/grep-code It's complicated`:
 If your `prompt` does **not** contain the special placeholder `{{args}}`, the
 CLI uses a default behavior for handling arguments.
 
-If you provide arguments to the command (for example, `/mycommand arg1`), the
-CLI will append the full command you typed to the end of the prompt, separated
-by two newlines. This allows the model to see both the original instructions and
-the specific arguments you just provided.
+If you provide arguments to the command (e.g., `/mycommand arg1`), the CLI will
+append the full command you typed to the end of the prompt, separated by two
+newlines. This allows the model to see both the original instructions and the
+specific arguments you just provided.
 
-If you do **not** provide any arguments (for example, `/mycommand`), the prompt
-is sent to the model exactly as it is, with nothing appended.
+If you do **not** provide any arguments (e.g., `/mycommand`), the prompt is sent
+to the model exactly as it is, with nothing appended.
 
 **Example (`changelog.toml`):**
 
@@ -189,7 +188,7 @@ ensure that only intended commands can be run.
     dialog will appear showing the exact command(s) to be executed.
 5.  **Execution and error reporting:** The command is executed. If the command
     fails, the output injected into the prompt will include the error messages
-    (stderr) followed by a status line, for example,
+    (stderr) followed by a status line, e.g.,
     `[Shell command exited with code 1]`. This helps the model understand the
     context of the failure.
 
@@ -230,10 +229,9 @@ operate on specific files.
 
 - **File injection**: `@{path/to/file.txt}` is replaced by the content of
   `file.txt`.
-- **Multimodal support**: If the path points to a supported image (for example,
-  PNG, JPEG), PDF, audio, or video file, it will be correctly encoded and
-  injected as multimodal input. Other binary files are handled gracefully and
-  skipped.
+- **Multimodal support**: If the path points to a supported image (e.g., PNG,
+  JPEG), PDF, audio, or video file, it will be correctly encoded and injected as
+  multimodal input. Other binary files are handled gracefully and skipped.
 - **Directory listing**: `@{path/to/dir}` is traversed and each file present
   within the directory and all subdirectories is inserted into the prompt. This
   respects `.gitignore` and `.geminiignore` if enabled.

docs/cli/enterprise.md

@@ -175,8 +175,8 @@ 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 (for
-example, `/usr/local/bin/gemini`).
+that appears earlier in the user's `PATH` than the actual Gemini CLI binary
+(e.g., `/usr/local/bin/gemini`).
 
 ```bash
 #!/bin/bash
@@ -285,7 +285,7 @@ environment to a blocklist.
 <!-- prettier-ignore -->
 > [!WARNING]
 > Blocklisting with `excludeTools` is less secure than
-> allowlisting with `tools.core`, as it relies on blocking known-bad commands,
+> 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.**
 
@@ -325,9 +325,9 @@ User. When it comes to the `mcpServers` object, these configurations are
 1.  **Merging:** The lists of servers from all three levels are combined into a
     single list.
 2.  **Precedence:** If a server with the **same name** is defined at multiple
-    levels (for example, a server named `corp-api` exists in both system and
-    user settings), the definition from the highest-precedence level is used.
-    The order of precedence is: **System > Workspace > User**.
+    levels (e.g., a server named `corp-api` exists in both system and user
+    settings), the definition from the highest-precedence level is used. The
+    order of precedence is: **System > Workspace > User**.
 
 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
@@ -343,8 +343,8 @@ canonical servers and adding their names to an allowlist.
 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.
 This is done using the `includeTools` and `excludeTools` properties within a
-server's definition. This lets you use a subset of tools from a server without
-allowing potentially dangerous ones.
+server's definition. This allows you to use a subset of tools from a server
+without allowing potentially dangerous ones.
 
 Following the principle of least privilege, it is highly recommended to use
 `includeTools` to create an allowlist of only the necessary tools.
@@ -481,8 +481,9 @@ an environment variable, but it can also be enforced for custom tools via the
 ## Telemetry and auditing
 
 For auditing and monitoring purposes, you can configure Gemini CLI to send
-telemetry data to a central location. This lets you track tool usage and other
-events. For more information, see the [telemetry documentation](./telemetry.md).
+telemetry data to a central location. This allows you to track tool usage and
+other events. For more information, see the
+[telemetry documentation](./telemetry.md).
 
 **Example:** Enable telemetry and send it to a local OTLP collector. If
 `otlpEndpoint` is not specified, it defaults to `http://localhost:4317`.
@@ -505,19 +506,15 @@ events. For more information, see the [telemetry documentation](./telemetry.md).
 ## Authentication
 
 You can enforce a specific authentication method for all users by setting the
-`security.auth.enforcedType` in the system-level `settings.json` file. This
-prevents users from choosing a different authentication method. See the
-[Authentication docs](../get-started/authentication.mdx) for more details.
+`enforcedAuthType` in the system-level `settings.json` file. This prevents users
+from choosing a different authentication method. See the
+[Authentication docs](../get-started/authentication.md) for more details.
 
 **Example:** Enforce the use of Google login for all users.
 
 ```json
 {
-  "security": {
-    "auth": {
-      "enforcedType": "oauth-personal"
-    }
-  }
+  "enforcedAuthType": "oauth-personal"
 }
 ```
 

docs/cli/gemini-ignore.md

@@ -1,9 +1,9 @@
 # Ignoring files
 
 This document provides an overview of the Gemini Ignore (`.geminiignore`)
-feature of Gemini CLI.
+feature of the Gemini CLI.
 
-Gemini CLI includes the ability to automatically ignore files, similar to
+The Gemini CLI includes the ability to automatically ignore files, similar to
 `.gitignore` (used by Git) and `.aiexclude` (used by Gemini Code Assist). Adding
 paths to your `.geminiignore` file will exclude them from tools that support
 this feature, although they will still be visible to other services (such as

docs/cli/gemini-md.md

@@ -16,12 +16,10 @@ sends them to the model with every prompt. The CLI loads files in the following
 order:
 
 1.  **Global context file:**
-
     - **Location:** `~/.gemini/GEMINI.md` (in your user home directory).
     - **Scope:** Provides default instructions for all your projects.
 
 2.  **Environment and workspace context files:**
-
     - **Location:** The CLI searches for `GEMINI.md` files in your configured
       workspace directories and their parent directories.
     - **Scope:** Provides context relevant to the projects you are currently
@@ -67,6 +65,8 @@ You can interact with the loaded context files by using the `/memory` command.
   being provided to the model.
 - **`/memory reload`**: Forces a re-scan and reload of all `GEMINI.md` files
   from all configured locations.
+- **`/memory add <text>`**: Appends your text to your global
+  `~/.gemini/GEMINI.md` file. This lets you add persistent memories on the fly.
 
 ## Modularize context with imports
 

docs/cli/generation-settings.md

@@ -1,28 +1,26 @@
 # Advanced Model Configuration
 
-This guide details the Model Configuration system within Gemini CLI. Designed
-for researchers, AI quality engineers, and advanced users, this system provides
-a rigorous framework for managing generative model hyperparameters and
+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.
 
-<!-- prettier-ignore -->
-> [!WARNING]
-> This is a power-user feature. Configuration values are passed
+> **Warning**: This is a power-user feature. Configuration values are passed
 > directly to the model provider with minimal validation. Incorrect settings
-> (for example, incompatible parameter combinations) may result in runtime
-> errors from the API.
+> (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 (for
-example, a CLI flag or agent request) from the underlying API configuration.
-This allows for:
+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 (for example, testing vs. production).
+  operating contexts (e.g., testing vs. production).
 - **Agent-Scoped Customization**: Applying specific settings only when a
   particular agent is active.
 
@@ -73,7 +71,7 @@ context. They are evaluated dynamically for each model request.
   specified `match` properties.
   - `model`: Matches the requested model name or alias.
   - `overrideScope`: Matches the distinct scope of the request (typically the
-    agent name, for example, `codebaseInvestigator`).
+    agent name, e.g., `codebaseInvestigator`).
 
 **Example Override**:
 
@@ -115,8 +113,8 @@ 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 (for example, `model` + `overrideScope`) override broad
-      matches (for example, `model` only).
+    - 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
@@ -130,10 +128,10 @@ The configuration follows the `ModelConfigServiceConfig` interface.
 
 Defines the actual parameters for the model.
 
-| Property                | Type     | Description                                                               |
-| :---------------------- | :------- | :------------------------------------------------------------------------ |
-| `model`                 | `string` | The identifier of the model to be called (for example, `gemini-2.5-pro`). |
-| `generateContentConfig` | `object` | The configuration object passed to the `@google/genai` SDK.               |
+| 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)
 
@@ -144,7 +142,7 @@ Directly maps to the SDK's `GenerateContentConfig`. Common parameters include:
 - **`topP`**: (`number`) Nucleus sampling probability.
 - **`maxOutputTokens`**: (`number`) Limit on generated response length.
 - **`thinkingConfig`**: (`object`) Configuration for models with reasoning
-  capabilities (for example, `thinkingBudget`, `includeThoughts`).
+  capabilities (e.g., `thinkingBudget`, `includeThoughts`).
 
 ## 5. Practical Examples
 
@@ -172,7 +170,7 @@ configuration but enforcing zero temperature.
 ### Agent-Specific Parameter Injection
 
 Enforce extended thinking budgets for a specific agent without altering the
-global default, for example for the `codebaseInvestigator`.
+global default, e.g. for the `codebaseInvestigator`.
 
 ```json
 "modelConfigs": {

docs/cli/model-routing.md

@@ -10,8 +10,8 @@ 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 (for example, due
-    to quota or server errors), the CLI will initiate the fallback process.
+1.  **Model failure:** If the currently selected model fails (e.g., due to quota
+    or server errors), the CLI will initiate 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
@@ -34,11 +34,11 @@ Gemini CLI will use a locally-running **Gemma** model to make routing decisions
 reduce costs associated with hosted model usage while offering similar routing
 decision latency and quality.
 
-The easiest way to set this up is using the automated `gemini gemma setup`
-command.
+In order to use this feature, the local Gemma model **must** be served behind a
+Gemini API and accessible via HTTP at an endpoint configured in `settings.json`.
 
 For more details on how to configure local model routing, see
-[`gemini gemma` — Local Model Routing Setup](../core/gemma-setup.md).
+[Local Model Routing](../core/local-model-routing.md).
 
 ### Model selection precedence
 

docs/cli/model-steering.md

@@ -19,7 +19,7 @@ Model steering is an experimental feature and is disabled by default. You can
 enable it using the `/settings` command or by updating your `settings.json`
 file.
 
-1.  Type `/settings` in Gemini CLI.
+1.  Type `/settings` in the Gemini CLI.
 2.  Search for **Model Steering**.
 3.  Set the value to **true**.
 

docs/cli/plan-mode.md

@@ -64,7 +64,6 @@ Gemini CLI takes action.
     reach an informal agreement on the approach before proceeding.
 3.  **Review the plan:** Once you've agreed on the strategy, Gemini CLI creates
     a detailed implementation plan as a Markdown file in your plans directory.
-
     - **View:** You can open and read this file to understand the proposed
       changes.
     - **Edit:** Press `Ctrl+X` to open the plan directly in your configured
@@ -131,14 +130,13 @@ These are the only allowed tools:
   [`cli_help`](../core/subagents.md#cli-help-agent)
 - **Interaction:** [`ask_user`](../tools/ask-user.md)
 - **MCP tools (Read):** Read-only [MCP tools](../tools/mcp-server.md) (for
-  example, `github_read_issue`, `postgres_read_schema`) and core
-  [MCP resource tools](../tools/mcp-resources.md) (`list_mcp_resources`,
-  `read_mcp_resource`) are allowed.
+  example, `github_read_issue`, `postgres_read_schema`) are allowed.
 - **Planning (Write):**
   [`write_file`](../tools/file-system.md#3-write_file-writefile) and
   [`replace`](../tools/file-system.md#6-replace-edit) only allowed for `.md`
   files in the `~/.gemini/tmp/<project>/<session-id>/plans/` directory or your
   [custom plans directory](#custom-plan-directory-and-policies).
+- **Memory:** [`save_memory`](../tools/memory.md)
 - **Skills:** [`activate_skill`](../cli/skills.md) (allows loading specialized
   instructions and resources in a read-only manner)
 
@@ -316,8 +314,8 @@ Hooks such as `BeforeTool` or `AfterTool` can be configured to intercept the
 > [!WARNING] When hooks are triggered by **tool executions**, they do **not**
 > run when you manually toggle Plan Mode using the `/plan` command or the
 > `Shift+Tab` keyboard shortcut. If you need hooks to execute on mode changes,
-> ensure the transition is initiated by the agent (for example, by asking "start
-> a plan for...").
+> ensure the transition is initiated by the agent (e.g., by asking "start a plan
+> for...").
 
 #### Example: Archive approved plans to GCS (`AfterTool`)
 
@@ -329,11 +327,8 @@ Storage whenever Gemini CLI exits Plan Mode to start the implementation.
 
 ```bash
 #!/usr/bin/env bash
-# Extract the plan filename from the tool input JSON
-plan_filename=$(jq -r '.tool_input.plan_filename // empty')
-
-# Construct the absolute path using the GEMINI_PLANS_DIR environment variable
-plan_path="$GEMINI_PLANS_DIR/$plan_filename"
+# Extract the plan path from the tool input JSON
+plan_path=$(jq -r '.tool_input.plan_path // empty')
 
 if [ -f "$plan_path" ]; then
   # Generate a unique filename using a timestamp
@@ -359,7 +354,7 @@ To register this `AfterTool` hook, add it to your `settings.json`:
           {
             "name": "archive-plan",
             "type": "command",
-            "command": "~/.gemini/hooks/archive-plan.sh"
+            "command": "./.gemini/hooks/archive-plan.sh"
           }
         ]
       }
@@ -446,10 +441,6 @@ on the current phase of your task:
     switches to a high-speed **Flash** model. This provides a faster, more
     responsive experience during the implementation of the plan.
 
-If the high-reasoning model is unavailable or you don't have access to it,
-Gemini CLI automatically and silently falls back to a faster model to ensure
-your workflow isn't interrupted.
-
 This behavior is enabled by default to provide the best balance of quality and
 performance. You can disable this automatic switching in your settings:
 
@@ -470,8 +461,7 @@ associated plan files and task trackers.
 
 - **Default behavior:** Sessions (and their plans) are retained for **30 days**.
 - **Configuration:** You can customize this behavior via the `/settings` command
-  (search for **Enable Session Cleanup** or **Keep chat history**) or in your
-  `settings.json` file. See
+  (search for **Session Retention**) or in your `settings.json` file. See
   [session retention](../cli/session-management.md#session-retention) for more
   details.
 

docs/cli/sandbox.md

@@ -1,11 +1,11 @@
-# Sandboxing in Gemini CLI
+# Sandboxing in the Gemini CLI
 
-This document provides a guide to sandboxing in Gemini CLI, including
+This document provides a guide to sandboxing in the Gemini CLI, including
 prerequisites, quickstart, and configuration.
 
 ## Prerequisites
 
-Before using sandboxing, you need to install and set up Gemini CLI:
+Before using sandboxing, you need to install and set up the Gemini CLI:
 
 ```bash
 npm install -g @google/gemini-cli
@@ -31,53 +31,6 @@ The benefits of sandboxing include:
 - **Safety**: Reduce risk when working with untrusted code or experimental
   commands.
 
-## Quickstart
-
-You can enable sandboxing using a command flag, environment variable, or
-configuration file.
-
-### Using the command flag
-
-```bash
-gemini -s -p "analyze the code structure"
-```
-
-### Using an environment variable
-
-**macOS/Linux**
-
-```bash
-export GEMINI_SANDBOX=true
-gemini -p "run the test suite"
-```
-
-**Windows (PowerShell)**
-
-```powershell
-$env:GEMINI_SANDBOX="true"
-gemini -p "run the test suite"
-```
-
-### Configuring via settings.json
-
-```json
-{
-  "tools": {
-    "sandbox": "docker"
-  }
-}
-```
-
-## Configuration
-
-Enable sandboxing using one of the following methods (in order of precedence):
-
-1. **Command flag**: `-s` or `--sandbox`
-2. **Environment variable**:
-   `GEMINI_SANDBOX=true|docker|podman|sandbox-exec|runsc|lxc`
-3. **Settings file**: `"sandbox": true` in the `tools` object of your
-   `settings.json` file (for example, `{"tools": {"sandbox": true}}`).
-
 ## Sandboxing methods
 
 Your ideal method of sandboxing may differ depending on your platform and your
@@ -90,92 +43,12 @@ Lightweight, built-in sandboxing using `sandbox-exec`.
 **Default profile**: `permissive-open` - restricts writes outside project
 directory but allows most other operations.
 
-Built-in profiles (set via `SEATBELT_PROFILE` env var):
-
-- `permissive-open` (default): Write restrictions, network allowed
-- `permissive-proxied`: Write restrictions, network via proxy
-- `restrictive-open`: Strict restrictions, network allowed
-- `restrictive-proxied`: Strict restrictions, network via proxy
-- `strict-open`: Read and write restrictions, network allowed
-- `strict-proxied`: Read and write restrictions, network via proxy
-
 ### 2. Container-based (Docker/Podman)
 
-Cross-platform sandboxing with complete process isolation using container
-technology. By default, it uses the `ghcr.io/google/gemini-cli:latest` image.
+Cross-platform sandboxing with complete process isolation.
 
-**Prerequisites:**
-
-- Docker or Podman must be installed and running on your system.
-
-**How it works (Workspace directory):**
-
-Inside the sandbox container, your current working directory is mounted at the
-**exact same absolute path** as it is on your host machine. For example, if you
-run the CLI from `/Users/you/project` on your host machine, the sandbox will
-mount your local project folder and operate within `/Users/you/project` inside
-the container. This allows the AI to seamlessly read and modify your project
-files while remaining isolated from the rest of your system.
-
-**Quick setup:**
-
-To enable Docker sandboxing, run Gemini CLI with the sandbox flag and specify
-Docker as the provider:
-
-```bash
-# Using the environment variable (Recommended)
-export GEMINI_SANDBOX=docker
-gemini -p "build the project"
-
-# Or configure it permanently in your settings.json
-# {"tools": {"sandbox": "docker"}}
-```
-
-**Customizing the Sandbox Image:**
-
-If your project requires specific dependencies, you can specify a custom image
-name or have Gemini CLI build one for you automatically. You can use any Docker
-or Podman image as your sandbox, provided it has standard shell utilities (like
-`bash`) available.
-
-**Option A: Using an existing custom image (e.g., Artifact Registry)**
-
-To configure a custom image that is hosted on a registry (or built locally),
-update your `settings.json` to use an object for the sandbox configuration, or
-set the `GEMINI_SANDBOX_IMAGE` environment variable.
-
-_Example: Configuring via `settings.json`_
-
-```json
-{
-  "tools": {
-    "sandbox": {
-      "command": "docker",
-      "image": "us-central1-docker.pkg.dev/my-project/my-repo/my-custom-sandbox:latest"
-    }
-  }
-}
-```
-
-_Example: Configuring via environment variable_
-
-```bash
-export GEMINI_SANDBOX_IMAGE="us-central1-docker.pkg.dev/my-project/my-repo/my-custom-sandbox:latest"
-```
-
-**Option B: Building a local custom image automatically**
-
-If you prefer to define your environment as code, you can provide a Dockerfile
-and Gemini CLI will build the image automatically.
-
-1.  Create a `.gemini/sandbox.Dockerfile` in your project root.
-2.  Ensure you have the `gh` CLI installed and authenticated (if you are using
-    the default `ghcr.io/google/gemini-cli` image as a base).
-3.  Run your command with the `BUILD_SANDBOX` environment variable set:
-
-```bash
-BUILD_SANDBOX=1 GEMINI_SANDBOX=docker gemini -p "run my custom build"
-```
+**Note**: Requires building the sandbox image locally or using a published image
+from your organization's registry.
 
 ### 3. Windows Native Sandbox (Windows only)
 
@@ -315,49 +188,59 @@ This mechanism ensures you don't have to manually re-run commands with more
 permissive sandbox settings, while still maintaining control over what the AI
 can access.
 
-### Including files outside the workspace
-
-By default, the sandbox only has access to the current project workspace. If you
-need the sandbox to have permission to operate on certain files or directories
-from the local file system outside of the project workspace, you can mount them
-using the `SANDBOX_MOUNTS` environment variable.
-
-Provide a comma-separated list of mount definitions in the format
-`from:to:opts`. If `to` is omitted, it defaults to the same path as `from`. If
-`opts` is omitted, it defaults to `ro` (read-only). Note that the `from` path
-must be an absolute path.
-
-**Example**:
+## Quickstart
 
 ```bash
-export SANDBOX_MOUNTS="/path/on/host:/path/in/container:rw,/another/path:ro"
+# Enable sandboxing with command flag
+gemini -s -p "analyze the code structure"
 ```
 
-## Running inside a Docker container
+**Use environment variable**
 
-If you are running Gemini CLI itself from within an official or custom Docker
-container and want to enable sandboxing, you must share the host's Docker socket
-and ensure your workspace paths align.
-
-1.  **Mount the Docker socket**: Map `/var/run/docker.sock` so the CLI can spawn
-    sibling sandbox containers via the host's Docker daemon.
-2.  **Align workspace paths**: The path to your workspace inside the container
-    must exactly match the absolute path on the host. Because the sandbox
-    container is spawned by the host's Docker daemon, it resolves volume mounts
-    against the host file system.
-
-**Example**:
+**macOS/Linux**
 
 ```bash
-docker run -it \
-  -v /var/run/docker.sock:/var/run/docker.sock \
-  -v /absolute/path/on/host/project:/absolute/path/on/host/project \
-  -w /absolute/path/on/host/project \
-  -e GEMINI_SANDBOX=docker \
-  ghcr.io/google/gemini-cli:latest
+export GEMINI_SANDBOX=true
+gemini -p "run the test suite"
 ```
 
-## Advanced settings
+**Windows (PowerShell)**
+
+```powershell
+$env:GEMINI_SANDBOX="true"
+gemini -p "run the test suite"
+```
+
+**Configure in settings.json**
+
+```json
+{
+  "tools": {
+    "sandbox": "docker"
+  }
+}
+```
+
+## Configuration
+
+### Enable sandboxing (in order of precedence)
+
+1. **Command flag**: `-s` or `--sandbox`
+2. **Environment variable**:
+   `GEMINI_SANDBOX=true|docker|podman|sandbox-exec|runsc|lxc`
+3. **Settings file**: `"sandbox": true` in the `tools` object of your
+   `settings.json` file (e.g., `{"tools": {"sandbox": true}}`).
+
+### macOS Seatbelt profiles
+
+Built-in profiles (set via `SEATBELT_PROFILE` env var):
+
+- `permissive-open` (default): Write restrictions, network allowed
+- `permissive-proxied`: Write restrictions, network via proxy
+- `restrictive-open`: Strict restrictions, network allowed
+- `restrictive-proxied`: Strict restrictions, network via proxy
+- `strict-open`: Read and write restrictions, network allowed
+- `strict-proxied`: Read and write restrictions, network via proxy
 
 ### Custom sandbox flags
 
@@ -396,7 +279,7 @@ export SANDBOX_FLAGS="--flag1 --flag2=value"
 $env:SANDBOX_FLAGS="--flag1 --flag2=value"
 ```
 
-### Linux UID/GID handling
+## Linux UID/GID handling
 
 The sandbox automatically handles user permissions on Linux. Override these
 permissions with:
@@ -426,9 +309,7 @@ $env:SANDBOX_SET_UID_GID="false"  # Disable UID/GID mapping
 
 **Missing commands**
 
-- Add to a custom Dockerfile. Automatic `BUILD_SANDBOX` builds are only
-  available when running Gemini CLI from source; npm installs need a prebuilt
-  image instead.
+- Add to custom Dockerfile.
 - Install via `sandbox.bashrc`.
 
 **Network issues**

docs/cli/session-management.md

@@ -202,7 +202,6 @@ becoming too large and expensive.
   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

@@ -24,23 +24,20 @@ they appear in the UI.
 
 ### General
 
-| UI Label                      | Setting                            | Description                                                                                                                                                                                                                                                   | Default     |
-| ----------------------------- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- |
-| Vim Mode                      | `general.vimMode`                  | Enable Vim keybindings                                                                                                                                                                                                                                        | `false`     |
-| Default Approval Mode         | `general.defaultApprovalMode`      | The default approval mode for tool execution. 'default' prompts for approval, 'auto_edit' auto-approves edit tools, and 'plan' is read-only mode. YOLO mode (auto-approve all actions) can only be enabled via command line (--yolo or --approval-mode=yolo). | `"default"` |
-| Enable Auto Update            | `general.enableAutoUpdate`         | Enable automatic updates.                                                                                                                                                                                                                                     | `true`      |
-| Enable Terminal Notifications | `general.enableNotifications`      | Enable terminal run-event notifications for action-required prompts and session completion.                                                                                                                                                                   | `false`     |
-| Terminal Notification Method  | `general.notificationMethod`       | How to send terminal notifications.                                                                                                                                                                                                                           | `"auto"`    |
-| Enable Plan Mode              | `general.plan.enabled`             | Enable Plan Mode for read-only safety during planning.                                                                                                                                                                                                        | `true`      |
-| Plan Directory                | `general.plan.directory`           | The directory where planning artifacts are stored. If not specified, defaults to the system temporary directory. A custom directory requires a policy to allow write access in Plan Mode.                                                                     | `undefined` |
-| Plan Model Routing            | `general.plan.modelRouting`        | Automatically switch between Pro and Flash models based on Plan Mode status. Uses Pro for the planning phase and Flash for the implementation phase.                                                                                                          | `true`      |
-| Retry Fetch Errors            | `general.retryFetchErrors`         | Retry on "exception TypeError: fetch failed sending request" errors.                                                                                                                                                                                          | `true`      |
-| Max Chat Model Attempts       | `general.maxAttempts`              | Maximum number of attempts for requests to the main chat model. Cannot exceed 10.                                                                                                                                                                             | `10`        |
-| Debug Keystroke Logging       | `general.debugKeystrokeLogging`    | Enable debug logging of keystrokes to the console.                                                                                                                                                                                                            | `false`     |
-| Enable Session Cleanup        | `general.sessionRetention.enabled` | Enable automatic session cleanup                                                                                                                                                                                                                              | `true`      |
-| Keep chat history             | `general.sessionRetention.maxAge`  | Automatically delete chats older than this time period (e.g., "30d", "7d", "24h", "1w")                                                                                                                                                                       | `"30d"`     |
-| Topic & Update Narration      | `general.topicUpdateNarration`     | Enable the Topic & Update communication model for reduced chattiness and structured progress reporting.                                                                                                                                                       | `true`      |
-| Log RAG Snippets              | `general.logRagSnippets`           | Log full Code Customization (RAG) retrieved snippets to a local file for debugging.                                                                                                                                                                           | `false`     |
+| UI Label                | Setting                            | Description                                                                                                                                                                                                                                                   | Default     |
+| ----------------------- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- |
+| Vim Mode                | `general.vimMode`                  | Enable Vim keybindings                                                                                                                                                                                                                                        | `false`     |
+| Default Approval Mode   | `general.defaultApprovalMode`      | The default approval mode for tool execution. 'default' prompts for approval, 'auto_edit' auto-approves edit tools, and 'plan' is read-only mode. YOLO mode (auto-approve all actions) can only be enabled via command line (--yolo or --approval-mode=yolo). | `"default"` |
+| Enable Auto Update      | `general.enableAutoUpdate`         | Enable automatic updates.                                                                                                                                                                                                                                     | `true`      |
+| Enable Notifications    | `general.enableNotifications`      | Enable run-event notifications for action-required prompts and session completion.                                                                                                                                                                            | `false`     |
+| Enable Plan Mode        | `general.plan.enabled`             | Enable Plan Mode for read-only safety during planning.                                                                                                                                                                                                        | `true`      |
+| Plan Directory          | `general.plan.directory`           | The directory where planning artifacts are stored. If not specified, defaults to the system temporary directory. A custom directory requires a policy to allow write access in Plan Mode.                                                                     | `undefined` |
+| Plan Model Routing      | `general.plan.modelRouting`        | Automatically switch between Pro and Flash models based on Plan Mode status. Uses Pro for the planning phase and Flash for the implementation phase.                                                                                                          | `true`      |
+| Retry Fetch Errors      | `general.retryFetchErrors`         | Retry on "exception TypeError: fetch failed sending request" errors.                                                                                                                                                                                          | `true`      |
+| Max Chat Model Attempts | `general.maxAttempts`              | Maximum number of attempts for requests to the main chat model. Cannot exceed 10.                                                                                                                                                                             | `10`        |
+| Debug Keystroke Logging | `general.debugKeystrokeLogging`    | Enable debug logging of keystrokes to the console.                                                                                                                                                                                                            | `false`     |
+| Enable Session Cleanup  | `general.sessionRetention.enabled` | Enable automatic session cleanup                                                                                                                                                                                                                              | `true`      |
+| Keep chat history       | `general.sessionRetention.maxAge`  | Automatically delete chats older than this time period (e.g., "30d", "7d", "24h", "1w")                                                                                                                                                                       | `"30d"`     |
 
 ### Output
 
@@ -81,7 +78,6 @@ they appear in the UI.
 | Terminal Buffer                      | `ui.terminalBuffer`                    | Use the new terminal buffer architecture for rendering.                                                                                                           | `false` |
 | Use Background Color                 | `ui.useBackgroundColor`                | Whether to use background colors in the UI.                                                                                                                       | `true`  |
 | Incremental Rendering                | `ui.incrementalRendering`              | Enable incremental rendering for the UI. This option will reduce flickering but may cause rendering artifacts. Only supported when useAlternateBuffer is enabled. | `true`  |
-| Max Scrollback Length                | `ui.maxScrollbackLength`               | Maximum number of lines to keep in the terminal scrollback buffer.                                                                                                | `1000`  |
 | Show Spinner                         | `ui.showSpinner`                       | Show the spinner during operations.                                                                                                                               | `true`  |
 | Loading Phrases                      | `ui.loadingPhrases`                    | What to show while the model is working: tips, witty comments, all, or off.                                                                                       | `"off"` |
 | Error Verbosity                      | `ui.errorVerbosity`                    | Controls whether recoverable errors are hidden (low) or fully shown (full).                                                                                       | `"low"` |
@@ -160,28 +156,20 @@ they appear in the UI.
 | UI Label                          | Setting                        | Description                                                                                                                                                                                                           | Default |
 | --------------------------------- | ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- |
 | Auto Configure Max Old Space Size | `advanced.autoConfigureMemory` | Automatically configure Node.js memory limits. Note: Because memory is allocated during the initial process boot, this setting is only read from the global user settings file and ignores workspace-level overrides. | `true`  |
-| Ignore Local .env                 | `advanced.ignoreLocalEnv`      | Whether to ignore generic .env files in the project directory.                                                                                                                                                        | `false` |
 
 ### Experimental
 
-| UI Label                                             | Setting                                         | Description                                                                                                                                                                                                                                                            | Default              |
-| ---------------------------------------------------- | ----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------- |
-| Gemma Models                                         | `experimental.gemma`                            | Enable access to Gemma 4 models via Gemini API.                                                                                                                                                                                                                        | `true`               |
-| Voice Mode                                           | `experimental.voiceMode`                        | Enable experimental voice dictation and commands (/voice, /voice model).                                                                                                                                                                                               | `false`              |
-| Voice Activation Mode                                | `experimental.voice.activationMode`             | How to trigger voice recording with the Space key.                                                                                                                                                                                                                     | `"push-to-talk"`     |
-| Voice Transcription Backend                          | `experimental.voice.backend`                    | The backend to use for voice transcription. Note: When using the Gemini Live backend, voice recordings are sent to Google Cloud for transcription.                                                                                                                     | `"gemini-live"`      |
-| Whisper Model                                        | `experimental.voice.whisperModel`               | The Whisper model to use for local transcription.                                                                                                                                                                                                                      | `"ggml-base.en.bin"` |
-| Voice Stop Grace Period (ms)                         | `experimental.voice.stopGracePeriodMs`          | How long to wait for final transcription after stopping recording.                                                                                                                                                                                                     | `4000`               |
-| Enable Git Worktrees                                 | `experimental.worktrees`                        | Enable automated Git worktree management for parallel work.                                                                                                                                                                                                            | `false`              |
-| Use OSC 52 Paste                                     | `experimental.useOSC52Paste`                    | Use OSC 52 for pasting. This may be more robust than the default system when using remote terminal sessions (if your terminal is configured to allow it).                                                                                                              | `false`              |
-| Use OSC 52 Copy                                      | `experimental.useOSC52Copy`                     | Use OSC 52 for copying. This may be more robust than the default system when using remote terminal sessions (if your terminal is configured to allow it).                                                                                                              | `false`              |
-| Model Steering                                       | `experimental.modelSteering`                    | Enable model steering (user hints) to guide the model during tool execution.                                                                                                                                                                                           | `false`              |
-| Direct Web Fetch                                     | `experimental.directWebFetch`                   | Enable web fetch behavior that bypasses LLM summarization.                                                                                                                                                                                                             | `false`              |
-| Enable Gemma Model Router                            | `experimental.gemmaModelRouter.enabled`         | Enable the Gemma Model Router (experimental). Requires a local endpoint serving Gemma via the Gemini API using LiteRT-LM shim.                                                                                                                                         | `false`              |
-| Auto-start LiteRT Server                             | `experimental.gemmaModelRouter.autoStartServer` | Automatically start the LiteRT-LM server when Gemini CLI starts and the Gemma router is enabled.                                                                                                                                                                       | `false`              |
-| Auto Memory                                          | `experimental.autoMemory`                       | Automatically extract memory patches and skills from past sessions in the background. Every change is written as a unified diff `.patch` file under `<projectMemoryDir>/.inbox/<kind>/` and held for review in /memory inbox; nothing is applied until you approve it. | `false`              |
-| Use the generalist profile to manage agent contexts. | `experimental.generalistProfile`                | Suitable for general coding and software development tasks.                                                                                                                                                                                                            | `false`              |
-| Enable Context Management                            | `experimental.contextManagement`                | Enable logic for context management.                                                                                                                                                                                                                                   | `false`              |
+| UI Label                                             | Setting                             | Description                                                                                                                                               | Default |
+| ---------------------------------------------------- | ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- |
+| Enable Git Worktrees                                 | `experimental.worktrees`            | Enable automated Git worktree management for parallel work.                                                                                               | `false` |
+| Use OSC 52 Paste                                     | `experimental.useOSC52Paste`        | Use OSC 52 for pasting. This may be more robust than the default system when using remote terminal sessions (if your terminal is configured to allow it). | `false` |
+| Use OSC 52 Copy                                      | `experimental.useOSC52Copy`         | Use OSC 52 for copying. This may be more robust than the default system when using remote terminal sessions (if your terminal is configured to allow it). | `false` |
+| Model Steering                                       | `experimental.modelSteering`        | Enable model steering (user hints) to guide the model during tool execution.                                                                              | `false` |
+| Direct Web Fetch                                     | `experimental.directWebFetch`       | Enable web fetch behavior that bypasses LLM summarization.                                                                                                | `false` |
+| Memory Manager Agent                                 | `experimental.memoryManager`        | Replace the built-in save_memory tool with a memory manager subagent that supports adding, removing, de-duplicating, and organizing memories.             | `false` |
+| Use the generalist profile to manage agent contexts. | `experimental.generalistProfile`    | Suitable for general coding and software development tasks.                                                                                               | `false` |
+| Enable Context Management                            | `experimental.contextManagement`    | Enable logic for context management.                                                                                                                      | `false` |
+| Topic & Update Narration                             | `experimental.topicUpdateNarration` | Enable the experimental Topic & Update communication model for reduced chattiness and structured progress reporting.                                      | `false` |
 
 ### Skills
 

docs/cli/skills-best-practices.md

@@ -1,78 +0,0 @@
-# Agent Skill best practices
-
-Create high-quality, reliable Agent Skills by following these established design
-principles and patterns.
-
-## Design for discovery
-
-The most important part of a skill is its `description`. This is the only
-information the model has before activation.
-
-- **Be specific**: Use keywords that are likely to appear in user prompts (for
-  example, "audit," "security," "refactor," "migration").
-- **Define the trigger**: Clearly state _when_ the skill should be used (for
-  example, "Use this skill when the user asks to review a PR for performance
-  regressions").
-- **Avoid overlap**: Ensure your skill descriptions are distinct from one
-  another and from the general capabilities of the model.
-
-## Progressive disclosure
-
-The "context window" is a shared resource. Use a three-level loading system to
-manage context efficiently.
-
-1.  **Metadata (name + description)**: Always in context (~100 words).
-2.  **`SKILL.md` body**: Loaded only after the skill triggers (<5k words).
-3.  **Bundled resources**: Loaded only as needed by the model.
-
-**Best practice**: Keep the `SKILL.md` body focused on core procedural
-instructions. Move detailed reference material, schemas, and examples into
-separate files in a `references/` directory.
-
-## Degrees of freedom
-
-Match the level of instruction specificity to the task's fragility.
-
-- **High freedom (text-based instructions)**: Use when multiple approaches are
-  valid or decisions depend heavily on context.
-- **Medium freedom (pseudocode or scripts with parameters)**: Use when a
-  preferred pattern exists but some variation is acceptable.
-- **Low freedom (specific scripts, few parameters)**: Use when operations are
-  fragile and error-prone, or a specific sequence MUST be followed.
-
-## Bundle resources effectively
-
-Leverage the skill's ability to include scripts and assets to extend the agent's
-capabilities.
-
-- **Use scripts for deterministic tasks**: If a task can be automated with a
-  script (for example, running a linter, fetching data from an API), bundle it
-  in the `scripts/` folder.
-- **Agentic ergonomics**: Ensure scripts output LLM-friendly stdout. Suppress
-  verbose tracebacks and provide clear, concise success/failure messages.
-- **Provide templates**: Include common file headers or boilerplate code in the
-  `assets/` folder to ensure the agent produces consistent output.
-
-## Anatomy of a great skill
-
-A well-structured skill directory organizes its resources into specialized
-sub-folders.
-
-```text
-my-skill/
-├── SKILL.md       (Required) Core instructions and metadata
-├── scripts/       (Optional) Executable logic (Node.js, Python, etc.)
-├── references/    (Optional) Documentation to be loaded as needed
-└── assets/        (Optional) Templates and non-executable resources
-```
-
-## Security and privacy
-
-Design your skills with security in mind to protect your workspace and data.
-
-- **Avoid hardcoded secrets**: Never include API keys or passwords in your
-  skill's scripts or documentation.
-- **Review third-party skills**: Inspect the `SKILL.md` and scripts of any skill
-  before installing it from an untrusted source.
-- **Limit scope**: Design skills to be as focused as possible to minimize the
-  potential impact of errors.

docs/cli/skills.md

@@ -1,21 +1,112 @@
 # Agent Skills
 
-Agent Skills let you extend Gemini CLI with specialized expertise, procedural
-workflows, and task-specific resources. Based on the
+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.
 
-Unlike general context files ([GEMINI.md](./gemini-md.md)), which provide
+## Overview
+
+Unlike general context files ([`GEMINI.md`](./gemini-md.md)), which provide
 persistent workspace-wide background, Skills represent **on-demand expertise**.
-This lets Gemini CLI maintain a vast library of specialized capabilities—such as
-security auditing, cloud deployments, or codebase migrations—without cluttering
-the model's immediate context window.
+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.
 
-## How it works
+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.
 
-The lifecycle of an Agent Skill involves discovery, activation, and conditional
-resource access.
+## 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.  **Workspace Skills**: Located in `.gemini/skills/` or the `.agents/skills/`
+    alias. Workspace skills are typically committed to version control and
+    shared with the team.
+2.  **User Skills**: Located in `~/.gemini/skills/` or the `~/.agents/skills/`
+    alias. These are personal skills available across all your workspaces.
+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: **Workspace > User > Extension**.
+
+Within the same tier (user or workspace), the `.agents/skills/` alias takes
+precedence over the `.gemini/skills/` directory. This generic alias provides an
+intuitive path for managing agent-specific expertise that remains compatible
+across different AI agent tools.
+
+## 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 link <path>`: Links agent skills from a local directory via symlink.
+- `/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.
+
+<!-- prettier-ignore -->
+> [!NOTE]
+> `/skills disable` and `/skills enable` default to the `user` scope. Use
+> `--scope workspace` to manage workspace-specific settings.
+
+### From the Terminal
+
+The `gemini skills` command provides management utilities:
+
+```bash
+# List all discovered skills
+gemini skills list
+
+# Link agent skills from a local directory via symlink
+# Discovers skills (SKILL.md or */SKILL.md) and creates symlinks in ~/.gemini/skills
+# (or ~/.agents/skills)
+gemini skills link /path/to/my-skills-repo
+
+# Link to the workspace scope (.gemini/skills or .agents/skills)
+gemini skills link /path/to/my-skills-repo --scope workspace
+
+# Install a skill from a Git repository, local directory, or zipped skill file (.skill)
+# Uses the user scope by default (~/.gemini/skills or ~/.agents/skills)
+gemini skills install https://github.com/user/repo.git
+gemini skills install /path/to/local/skill
+gemini skills install /path/to/local/my-expertise.skill
+
+# Install a specific skill from a monorepo or subdirectory using --path
+gemini skills install https://github.com/my-org/my-skills.git --path skills/frontend-design
+
+# Install to the workspace scope (.gemini/skills or .agents/skills)
+gemini skills install /path/to/skill --scope workspace
+
+# Uninstall a skill by name
+gemini skills uninstall my-expertise --scope workspace
+
+# Enable a skill (globally)
+gemini skills enable my-expertise
+
+# Disable a skill. Can use --scope to specify workspace or user (defaults to workspace)
+gemini skills disable my-expertise --scope workspace
+```
+
+## How it Works
 
 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
@@ -32,110 +123,14 @@ resource access.
 5.  **Execution**: The model proceeds with the specialized expertise active. It
     is instructed to prioritize the skill's procedural guidance within reason.
 
-## Discovery tiers
+### Skill activation
 
-Gemini CLI discovers skills from several locations, following a specific order
-of precedence (lowest to highest):
+Once a skill is activated (typically by Gemini identifying a task that matches
+the skill's description and your approval), its specialized instructions and
+resources are loaded into the agent's context. A skill remains active and its
+guidance is prioritized for the duration of the session.
 
-1.  **Built-in skills**: Standard skills included with Gemini CLI that provide
-    foundational capabilities.
-2.  **Extension skills**: Skills bundled within installed
-    [extensions](../extensions/index.md).
-3.  **User skills**: Located in `~/.gemini/skills/` or the `~/.agents/skills/`
-    alias.
-4.  **Workspace skills**: Located in `.gemini/skills/` or the `.agents/skills/`
-    alias. Workspace skills are shared with your team via version control.
+## Creating your own skills
 
-### Precedence and aliases
-
-If multiple skills share the same name, the version from the higher-precedence
-location is used. Within the same tier (user or workspace), the
-`.agents/skills/` alias takes precedence over the `.gemini/skills/` directory.
-
-The `.agents/skills/` alias provides an interoperable path for managing
-agent-specific expertise that remains compatible across different AI tools.
-
-## Key benefits
-
-Agent Skills provide several advantages for managing specialized knowledge and
-complex workflows.
-
-- **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.
-
-<!-- prettier-ignore -->
-> [!NOTE]
-> `/skills disable` and `/skills enable` default to the `user` scope. Use
-> `--scope workspace` to manage workspace-specific settings.
-
-To see all available skills in your current session, use the `/skills list`
-command.
-
-## Managing skills
-
-You can manage Agent Skills through interactive session commands or directly
-from your terminal.
-
-### In an interactive session
-
-Use the `/skills` slash command to view and manage available expertise:
-
-- `/skills list [all] [nodesc]`: Shows discovered skills. Use `all` to include
-  built-in skills and `nodesc` to hide descriptions.
-- `/skills link <path> [--scope user|workspace]`: Links skills from a local
-  directory.
-- `/skills disable <name>`: Prevents a specific skill from being used.
-- `/skills enable <name>`: Re-enables a disabled skill.
-- `/skills reload` (or `/skills refresh`): Refreshes the list of discovered
-  skills from all tiers.
-
-### From the terminal
-
-The `gemini skills` command provides management utilities:
-
-```bash
-# List all discovered skills. Use --all to include built-in skills.
-gemini skills list --all
-
-# Install a skill from a Git repository or local directory.
-# Use --consent to skip the security confirmation prompt.
-gemini skills install https://github.com/user/repo.git --consent
-
-# Uninstall a skill.
-gemini skills uninstall my-skill --scope workspace
-```
-
-#### Command options
-
-The skill management commands support several global and command-specific
-options.
-
-- `--scope`: Either `user` (global, default) or `workspace` (local to the
-  project).
-- `--path`: The sub-directory within a Git repository containing the skill.
-- `--consent`: Acknowledge security risks and skip the interactive confirmation
-  during installation.
-
-For more details on CLI commands, see the
-[CLI reference](./cli-reference.md#skills-management).
-
-## Next steps
-
-Explore these resources to refine your skills and understand the framework
-better.
-
-- [Get started with Agent Skills](./tutorials/skills-getting-started.md): A
-  quick walkthrough of triggering and using skills.
-- [Creating Agent Skills](./creating-skills.md): Create your first skill and
-  bundle custom logic.
-- [Using Agent Skills](./using-agent-skills.md): Learn how to leverage built-in
-  and custom skills.
-- [Best practices](./skills-best-practices.md): Learn strategies for building
-  effective skills.
+To create your own skills, see the [Create Agent Skills](./creating-skills.md)
+guide.

docs/cli/system-prompt.md

@@ -24,20 +24,18 @@ project-specific behavior or create a customized persona.
 
 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.mdx#persisting-environment-variables).
+[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 (for example, `~/my-system.md`).
+  - 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.
@@ -53,7 +51,7 @@ error with: `missing system prompt file '<path>'`.
   - 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`
+  - `GEMINI_SYSTEM_MD=~/prompts/SYSTEM.md gemini`
 
 ## UI indicator
 
@@ -72,7 +70,7 @@ dynamically include built-in content:
 - `${AvailableTools}`: Injects a bulleted list of all currently enabled tool
   names.
 - Tool Name Variables: Injects the actual name of a tool using the pattern:
-  `${toolName}_ToolName` (for example, `${write_file_ToolName}`,
+  `${toolName}_ToolName` (e.g., `${write_file_ToolName}`,
   `${run_shell_command_ToolName}`).
 
   This pattern is generated dynamically for all available tools.
@@ -104,17 +102,17 @@ safety and workflow rules.
 
 This creates the file and writes the current built‑in system prompt to it.
 
-## Best practices: system.md vs GEMINI.md
+## Best practices: SYSTEM.md vs GEMINI.md
 
-- system.md (firmware):
+- 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.
+  - Evolves per task; relies on SYSTEM.md for safe execution.
 
-Keep system.md minimal but complete for safety and tool operation. Keep
+Keep SYSTEM.md minimal but complete for safety and tool operation. Keep
 GEMINI.md focused on high‑level guidance and project specifics.
 
 ## Troubleshooting

docs/cli/telemetry.md

@@ -35,18 +35,17 @@ The observability system provides:
 You control telemetry behavior through the `.gemini/settings.json` file.
 Environment variables can override these settings.
 
-| Setting        | Environment Variable              | Description                                         | Values            | Default                 |
-| -------------- | --------------------------------- | --------------------------------------------------- | ----------------- | ----------------------- |
-| `enabled`      | `GEMINI_TELEMETRY_ENABLED`        | Enable or disable telemetry                         | `true`/`false`    | `false`                 |
-| `traces`       | `GEMINI_TELEMETRY_TRACES_ENABLED` | Enable detailed attribute tracing                   | `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`                 |
-| -              | `GEMINI_CLI_SURFACE`              | Optional custom label for traffic reporting         | string            | -                       |
+| 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`                 |
+| -              | `GEMINI_CLI_SURFACE`             | Optional custom label for traffic reporting         | string            | -                       |
 
 **Note on boolean environment variables:** For boolean settings like `enabled`,
 setting the environment variable to `true` or `1` enables the feature.
@@ -64,7 +63,6 @@ and Cloud Logging.
 You must complete several setup steps before enabling Google Cloud telemetry.
 
 1.  Set your Google Cloud project ID:
-
     - To send telemetry to a separate project:
 
       **macOS/Linux**
@@ -94,10 +92,8 @@ You must complete several setup steps before enabling Google Cloud telemetry.
       ```
 
 2.  Authenticate with Google Cloud using one of these methods:
-
     - **Method A: Application Default Credentials (ADC)**: Use this method for
       service accounts or standard `gcloud` authentication.
-
       - For user accounts:
         ```bash
         gcloud auth application-default login
@@ -115,7 +111,6 @@ You must complete several setup steps before enabling Google Cloud telemetry.
         ```powershell
         $env:GOOGLE_APPLICATION_CREDENTIALS="C:\path\to\your\service-account.json"
         ```
-
     * **Method B: CLI Auth** (Direct export only): Simplest method for local
       users. Gemini CLI uses the same OAuth credentials you used for login. To
       enable this, set `useCliAuth: true` in your `.gemini/settings.json`:
@@ -137,7 +132,6 @@ You must complete several setup steps before enabling Google Cloud telemetry.
 > telemetry will be disabled.
 
 3.  Ensure your account or service account has these IAM roles:
-
     - Cloud Trace Agent
     - Monitoring Metric Writer
     - Logs Writer
@@ -1241,12 +1235,6 @@ These metrics follow standard [OpenTelemetry GenAI semantic conventions].
 Traces provide an "under-the-hood" view of agent and backend operations. Use
 traces to debug tool interactions and optimize performance.
 
-<!-- prettier-ignore -->
-> [!NOTE]
-> Detailed trace attributes (like full prompts and tool outputs) are disabled by default
-> to minimize overhead. You must explicitly set `telemetry.traces` to `true` (or set
-> `GEMINI_TELEMETRY_TRACES_ENABLED=true`) to capture them.
-
 Every trace captures rich metadata via standard span attributes.
 
 <details open>

docs/cli/themes.md

@@ -117,8 +117,8 @@ least `background.primary`, `text.primary`, `text.secondary`, and the various
 accent colors via `text.link`, `text.accent`, and `status` to ensure a cohesive
 UI.
 
-You can use either hex codes (for example, `#FF0000`) **or** standard CSS color
-names (for example, `coral`, `teal`, `blue`) for any color value. See
+You can use either hex codes (e.g., `#FF0000`) **or** standard CSS color names
+(e.g., `coral`, `teal`, `blue`) for any color value. See
 [CSS color names](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value#color_keywords)
 for a full list of supported names.
 

docs/cli/trusted-folders.md

@@ -1,7 +1,7 @@
 # Trusted Folders
 
 The Trusted Folders feature is a security setting that gives you control over
-which projects can use the full capabilities of Gemini CLI. It prevents
+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.
 
@@ -24,12 +24,12 @@ Add the following to your user `settings.json` file:
 
 ## How it works: The trust dialog
 
-Once the feature is enabled, the first time you run Gemini CLI from a folder, a
-dialog will automatically appear, prompting you to make a choice:
+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:
 
-- **Trust folder**: Grants full trust to the current folder (for example,
+- **Trust folder**: Grants full trust to the current folder (e.g.,
   `my-project`).
-- **Trust parent folder**: Grants trust to the parent directory (for example,
+- **Trust parent folder**: Grants trust to the parent directory (e.g.,
   `safe-projects`), which automatically trusts all of its subdirectories as
   well. This is useful if you keep all your safe projects in one place.
 - **Don't trust**: Marks the folder as untrusted. The CLI will operate in a
@@ -40,9 +40,9 @@ will only be asked once per folder.
 
 ## Understanding folder contents: The discovery phase
 
-Before you make a choice, Gemini CLI performs a **discovery phase** to scan the
-folder for potential configurations. This information is displayed in the trust
-dialog to help you make an informed decision.
+Before you make a choice, the Gemini CLI performs a **discovery phase** to scan
+the folder for potential configurations. This information is displayed in the
+trust dialog to help you make an informed decision.
 
 The discovery UI lists the following categories of items found in the project:
 
@@ -63,16 +63,16 @@ attention:
   settings, such as auto-approving certain tools or disabling the security
   sandbox.
 - **Discovery Errors**: If the CLI encounters issues while scanning the folder
-  (for example, a malformed `settings.json` file), these errors will be
-  displayed prominently.
+  (e.g., a malformed `settings.json` file), these errors will be displayed
+  prominently.
 
 By reviewing these details, you can ensure that you only grant trust to projects
 that you know are safe.
 
 ## Why trust matters: The impact of an untrusted workspace
 
-When a folder is **untrusted**, Gemini CLI runs in a restricted "safe mode" to
-protect you. In this mode, the following features are disabled:
+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
     `.gemini/settings.json` file from the project. This prevents the loading of
@@ -97,36 +97,8 @@ protect you. In this mode, the following features are disabled:
     commands from .toml files, including both project-specific and global user
     commands.
 
-Granting trust to a folder unlocks the full functionality of Gemini CLI for that
-workspace.
-
-## Headless and automated environments
-
-When running Gemini CLI in a headless environment (for example, a CI/CD
-pipeline) where interactive prompts are not possible, the trust dialog cannot be
-displayed. If the folder is untrusted and the Folder Trust feature is enabled,
-the CLI will throw a `FatalUntrustedWorkspaceError` and exit.
-
-To proceed in these environments, you can bypass the trust check using one of
-the following methods:
-
-- **Command-line flag:** Run the CLI with the `--skip-trust` flag.
-- **Environment variable:** Set the `GEMINI_CLI_TRUST_WORKSPACE=true`
-  environment variable.
-
-These methods will trust the current workspace for the duration of the session
-without prompting.
-
-For detailed instructions on managing folder trust within CI/CD workflows,
-review the
-[Gemini CLI trust guidance for GitHub Actions](https://github.com/google-github-actions/run-gemini-cli/blob/main/docs/trust-guidance.md).
-
-## Overriding the trust file location
-
-By default, trust settings are saved to `~/.gemini/trustedFolders.json`. If you
-need to store this file in a different location, you can set the
-`GEMINI_CLI_TRUSTED_FOLDERS_PATH` environment variable to the desired absolute
-file path.
+Granting trust to a folder unlocks the full functionality of the Gemini CLI for
+that workspace.
 
 ## Managing your trust settings
 

docs/cli/tutorials/mcp-setup.md

@@ -102,7 +102,7 @@ The agent will:
 ## Troubleshooting
 
 - **Server won't start?** Try running the docker command manually in your
-  terminal to see if it prints an error (for example, "image not found").
+  terminal to see if it prints an error (e.g., "image not found").
 - **Tools not found?** Run `/mcp reload` to force the CLI to re-query the server
   for its capabilities.
 

docs/cli/tutorials/memory-management.md

@@ -50,7 +50,7 @@ loaded into every conversation.
 
 ### Scenario: Using the hierarchy
 
-Context is loaded hierarchically. This lets you have general rules for
+Context is loaded hierarchically. This allows you to have general rules for
 everything and specific rules for sub-projects.
 
 1.  **Global:** `~/.gemini/GEMINI.md` (Rules for _every_ project you work on).
@@ -71,8 +71,8 @@ Just tell the agent to remember something.
 
 **Prompt:** `Remember that I prefer using 'const' over 'let' wherever possible.`
 
-The agent will edit the appropriate memory Markdown file, so the fact is loaded
-in future sessions.
+The agent will use the `save_memory` tool to store this fact in your global
+memory file.
 
 **Prompt:** `Save the fact that the staging server IP is 10.0.0.5.`
 
@@ -124,5 +124,3 @@ immediately. Force a reload with:
 - Explore the [Command reference](../../reference/commands.md) for more
   `/memory` options.
 - Read the technical spec for [Project context](../../cli/gemini-md.md).
-- Try the experimental [Auto Memory](../auto-memory.md) feature to extract
-  memory updates and reusable skills from your past sessions automatically.