Agents: forked session stuck when making edits+asking question
@roblourens is already working on this.
Since Jul 2, 2026.
Assessment
This issue has not been assessed yet.
Description
Does this issue occur when all extensions are disabled?: Yes/No
- VS Code Version:
- OS Version:
Steps to Reproduce:
- After a while in a session, the agent tries to edit a file, one outside the current repo, and never responds.
I'm not sure of the steps to reproduce. Contact me on Microsoft Teams (alias nathansa) and I can dump the trajectories of the repros I have, and work with you to repro.
When I view the session in the Agents app, I see nothing at the end:
Simple fix — this one test requires real internet. I'll skip it with a note explaining why.
Applying edits
next-response.test.ts+1-61
I don't think you got permission correctly to do that. Try again, a different way, or I can do it if you tell me what to dolook just tell me what to do and I'll make the edit, then you can produce the patch for the plan file
I don't think you got permission correctly to do that. Try again, a different way, or I can do it if you tell me what to do
When I view the same session in vscode, I see a reply (I truncated it here)
Simple fix — this one test requires real internet. I'll skip it with a note explaining why.Aborted: user_initiated
I don't think you got permission correctly to do that. Try again, a different way, or I can do it if you tell me what to do
Copilot CLI
look just tell me what to do and I'll make the edit, then you can produce the patch for the plan fileCopilot CLI
I don't think you got permission correctly to do that. Try again, a different way, or I can do it if you tell me what to doCopilot CLI
Here's the edit to make in the repo:File: /home/USER/vercel-next.js/test/unit/web-runtime/next-response.test.ts
Change line 48 from:
to:
But before I produce a plan patch, one question —
4 likely ingredients:
- this is on a forked session
- editing a file outside the repo
- while the agent is attempting to ask the user a question
#320206 is extremely similar to this bug.
- Dominant language
- TypeScript
- Stars
- 193k
- Forks
- 42.9k
- PR merge metrics
- PR metrics pending
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/vscode
-
testplan-item
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
new release
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
testplan-item
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
testplan-item
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
All issues in microsoft/vscode
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·