Auto-accept tool-calls

[valdebrutal]

Hey, is it possible at all to autoaccept tool calls? I find myself having to accept tons of these on a given prompt. Is this on the roadmap perhaps? Thanks in advance.

[deathbeam]

Currently it is not possible and not planned either. Tool calling is inherently insecure (especially when using MCP servers) so the process being very explicit is intentional. But it can be added regardless if there is enough demand for it I guess (so far there wasnt much demand really)

[valdebrutal]

Yeah, on a second thought accepting everything like I stated is probably downright reckless. Maybe conditionally auto-accepting certain functions such as reading files under the root dir could be reasonable. Food for thought! Thanks for the answer.

[josealvaradoo]

I've been reading some issues and discussion about the auto-approval. I know your thoughts about the risk, but I feel the plugin is falling behind the modern alternatives. Maybe we should treat it as non auto-approval by default but keep it optional for advanced users.
cc @deathbeam

[FlashOnFire]

Most other Copilot implementations don't ask for consent for non destructive ops (read, search, and even direct file edits since git history is already there as a safety net).
The only hazards lies in the terminal tool and MCPs, so it makes sense to keep the explicit approval for those, and relax it for the rest.
I think the best way to handle this is to add a config option to enable / disable auto approval on a per tool basis.

[josealvaradoo]

I'm absolutely agree with you @FlashOnFire
I've been playing in a fork with this for a week, and it feels really satisfactory the workflow speed. In addition what you commented, I was thinking to add the typical option like | "Approve always for this session" | "Approve" | "Reject" |, because sometimes we want be aware about what command is running, but we might approve always a ls for example.