1. What this message really means
When using GitHub Copilot in VS Code or in the new Copilot Agent mode, you may see:
“Copilot has been working on this problem for a while.”
This simply indicates that Copilot is trying to process your request — but in practice it often means it is stuck, overloaded, or has hit an internal error.
References:
https://github.com/microsoft/vscode-copilot-release/issues/7150
https://en.wikipedia.org/wiki/GitHub_Copilot
https://arxiv.org/abs/2303.17125
https://arxiv.org/abs/2406.17910
https://www.reddit.com/r/GithubCopilot/comments/1khpm8m/continue_to_iterate_prompt_in_vscode/
2. Why it happens
Based on many reports and technical documentation, the major causes are:
● Heavy or overly broad tasks
Asking Copilot to modify an entire project or solve a multi-file logic problem will overload it.
● Unstable Agent Mode behavior
The Agent mode tries to take multi-step actions (edit files, plan tasks, create PRs), and often gets stuck.
● Network lag between VS Code and GitHub API
Copilot relies on near-realtime communication with GitHub’s backend.
● Internal Copilot errors
Many users have confirmed reproducible cases where Copilot simply hangs.
3. Common real-world patterns
Typical user experiences include:
- The message stays on screen for a long time
- No response ever returns
- Eventually another error pops up
- Restarting VS Code instantly fixes it
- Copilot was “thinking” in the wrong direction anyway
In reality, the message often means “not progressing” rather than “thinking deeply.”
4. Effective solutions
The most effective fixes found during research:
● Restart VS Code
The most reliable solution in almost all cases.
● Reduce task size
“Refactor the entire file” → ❌
“Rename this single function” → ⭕
● Reduce open context
Less open files = better stability.
● Check your network
Copilot is sensitive to inconsistent API connectivity.
● Disable Agent Mode
Agent Mode significantly increases the chance of getting stuck.
5. Fundamental limitations of Copilot
Research highlights clear boundaries of Copilot’s ability:
● Excellent at routine patterns
Loops, boilerplate, test scaffolding → very strong.
● Weak with architecture-level context
Business logic, multi-file dependencies, complex state → often wrong.
● Hallucination is unavoidable
Copilot frequently produces “plausible but incorrect” code.
(Discussed in the following paper)
https://arxiv.org/abs/2406.17910
● Human review is mandatory
Security, correctness, and licensing all require oversight.
6. Conclusion
- The message “Copilot has been working on this problem for a while” often indicates an overloaded or stuck state, not meaningful progress.
- Particularly common in Agent Mode.
- The most reliable fix is restart + task decomposition.