New request
#3100: Allow selecting active profile toolsets instead of manually entering each tool
We'll provision a sandbox, run an agent against the issue, and open a draft PR. You can pull the branch and iterate from there.
Hermes WebUI currently requires users to manually enter toolset names in the toolset chip, for example:
terminal, file, web, gitnexus
But when using a Hermes profile, I expect to be able to select/use the profile’s configured toolsets directly, instead of manually typing every tool that is already set in the active profile.
Hermes CLI already resolves this correctly: if the active profile has MCP tools configured, those tools are available automatically.
Example:
mcp_servers:
gitnexus:
url: http://localhost:4747/api/mcp
enabled: true
In CLI, the active profile resolves gitnexus correctly. In WebUI, I have to manually type gitnexus into the toolset chip for it to appear.
Expected behavior:
- WebUI should provide an option like Use active profile toolsets.
- It should resolve the same toolsets/MCP tools that Hermes CLI resolves for the active profile.
- Users should not need to manually enter every tool already configured in the profile.
- Custom manual toolsets can still exist, but should be clearly separate from profile-resolved defaults.
New profile-toolset resolution capability bridging backend profile config with frontend composer UI.
- static/composer.js
- static/panels.js
- api/profiles.py
- api/toolsets.py
- static/ui.js