feat(ui): surface @mux tool optimization on FeatureSets + approval opt-out link - #168
Closed
its-mash wants to merge 2 commits into
Closed
feat(ui): surface @mux tool optimization on FeatureSets + approval opt-out link#168its-mash wants to merge 2 commits into
its-mash wants to merge 2 commits into
Conversation
Two small discoverability nudges around tool optimization: - FeatureSets tab: add a branded "Let your AI build these for you" hint showing the `@mux optimize` chat affordance — the assistant can discover tools, compose a FeatureSet, and pin it to the current folder, each gated behind a one-click approval. - Meta-tool approval dialog: add a "Prefer not to be asked? Manage approval prompts" link that denies the current request (fail-closed, so the client is not left hanging for the 60s broker timeout) and routes to the Built-in tab, where the "Require approval for tool changes" switch can turn these prompts off. Covered by a new MetaToolApprovalDialog test asserting the link denies and navigates to builtin-servers. Signed-off-by: Mohammod Al Amin Ashik <maa.ashik00@gmail.com>
Member
Author
|
Consolidated into #171 per request (single branch, trimmed descriptions). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Two small discoverability nudges around tool optimization — making it obvious that the AI can curate its own toolset, and giving users a one-tap escape hatch from the approval prompt.
1. FeatureSets tab — "Let your AI build these for you" hint
A branded violet callout above the list shows the
@mux optimizechat affordance: in any connected client the assistant can discover the available tools, compose a FeatureSet, and pin it to the current folder — every change gated behind a one-click approval, so the user stays in control.2. Approval dialog — "Manage approval prompts" opt-out link
The meta-tool approval dialog now has a subtle footer link: "Prefer not to be asked? Manage approval prompts →". Clicking it:
mcpmux_bind_current_workspace).Why
The
@muxself-optimization flow is McpMux's standout feature but was previously undiscoverable from the FeatureSets surface, and there was no in-context path from the approval prompt to the toggle that disables it.Tests
MetaToolApprovalDialogtest: clicking the manage link denies the request (decision: 'deny') and callsnavigateTo('builtin-servers').tsc --noEmitclean, ESLint clean (only pre-existing warnings), clippy/fmt clean via pre-commit.Scope
UI-only; no Rust, schema, or gateway behavior changes. Existing approval testids (
-deny,-allow-once,-always) are untouched.