Repository navigation
[FEATURE]: edit/write permission with deny,allow,ask using glob #4287
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Maybe allow certain agents to edit specific files would be helpful for documentation agents.
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Nov 13, 2025
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
AceCodePt commentedon Nov 13, 2025
The first one is the closest. Though in my case I wasn't able to limit the agents permissions to just *.md
iamhenry commentedon Nov 13, 2025
The ability for my planning agent just to edit markdown files would be useful
rekram1-node commentedon Nov 13, 2025
Yeah we definitely wanna do this
redtux commentedon Nov 22, 2025
Does it depend on the used LLM provider or model if this is being respected? Sometimes I'm being told "I'm in read-only mode and can't edit", but sometimes the agent just starts working. Often it even starts to implement the plan without asking me for approval, while other times it tells me that the task tool can't be used in plan mode, and so on.
rekram1-node commentedon Nov 22, 2025
@redtux if you are using plan agent it will say its in read only mode, you can hit tab to change agents. But also the plan agent isn't that great we are improving it soon
redtux commentedon Nov 23, 2025
Well, it seems to depend 😃 I tried again in a fresh session (and using the most recent version) after asking my question here, and it did commit, move files, and other operations (without being instructed to do so). Only after explicitly being asked to edit a file the agent told me that it's in read-only mode. So lessons learned: 1. it doesn't depend on the model (I didn't switch the model), 2. it is being reminded that it's in plan mode when trying to call a tool, 3. I better not trust that plan mode is strictly read-only. It also tried commands that are in the deny list in my settings. Here at least the CLI tells the agent that it's not allowed to run this command, but I would expect the agent not even trying to run that command in plan mode (mv, rm, git reset, git checkout, edit files using bash/sed/pipe, etc.) But thanks for the explanation, now at least I seem to understand how it's expected to work. 👍
AceCodePt commentedon Jan 2, 2026
thdxr commentedon Mar 25, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.
AceCodePt commentedon Mar 25, 2026
Open a new issue of add a new message. Because it is still kinda relevant.
redtux commentedon May 23, 2026
Hi @rekram1-node, can you at least explain why this is not planned? Thanks!