Skip to content

Conversation

@Shironex
Copy link
Collaborator

@Shironex Shironex commented Jan 14, 2026

Changes from branch feature/v0.11.0rc-1768413909856-a0al

…ndling in agent info panel

- Reduced the maximum height of the task progress panel from 300px to 200px for better UI consistency.
- Introduced a new `effectiveTodos` calculation in the agent info panel to correctly display tasks from `planSpec` when available, ensuring accurate task counts and statuses.
- Updated references to use `effectiveTodos` instead of the original `agentInfo.todos` for task display logic in the agent info panel.
- Adjusted the height of various modal components to align with the new task progress panel height.
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @Shironex, 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 focuses on refining the user interface and experience for agent output and task management. It introduces a more robust way to display agent tasks by prioritizing structured plan specifications, while also making several layout adjustments to the agent output modal for improved visual presentation. These changes aim to provide clearer and more consistent feedback on agent progress and activities.

Highlights

  • Enhanced Task List Display: The task list in Kanban cards now intelligently derives tasks from planSpec.tasks when available, providing a more accurate representation for agents using a full plan mode. It falls back to agentInfo.todos if planSpec is not used.
  • Improved Agent Output Modal UI/UX: The agent output modal has received UI/UX adjustments, including reduced minimum heights for content sections (changes, summary, output log) and a more flexible styling for the task progress panel.
  • Task Status Mapping: The display logic for tasks now maps 'failed' statuses to 'pending' to ensure consistent and appropriate visual feedback within the task list.
  • Dependency Cleanup: Several peer: true declarations have been removed from @esbuild related entries in package-lock.json, streamlining dependency management.

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

@Shironex Shironex self-assigned this Jan 14, 2026
@Shironex Shironex added Bug Something isn't working Testers-Requested Request for others to test an enhancement or bug fix/etc. Do Not Merge Use this label if something should not be merged. labels Jan 14, 2026
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 a fix for the task list display on Kanban cards, ensuring tasks are correctly sourced from planSpec when available. The implementation using useMemo to create effectiveTodos is well-done and correctly handles the fallback to agentInfo.todos. Additionally, several UI/UX tweaks have been made to reduce the height of modal components, which should improve the layout on smaller screens. I have one minor suggestion to improve code conciseness.

// instead of emitting TodoWrite tool calls in the output log
const effectiveTodos = useMemo(() => {
// First priority: use planSpec.tasks if available (modern approach)
if (feature.planSpec?.tasks && feature.planSpec.tasks.length > 0) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The condition to check for the existence and non-emptiness of feature.planSpec.tasks can be made more concise by using optional chaining on the length property. The current check is a bit verbose.

Suggested change
if (feature.planSpec?.tasks && feature.planSpec.tasks.length > 0) {
if (feature.planSpec?.tasks?.length) {

@coderabbitai
Copy link

coderabbitai bot commented Jan 14, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

… fresh planSpec integration

- Added support for real-time task status updates using WebSocket events, allowing the Kanban card to reflect current task progress accurately.
- Introduced a new state for fresh planSpec data fetched from the API to ensure the agent info panel displays up-to-date task information.
- Updated the effectiveTodos calculation to prioritize fresh planSpec data and incorporate real-time status, improving task display accuracy.
- Enhanced the logic to listen for relevant WebSocket events and update task statuses accordingly, ensuring synchronization with the agent output modal.
@Shironex Shironex merged commit 425e388 into v0.11.0rc Jan 14, 2026
5 of 6 checks passed
@Shironex Shironex deleted the feature/v0.11.0rc-1768413909856-a0al branch January 14, 2026 21:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Bug Something isn't working Do Not Merge Use this label if something should not be merged. Testers-Requested Request for others to test an enhancement or bug fix/etc.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants