fix(agent-core-v2): honor configured permission rules - #2337
Open
gunnlace wants to merge 1 commit into
Open
Conversation
🦋 Changeset detectedLatest commit: ee0cc67 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
Related Issue
Fixes #2100
Problem
See linked issue.
What changed
Load configured permission rules into the effective Agent permission rule view alongside live runtime rules.
This keeps configured rules outside the persisted Agent wire state, so resumed agents continue to read the current configuration without duplicating or retaining stale rules.
Added regression coverage for merging configured and runtime rules, and for approving a configured MCP tool before the manual-mode fallback.
Manually verified in
kimi webthat an MCP call prompts without an allow rule and executes without prompting after adding the matching rule.Checklist