fix: unbreak client closed errors when using vertexai session service

PiperOrigin-RevId: 811911528

.gemini/settings.json

@@ -0,0 +1,3 @@
+{
+  "contextFileName": "AGENTS.md"
+}

.github/ISSUE_TEMPLATE/bug_report.md

@@ -14,11 +14,12 @@ assignees: ''
 A clear and concise description of what the bug is.
 
 **To Reproduce**
+Please share a minimal code and data to reproduce your problem.
 Steps to reproduce the behavior:
 1. Install '...'
 2. Run '....'
 3. Open '....'
-4. See error
+4. Provie error or stacktrace
 
 **Expected behavior**
 A clear and concise description of what you expected to happen.
@@ -27,9 +28,13 @@ A clear and concise description of what you expected to happen.
 If applicable, add screenshots to help explain your problem.
 
 **Desktop (please complete the following information):**
- - OS: [e.g. iOS]
+ - OS: [e.g. macOS, Linux, Windows]
  - Python version(python -V):
  - ADK version(pip show google-adk):
 
+ **Model Information:**
+ - Are you using LiteLLM: Yes/No
+ - Which model is being used(e.g. gemini-2.5-pro)
+
 **Additional context**
 Add any other context about the problem here.

.github/workflows/analyze-releases-for-adk-docs-updates.yml

@@ -0,0 +1,47 @@
+name: Analyze New Release for ADK Docs Updates
+
+on:
+  # Runs on every new release.
+  release:
+    types: [published]
+  # Manual trigger for testing and retrying.
+  workflow_dispatch:
+
+jobs:
+  analyze-new-release-for-adk-docs-updates:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      issues: write
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: '3.11'
+
+      - name: Load adk-bot SSH Private Key
+        uses: webfactory/ssh-agent@v0.9.0
+        with:
+          ssh-private-key: ${{ secrets.ADK_BOT_SSH_PRIVATE_KEY }}
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install requests google-adk
+
+      - name: Run Analyzing Script
+        env:
+          GITHUB_TOKEN: ${{ secrets.ADK_TRIAGE_AGENT }}
+          GOOGLE_API_KEY: ${{ secrets.GOOGLE_API_KEY }}
+          GOOGLE_GENAI_USE_VERTEXAI: 0
+          DOC_OWNER: 'google'
+          CODE_OWNER: 'google'
+          DOC_REPO: 'adk-docs'
+          CODE_REPO: 'adk-python'
+          INTERACTIVE: 0
+          PYTHONPATH: contributing/samples/adk_documentation
+        run: python -m adk_release_analyzer.main

.github/workflows/check-file-contents.yml

@@ -70,7 +70,7 @@ jobs:
 
             # Use grep -L to find files that DO NOT contain the pattern.
             # This command will output a list of non-compliant files.
-            FILES_MISSING_IMPORT=$(grep -L 'from __future__ import annotations' $CHANGED_FILES)
+            FILES_MISSING_IMPORT=$(grep -L 'from __future__ import annotations' $CHANGED_FILES || true)
 
             # Check if the list of non-compliant files is empty
             if [ -z "$FILES_MISSING_IMPORT" ]; then

.github/workflows/discussion_answering.yml

@@ -0,0 +1,54 @@
+name: ADK Answering Agent for Discussions
+
+on:
+  discussion:
+    types: [created]
+  discussion_comment:
+    types: [created]
+
+jobs:
+  agent-answer-questions:
+    if: >-
+      (github.event_name == 'discussion' && github.event.discussion.category.name == 'Q&A') ||
+      (github.event_name == 'discussion_comment' && contains(github.event.comment.body, '@adk-bot') && github.event.sender.login != 'adk-bot')
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: '3.11'
+
+      - name: Authenticate to Google Cloud
+        id: auth
+        uses: 'google-github-actions/auth@v2'
+        with:
+          credentials_json: '${{ secrets.ADK_GCP_SA_KEY }}'
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install google-adk google-cloud-discoveryengine
+
+      - name: Run Answering Script
+        env:
+          GITHUB_TOKEN: ${{ secrets.ADK_TRIAGE_AGENT }}
+          ADK_GCP_SA_KEY: ${{ secrets.ADK_GCP_SA_KEY }}
+          GOOGLE_CLOUD_PROJECT: ${{ secrets.GOOGLE_CLOUD_PROJECT }}
+          GOOGLE_CLOUD_LOCATION: ${{ secrets.GOOGLE_CLOUD_LOCATION }}
+          VERTEXAI_DATASTORE_ID: ${{ secrets.VERTEXAI_DATASTORE_ID }}
+          GEMINI_API_DATASTORE_ID: ${{ secrets.GEMINI_API_DATASTORE_ID }}
+          GOOGLE_GENAI_USE_VERTEXAI: 1
+          OWNER: 'google'
+          REPO: 'adk-python'
+          INTERACTIVE: 0
+          PYTHONPATH: contributing/samples
+        run: |
+          # Write discussion data to temporary file to avoid secret masking issues
+          cat > /tmp/discussion.json << 'EOF'
+          ${{ toJson(github.event.discussion) }}
+          EOF
+          python -m adk_answering_agent.main --discussion-file /tmp/discussion.json

.github/workflows/pr-triage.yml

@@ -0,0 +1,39 @@
+name: ADK Pull Request Triaging Agent
+
+on:
+  pull_request_target:
+    types: [opened, reopened, edited]
+
+jobs:
+  agent-triage-pull-request:
+    if: "!contains(github.event.pull_request.labels.*.name, 'bot triaged') && !contains(github.event.pull_request.labels.*.name, 'google-contributor')"
+    runs-on: ubuntu-latest
+    permissions:
+      pull-requests: write
+      contents: read
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: '3.11'
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install requests google-adk
+
+      - name: Run Triaging Script
+        env:
+          GITHUB_TOKEN: ${{ secrets.ADK_TRIAGE_AGENT }}
+          GOOGLE_API_KEY: ${{ secrets.GOOGLE_API_KEY }}
+          GOOGLE_GENAI_USE_VERTEXAI: 0
+          OWNER: 'google'
+          REPO: 'adk-python'
+          PULL_REQUEST_NUMBER: ${{ github.event.pull_request.number }}
+          INTERACTIVE: ${{ vars.PR_TRIAGE_INTERACTIVE }}
+          PYTHONPATH: contributing/samples
+        run: python -m adk_pr_triaging_agent.main

.github/workflows/python-unit-tests.yml

@@ -25,7 +25,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        python-version: ["3.9", "3.10", "3.11"]
+        python-version: ["3.9", "3.10", "3.11", "3.12", "3.13"]
 
     steps:
     - name: Checkout code
@@ -36,8 +36,8 @@ jobs:
       with:
         python-version: ${{ matrix.python-version }}
 
-    - name: Install uv
-      run: curl -LsSf https://astral.sh/uv/install.sh | sh
+    - name: Install the latest version of uv
+      uses: astral-sh/setup-uv@v6
 
     - name: Install dependencies
       run: |

.github/workflows/triage.yml

@@ -40,4 +40,5 @@ jobs:
           ISSUE_TITLE: ${{ github.event.issue.title }}
           ISSUE_BODY: ${{ github.event.issue.body }}
           ISSUE_COUNT_TO_PROCESS: '3' # Process 3 issues at a time on schedule
-        run: python contributing/samples/adk_triaging_agent/main.py
+          PYTHONPATH: contributing/samples
+        run: python -m adk_triaging_agent.main

.github/workflows/upload-adk-docs-to-vertex-ai-search.yml

@@ -0,0 +1,51 @@
+name: Upload ADK Docs to Vertex AI Search
+
+on:
+  # Runs once per day at 16:00 UTC
+  schedule:
+   - cron: '00 16 * * *'
+  # Manual trigger for testing and fixing
+  workflow_dispatch:
+
+jobs:
+  upload-adk-docs-to-vertex-ai-search:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Clone adk-docs repository
+        run: git clone https://github.com/google/adk-docs.git /tmp/adk-docs
+
+      - name: Clone adk-python repository
+        run: git clone https://github.com/google/adk-python.git /tmp/adk-python
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: '3.11'
+
+      - name: Authenticate to Google Cloud
+        id: auth
+        uses: 'google-github-actions/auth@v2'
+        with:
+          credentials_json: '${{ secrets.ADK_GCP_SA_KEY }}'
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install google-adk markdown google-cloud-storage google-cloud-discoveryengine
+
+      - name: Run Answering Script
+        env:
+          GITHUB_TOKEN: ${{ secrets.ADK_TRIAGE_AGENT }}
+          GOOGLE_CLOUD_PROJECT: ${{ secrets.GOOGLE_CLOUD_PROJECT }}
+          GOOGLE_CLOUD_LOCATION: ${{ secrets.GOOGLE_CLOUD_LOCATION }}
+          VERTEXAI_DATASTORE_ID: ${{ secrets.VERTEXAI_DATASTORE_ID }}
+          GOOGLE_GENAI_USE_VERTEXAI: 1
+          GCS_BUCKET_NAME: ${{ secrets.GCS_BUCKET_NAME }}
+          ADK_DOCS_ROOT_PATH: /tmp/adk-docs
+          ADK_PYTHON_ROOT_PATH: /tmp/adk-python
+          PYTHONPATH: contributing/samples
+        run: python -m adk_answering_agent.upload_docs_to_vertex_ai_search

.gitignore

@@ -82,6 +82,7 @@ log/
 .env.development.local
 .env.test.local
 .env.production.local
+uv.lock
 
 # Google Cloud specific
 .gcloudignore

AGENTS.md

