fix(web): remove stale capabilities from agent wizard - #249
Merged
MiniMax-AI-Dev merged 1 commit intoAug 13, 2026
Merged
Conversation
3 tasks
MiniMax-AI-Dev
merged commit Aug 13, 2026
51cd67f
into
fix/agent-wizard-mcp-skill-only
9 checks passed
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
2 participants
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 & why
Agent profiles can retain capability names after their backing capability is removed. The edit wizard synthesized those unmatched names as Deprecated rows even when no deprecated capability existed, so stale profile text appeared as a real capability state.
How
Verification
make checkpnpm --filter @parsar/web buildNotes for reviewers
Stacked on #248 because both patches touch the same Agent wizard block. This PR contains one additional frontend commit and no API, database, or migration changes.