After upgrading to 1.
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
After upgrading to 1.1.17 today, I encountered the "no response was returned" error frequently. GPT 5.6 Sol model.
Copilot couldn't respond because MCP servers, tools, and instructions are using too much context. Run /context to review
context usage and disable anything you don't need.
No response was returned. Send your message again to retry.
| Field | Value |
|---|---|
| App version | 1.1.17 |
| OS | Windows 10.0.26200 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 2 |
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.
Research direction
Start at the /chat path and reproduce the "no response was returned" error on Windows 10 with app version 1.1.17 and the GPT 5.6 Sol model. Review /context and the configured MCP servers, tools, and instructions to determine whether context usage consistently triggers the failure. Done means the cause and reliable reproduction conditions are identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- ai, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100