Skip to content

Conversation

@yingyinggu-dev
Copy link

@yingyinggu-dev yingyinggu-dev commented Jan 18, 2026

Please ensure you have read the contribution guide before creating a pull request.

Link to Issue or Description of Change

1. Link to an existing issue (if applicable):

  • Closes: #issue_number
  • Related: #issue_number

2. Or, if no issue exists, describe the change:

If applicable, please follow the issue templates to provide as much detail as
possible.

Problem:
A clear and concise description of what the problem is.

Solution:
A clear and concise description of what you want to happen and why you choose
this solution.

Testing Plan

Please describe the tests that you ran to verify your changes. This is required
for all PRs that are not small documentation or typo fixes.

Unit Tests:

  • I have added or updated unit tests for my change.
  • All unit tests pass locally.

Please include a summary of passed pytest results.

pytest tests/unittests/test_runners.py::test_run_live_state_delta_applied_to_session -v
===test session starts===
tests/unittests/test_runners.py::test_run_live_state_delta_applied_to_session PASSED [100%]
=== 1 passed in 3.30s ===

Manual End-to-End (E2E) Tests:

Please provide instructions on how to manually test your changes, including any
necessary setup or configuration. Please provide logs or screenshots to help
reviewers better understand the fix.

Checklist

  • I have read the CONTRIBUTING.md document.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have added tests that prove my fix is effective or that my feature works.
  • New and existing unit tests pass locally with my changes.
  • I have manually tested my changes end-to-end.
  • Any dependent changes have been merged and published in downstream modules.

Additional context

Add any other context or screenshots about the feature request here.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @yingyinggu-dev, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the run_live function by introducing a new state_delta parameter. This addition provides a mechanism to apply optional state changes directly to a session during its live execution, offering greater flexibility in managing and updating session data dynamically.

Highlights

  • New state_delta parameter: Introduced an optional state_delta parameter to the run_live function in src/google/adk/runners.py. This parameter allows for dynamic, optional state changes to be applied to a session.
  • Session State Modification: Implemented logic within run_live to process the state_delta. If provided, an Event containing the specified state changes is created and appended to the current session, effectively modifying its state during runtime.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@adk-bot
Copy link
Collaborator

adk-bot commented Jan 18, 2026

Response from ADK Triaging Agent

Hello @yingyinggu-dev, thank you for creating this PR!

In order to help the reviewers to better understand the context of this PR, could you please fill out the PR template and provide the following information?

  • Link to an existing issue or a description of the change
  • Testing plan, including unit tests and manual end-to-end tests.

This information will help reviewers to review your PR more efficiently. Thanks!

@adk-bot adk-bot added the live [Component] This issue is related to live, voice and video chat label Jan 18, 2026
@adk-bot
Copy link
Collaborator

adk-bot commented Jan 18, 2026

Response from ADK Triaging Agent

Hello @yingyinggu-dev, thank you for creating this PR!

Could you please fill out the PR template, including the link to an issue (or a description of the change) and the testing plan?

This information will help reviewers to review your PR more efficiently. Thanks!

@adk-bot
Copy link
Collaborator

adk-bot commented Jan 18, 2026

Response from ADK Triaging Agent

Hello @yingyinggu-dev, thank you for creating this PR!

Could you please associate a GitHub issue with this PR? If one doesn't exist, you can create one or describe the feature in the PR description.

Additionally, could you please provide a testing plan in the PR description to detail how you've tested these changes?

This information will help reviewers to review your PR more efficiently. Thanks!

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces an optional state_delta parameter to the run_live method, allowing for state changes to be applied to the session at the beginning of a live run. The implementation is sound and follows existing patterns in the codebase for creating and appending events. My main feedback is a suggestion to refactor the logic for creating state change events to reduce code duplication across the Runner class, which could be addressed in a follow-up.

Comment on lines +1015 to +1022
if state_delta:
state_event = Event(
invocation_id=invocation_context.invocation_id,
author='user',
actions=EventActions(state_delta=state_delta),
)
_apply_run_config_custom_metadata(state_event, run_config)
await self.session_service.append_event(session=session, event=state_event)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The logic to create and append a state change event is similar to logic in other methods like _append_new_message_to_session and rewind_async. To improve maintainability and reduce code duplication, consider extracting this into a private helper method in a follow-up change. A shared helper would centralize the creation of these control events.

For example, a helper could look like this:

async def _append_control_event(self, session: Session, invocation_context: InvocationContext, actions: EventActions, run_config: Optional[RunConfig]):
    event = Event(
        invocation_id=invocation_context.invocation_id,
        author='user',
        actions=actions,
    )
    _apply_run_config_custom_metadata(event, run_config)
    await self.session_service.append_event(session=session, event=event)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

live [Component] This issue is related to live, voice and video chat

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants