feat(ui): gui shell redesign, add agent detail, settings page

[kapetr]

Summary

Implements latest GUI shell redesign changes including the new agent detail page and the agent settings page.

Linked Issues

Closes #1565

Documentation

• No Docs Needed: mostly design changes

[gemini-code-assist]

Summary of Changes

Hello @kapetr, 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 delivers a comprehensive overhaul of the user interface, focusing on a cleaner, more intuitive GUI shell. It introduces dedicated pages for viewing agent details and managing agent-specific settings, alongside a significant refactoring of the application's routing and navigation components. The changes aim to improve user experience by providing clearer information and more direct control over agents and their configurations.

Highlights

• GUI Shell Redesign: The entire GUI shell has undergone a significant redesign, affecting core layout components, navigation, and overall user interface structure. This includes refactoring existing layouts and introducing new common layout components.
• New Agent Detail Page: A dedicated agent detail page has been added, providing comprehensive information about an agent, including its description, documentation links, authors, contributors, and a list of its associated tools.
• New Agent Settings Page: A new agent-specific settings page has been introduced, allowing users to manage and save secrets required by individual agents using a form-based interface with react-hook-form.
• URL Structure Update: The application's URL routing has been updated, moving agent-related routes from /run/[providerId] to a more streamlined /[providerId] structure, with redirects in place for backward compatibility.
• Enhanced Agent Metadata Definition: The agentstack-sdk-py now supports richer agent metadata through AgentDetail and AgentDetailContributor, allowing agents to define their name, interaction mode, author, contributors, and license directly in their Python code.
• Simplified Home Page and Navigation: The home page now features a simplified list of agents, replacing the previous card-based layout. Sidebar navigation has been refactored, removing several dedicated navigation components and introducing a more dynamic and consolidated approach for sessions and global settings.

🧠 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 significant redesign of the GUI shell, including new agent detail and settings pages, and a refactored navigation structure. The changes align the application more closely with modern Next.js App Router patterns, which is a great improvement. The code is well-structured, and the introduction of new pages for agent details and settings enhances functionality.

My review focuses on a few key areas:

• Props Typing in Page Components: I've noticed an unconventional use of Promise for the params prop in several new page components. I've suggested aligning this with standard Next.js practices for better clarity and correctness.
• URL Generation Safety: There are a few places where providerId is used to generate URLs. Since it can be undefined, I've recommended adding guards or using safer type assertions to prevent generating invalid URLs.
• Code Cleanup: I found a leftover console.log statement that should be removed.

Overall, this is a solid refactoring that modernizes the UI architecture. Addressing the points above will improve the robustness and maintainability of the new code.

[kapetr]

/gemini review

[gemini-code-assist]

Code Review

This pull request introduces a significant redesign of the GUI shell, including a new agent detail page and an agent settings page. The changes are extensive, involving refactoring of layouts, navigation components, and routing logic. The sidebar has been replaced with a new navbar, and agent-specific views are now handled as separate pages rather than side panels. Overall, the changes appear well-structured and consistent with the goal of a UI redesign. I've identified a couple of minor issues: a leftover console.log statement that should be removed, and an opportunity for a small optimization in one of the Python examples. Great work on this large-scale refactoring!