Merge commandConfig entries into Magenta options.json files.
npx skills add https://github.com/dlants/magenta.nvim --skill update-permissions
Please help me install this Agent Skill. Skill: update-permissions Source: https://github.com/dlants/magenta.nvim/tree/main/node/skills/update-permissions Command: npx skills add https://github.com/dlants/magenta.nvim --skill update-permissions
Magenta users often need to allowlist certain Bash commands and file paths across projects and across machines. This skill provides a centralized, repeatable way to configure and merge command permissions and file access rules into Magenta's options.
Use the update-permissions skill to add or merge a new commandConfig entry into the appropriate options.json to allow a safe script execution without prompts.
High-intent search queries and answers about installing and using this skill.
To permanently allowlist bash commands and file access in Magenta, you configure commandConfig entries in the options.json file, defining ArgSpec patterns and read or write file permissions to prevent execution prompts.
Project-level Magenta options.json applies settings to a specific project directory, while user-level options.json applies permissions globally across all projects on the machine. This skill merges new rules into either scope.
You configure ArgSpec patterns and file permissions by adding entries to the commandConfig array in Magenta's options.json, specifying structured read or write access rules and path constraints for your bash commands.
Yes, when merging new commandConfig entries into Magenta options, the process validates restFiles and restAny placement and ensures built-in permissions remain intact, preventing conflicts with existing configurations.
Commands may still prompt if ArgSpec patterns or file permissions are incorrectly formatted. The configuration validates restFiles and restAny placement, so malformed path constraints can prevent rules from applying correctly.
Yes, configuring Magenta permissions supports both project-level and user-level scopes. You can define commandConfig entries in either the project or user home directory to manage access across different environments.
sandgardenhqLoad and validate JSON files in Go with contextual error handling.
ybbms777Scan Claude Code session history and generate optimized Bash command allowlists.
patrickhaahrGuide Tauri v2 application development with capability-based security and plugin architecture.
Ven0m0Configure Claude Code allow, ask, and deny rules in settings.json.
