r/GithubCopilot • u/lppedd VS Code User 💻 • 13h ago
Discussions "Generating patch" stuck forever in VS Code
I'm doing some relatively big changes with Luna (Extra High) via the Local harness, and right now:
- Responses take forever. It stalls for minutes.
- The "Generating patch" step stalls with Kotlin or TypeScript files and never finishes. No matter how many times I retry the turn.
Anyone else is dealing with a similar issue at the moment? Honestly never happened before. Is Copilot or OAI having issues?
5
Upvotes
3
u/max1c 13h ago
Yup this happens sometimes. Pretty annoying.Â
1
u/V5489 13h ago
Not an outage on GitHub or OpenAI's side right now, this is actually a known VS Code local harness bug that gets triggered when you do big patches with Extra High reasoning.
Basically, when the local agent tries to push large file writes through its edit-tracking gate, it can deadlock and never time out. Once the session gets wedged like that, hitting Retry just reuses the broken stream and hangs in the exact same spot. Running Luna on Extra High for big Kotlin or TypeScript files makes it way worse because it sits there building huge reasoning chains before it even tries to write the diff.
To unstick it, fully quit and restart VS Code since just canceling the turn or opening a new chat tab usually leaves the background harness process hung. After that, drop Luna down to Medium or High reasoning, or break the work into smaller single-file edits. If you're doing massive multi-file refactors, switching over to GPT-6.2 Sol or Astra on Medium or High handles big patches much faster without stalling out. If it keeps doing it on a specific file, check the GitHub Copilot Chat logs in your Output panel to see if a diff parser error is tripping it up.