-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Permissions UX is divergent between VSCode and CLI #920
Copy link
Copy link
Open
Labels
area:permissionsTool approval, security boundaries, sandbox mode, and directory restrictionsTool approval, security boundaries, sandbox mode, and directory restrictions
Description
Describe the feature or problem you'd like to solve
Permissions UX should be aligned between VSCode and CLI
Proposed solution
Permission UX should be aligned between VSCode and CLI. Currently, e.g. VSCode allows saying allow all for this session. This option should exist in CLI, it doesn't seem to be.
There are proposals s.a. #307 (which is amazing, btw) which suggest complex permisisons system, but that - again - risk it being substentially divergent between CLI and VSCode.
Either it should be clearly communicated that divergence is expected due to exploratory reasons or there should be way bigger focus on aligning the UX.
Example prompts or workflows
No response
Additional context
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area:permissionsTool approval, security boundaries, sandbox mode, and directory restrictionsTool approval, security boundaries, sandbox mode, and directory restrictions
Type
Fields
Give feedbackNo fields configured for Feature.