Conversation
Summary of ChangesHello, 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 introduces a significant upgrade to how agent process flow data is visualized and interacted with. By implementing a dedicated Highlights
Changelog
Activity
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request introduces a new, more detailed process flow display, adding a NodeDetailsDialog to show comprehensive information about each node in the workflow and improving user experience. A high-severity Cross-Site Scripting (XSS) vulnerability was identified in the NodeDetailsDialog component where HTML artifacts are rendered without sanitization, which must be addressed before merging. Additionally, a critical issue with a hardcoded path in a configuration file needs attention. Further suggestions include improving the maintainability of the NodeDetailsDialog by breaking it down and reverting inlined CSS styles in RichTreeView for better separation of concerns.
# Conflicts: # dist/web.js # dist/web.umd.js
| return ( | ||
| <div class="mt-2"> | ||
| <div innerHTML={src} /> | ||
| <div innerHTML={DOMPurify.sanitize(src)} /> |
mmattu-wd
left a comment
There was a problem hiding this comment.
LGTM!
Made some small changes so the responsive behaviour is a bit cleaner and so scroll behaviour matches what we have in the flowise agent chat.
Widget:
Screen.Recording.2026-03-09.at.12.22.19.PM.mov
Full Page:
Screen.Recording.2026-03-09.at.12.42.33.PM.mov
| <NodeIcon name={props.node!.name} apiHost={props.apiHost} size={36} /> | ||
| <div style={{ 'font-weight': '600', 'font-size': '1.05rem' }}>{props.node!.label}</div> | ||
| </div> | ||
| <div style={{ display: 'flex', 'justify-content': 'flex-end', 'align-items': 'center', gap: '8px', 'flex-wrap': 'wrap', flex: '1' }}> |
There was a problem hiding this comment.
there is a PR that will start bringing in the total costs, can we have these metrics at the bottom of the node title instead of stacking to the right?

| </div> | ||
|
|
||
| {/* Content */} | ||
| <div class="node-dialog-body" style={{ padding: '16px 20px', 'overflow-y': 'initial', 'max-height': '100%' }}> |
There was a problem hiding this comment.
small change so scroll behaviour is like the flowise agent chat:
|
thanks @mmattu-wd ! lmk when its good to merge |





pf1-ezgif.com-crop-video.mp4
pf2-ezgif.com-crop-video.mp4