@@ -0,0 +1,221 @@
+# Gemini CLI / Gemini Code Assist Context
+
+This document provides context for the Gemini CLI and Gemini Code Assist to understand the project and assist with development.
+
+## Project Overview
+
+The Agent Development Kit (ADK) is an open-source, code-first Python toolkit for building, evaluating, and deploying sophisticated AI agents with flexibility and control. While optimized for Gemini and the Google ecosystem, ADK is model-agnostic, deployment-agnostic, and is built for compatibility with other frameworks. ADK was designed to make agent development feel more like software development, to make it easier for developers to create, deploy, and orchestrate agentic architectures that range from simple tasks to complex workflows.
+
+## Project Architecture
+
+Please refer to [ADK Project Overview and Architecture](https://github.com/google/adk-python/blob/main/contributing/adk_project_overview_and_architecture.md) for details.
+
+### ADK Live (Bidi-streaming)
+
+- ADK live feature can be accessed from runner.run_live(...) and corresponding FAST api endpoint.
+- ADK live feature is built on top of [Gemini Live API](https://cloud.google.com/vertex-ai/generative-ai/docs/live-api). We integrate Gemini Live API through [GenAI SDK](https://github.com/googleapis/python-genai).
+- ADK live related configs are in [run_config.py](https://github.com/google/adk-python/blob/main/src/google/adk/agents/run_config.py).
+- ADK live under multi-agent scenario: we convert the audio into text. This text will be passed to next agent as context.
+- Most logics are in [base_llm_flow.py](https://github.com/google/adk-python/blob/main/src/google/adk/flows/llm_flows/base_llm_flow.py) and [gemini_llm_connection.py](https://github.com/google/adk-python/blob/main/src/google/adk/models/gemini_llm_connection.py).
+- Input transcription and output transcription should be added to session as Event.
+- User audio or model audio should be saved into artifacts with a reference in Event to it.
+- Tests are in [tests/unittests/streaming](https://github.com/google/adk-python/tree/main/tests/unittests/streaming).
+
+## ADK: Style Guides
+
+### Python Style Guide
+
+The project follows the Google Python Style Guide. Key conventions are enforced using `pylint` with the provided `pylintrc` configuration file. Here are some of the key style points:
+
+*   **Indentation**: 2 spaces.
+*   **Line Length**: Maximum 80 characters.
+*   **Naming Conventions**:
+    *   `function_and_variable_names`: `snake_case`
+    *   `ClassNames`: `CamelCase`
+    *   `CONSTANTS`: `UPPERCASE_SNAKE_CASE`
+*   **Docstrings**: Required for all public modules, functions, classes, and methods.
+*   **Imports**: Organized and sorted.
+*   **Error Handling**: Specific exceptions should be caught, not general ones like `Exception`.
+
+### Autoformat
+
+We have autoformat.sh to help solve import organize and formatting issues.
+
+```bash
+# Run in open_source_workspace/
+$ ./autoformat.sh
+```
+
+### In ADK source
+
+Below styles applies to the ADK source code (under `src/` folder of the Github.
+repo).
+
+#### Use relative imports
+
+```python
+# DO
+from ..agents.llm_agent import LlmAgent
+
+# DON'T
+from google.adk.agents.llm_agent import LlmAgent
+```
+
+#### Import from module, not from `__init__.py`
+
+```python
+# DO
+from ..agents.llm_agent import LlmAgent
+
+# DON'T
+from ..agents  import LlmAgent # import from agents/__init__.py
+```
+
+#### Always do `from __future__ import annotations`
+
+```python
+# DO THIS, right after the open-source header.
+from __future__ import annotations
+```
+
+Like below:
+
+```python
+# Copyright 2025 Google LLC
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+from __future__ import annotations
+
+# ... the rest of the file.
+```
+
+This allows us to forward-reference a class without quotes.
+
+Check out go/pep563 for details.
+
+### In ADK tests
+
+#### Use absolute imports
+
+In tests, we use `google.adk` same as how our users uses.
+
+```python
+# DO
+from google.adk.agents.llm_agent import LlmAgent
+
+# DON'T
+from ..agents.llm_agent import LlmAgent
+```
+
+## ADK: Local testing
+
+### Unit tests
+
+Run below command:
+
+```bash
+$ pytest tests/unittests
+```
+
+## Docstring and comments
+
+### Comments - Explaining the Why, Not the What
+Philosophy: Well-written code should be largely self-documenting. Comments
+ serve a different purpose: they should explain the complex algorithms,
+ non-obvious business logic, or the rationale behind a particular implementation
+ choice—the things the code cannot express on its own. Avoid comments that
+ merely restate what the code does (e.g., # increment i above i += 1).
+
+Style: Comments should be written as complete sentences. Block comments must
+begin with a # followed by a single space.
+
+## Versioning
+ADK adherence to Semantic Versioning 2.0.0
+
+Core Principle: The adk-python project strictly adheres to the Semantic
+Versioning 2.0.0 specification. All release versions will follow the
+MAJOR.MINOR.PATCH format.
+
+### Breaking Change
+
+A breaking change is any modification that introduces backward-incompatible
+changes to the public API. In the context of the ADK, this means a change that
+could force a developer using the framework to alter their existing code to
+upgrade to the new version. The public API is not limited to just the Python
+function and class signatures; it also encompasses data schemas for stored
+information (like evaluation datasets), the command-line interface (CLI),
+and the data format used for server communications.
+
+### Public API Surface Definition
+
+The "public API" of ADK is a broad contract that extends beyond its Python
+function signatures. A breaking change in any of the following areas can
+disrupt user workflows and the wider ecosystem of agents and tools built with
+ADK. The analysis of the breaking changes introduced in v1.0.0 demonstrates the
+expansive nature of this contract. For the purposes of versioning, the ADK
+Public API Surface is defined as:
+
+- All public classes, methods, and functions in the google.adk namespace.
+
+- The names, required parameters, and expected behavior of all built-in Tools
+ (e.g., google_search, BuiltInCodeExecutor).
+
+- The structure and schema of persisted data, including Session data, Memory,
+ and Evaluation datasets.
+
+- The JSON request/response format of the ADK API server(FastAPI server)
+ used by adk web, including field casing conventions.
+
+- The command-line interface (CLI) commands, arguments, and flags (e.g., adk deploy).
+
+- The expected file structure for agent definitions that are loaded by the
+ framework (e.g., the agent.py convention).
+
+#### Checklist for Breaking Changes:
+
+The following changes are considered breaking and necessitate a MAJOR version
+ bump.
+
+- API Signature Change: Renaming, removing, or altering the required parameters
+ of any public class, method, or function (e.g., the removal of the list_events
+ method from BaseSessionService).
+
+- Architectural Shift: A fundamental change to a core component's behavior
+ (e.g., making all service methods async, which requires consumers to use await).
+
+- Data Schema Change: A non-additive change to a persisted data schema that
+ renders old data unreadable or invalid (e.g., the redesign of the
+  MemoryService and evaluation dataset schemas).
+
+- Tool Interface Change: Renaming a built-in tool, changing its required
+ parameters, or altering its fundamental purpose (e.g., replacing
+ BuiltInCodeExecutionTool with BuiltInCodeExecutor and moving it from the tools
+ parameter to the code_executor parameter of an Agent).
+
+- Configuration Change: Altering the required structure of configuration files
+ or agent definition files that the framework loads (e.g., the simplification
+ of the agent.py structure for MCPToolset).
+
+- Wire Format Change: Modifying the data format for API server interactions
+ (e.g., the switch from snake_case to camelCase for all JSON payloads).
+
+- Dependency Removal: Removing support for a previously integrated third-party
+ library or tool type.
+
+## Commit Message Format
+
+- Please use [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/)
+format.
+- If it's not a breaking change, please add #non-breaking tag. If it's a
+breaking change, please add #breaking.

CONTRIBUTING.md

@@ -2,25 +2,24 @@
 
 We'd love to accept your patches and contributions to this project.
 
-- [How to contribute](#how-to-contribute)
-- [Before you begin](#before-you-begin)
-  - [Sign our Contributor License Agreement](#sign-our-contributor-license-agreement)
-  - [Review our community guidelines](#review-our-community-guidelines)
-- [Contribution workflow](#contribution-workflow)
-  - [Finding Issues to Work On](#finding-issues-to-work-on)
-  - [Requirement for PRs](#requirement-for-prs)
-  - [Large or Complex Changes](#large-or-complex-changes)
-  - [Testing Requirements](#testing-requirements)
-    - [Unit Tests](#unit-tests)
-    - [Manual End-to-End (E2E) Tests](#manual-end-to-end-e2e-tests)
-  - [Documentation](#documentation)
-  - [Development Setup](#development-setup)
-  - [Code reviews](#code-reviews)
+-   [How to contribute](#how-to-contribute)
+-   [Before you begin](#before-you-begin)
+    -   [Sign our Contributor License Agreement](#sign-our-contributor-license-agreement)
+    -   [Review our community guidelines](#review-our-community-guidelines)
+-   [Contribution workflow](#contribution-workflow)
+    -   [Finding Issues to Work On](#finding-issues-to-work-on)
+    -   [Requirement for PRs](#requirement-for-prs)
+    -   [Large or Complex Changes](#large-or-complex-changes)
+    -   [Testing Requirements](#testing-requirements)
+    -   [Unit Tests](#unit-tests)
+    -   [Manual End-to-End (E2E) Tests](#manual-end-to-end-e2e-tests)
+    -   [Documentation](#documentation)
+    -   [Development Setup](#development-setup)
+    -   [Code reviews](#code-reviews)
 
+## Before you begin
 
-# Before you begin
-
-## Sign our Contributor License Agreement
+### Sign our Contributor License Agreement
 
 Contributions to this project must be accompanied by a
 [Contributor License Agreement](https://cla.developers.google.com/about) (CLA).
@@ -34,73 +33,102 @@ was for a different project), you probably don't need to do it again.
 Visit <https://cla.developers.google.com/> to see your current agreements or to
 sign a new one.
 
-## Review our community guidelines
+### Review our community guidelines
 
 This project follows
 [Google's Open Source Community Guidelines](https://opensource.google/conduct/).
 
-# Contribution workflow
+### Code reviews
 
-## Finding Issues to Work On
+All submissions, including submissions by project members, require review. We
+use GitHub pull requests for this purpose. Consult
+[GitHub Help](https://help.github.com/articles/about-pull-requests/) for more
+information on using pull requests.
 
-- Browse issues labeled **`good first issue`** (newcomer-friendly) or **`help wanted`** (general contributions).
-- For other issues, please kindly ask before contributing to avoid duplication.
+## Contribution workflow
 
+### Finding Issues to Work On
 
-## Requirement for PRs
+-   Browse issues labeled **`good first issue`** (newcomer-friendly) or **`help
+    wanted`** (general contributions).
+-   For other issues, please kindly ask before contributing to avoid
+    duplication.
 
-- All PRs, other than small documentation or typo fixes, should have a Issue assoicated. If not, please create one.
-- Small, focused PRs. Keep changes minimal—one concern per PR.
-- For bug fixes or features, please provide logs or screenshot after the fix is applied to help reviewers better understand the fix.
-- Please include a `testing plan` section in your PR to talk about how you will test. This will save time for PR review. See `Testing Requirements` section for more details.
+### Requirement for PRs
+
+-   All PRs, other than small documentation or typo fixes, should have a Issue
+    associated. If not, please create one.
+-   Small, focused PRs. Keep changes minimal—one concern per PR.
+-   For bug fixes or features, please provide logs or screenshot after the fix
+    is applied to help reviewers better understand the fix.
+-   Please include a `testing plan` section in your PR to talk about how you
+    will test. This will save time for PR review. See `Testing Requirements`
+    section for more details.
+
+### Large or Complex Changes
 
-## Large or Complex Changes
 For substantial features or architectural revisions:
 
-- Open an Issue First: Outline your proposal, including design considerations and impact.
-- Gather Feedback: Discuss with maintainers and the community to ensure alignment and avoid duplicate work
+-   Open an Issue First: Outline your proposal, including design considerations
+    and impact.
+-   Gather Feedback: Discuss with maintainers and the community to ensure
+    alignment and avoid duplicate work
 
-## Testing Requirements
+### Testing Requirements
 
-To maintain code quality and prevent regressions, all code changes must include comprehensive tests and verifiable end-to-end (E2E) evidence.
+To maintain code quality and prevent regressions, all code changes must include
+comprehensive tests and verifiable end-to-end (E2E) evidence.
 
+#### Unit Tests
 
-### Unit Tests
-
-Please add or update unit tests for your change. Please include a summary of passed `pytest` results.
+Please add or update unit tests for your change. Please include a summary of
+passed `pytest` results.
 
 Requirements for unit tests:
 
-- **Coverage:** Cover new features, edge cases, error conditions, and typical use cases.
-- **Location:** Add or update tests under `tests/unittests/`, following existing naming conventions (e.g., `test_<module>_<feature>.py`).
-- **Framework:** Use `pytest`. Tests should be:
-  - Fast and isolated.
-  - Written clearly with descriptive names.
-  - Free of external dependencies (use mocks or fixtures as needed).
-- **Quality:** Aim for high readability and maintainability; include docstrings or comments for complex scenarios.
+-   **Coverage:** Cover new features, edge cases, error conditions, and typical
+    use cases.
+-   **Location:** Add or update tests under `tests/unittests/`, following
+    existing naming conventions (e.g., `test_<module>_<feature>.py`).
+-   **Framework:** Use `pytest`. Tests should be:
+    -   Fast and isolated.
+    -   Written clearly with descriptive names.
+    -   Free of external dependencies (use mocks or fixtures as needed).
+-   **Quality:** Aim for high readability and maintainability; include
+    docstrings or comments for complex scenarios.
 
-### Manual End-to-End (E2E) Tests
+#### Manual End-to-End (E2E) Tests
 
-Manual E2E tests ensure integrated flows work as intended. Your tests should cover all scenarios. Sometimes, it's also good to ensure relevant functionality is not impacted.
+Manual E2E tests ensure integrated flows work as intended. Your tests should
+cover all scenarios. Sometimes, it's also good to ensure relevant functionality
+is not impacted.
 
 Depending on your change:
 
-- **ADK Web:**
-  - Use the `adk web` to verify functionality.
-  - Capture and attach relevant screenshots demonstrating the UI/UX changes or outputs.
-  - Label screenshots clearly in your PR description.
+-   **ADK Web:**
 
-- **Runner:**
-  - Provide the testing setup. For example, the agent definition, and the runner setup.
-  - Execute the `runner` tool to reproduce workflows.
-  - Include the command used and console output showing test results.
-  - Highlight sections of the log that directly relate to your change.
+    -   Use the `adk web` to verify functionality.
+    -   Capture and attach relevant screenshots demonstrating the UI/UX changes
+        or outputs.
+    -   Label screenshots clearly in your PR description.
 
-## Documentation
+-   **Runner:**
 
-For any changes that impact user-facing documentation (guides, API reference, tutorials), please open a PR in the [adk-docs](https://github.com/google/adk-docs) repository to update relevant part before or alongside your code PR.
+    -   Provide the testing setup. For example, the agent definition, and the
+        runner setup.
+    -   Execute the `runner` tool to reproduce workflows.
+    -   Include the command used and console output showing test results.
+    -   Highlight sections of the log that directly relate to your change.
+
+### Documentation
+
+For any changes that impact user-facing documentation (guides, API reference,
+tutorials), please open a PR in the
+[adk-docs](https://github.com/google/adk-docs) repository to update relevant
+part before or alongside your code PR.
 
 ## Development Setup
+
 1.  **Clone the repository:**
 
     ```shell
@@ -110,11 +138,13 @@ For any changes that impact user-facing documentation (guides, API reference, tu
 
 2.  **Install uv:**
 
-    Check out [uv installation guide](https://docs.astral.sh/uv/getting-started/installation/).
+    Check out
+    [uv installation guide](https://docs.astral.sh/uv/getting-started/installation/).
 
 3.  **Create and activate a virtual environment:**
 
-    **NOTE**: ADK supports Python 3.9+. Python 3.11 and above is strongly recommended.
+    **NOTE**: ADK supports Python 3.9+. Python 3.11 and above is strongly
+    recommended.
 
     Create a workspace venv using uv.
 
@@ -128,10 +158,7 @@ For any changes that impact user-facing documentation (guides, API reference, tu
     source .venv/bin/activate
     ```
 
-    **windows**
-    ```shell
-    source .\.venv\Scripts\activate
-    ```
+    **windows** `shell source .\.venv\Scripts\activate`
 
 4.  **Install dependencies:**
 
@@ -147,11 +174,11 @@ For any changes that impact user-facing documentation (guides, API reference, tu
     pytest ./tests/unittests
     ```
 
-    NOTE: for accurately repro test failure, only include `test` and `eval` as
-    extra dependencies.
+    NOTE: for accurate repro of test failure, only include `test`, `eval` and
+    `a2a` as extra dependencies.
 
     ```shell
-    uv sync --extra test --extra eval
+    uv sync --extra test --extra eval --extra a2a
     pytest ./tests/unittests
     ```
 
@@ -164,14 +191,14 @@ For any changes that impact user-facing documentation (guides, API reference, tu
     ./autoformat.sh
     ```
 
-7. **Build the wheel file:**
+7.  **Build the wheel file:**
 
     ```shell
     uv build
     ```
 
-8.  **Test the locally built wheel file:**
-    Have a simple testing folder setup as mentioned in the
+8.  **Test the locally built wheel file:** Have a simple testing folder setup as
+    mentioned in the
     [quickstart](https://google.github.io/adk-docs/get-started/quickstart/).
 
     Then following below steps to test your changes:
@@ -200,12 +227,11 @@ For any changes that impact user-facing documentation (guides, API reference, tu
 
 ## Contributing Resources
 
-[Contributing folder](https://github.com/google/adk-python/tree/main/contributing/samples) has resources that is helpful for contributors.
+[Contributing folder](https://github.com/google/adk-python/tree/main/contributing)
+has resources that is helpful for contributors.
 
+## Vibe Coding
 
-## Code reviews
-
-All submissions, including submissions by project members, require review. We
-use GitHub pull requests for this purpose. Consult
-[GitHub Help](https://help.github.com/articles/about-pull-requests/) for more
-information on using pull requests.
+If you want to contribute by leveraging viber coding, the AGENTS.md
+(https://github.com/google/adk-python/tree/main/AGENTS.md) could be used as
+context to your LLM.

README.md

@@ -1,6 +1,7 @@
 # Agent Development Kit (ADK)
 
 [![License](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](LICENSE)
+[![PyPI](https://img.shields.io/pypi/v/google-adk)](https://pypi.org/project/google-adk/)
 [![Python Unit Tests](https://github.com/google/adk-python/actions/workflows/python-unit-tests.yml/badge.svg)](https://github.com/google/adk-python/actions/workflows/python-unit-tests.yml)
 [![r/agentdevelopmentkit](https://img.shields.io/badge/Reddit-r%2Fagentdevelopmentkit-FF4500?style=flat&logo=reddit&logoColor=white)](https://www.reddit.com/r/agentdevelopmentkit/)
 [![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/google/adk-python)
@@ -14,7 +15,7 @@
     </h3>
     <h3 align="center">
       Important Links:
-      <a href="https://google.github.io/adk-docs/">Docs</a>, 
+      <a href="https://google.github.io/adk-docs/">Docs</a>,
       <a href="https://github.com/google/adk-samples">Samples</a>,
       <a href="https://github.com/google/adk-java">Java ADK</a> &
       <a href="https://github.com/google/adk-web">ADK Web</a>.
@@ -26,6 +27,13 @@ Agent Development Kit (ADK) is a flexible and modular framework for developing a
 
 ---
 
+## 🔥 What's new
+
+- **Agent Config**: Build agents without code. Check out the
+  [Agent Config](https://google.github.io/adk-docs/agents/config/) feature.
+
+- **Tool Confirmation**: A [tool confirmation flow(HITL)](https://google.github.io/adk-docs/tools/confirmation/) that can guard tool execution with explicit confirmation and custom input
+
 ## ✨ Key Features
 
 - **Rich Tool Ecosystem**: Utilize pre-built tools, custom functions,
@@ -45,7 +53,7 @@ Agent Development Kit (ADK) is a flexible and modular framework for developing a
 
 For remote agent-to-agent communication, ADK integrates with the
 [A2A protocol](https://github.com/google-a2a/A2A/).
-See this [example](https://github.com/google-a2a/a2a-samples/tree/main/samples/python/agents/google_adk)
+See this [example](https://github.com/a2aproject/a2a-samples/tree/main/samples/python/agents)
 for how they can work together.
 
 ## 🚀 Installation
@@ -58,7 +66,7 @@ You can install the latest stable version of ADK using `pip`:
 pip install google-adk
 ```
 
-The release cadence is weekly.
+The release cadence is roughly bi-weekly.
 
 This version is recommended for most users as it represents the most recent official release.
 
@@ -88,7 +96,7 @@ from google.adk.tools import google_search
 
 root_agent = Agent(
     name="search_assistant",
-    model="gemini-2.0-flash", # Or your preferred Gemini model
+    model="gemini-2.5-flash", # Or your preferred Gemini model
     instruction="You are a helpful assistant. Answer user questions using Google Search when needed.",
     description="An assistant that can search the web.",
     tools=[google_search]
@@ -103,13 +111,13 @@ Define a multi-agent system with coordinator agent, greeter agent, and task exec
 from google.adk.agents import LlmAgent, BaseAgent
 
 # Define individual agents
-greeter = LlmAgent(name="greeter", model="gemini-2.0-flash", ...)
-task_executor = LlmAgent(name="task_executor", model="gemini-2.0-flash", ...)
+greeter = LlmAgent(name="greeter", model="gemini-2.5-flash", ...)
+task_executor = LlmAgent(name="task_executor", model="gemini-2.5-flash", ...)
 
 # Create parent agent and assign children via sub_agents
 coordinator = LlmAgent(
     name="Coordinator",
-    model="gemini-2.0-flash",
+    model="gemini-2.5-flash",
     description="I coordinate greetings and tasks.",
     sub_agents=[ # Assign sub_agents here
         greeter,
@@ -135,9 +143,13 @@ adk eval \
 ## 🤝 Contributing
 
 We welcome contributions from the community! Whether it's bug reports, feature requests, documentation improvements, or code contributions, please see our
-- [General contribution guideline and flow](https://google.github.io/adk-docs/contributing-guide/#questions).
+- [General contribution guideline and flow](https://google.github.io/adk-docs/contributing-guide/).
 - Then if you want to contribute code, please read [Code Contributing Guidelines](./CONTRIBUTING.md) to get started.
 
+## Vibe Coding
+
+If you are to develop agent via vibe coding the [llms.txt](./llms.txt) and the [llms-full.txt](./llms-full.txt) can be used as context to LLM. While the former one is a summarized one and the later one has the full information in case your LLM has big enough context window.
+
 ## 📄 License
 
 This project is licensed under the Apache 2.0 License - see the [LICENSE](LICENSE) file for details.

autoformat.sh

@@ -52,16 +52,16 @@ echo '---------------------------------------'
 echo '|  Auto-formatting src/...'
 echo '---------------------------------------'
 
-find -L src/ -type f -name "*.py" -exec pyink --config pyproject.toml {} +
+find -L src/ -not -path "*/.*" -type f -name "*.py" -exec pyink --config pyproject.toml {} +
 
 echo '---------------------------------------'
 echo '|  Auto-formatting tests/...'
 echo '---------------------------------------'
 
-find -L tests/ -type f -name "*.py" -exec pyink --config pyproject.toml {} +
+find -L tests/ -not -path "*/.*" -type f -name "*.py" -exec pyink --config pyproject.toml {} +
 
 echo '---------------------------------------'
 echo '|  Auto-formatting contributing/...'
 echo '---------------------------------------'
 
-find -L contributing/ -type f -name "*.py" -exec pyink --config pyproject.toml {} +
+find -L contributing/ -not -path "*/.*" -type f -name "*.py" -exec pyink --config pyproject.toml {} +

contributing/README.md

@@ -7,3 +7,10 @@ This folder host resources for ADK contributors, for example, testing samples et
 Samples folder host samples to test different features. The samples are usually minimal and simplistic to test one or a few scenarios.
 
 **Note**: This is different from the [google/adk-samples](https://github.com/google/adk-samples) repo, which hosts more complex e2e samples for customers to use or modify directly.
+
+## ADK project and architecture overview
+
+The [adk_project_overview_and_architecture.md](adk_project_overview_and_architecture.md) describes the ADK project overview and its technical architecture from high-level.
+
+This is helpful for contributors to understand the project and design philosophy.
+ It can also be feed into LLMs for vibe-coding.

contributing/adk_project_overview_and_architecture.md

@@ -0,0 +1,112 @@
+# ADK Project Overview and Architecture
+
+Google Agent Development Kit (ADK) for Python
+
+## Core Philosophy & Architecture
+
+- Code-First: Everything is defined in Python code for versioning, testing, and IDE support. Avoid GUI-based logic.
+
+- Modularity & Composition: We build complex multi-agent systems by composing multiple, smaller, specialized agents.
+
+- Deployment-Agnostic: The agent's core logic is separate from its deployment environment. The same agent.py can be run locally for testing, served via an API, or deployed to the cloud.
+
+## Foundational Abstractions (Our Vocabulary)
+
+- Agent: The blueprint. It defines an agent's identity, instructions, and tools. It's a declarative configuration object.
+
+- Tool: A capability. A Python function an agent can call to interact with the world (e.g., search, API call).
+
+- Runner: The engine. It orchestrates the "Reason-Act" loop, manages LLM calls, and executes tools.
+
+- Session: The conversation state. It holds the history for a single, continuous dialogue.
+
+- Memory: Long-term recall across different sessions.
+
+- Artifact Service: Manages non-textual data like files.
+
+## Canonical Project Structure
+
+Adhere to this structure for compatibility with ADK tooling.
+
+```
+my_adk_project/
+└── src/
+    └── my_app/
+        ├── agents/
+        │   ├── my_agent/
+        │   │   ├── __init__.py   # Must contain: from. import agent \
+        │   │   └── agent.py      # Must contain: root_agent = Agent(...) \
+        │   └── another_agent/
+        │       ├── __init__.py
+        │       └── agent.py\
+```
+
+agent.py: Must define the agent and assign it to a variable named root_agent. This is how ADK's tools find it.
+
+`__init__.py`: In each agent directory, it must contain from. import agent to make the agent discoverable.
+
+## Local Development & Debugging
+
+Interactive UI (adk web): This is our primary debugging tool. It's a decoupled system:
+
+Backend: A FastAPI server started with adk api_server.
+
+Frontend: An Angular app that connects to the backend.
+
+Use the "Events" tab to inspect the full execution trace (prompts, tool calls, responses).
+
+CLI (adk run): For quick, stateless functional checks in the terminal.
+
+Programmatic (pytest): For writing automated unit and integration tests.
+
+## The API Layer (FastAPI)
+
+We expose agents as production APIs using FastAPI.
+
+- get_fast_api_app: This is the key helper function from google.adk.cli.fast_api that creates a FastAPI app from our agent directory.
+
+- Standard Endpoints: The generated app includes standard routes like /list-apps and /run_sse for streaming responses. The wire format is camelCase.
+
+- Custom Endpoints: We can add our own routes (e.g., /health) to the app object returned by the helper.
+
+Python
+
+from google.adk.cli.fast_api import get_fast_api_app
+app = get_fast_api_app(agent_dir="./agents")
+
+@app.get("/health")
+async def health_check():
+    return {"status": "ok"}
+
+
+## Deployment to Production
+
+The adk cli provides the "adk deploy" command to deploy to Google Vertex Agent Engine, Google CloudRun, Google GKE.
+
+## Testing & Evaluation Strategy
+
+Testing is layered, like a pyramid.
+
+### Layer 1: Unit Tests (Base)
+
+What: Test individual Tool functions in isolation.
+
+How: Use pytest in tests/test_tools.py. Verify deterministic logic.
+
+### Layer 2: Integration Tests (Middle)
+
+What: Test the agent's internal logic and interaction with tools.
+
+How: Use pytest in tests/test_agent.py, often with mocked LLMs or services.
+
+### Layer 3: Evaluation Tests (Top)
+
+What: Assess end-to-end performance with a live LLM. This is about quality, not just pass/fail.
+
+How: Use the ADK Evaluation Framework.
+
+Test Cases: Create JSON files with input and a reference (expected tool calls and final response).
+
+Metrics: tool_trajectory_avg_score (does it use tools correctly?) and response_match_score (is the final answer good?).
+
+Run via: adk web (UI), pytest (for CI/CD), or adk eval (CLI).

contributing/dev/utils/build_llms_txt.py

@@ -0,0 +1,338 @@
+#!/usr/bin/env python3
+"""
+build_llms_txt.py – produce llms.txt and llms-full.txt
+                   – skips ```java``` blocks
+                   – README can be next to docs/ or inside docs/
+                   – includes Python API reference from HTML files
+                   – includes adk-python repository README
+"""
+from __future__ import annotations
+
+import argparse
+from pathlib import Path
+import re
+import sys
+import textwrap
+from typing import List
+from typing import Tuple
+import urllib.error
+import urllib.request
+
+RE_JAVA = re.compile(r"```java[ \t\r\n][\s\S]*?```", re.I | re.M)
+RE_SNIPPET = re.compile(r"^(\s*)--8<--\s+\"([^\"]+?)(?::([^\"]+))?\"$", re.M)
+
+
+def fetch_adk_python_readme() -> str:
+  """Fetch README content from adk-python repository"""
+  try:
+    url = "https://raw.githubusercontent.com/google/adk-python/main/README.md"
+    with urllib.request.urlopen(url) as response:
+      return response.read().decode("utf-8")
+  except (urllib.error.URLError, urllib.error.HTTPError) as e:
+    print(f"Warning: Could not fetch adk-python README: {e}")
+    return ""
+
+
+def strip_java(md: str) -> str:
+  return RE_JAVA.sub("", md)
+
+
+def first_heading(md: str) -> str | None:
+  for line in md.splitlines():
+    if line.startswith("#"):
+      return line.lstrip("#").strip()
+  return None
+
+
+def md_to_text(md: str) -> str:
+  import bs4
+  import markdown
+
+  html = markdown.markdown(
+      md, extensions=["fenced_code", "tables", "attr_list"]
+  )
+  return bs4.BeautifulSoup(html, "html.parser").get_text("\n")
+
+
+def html_to_text(html_file: Path) -> str:
+  """Extract text content from HTML files (for Python API reference)"""
+  import bs4
+
+  try:
+    html_content = html_file.read_text(encoding="utf-8")
+    soup = bs4.BeautifulSoup(html_content, "html.parser")
+
+    # Remove script and style elements
+    for script in soup(["script", "style"]):
+      script.decompose()
+
+    # Get text and clean it up
+    text = soup.get_text()
+    lines = (line.strip() for line in text.splitlines())
+    chunks = (phrase.strip() for line in lines for phrase in line.split("  "))
+    text = "\n".join(chunk for chunk in chunks if chunk)
+
+    return text
+  except Exception as e:
+    print(f"Warning: Could not process {html_file}: {e}")
+    return ""
+
+
+def count_tokens(text: str, model: str = "cl100k_base") -> int:
+  try:
+    import tiktoken
+
+    return len(tiktoken.get_encoding(model).encode(text))
+  except Exception:
+    return len(text.split())
+
+
+def expand_code_snippets(content: str, project_root: Path) -> str:
+  """
+  Expands code snippets marked with --8<-- "path/to/file.py" or
+  --8<-- "path/to/file.py:section_name" into the content.
+  """
+
+  def replace_snippet(match):
+    indent = match.group(1)  # Capture leading spaces
+    snippet_path_str = match.group(
+        2
+    )  # Capture the file path (e.g., "examples/python/snippets/file.py")
+    section_name = match.group(
+        3
+    )  # Capture the section name if present (e.g., "init")
+    snippet_full_path = (
+        project_root / snippet_path_str
+    )  # Changed from base_path to project_root
+
+    # If not found in project root, try adk-docs directory
+    if not snippet_full_path.exists():
+      script_dir = Path(__file__).resolve().parent
+      adk_docs_path = script_dir / "adk-docs" / snippet_path_str
+      if adk_docs_path.exists():
+        snippet_full_path = adk_docs_path
+
+    if snippet_full_path.exists():
+      try:
+        file_content = snippet_full_path.read_text(encoding="utf-8")
+        if section_name:
+          # Extract content based on section markers
+          # Handle both single and double hash markers with optional spacing
+          start_marker_patterns = [
+              f"# --8<-- [start:{section_name.strip()}]",
+              f"## --8<-- [start:{section_name.strip()}]",
+          ]
+          end_marker_patterns = [
+              f"# --8<-- [end:{section_name.strip()}]",
+              f"## --8<-- [end:{section_name.strip()}]",
+              f"##  --8<-- [end:{section_name.strip()}]",  # Handle extra space
+          ]
+
+          start_index = -1
+          end_index = -1
+
+          # Find start marker
+          for pattern in start_marker_patterns:
+            start_index = file_content.find(pattern)
+            if start_index != -1:
+              start_marker = pattern
+              break
+
+          # Find end marker
+          for pattern in end_marker_patterns:
+            end_index = file_content.find(pattern)
+            if end_index != -1:
+              break
+
+          if start_index != -1 and end_index != -1 and start_index < end_index:
+            # Adjust start_index to begin immediately after the start_marker
+            start_of_code = start_index + len(start_marker)
+            temp_content = file_content[start_of_code:end_index]
+            lines = temp_content.splitlines(keepends=True)
+            extracted_lines = []
+            for line in lines:
+              if (
+                  not line.strip().startswith("# --8<--")
+                  and not line.strip().startswith("## --8<--")
+                  and line.strip() != ""
+              ):
+                extracted_lines.append(line)
+            extracted_content = "".join(extracted_lines).strip("\n")
+
+            return textwrap.indent(extracted_content, indent)
+          else:
+            print(
+                f"Warning: Section '{section_name}' not found or markers"
+                f" malformed in {snippet_full_path}"
+            )
+            return match.group(0)
+        else:
+          # Read entire file if no section name
+          return textwrap.indent(file_content, indent)
+      except Exception as e:
+        print(f"Warning: Could not read snippet file {snippet_full_path}: {e}")
+        return match.group(0)
+    else:
+      print(f"Warning: Snippet file not found: {snippet_full_path}")
+      return match.group(0)
+
+  expanded_content = RE_SNIPPET.sub(replace_snippet, content)
+  return expanded_content
+
+
+# ---------- index (llms.txt) ----------
+def build_index(docs: Path) -> str:
+  # Locate README
+  for cand in (docs / "README.md", docs.parent / "README.md"):
+    if cand.exists():
+      readme = cand.read_text(encoding="utf-8")
+      break
+  else:
+    sys.exit("README.md not found in docs/ or its parent")
+
+  title = first_heading(readme) or "Documentation"
+  summary = md_to_text(readme).split("\n\n")[0]
+  lines = [f"# {title}", "", f"> {summary}", ""]
+
+  # Add adk-python repository README content
+  adk_readme = fetch_adk_python_readme()
+  if adk_readme:
+    lines.append("## ADK Python Repository")
+    lines.append("")
+    # Include the full README content, properly formatted
+    adk_text = md_to_text(strip_java(adk_readme))
+    lines.append(adk_text)
+    lines.append("")
+    lines.append(
+        f"**Source:** [adk-python"
+        f" repository](https://github.com/google/adk-python)"
+    )
+    lines.append("")
+
+  primary: List[Tuple[str, str]] = []
+  secondary: List[Tuple[str, str]] = []
+
+  # Process Markdown files
+  for md in sorted(docs.rglob("*.md")):
+    # Skip Java API reference files
+    if "api-reference" in md.parts and "java" in md.parts:
+      continue
+
+    rel = md.relative_to(docs)
+    # Construct the correct GitHub URL for the Markdown file
+    url = f"https://github.com/google/adk-docs/blob/main/docs/{rel}".replace(
+        " ", "%20"
+    )
+    h = first_heading(strip_java(md.read_text(encoding="utf-8"))) or rel.stem
+    (
+        secondary
+        if "sample" in rel.parts or "tutorial" in rel.parts
+        else primary
+    ).append((h, url))
+
+  # Add Python API reference
+  python_api_dir = docs / "api-reference" / "python"
+  if python_api_dir.exists():
+    primary.append((
+        "Python API Reference",
+        "https://github.com/google/adk-docs/blob/main/docs/api-reference/python/",
+    ))
+
+  def emit(name: str, items: List[Tuple[str, str]]):
+    nonlocal lines
+    if items:
+      lines.append(f"## {name}")
+      lines += [f"- [{h}]({u})" for h, u in items]
+      lines.append("")
+
+  emit("Documentation", primary)
+  emit("Optional", secondary)
+  return "\n".join(lines)
+
+
+# ---------- full corpus ----------
+def build_full(docs: Path) -> str:
+  out = []
+
+  script_dir = Path(__file__).resolve().parent
+  project_root = script_dir.parents[2]  # Correct project root
+  print(f"DEBUG: Project Root: {project_root}")
+  print(f"DEBUG: Docs Dir: {docs}")
+
+  # Add adk-python repository README content at the beginning
+  adk_readme = fetch_adk_python_readme()
+  if adk_readme:
+    # Expand snippets in README if any
+    expanded_adk_readme = expand_code_snippets(
+        strip_java(adk_readme), project_root
+    )  # Pass project_root
+    out.append("# ADK Python Repository")
+    out.append("")
+    out.append(expanded_adk_readme)  # Use expanded content
+    out.append("")
+    out.append("---")
+    out.append("")
+
+  # Process Markdown files
+  for md in sorted(docs.rglob("*.md")):
+    # Skip Java API reference files
+    if "api-reference" in md.parts and "java" in md.parts:
+      continue
+
+    md_content = md.read_text(encoding="utf-8")
+    print(f"DEBUG: Processing markdown file: {md.relative_to(docs)}")
+    expanded_md_content = expand_code_snippets(
+        strip_java(md_content), project_root
+    )  # Changed back to project_root
+    out.append(expanded_md_content)  # Use expanded content
+
+  # Process Python API reference HTML files
+  python_api_dir = docs / "api-reference" / "python"
+  if python_api_dir.exists():
+    # Add a separator and header for Python API reference
+    out.append("\n\n# Python API Reference\n")
+
+    # Process main HTML files (skip static assets and generated files)
+    html_files = [
+        python_api_dir / "index.html",
+        python_api_dir / "google-adk.html",
+        python_api_dir / "genindex.html",
+        python_api_dir / "py-modindex.html",
+    ]
+
+    for html_file in html_files:
+      if html_file.exists():
+        text = html_to_text(html_file)
+        if text.strip():
+          out.append(f"\n## {html_file.stem}\n")
+          out.append(text)
+
+  return "\n\n".join(out)
+
+
+def main() -> None:
+  ap = argparse.ArgumentParser(
+      description="Generate llms.txt / llms-full.txt",
+      formatter_class=argparse.RawDescriptionHelpFormatter,
+  )
+  ap.add_argument("--docs-dir", required=True, type=Path)
+  ap.add_argument("--out-root", default=Path("."), type=Path)
+  ap.add_argument("--index-limit", type=int, default=50_000)
+  ap.add_argument("--full-limit", type=int, default=500_000)
+  args = ap.parse_args()
+
+  idx, full = build_index(args.docs_dir), build_full(args.docs_dir)
+  if (tok := count_tokens(idx)) > args.index_limit:
+    sys.exit(f"Index too big: {tok:,}")
+  if (tok := count_tokens(full)) > args.full_limit:
+    sys.exit(f"Full text too big: {tok:,}")
+
+  (args.out_root / "llms.txt").write_text(idx, encoding="utf-8")
+  (args.out_root / "llms-full.txt").write_text(full, encoding="utf-8")
+  print("✅ Generated llms.txt and llms-full.txt successfully")
+  print(f"llms.txt tokens: {count_tokens(idx)}")
+  print(f"llms-full.txt tokens: {count_tokens(full)}")
+
+
+if __name__ == "__main__":
+  main()

contributing/samples/a2a_auth/README.md

@@ -0,0 +1,216 @@
+# A2A OAuth Authentication Sample Agent
+
+This sample demonstrates the **Agent-to-Agent (A2A)** architecture with **OAuth Authentication** workflows in the Agent Development Kit (ADK). The sample implements a multi-agent system where a remote agent can surface OAuth authentication requests to the local agent, which then guides the end user through the OAuth flow before returning the authentication credentials to the remote agent for API access.
+
+## Overview
+
+The A2A OAuth Authentication sample consists of:
+
+- **Root Agent** (`root_agent`): The main orchestrator that handles user requests and delegates tasks to specialized agents
+- **YouTube Search Agent** (`youtube_search_agent`): A local agent that handles YouTube video searches using LangChain tools
+- **BigQuery Agent** (`bigquery_agent`): A remote A2A agent that manages BigQuery operations and requires OAuth authentication for Google Cloud access
+
+## Architecture
+
+```
+┌─────────────────┐    ┌────────────────────┐    ┌──────────────────┐
+│   End User      │───▶│   Root Agent       │───▶│   BigQuery Agent │
+│   (OAuth Flow)  │    │    (Local)         │    │  (Remote A2A)    │
+│                 │    │                    │    │ (localhost:8001) │
+│   OAuth UI      │◀───│                    │◀───│   OAuth Request  │
+└─────────────────┘    └────────────────────┘    └──────────────────┘
+```
+
+## Key Features
+
+### 1. **Multi-Agent Architecture**
+- Root agent coordinates between local YouTube search and remote BigQuery operations
+- Demonstrates hybrid local/remote agent workflows
+- Seamless task delegation based on user request types
+
+### 2. **OAuth Authentication Workflow**
+- Remote BigQuery agent surfaces OAuth authentication requests to the root agent
+- Root agent guides end users through Google OAuth flow for BigQuery access
+- Secure token exchange between agents for authenticated API calls
+
+### 3. **Google Cloud Integration**
+- BigQuery toolset with comprehensive dataset and table management capabilities
+- OAuth-protected access to user's Google Cloud BigQuery resources
+- Support for listing, creating, and managing datasets and tables
+
+### 4. **LangChain Tool Integration**
+- YouTube search functionality using LangChain community tools
+- Demonstrates integration of third-party tools in agent workflows
+
+## Setup and Usage
+
+### Prerequisites
+
+1. **Set up OAuth Credentials**:
+   ```bash
+   export OAUTH_CLIENT_ID=your_google_oauth_client_id
+   export OAUTH_CLIENT_SECRET=your_google_oauth_client_secret
+   ```
+
+2. **Start the Remote BigQuery Agent server**:
+   ```bash
+   # Start the remote a2a server that serves the BigQuery agent on port 8001
+   adk api_server --a2a --port 8001 contributing/samples/a2a_auth/remote_a2a
+   ```
+
+3. **Run the Main Agent**:
+   ```bash
+   # In a separate terminal, run the adk web server
+   adk web contributing/samples/
+   ```
+
+### Example Interactions
+
+Once both services are running, you can interact with the root agent:
+
+**YouTube Search (No Authentication Required):**
+```
+User: Search for 3 Taylor Swift music videos
+Agent: I'll help you search for Taylor Swift music videos on YouTube.
+[Agent delegates to YouTube Search Agent]
+Agent: I found 3 Taylor Swift music videos:
+1. "Anti-Hero" - Official Music Video
+2. "Shake It Off" - Official Music Video
+3. "Blank Space" - Official Music Video
+```
+
+**BigQuery Operations (OAuth Required):**
+```
+User: List my BigQuery datasets
+Agent: I'll help you access your BigQuery datasets. This requires authentication with your Google account.
+[Agent delegates to BigQuery Agent]
+Agent: To access your BigQuery data, please complete the OAuth authentication.
+[OAuth flow initiated - user redirected to Google authentication]
+User: [Completes OAuth flow in browser]
+Agent: Authentication successful! Here are your BigQuery datasets:
+- dataset_1: Customer Analytics
+- dataset_2: Sales Data
+- dataset_3: Marketing Metrics
+```
+
+**Dataset Management:**
+```
+User: Show me details for my Customer Analytics dataset
+Agent: I'll get the details for your Customer Analytics dataset.
+[Using existing OAuth token]
+Agent: Customer Analytics Dataset Details:
+- Created: 2024-01-15
+- Location: US
+- Tables: 5
+- Description: Customer behavior and analytics data
+```
+
+## Code Structure
+
+### Main Agent (`agent.py`)
+
+- **`youtube_search_agent`**: Local agent with LangChain YouTube search tool
+- **`bigquery_agent`**: Remote A2A agent configuration for BigQuery operations
+- **`root_agent`**: Main orchestrator with task delegation logic
+
+### Remote BigQuery Agent (`remote_a2a/bigquery_agent/`)
+
+- **`agent.py`**: Implementation of the BigQuery agent with OAuth toolset
+- **`agent.json`**: Agent card of the A2A agent
+- **`BigQueryToolset`**: OAuth-enabled tools for BigQuery dataset and table management
+
+## OAuth Authentication Workflow
+
+The OAuth authentication process follows this pattern:
+
+1. **Initial Request**: User requests BigQuery operation through root agent
+2. **Delegation**: Root agent delegates to remote BigQuery agent
+3. **Auth Check**: BigQuery agent checks for valid OAuth token
+4. **Auth Request**: If no token, agent surfaces OAuth request to root agent
+5. **User OAuth**: Root agent guides user through Google OAuth flow
+6. **Token Exchange**: Root agent sends OAuth token to BigQuery agent
+7. **API Call**: BigQuery agent uses token to make authenticated API calls
+8. **Result Return**: BigQuery agent returns results through root agent to user
+
+## Supported BigQuery Operations
+
+The BigQuery agent supports the following operations:
+
+### Dataset Operations:
+- **List Datasets**: `bigquery_datasets_list` - Get all user's datasets
+- **Get Dataset**: `bigquery_datasets_get` - Get specific dataset details
+- **Create Dataset**: `bigquery_datasets_insert` - Create new dataset
+
+### Table Operations:
+- **List Tables**: `bigquery_tables_list` - Get tables in a dataset
+- **Get Table**: `bigquery_tables_get` - Get specific table details
+- **Create Table**: `bigquery_tables_insert` - Create new table in dataset
+
+## Extending the Sample
+
+You can extend this sample by:
+
+- Adding more Google Cloud services (Cloud Storage, Compute Engine, etc.)
+- Implementing token refresh and expiration handling
+- Adding role-based access control for different BigQuery operations
+- Creating OAuth flows for other providers (Microsoft, Facebook, etc.)
+- Adding audit logging for authentication events
+- Implementing multi-tenant OAuth token management
+
+## Deployment to Other Environments
+
+When deploying the remote BigQuery A2A agent to different environments (e.g., Cloud Run, different hosts/ports), you **must** update the `url` field in the agent card JSON file:
+
+### Local Development
+```json
+{
+  "url": "http://localhost:8001/a2a/bigquery_agent",
+  ...
+}
+```
+
+### Cloud Run Example
+```json
+{
+  "url": "https://your-bigquery-service-abc123-uc.a.run.app/a2a/bigquery_agent",
+  ...
+}
+```
+
+### Custom Host/Port Example
+```json
+{
+  "url": "https://your-domain.com:9000/a2a/bigquery_agent",
+  ...
+}
+```
+
+**Important:** The `url` field in `remote_a2a/bigquery_agent/agent.json` must point to the actual RPC endpoint where your remote BigQuery A2A agent is deployed and accessible.
+
+## Troubleshooting
+
+**Connection Issues:**
+- Ensure the local ADK web server is running on port 8000
+- Ensure the remote A2A server is running on port 8001
+- Check that no firewall is blocking localhost connections
+- **Verify the `url` field in `remote_a2a/bigquery_agent/agent.json` matches the actual deployed location of your remote A2A server**
+- Verify the agent card URL passed to RemoteA2AAgent constructor matches the running A2A server
+
+
+**OAuth Issues:**
+- Verify OAuth client ID and secret are correctly set in .env file
+- Ensure OAuth redirect URIs are properly configured in Google Cloud Console
+- Check that the OAuth scopes include BigQuery access permissions
+- Verify the user has access to the BigQuery projects/datasets
+
+**BigQuery Access Issues:**
+- Ensure the authenticated user has BigQuery permissions
+- Check that the Google Cloud project has BigQuery API enabled
+- Verify dataset and table names are correct and accessible
+- Check for quota limits on BigQuery API calls
+
+**Agent Communication Issues:**
+- Check the logs for both the local ADK web server and remote A2A server
+- Verify OAuth tokens are properly passed between agents
+- Ensure agent instructions are clear about authentication requirements
+- **Double-check that the RPC URL in the agent.json file is correct and accessible**