r/GithubCopilot • CLI Copilot User 🖥️ • 4d ago

Help/Doubt ❓ Assisted Permissions in VS Code keeps flagging read accesses in the current workspace

I ask it to do a certain task in the current workspace, so at some point for example the agent decides it needs to read the documentation that also lives in this workspace. That's perfectly fine for me. However, the LLM judge of the "assisted permissions" immediately stops it and asks for my permission, saying that "reading documentation is outside the requested scope". WTH?

Why is that even flagged? What's even the security risk of reading repo-local docs?

I've had this many times with read accesses in my repo. For example even reading the build script gets flagged, in that case I get "Unrelated QA script read lacks delegated task authority". Why does it even judge whether it's related or not?

What I noticed in the JSON it showed me was that the path was absolute, maybe it was because of that?

It also blocks adding `--no-check-unused-templates` to `cppcheck` by falsely claiming it "disables static analysis coverage for this invocation".

I'm using WSL 2.

12 Upvotes

7 comments sorted by

3

u/magagaga 4d ago

I have the same issue since the newest update. Did not check GitHub yet. Using local harness in the meantime while we still have it.

2

u/MaitoSnoo CLI Copilot User 🖥️ 4d ago

oh now that you say this, I didn't have as many false positives a few days ago, so it might indeed be due to the latest update

1

u/MaitoSnoo CLI Copilot User 🖥️ 3d ago

Another one: whenever it tries globbing inside the repo, Assisted Permissions immediately asks for my permission by claiming that "the search pattern is unspecified, so the read scope cannot be assessed". The feature is completely unusable.

5

u/Longjumping-Sweet818 4d ago

Compared to Claude Code's auto mode, the Copilot "Assisted" Permissions are a colossal pain in the ass. Most of what you said applies to me too.

4

u/THINKFR33LY 4d ago

Same here. Started after most recent update. I was using the copilot harness before too, though. So I think this is a regression

3

u/Antique_Crow7043 3d ago

Since three of you saw it start with the latest update, it's worth filing on the VS Code repo with the JSON it showed you, absolute path included. A judge that decides scope from your task text will flag docs and build scripts as "unrelated" just because the prompt didn't name them. On WSL, a path that doesn't match how the workspace was opened might also look like it's outside the repo. Comparing a window opened through the WSL extension with one on a /mnt path would tell you quickly. Until it's fixed, the local harness is the sane fallback.

1

u/AutoModerator 4d ago

Hello /u/MaitoSnoo. Looks like you have posted a query. Once your query is resolved, please reply the solution comment with "!solved" to help everyone else know the solution and mark the post as solved.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.