feat: refactor toolkit icons to align with tool categories#1218
feat: refactor toolkit icons to align with tool categories#12184pmtong merged 2 commits intoeigent-ai:mainfrom
Conversation
|
@Pakchoioioi @Wendong-Fan @4pmtong would you review my PR? |
76197ce to
c9fc2d2
Compare
|
@bytecii as this PR has the screenshots, would you review please? |
|
Hi @Douglasymlai thank you for your reviewing my two PRs |
|
thanks @eureka928 for the PR, could @4pmtong and @nitpicker55555 help reviewing this? |
I will keep the pace as is... but would you merge my 4 PRs as well? |
Create getToolkitIcon() that maps toolkit names to lucide-react icons by tool category (dev, browser, documents, media, communication, integrations) with a Wrench fallback for unknown toolkits.
Replace agent-type icons with per-toolkit icons using getToolkitIcon() so each tool action (Terminal, Browser, Note, etc.) is visually distinct.
c9fc2d2 to
545cbf2
Compare
|
Thanks @eureka928 for your contribution, it looks good to me. @Douglasymlai could you help check the design? |
|
Hi @4pmtong is this not ready to merge? |
Related Issue
Fixes #1216
Description
Toolkit icons in workflow nodes currently display based on agent type (e.g. every toolkit in Developer Agent shows
CodeXml), making it hard to distinguish between different tool actions at a glance. This PR updates icons to display based on tool type (Terminal, Browser, Note, File, etc.) so each toolkit is visually distinct.Changes Made
src/lib/toolkitIcons.tsx(new): Toolkit name → lucide-react icon mapping withgetToolkitIcon()helper. Covers 30+ toolkits across 7 categories (Dev/Code, Browser/Web, Documents, Media, Communication, Integrations, Meta) with aWrenchfallback for unknown/MCP toolkits.src/components/WorkFlow/node.tsx: ReplacedagentMap[data.type]?.iconwithgetToolkitIcon()at both the left-panel running toolkit indicator and the right-panel toolkit detail view. ExtractedlastActiveToolkitvariable to avoid duplicate filter computation. Removed unusedBotimport.Testing Evidence (REQUIRED)
What is the purpose of this pull request?
Contribution Guidelines Acknowledgement