-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Harden Plan Mode policy for activate_skill #24942
Copy link
Copy link
Labels
area/coreIssues related to User Interface, OS Support, Core FunctionalityIssues related to User Interface, OS Support, Core Functionalityworkstream-rollupLabel used to tag epics and features that are associated with one of the three primary workstreamsLabel used to tag epics and features that are associated with one of the three primary workstreams🔒 maintainer only⛔ Do not contribute. Internal roadmap item.⛔ Do not contribute. Internal roadmap item.
Metadata
Metadata
Assignees
Labels
area/coreIssues related to User Interface, OS Support, Core FunctionalityIssues related to User Interface, OS Support, Core Functionalityworkstream-rollupLabel used to tag epics and features that are associated with one of the three primary workstreamsLabel used to tag epics and features that are associated with one of the three primary workstreams🔒 maintainer only⛔ Do not contribute. Internal roadmap item.⛔ Do not contribute. Internal roadmap item.
Type
Fields
Give feedbackNo fields configured for Task.
Projects
Status
Closed
What would you like to be added?
Move 'activate_skill' from automatically allowed to requiring user confirmation ('ask_user') in Plan Mode.
Why is this needed?
Plan Mode should be restrictive. Automatically allowing skill activation might lead to unintended side effects if the skill's tools aren't all read-only, or simply for better user awareness. This aligns 'activate_skill' with other sensitive tools (ask_user, save_memory, web_fetch) in Plan Mode.
Additional context
Modified
packages/core/src/policy/policies/plan.tomlto moveactivate_skillfrom an 'allow' rule to the 'ask_user' group.