Changelog jan 2026 updates

[Yash1hi]

No description provided.

[github-actions]

🖼️ Image Usage Check ✅

All 230 images in the repository are being used! No unused images found.

Great job keeping the repository clean! 🎉

[gemini-code-assist]

Summary of Changes

Hello @Yash1hi, 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 introduces significant enhancements to record management and documentation. New features include a conversation tab for AI interactions, CSV export for records, and arbitrary string search capabilities. Additionally, it refines and clarifies existing documentation, notably revamping the Playground guide to emphasize its visual workflow builder and updating the LangChain integration documentation to highlight improved trace and tool visualization.

Highlights

• New Conversation Tab: A dedicated tab on the record details page now displays multi-turn AI interactions in an easy-to-read chat format, simplifying review and debugging.
• Records CSV Export: Users can now export records directly from the Records page as a CSV file, facilitating sharing, offline analysis, and integration with external tools.
• Arbitrary String Search in Records: The Records page supports full-text search across all record fields, allowing users to quickly find specific records by searching any substring in inputs, outputs, or expected values.
• Playground Documentation Revamp: The Playground documentation has been significantly updated to describe it as a visual workflow builder, with a concise overview and simplified evaluation steps.
• Enhanced LangChain Tracing Documentation: The LangChain quickstart guide now details improved trace visualization, including enhanced span classification and specific tool categorization for better understanding of AI agent operations.

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

[gemini-code-assist]

Code Review

This pull request introduces a series of documentation updates across the product. It adds a new changelog entry for January 2026, completely revamps the Playground documentation to reflect a new visual workflow, and enhances the documentation for Records, Runs, and LangChain tracing with more details on new features and capabilities. My review focuses on improving the consistency and clarity of the new content. I've suggested aligning the text about clickable table rows between the 'Runs' and 'Records' pages for a more consistent user experience. I also recommended clarifying the examples for span classification in the LangChain quickstart guide to avoid potential confusion.