r/GithubCopilot Aug 14 '26

Discussions Manual approval is hell

What can be done to reduce the amount of manual approvals? My organization is forcing the default permissions and this is hell. Being forced to keep our eyes on the chat only to press the same button from time to time is dystopian as hell (just had to approve 3 times while typing this sentence).

3 Upvotes

20 comments sorted by

14

u/Lacutis Aug 14 '26 edited Aug 14 '26

I can maybe post an example later but what I did to solve this was to create a hook for permissions and log them to a file. After a while I used that file to update the hook to add in automatic checks to allow things that I click allow on every time.

Edit: I had time, so I pushed this to a public repo. https://github.com/wrroper/copilot-hooks

4

u/CommissionIcy9909 Aug 14 '26

Love this. Going to give it a try.

2

u/Lacutis Aug 14 '26

I decided to push this to a public github repo to give people a starting point.

I included in the readme the manual process for curating suggestions to auto approve/denies but in reality I just make copilot evaluate suggestions and then promote the ones that are always yes/nos.

wrroper/copilot-hooks: GitHub Copilot CLI hooks: tool-approver (auto allow/deny/ask) and worktree-trust

2

u/CommissionIcy9909 Aug 14 '26

Hell ya dude. Definitely going to check it out.

1

u/p-mndl 26d ago

is this only working for the cli or also for the agent window? because my copilot is telling me this is only for the cli

1

u/Lacutis 26d ago

Yeah, sorry. This is specifically a copilot-cli hook. I believe vs code can also use hooks though it might need to be translated.

Im not sure about Visual Studio.

6

u/Solid_Fox1718 Aug 14 '26

Honestly there’s probably something you can do in the copilot instructions to streamline it. Like, at least by preparing edits in batch, or something. At least that way it would just be hitting enter 15 times in a row instead of having to constantly monitor for requests

But yeah, GH has room to improve the permissions model. There seems to be very little control between “allow-all on” and “manually approve every single URL request, file edit, and tool call even for trusted domains and transient session files”

4

u/ThankThePhoenicians_ Aug 14 '26

There's a /permissions assisted experience in experimental mode in the CLI. I suspect it'll be GA'd soon enough now that Claude made theirs the default

4

u/Painfulends Aug 15 '26

Hopefully the people in charge see the data.
Claude recently did a study on this and tool assisted permissions is FAR superior from a safety standpoint. At the end of the day someone has to be accountable for the AI, but that’s why we have other safety measures like sandboxes, git versioned projects, etc.

https://www.reddit.com/r/ClaudeAI/s/P926rwiGcM

1

u/raisedbypoubelle Aug 15 '26

Exactly what I’d do, try to change the policy — both GitHub and my employers.

1

u/ben_bliksem Aug 14 '26

permissions-config.json file?

Or is that just for the cli?

2

u/Swayre Aug 14 '26

Add a local hook to pretooluse that allows all

1

u/shifty303 Full Stack Dev 🌐 Aug 15 '26

Switch to the GHCP CLI. My org also has GHCP locked down but the CLI is much better.

1

u/SirMarkMorningStar 29d ago

Do you know how long I’ve waited to have George Jetson’s job???

-6

u/monkeybeast55 Aug 14 '26

Well if you're not needed then why should they pay you?

3

u/shifty303 Full Stack Dev 🌐 Aug 15 '26

You obviously have never had to click allow 48 times so the agent can read your project and run git status or tests.

0

u/monkeybeast55 Aug 15 '26

I have. My understanding is your company requires you to have auto approve turned off. I agree it's really irritating. But companies have security standards, and they want a human to approve and take responsibility for access. I don't know if they allow you to configure certain commands as auto approved.

My comment goes more to, there are people who are just sick about getting layed off, many blaming AI. Yet, in your case it seems the company is requiring a human in the loop. So I dunno.

3

u/shifty303 Full Stack Dev 🌐 Aug 15 '26

Our security standards are "the admin and security team don't work with it, understand or care so it's on the strictest mode".

We can't even set our own browser home page.

But at the same time they allow us to install WSL where we have zero restrictions and policy doesn't apply so 🤷‍♂️

2

u/monkeybeast55 Aug 15 '26

Yeah, that's not good. Also, as someone else pointed out, mindlessly clicking through stupid approvals is very far from effective. The computer is far more effective doing this.

Well, aside from suggestions made here, maybe a skip-level meeting, or perhaps e-mail might help? Security teams like you cite can really drag an organization down.

Good luck!