feat(py/genkit): add context, name, client_header to Genkit constructor

[yesudeep]

Summary

Adds three new parameters to the Genkit constructor for JS SDK parity:

Parameter	JS SDK Equivalent	Purpose
context	GenkitOptions.context	Default context data for flows and tools, stored on registry.context
name	GenkitOptions.name	Display name shown in developer tooling, written to the runtime file
client_header	GenkitOptions.clientHeader	Additional attribution info appended to x-goog-api-client header

Changes

Core (genkit.core):

• constants.py — Added get_client_header() and set_client_header() (thread-safe, matching JS global pattern)
• registry.py — Added context and name attributes to Registry
• __init__.py — Exported new functions

AI layer (genkit.ai):

• _aio.py — Added context, name, client_header params to Genkit.__init__
• _base_async.py — Propagated context/name to registry and RuntimeManager
• _runtime.py — Added name to runtime file JSON metadata
• __init__.py — Exported get_client_header and set_client_header

Tests (12 new, 512 total pass):

• constants_test.py — 3 tests for header get/set functions
• genkit_api_test.py — 6 tests for constructor parameters
• runtime_test.py — 3 tests for runtime file name field

Testing

• All 512 existing tests pass
• Ruff checks clean
• Pre-commit and pre-push hooks pass

[gemini-code-assist]

Summary of Changes

Hello @yesudeep, I'm Gemini Code Assist¹! 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 significantly enhances the Python Genkit SDK by introducing new configuration options to its main constructor, achieving greater feature parity with the JavaScript SDK. These additions provide developers with more control over application context, improve visibility in developer tools through custom naming, and allow for detailed API client attribution. The changes aim to make the Genkit Python SDK more flexible and observable for users.

Highlights

• Enhanced Genkit Constructor: The Genkit constructor now accepts context, name, and client_header parameters, aligning with the JavaScript SDK for feature parity.
• Context Data Management: The context parameter allows setting default context data for flows and tools, which is then made available via registry.context.
• Developer Tooling Identification: A new name parameter provides a display name for developer tooling (e.g., Genkit Dev UI), which is written to the runtime file for easier identification.
• API Client Attribution: The client_header parameter enables adding custom attribution information to the x-goog-api-client header. This is managed through new thread-safe get_client_header and set_client_header functions.
• Comprehensive Testing: 12 new tests have been added to thoroughly cover the functionality of these new constructor parameters and the client header management, ensuring robustness and correctness.

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

Changelog

• py/packages/genkit/src/genkit/ai/init.py
  • Exported get_client_header and set_client_header functions from genkit.core.
• py/packages/genkit/src/genkit/ai/_aio.py
  • Added context, name, and client_header as optional parameters to the Genkit.__init__ method.
  • Propagated context and name to the base async class constructor.
  • Called set_client_header if a client_header is provided.
  • Updated docstrings to reflect the new parameters.
• py/packages/genkit/src/genkit/ai/_base_async.py
  • Added context and name as optional parameters to _BaseGenkitAsync.__init__.
  • Assigned provided context and name values to self.registry.context and self.registry.name respectively.
  • Passed self.registry.name to the RuntimeManager constructor.
  • Updated docstrings for the new parameters.
• py/packages/genkit/src/genkit/ai/_runtime.py
  • Modified _create_and_write_runtime_file to accept an optional name parameter.
  • Included the name in the runtime file's JSON metadata if provided.
  • Added name as an optional parameter to RuntimeManager.__init__ and stored it internally.
  • Updated write_runtime_file to pass the stored name to _create_and_write_runtime_file.
• py/packages/genkit/src/genkit/core/init.py
  • Exported get_client_header and set_client_header functions.
• py/packages/genkit/src/genkit/core/constants.py
  • Introduced _client_header_lock (a threading.Lock) and _additional_client_header for thread-safe management of client header attribution.
  • Added get_client_header() to return the combined base and additional client header.
  • Added set_client_header(header: str) to set the additional client header attribution.
  • Updated module docstring to explain client header management.
• py/packages/genkit/src/genkit/core/registry.py
  • Added context (dict) and name (str) attributes to the Registry class, initialized to None.
  • Updated class docstring to describe these new attributes.
• py/packages/genkit/tests/genkit/ai/genkit_api_test.py
  • Added 6 new asynchronous tests to verify the correct handling and propagation of context, name, and client_header parameters in the Genkit constructor.
• py/packages/genkit/tests/genkit/ai/runtime_test.py
  • Added 3 new tests to ensure the name parameter is correctly included in the runtime file metadata by _create_and_write_runtime_file and RuntimeManager.
• py/packages/genkit/tests/genkit/core/constants_test.py
  • Added 3 new tests to validate the functionality of get_client_header and set_client_header, including default behavior and overwriting.

Activity

• The pull request introduces 12 new tests, bringing the total to 512 passing tests.
• All existing tests passed successfully.
• Ruff checks passed without issues.
• Pre-commit and pre-push hooks passed.

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

[gemini-code-assist]

Code Review

This pull request effectively adds context, name, and client_header parameters to the Genkit constructor, achieving parity with the JS SDK. The changes are well-implemented across the core and AI layers, including updates to the registry, runtime manager, and constants. The introduction of thread-safe functions for managing the client header is a good addition. The new functionality is thoroughly covered by new tests, which is excellent.

I have one suggestion to improve the testability of the new client header functionality by making a small adjustment to the set_client_header API. Overall, this is a solid contribution.