fix: Use str() to calculate fingerprint instead of json.dumps

This is to avoid serialization issue for some fields that are not json serializable.
meanwhile restructure the debug logs in context cache manager for better debugging potential issues.

PiperOrigin-RevId: 811182492

.gemini/settings.json

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

.github/ISSUE_TEMPLATE/bug_report.md

@@ -7,18 +7,19 @@ assignees: ''
 
 ---
 
-** Please make sure you read the contribution guide and file the issues in the rigth place. **
+** Please make sure you read the contribution guide and file the issues in the right place. **
 [Contribution guide.](https://google.github.io/adk-docs/contributing-guide/)
 
 **Describe the bug**
 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/ISSUE_TEMPLATE/feature_request.md

@@ -7,7 +7,7 @@ assignees: ''
 
 ---
 
-** Please make sure you read the contribution guide and file the issues in the rigth place. **
+** Please make sure you read the contribution guide and file the issues in the right place. **
 [Contribution guide.](https://google.github.io/adk-docs/contributing-guide/)
 
 **Is your feature request related to a problem? Please describe.**

.github/release-please.yml

@@ -0,0 +1,5 @@
+releaseType: python
+handleGHRelease: true
+bumpMinorPreMajor: false
+extraFiles:
+  - src/google/adk/version.py

.github/release-trigger.yml

@@ -0,0 +1 @@
+enabled: true

.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

@@ -0,0 +1,113 @@
+# 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.
+
+name: "Check file contents"
+
+on:
+  pull_request:
+    paths:
+      - '**.py'
+
+jobs:
+  check-file-contents:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout Code
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 2
+
+      - name: Check for logger pattern in all changed Python files
+        run: |
+          git fetch origin ${{ github.base_ref }}
+          CHANGED_FILES=$(git diff --diff-filter=ACMR --name-only origin/${{ github.base_ref }}...HEAD | grep -E '\.py$' || true)
+          if [ -n "$CHANGED_FILES" ]; then
+            echo "Changed Python files to check:"
+            echo "$CHANGED_FILES"
+            echo ""
+
+            # Check for 'logger = logging.getLogger(__name__)' in changed .py files.
+            # The grep command will exit with a non-zero status code if the pattern is not found.
+            # We invert the exit code with ! so the step succeeds if the pattern is NOT found.
+            set +e
+            FILES_WITH_FORBIDDEN_LOGGER=$(grep -lE 'logger = logging\.getLogger\(__name__\)' $CHANGED_FILES)
+            GREP_EXIT_CODE=$?
+            set -e
+
+            # grep exits with 0 if matches are found, 1 if no matches are found.
+            # A non-zero exit code other than 1 indicates an error.
+            if [ $GREP_EXIT_CODE -eq 0 ]; then
+              echo "❌ Found forbidden use of 'logger = logging.getLogger(__name__)'. Please use 'logger = logging.getLogger('google_adk.' + __name__)' instead."
+              echo "The following files contain the forbidden pattern:"
+              echo "$FILES_WITH_FORBIDDEN_LOGGER"
+              exit 1
+            elif [ $GREP_EXIT_CODE -eq 1 ]; then
+              echo "✅ No instances of 'logger = logging.getLogger(__name__)' found in changed Python files."
+            fi
+          else
+            echo "✅ No relevant Python files found."
+          fi
+
+      - name: Check for import pattern in certain changed Python files
+        run: |
+          git fetch origin ${{ github.base_ref }}
+          CHANGED_FILES=$(git diff --diff-filter=ACMR --name-only origin/${{ github.base_ref }}...HEAD | grep -E '\.py$' | grep -v -E '__init__.py$|version.py$|tests/.*|contributing/samples/' || true)
+          if [ -n "$CHANGED_FILES" ]; then
+            echo "Changed Python files to check:"
+            echo "$CHANGED_FILES"
+            echo ""
+
+            # 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 || true)
+
+            # Check if the list of non-compliant files is empty
+            if [ -z "$FILES_MISSING_IMPORT" ]; then
+              echo "✅ All modified Python files include 'from __future__ import annotations'."
+              exit 0
+            else
+              echo "❌ The following files are missing 'from __future__ import annotations':"
+              echo "$FILES_MISSING_IMPORT"
+              echo "This import is required to allow forward references in type annotations without quotes."
+              exit 1
+            fi
+          else
+            echo "✅ No relevant Python files found."
+          fi
+
+      - name: Check for import from cli package in certain changed Python files
+        run: |
+          git fetch origin ${{ github.base_ref }}
+          CHANGED_FILES=$(git diff --diff-filter=ACMR --name-only origin/${{ github.base_ref }}...HEAD | grep -E '\.py$' | grep -v -E 'cli/.*|tests/.*|contributing/samples/' || true)
+          if [ -n "$CHANGED_FILES" ]; then
+            echo "Changed Python files to check:"
+            echo "$CHANGED_FILES"
+            echo ""
+
+            set +e
+            FILES_WITH_FORBIDDEN_IMPORT=$(grep -lE '^from.*cli.*import.*$' $CHANGED_FILES)
+            GREP_EXIT_CODE=$?
+            set -e
+
+            if [[ $GREP_EXIT_CODE -eq 0 ]]; then
+              echo "❌ Do not import from the cli package outside of the cli package. If you need to reuse the code elsewhere, please move the code outside of the cli package."
+              echo "The following files contain the forbidden pattern:"
+              echo "$FILES_WITH_FORBIDDEN_IMPORT"
+              exit 1
+            else
+              echo "✅ No instances of importing from the cli package found in relevant changed Python files."
+            fi
+          else
+            echo "✅ No relevant Python files found."
+          fi

.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/isort.yml

@@ -0,0 +1,69 @@
+# 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.
+
+name: Check sorting of imports
+
+on:
+  pull_request:
+    paths:
+      - '**.py'
+      - 'pyproject.toml'
+
+jobs:
+  isort-check:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 2
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: '3.x'
+
+      - name: Install isort
+        run: |
+          pip install isort
+
+      - name: Run isort on changed files
+        id: run_isort
+        run: |
+          git fetch origin ${{ github.base_ref }}
+          CHANGED_FILES=$(git diff --diff-filter=ACMR --name-only origin/${{ github.base_ref }}...HEAD | grep -E '\.py$' || true)
+          if [ -n "$CHANGED_FILES" ]; then
+            echo "Changed Python files:"
+            echo "$CHANGED_FILES"
+            echo ""
+            FORMATTED_FILES=$(echo "$CHANGED_FILES" | tr '\n' ' ')
+
+            # Run isort --check
+            set +e
+            isort --check $CHANGED_FILES
+            RESULT=$?
+            set -e
+            if [ $RESULT -ne 0 ]; then
+              echo ""
+              echo "❌ isort check failed!"
+              echo "👉 To fix import order, run locally:"
+              echo ""
+              echo "    isort $FORMATTED_FILES"
+              echo ""
+              exit $RESULT
+            fi
+          else
+            echo "No Python files changed. Skipping isort check."
+          fi

.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/pyink.yml

@@ -17,8 +17,7 @@ name: Check Pyink Formatting
 on:
   pull_request:
     paths:
-      - 'src/**/*.py'
-      - 'tests/**/*.py'
+      - '**.py'
       - 'pyproject.toml'
 
 jobs:
@@ -28,6 +27,8 @@ jobs:
     steps:
       - name: Checkout code
         uses: actions/checkout@v4
+        with:
+          fetch-depth: 2
 
       - name: Set up Python
         uses: actions/setup-python@v5
@@ -38,36 +39,31 @@ jobs:
         run: |
           pip install pyink
 
-      - name: Detect changed Python files
-        id: detect_changes
+      - name: Run pyink on changed files
+        id: run_pyink
         run: |
           git fetch origin ${{ github.base_ref }}
           CHANGED_FILES=$(git diff --diff-filter=ACMR --name-only origin/${{ github.base_ref }}...HEAD | grep -E '\.py$' || true)
-          echo "CHANGED_FILES=${CHANGED_FILES}" >> $GITHUB_ENV
-
-      - name: Run pyink on changed files
-        if: env.CHANGED_FILES != ''
-        run: |
-          echo "Changed Python files:"
-          echo "$CHANGED_FILES"
-
-          # Run pyink --check
-          set +e
-          pyink --check --config pyproject.toml $CHANGED_FILES
-          RESULT=$?
-          set -e
-
-          if [ $RESULT -ne 0 ]; then
+          if [ -n "$CHANGED_FILES" ]; then
+            echo "Changed Python files:"
+            echo "$CHANGED_FILES"
             echo ""
-            echo "❌ Pyink formatting check failed!"
-            echo "👉 To fix formatting, run locally:"
-            echo ""
-            echo "    pyink --config pyproject.toml $CHANGED_FILES"
-            echo ""
-            exit $RESULT
+            FORMATTED_FILES=$(echo "$CHANGED_FILES" | tr '\n' ' ')
+
+            # Run pyink --check
+            set +e
+            pyink --check --diff --config pyproject.toml $CHANGED_FILES
+            RESULT=$?
+            set -e
+            if [ $RESULT -ne 0 ]; then
+              echo ""
+              echo "❌ Pyink formatting check failed!"
+              echo "👉 To fix formatting, run locally:"
+              echo ""
+              echo "    pyink --config pyproject.toml $FORMATTED_FILES"
+              echo ""
+              exit $RESULT
+            fi
+          else
+            echo "No Python files changed. Skipping pyink check."
           fi
-
-      - name: No changed Python files detected
-        if: env.CHANGED_FILES == ''
-        run: |
-          echo "No Python files changed. Skipping pyink check."

.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,19 +36,26 @@ 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: |
         uv venv .venv
         source .venv/bin/activate
-        uv sync --extra test --extra eval
+        uv sync --extra test --extra eval --extra a2a
 
     - name: Run unit tests with pytest
       run: |
         source .venv/bin/activate
-        pytest tests/unittests \
-          --ignore=tests/unittests/artifacts/test_artifact_service.py \
-          --ignore=tests/unittests/tools/google_api_tool/test_googleapi_to_openapi_converter.py        
-          
+        if [[ "${{ matrix.python-version }}" == "3.9" ]]; then
+          pytest tests/unittests \
+            --ignore=tests/unittests/a2a \
+            --ignore=tests/unittests/tools/mcp_tool \
+            --ignore=tests/unittests/artifacts/test_artifact_service.py \
+            --ignore=tests/unittests/tools/google_api_tool/test_googleapi_to_openapi_converter.py
+        else
+          pytest tests/unittests \
+            --ignore=tests/unittests/artifacts/test_artifact_service.py \
+            --ignore=tests/unittests/tools/google_api_tool/test_googleapi_to_openapi_converter.py
+        fi

.github/workflows/triage.yml

@@ -0,0 +1,44 @@
+name: ADK Issue Triaging Agent
+
+on:
+  issues:
+    types: [opened, reopened]
+  schedule:
+    - cron: '0 */6 * * *' # every 6h
+
+jobs:
+  agent-triage-issues:
+    runs-on: ubuntu-latest
+    permissions:
+      issues: 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'
+          INTERACTIVE: 0
+          EVENT_NAME: ${{ github.event_name }} # 'issues', 'schedule', etc.
+          ISSUE_NUMBER: ${{ github.event.issue.number }}
+          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
+          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
@@ -96,4 +97,4 @@ site/
 Thumbs.db
 *.bak
 *.tmp
-*.temp 
+*.temp

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,22 +2,20 @@
 
 We'd love to accept your patches and contributions to this project.
 
-## Table of Contents
-
-- [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)
-  - [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
 
@@ -40,124 +38,200 @@ sign a new one.
 This project follows
 [Google's Open Source Community Guidelines](https://opensource.google/conduct/).
 
-## Contribution workflow
-
-### Finding Issues to Work On
-
-- Browse issues labeled **`good first issue`** (newcomer-friendly) or **`help wanted`** (general contributions).
-- For other issues, please kindly ask before contributing to avoid duplication.
-
-
-### Requirement for PRs
-
-- 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.
-
-### 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
-
-### Testing Requirements
-
-To maintain code quality and prevent regressions, all code changes must include comprehensive tests and verifiable end-to-end (E2E) evidence.
-
-
-#### Unit Tests
-
-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.
-
-#### 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.
-
-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.
-
-- **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.
-
-### 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
-    git clone git@github.com:google/adk-python.git
-    cd adk-python
-    ```
-2.  **Create and activate a virtual environment:**
-
-    ```shell
-    python -m venv .venv
-    ```
-
-    ```shell
-    source .venv/bin/activate
-    ```
-
-    **windows**
-    ```shell
-    source .\.venv\Scripts\activate
-    ```
-
-3.  **Install dependencies:**
-
-    ```shell
-    pip install uv
-    uv sync --all-extras
-    ```
-4.  **Run unit tests:**
-
-    ```shell
-    uv run pytest ./tests/unittests
-    ```
-5.  **Run pyink to format codebase:**
-
-    ```shell
-    uv run pyink  --config pyproject.toml ./src
-    ```
-
-6. **Build the package**
-    ```shell
-    uv build
-    ```
-
-7. **Local Testing**
-    Have a simple testing folder setup as mentioned in the [quickstart](https://google.github.io/adk-docs/get-started/quickstart/)
-    then install the local package with changes after building it using the below command to test the changes.
-
-    ```shell
-    uv pip install <YOUR_WHL_FILE_PATH>
-
-    [eg]: uv pip install <ADK_PROJECT_PATH>/dist/google_adk-0.4.0-py3-none-any.whl
-    ```
-
 ### 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.
+
+## Contribution workflow
+
+### Finding Issues to Work On
+
+-   Browse issues labeled **`good first issue`** (newcomer-friendly) or **`help
+    wanted`** (general contributions).
+-   For other issues, please kindly ask before contributing to avoid
+    duplication.
+
+### 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
+
+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
+
+### Testing Requirements
+
+To maintain code quality and prevent regressions, all code changes must include
+comprehensive tests and verifiable end-to-end (E2E) evidence.
+
+#### Unit Tests
+
+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.
+
+#### 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.
+
+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.
+
+-   **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.
+
+### 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
+    gh repo clone google/adk-python
+    cd adk-python
+    ```
+
+2.  **Install uv:**
+
+    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.
+
+    Create a workspace venv using uv.
+
+    ```shell
+    uv venv --python "python3.11" ".venv"
+    ```
+
+    Activate the workspace venv.
+
+    ```shell
+    source .venv/bin/activate
+    ```
+
+    **windows** `shell source .\.venv\Scripts\activate`
+
+4.  **Install dependencies:**
+
+    ```shell
+    uv sync --all-extras
+    ```
+
+    **NOTE**: for convenience, installing all extra deps as a starting point.
+
+5.  **Run unit tests:**
+
+    ```shell
+    pytest ./tests/unittests
+    ```
+
+    NOTE: for accurate repro of test failure, only include `test`, `eval` and
+    `a2a` as extra dependencies.
+
+    ```shell
+    uv sync --extra test --extra eval --extra a2a
+    pytest ./tests/unittests
+    ```
+
+6.  **Auto-format the code:**
+
+    **NOTE**: We use `isort` and `pyink` for styles. Use the included
+    autoformat.sh to auto-format.
+
+    ```shell
+    ./autoformat.sh
+    ```
+
+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
+    [quickstart](https://google.github.io/adk-docs/get-started/quickstart/).
+
+    Then following below steps to test your changes:
+
+    Create a clean venv and activate it:
+
+    ```shell
+    VENV_PATH=~/venvs/adk-quickstart
+    ```
+
+    ```shell
+    command -v deactivate >/dev/null 2>&1 && deactivate
+    ```
+
+    ```shell
+    rm -rf $VENV_PATH \
+      && python3 -m venv $VENV_PATH \
+      && source $VENV_PATH/bin/activate
+    ```
+
+    Install the locally built wheel file:
+
+    ```shell
+    pip install dist/google_adk-<version>-py3-none-any.whl
+    ```
+
+## Contributing Resources
+
+[Contributing folder](https://github.com/google/adk-python/tree/main/contributing)
+has resources that is helpful for contributors.
+
+## Vibe Coding
+
+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,8 +1,10 @@
 # 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)
 
 <html>
     <h2 align="center">
@@ -13,8 +15,10 @@
     </h3>
     <h3 align="center">
       Important Links:
-      <a href="https://google.github.io/adk-docs/">Docs</a> &
-      <a href="https://github.com/google/adk-samples">Samples</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>.
     </h3>
 </html>
 
@@ -23,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,
@@ -38,6 +49,12 @@ Agent Development Kit (ADK) is a flexible and modular framework for developing a
 - **Deploy Anywhere**: Easily containerize and deploy agents on Cloud Run or
   scale seamlessly with Vertex AI Agent Engine.
 
+## 🤖 Agent2Agent (A2A) Protocol and ADK Integration
+
+For remote agent-to-agent communication, ADK integrates with the
+[A2A protocol](https://github.com/google-a2a/A2A/).
+See this [example](https://github.com/a2aproject/a2a-samples/tree/main/samples/python/agents)
+for how they can work together.
 
 ## 🚀 Installation
 
@@ -49,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.
 
@@ -79,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]
@@ -94,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,
@@ -123,27 +140,20 @@ adk eval \
     samples_for_testing/hello_world/hello_world_eval_set_001.evalset.json
 ```
 
-## 🤖 A2A and ADK integration
-
-For remote agent-to-agent communication, ADK integrates with the
-[A2A protocol](https://github.com/google/A2A/).
-See this [example](https://github.com/google/A2A/tree/main/samples/python/agents/google_adk)
-for how they can work together.
-
 ## 🤝 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).
+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/).
 - 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.
 
-## Preview
-
-This feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the [Service Specific Terms](https://cloud.google.com/terms/service-terms#1). Pre-GA features are available "as is" and might have limited support. For more information, see the [launch stage descriptions](https://cloud.google.com/products?hl=en#product-launch-stages).
-
 ---
 
 *Happy Agent Building!*

autoformat.sh

@@ -0,0 +1,67 @@
+#!/bin/bash
+# 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.
+
+# Autoformat ADK codebase.
+
+if ! command -v isort &> /dev/null
+then
+    echo "isort not found, refer to CONTRIBUTING.md to set up dev environment first."
+    exit
+fi
+
+if ! command -v pyink &> /dev/null
+then
+    echo "pyink not found, refer to CONTRIBUTING.md to set up dev environment first."
+    exit
+fi
+
+echo '---------------------------------------'
+echo '|  Organizing imports for src/...'
+echo '---------------------------------------'
+
+isort src/
+echo 'All done! ✨ 🍰 ✨'
+
+echo '---------------------------------------'
+echo '|  Organizing imports for tests/...'
+echo '---------------------------------------'
+
+isort tests/
+echo 'All done! ✨ 🍰 ✨'
+
+echo '---------------------------------------'
+echo '|  Organizing imports for contributing/...'
+echo '---------------------------------------'
+
+isort contributing/
+echo 'All done! ✨ 🍰 ✨'
+
+echo '---------------------------------------'
+echo '|  Auto-formatting src/...'
+echo '---------------------------------------'
+
+find -L src/ -not -path "*/.*" -type f -name "*.py" -exec pyink --config pyproject.toml {} +
+
+echo '---------------------------------------'
+echo '|  Auto-formatting tests/...'
+echo '---------------------------------------'
+
+find -L tests/ -not -path "*/.*" -type f -name "*.py" -exec pyink --config pyproject.toml {} +
+
+echo '---------------------------------------'
+echo '|  Auto-formatting contributing/...'
+echo '---------------------------------------'
+
+find -L contributing/ -not -path "*/.*" -type f -name "*.py" -exec pyink --config pyproject.toml {} +