Skip to content

Conversation

@pavelgj
Copy link
Collaborator

@pavelgj pavelgj commented Jan 27, 2026

it's behind --experimental-reflection-v2 flag.

RFC: #4211

Checklist (if applicable):

it's behind `--experimental-reflection-v2` flag.

RFC: #4211
@github-actions github-actions bot added docs Improvements or additions to documentation js tooling config labels Jan 27, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @pavelgj, 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 implements the experimental Reflection API V2, which shifts from HTTP to WebSockets for improved communication between the Genkit CLI and Genkit Runtimes. This architecture simplifies runtime management and introduces streaming capabilities. The changes include a new WebSocket-based runtime manager, updates to the CLI start command, and modifications to the common library to support the new protocol.

Highlights

  • Reflection API V2 Implementation: This PR introduces an experimental implementation of Reflection API V2, utilizing WebSockets for communication between the Genkit CLI and Genkit Runtimes. It's enabled via the --experimental-reflection-v2 flag.
  • WebSocket-Based Communication: V2 reverses the connection direction compared to V1, with the Genkit CLI starting a WebSocket server and the Genkit Runtime connecting as a client.
  • Streaming Support: The PR extends JSON-RPC 2.0 to support streaming using Notifications for streamChunk and runActionState messages.
  • CLI Changes: The start command in the CLI is modified to include options for enabling the experimental reflection server and specifying allowed telemetry CORS hostnames.

🧠 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.

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 Reflection API V2, which leverages WebSockets for bidirectional communication between the Genkit CLI and Runtimes. This is a significant architectural change that reverses the connection direction, allowing the CLI to act as a server and Runtimes as clients. The implementation includes a new BaseRuntimeManager abstract class, with separate concrete implementations for V1 (HTTP-based) and V2 (WebSocket-based) managers, ensuring a clean separation of concerns. The changes also include necessary dependency updates, new CLI options to enable V2, and comprehensive test coverage for the new WebSocket manager and server components. The documentation for the V2 protocol is well-detailed, outlining the message formats and protocol flow. Overall, this is a well-designed and implemented feature that enhances the flexibility and capabilities of the Genkit reflection mechanism.

pavelgj and others added 4 commits January 27, 2026 10:28
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
…ate `startManager` test call with new optional parameters.
@pavelgj pavelgj marked this pull request as ready for review January 27, 2026 16:27
@pavelgj pavelgj changed the title feat: implemented reflection API v2 feat: implemented reflection API v2 in CLI and JS Jan 27, 2026
@pavelgj pavelgj changed the title feat: implemented reflection API v2 in CLI and JS feat(cli,js): implemented reflection API v2 in CLI and JS Jan 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

config docs Improvements or additions to documentation js tooling

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

1 participant