Repository navigation
UI and workflow inconsistencies. #543
Replies: 2 comments
|
@ispyridis Thank you for your question, which made me start to ponder deeply: 1 'Enable each assistant to activate and select MCP in their own settings' is indeed an innovative idea. In the early days, we did inject MCP into the global system, but later we introduced assistants, added rules, skills, tools, and the skills market was also under our consideration. |
|
Hi @ispyridis, 感谢你先开讨论再决定要不要提 issue,很用心!同步一下进展 🎉
麻烦下载最新版 v2.1.40 体验一下~ 如果还有任何问题,欢迎直接在这里回复,或到 Discord 一起聊:https://discord.gg/2QAwJn7Egx 。再次感谢你的细致反馈!🙏 Hi @ispyridis, thanks for raising this as a discussion first! Quick update: the per-assistant MCP selection & unified CLI settings are now implemented, and both bugs you mentioned (lingering Windows bash processes, and settings disappearing after enabling WebUI) are fixed. Please grab the latest v2.1.40 and give it a try — let us know here or on Discord if anything's still off. 🙏 |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi @kuishou68 , I did not wanted to create issue without discussing it first.
The newer version have added mcp server management and assistant (agent ? subagent?) management.
I believe that an assistant should be directed to use specific mcps. So instead of activating - deactivating the mcp servers globally the activation and choice of mcp per assistant should be within the assistant settings. keep the central panel for monitoring (left column symbols) and then add a short description of the mcp and remove activation buttons from central panel. Then add an mcp selector/activator within the agents panel.
still believe cli settings should be in a unified dialog.
There is certainly a bug in windows there are many bash services after using the app for long time or if you restart it many times to update settings. it seems it does not close either mcp servers most likely or parallel subagents, or command executions that after were finished did not exit the bash environment.
The webui activation makes all settings disappear, what this means? Is it a bug or we set diferent settings for the webui? if so can we have an option to transfer settings?
I could not access the webui on my lan probably firewall settings, or network sharing i suppose
-another way to access the web ui could it be through nginx and ngrok?
All reactions