feat(agentstack-sdk-py): provide platform defaults

[JanPokorny]

Summary

Linked Issues

Fixes #2267

Documentation

• No Docs Needed:

If this PR adds new feature or changes existing. Make sure documentation is adjusted accordingly. If the docs is not needed, please explain why.

[gemini-code-assist]

Summary of Changes

Hello, 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 streamlines the agentstack-sdk-py by providing platform defaults for key server configurations. It simplifies agent deployment by removing the need to explicitly configure telemetry, context store, and authentication backend. The changes also include documentation updates to reflect the new default behavior and provide guidance on customization.

Highlights

• Platform Defaults: This PR configures the agentstack-sdk-py to use platform defaults for telemetry, context store, and authentication backend.
• Simplified Server Configuration: The server.run method no longer requires explicit configuration of telemetry, context store, and auth backend, simplifying agent deployment.
• Documentation Updates: The documentation has been updated to reflect the new default behavior and provide guidance on opting out of persistent storage and telemetry.

🧠 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

• agentstack-sdk-py
  • The server now defaults to using PlatformContextStore for persistent storage.
  • Telemetry is enabled by default.
  • PlatformAuthBackend is used by default for authentication.

Activity

• The PR addresses issue Default serve() to platform-ready configuration #2267.
• The PR removes explicit configuration of telemetry, context store, and auth backend in example agents.
• The PR updates documentation to reflect the new default behavior.

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 introduces sensible platform defaults for the AgentStack SDK, specifically for telemetry, context store, and authentication backend. This is a great improvement as it simplifies agent implementations by reducing boilerplate code. The changes are consistently applied across various agents and examples, and the documentation has been updated accordingly to reflect the new default behaviors. I have one minor suggestion for improving code consistency in the server implementation.