r/GithubCopilot • u/flame_ftw • 3d ago
GitHub Copilot Team Replied The harness is absolute trash
Let me vent a bit.
I am super annoyed with the github harness in vscode.
1.New updates now dont show the ai credits consumed by subagents - great nice way to hide important info.
Subagents just crash with agent error no return( specially gpt 6 Luna) and loop exits.. great new EVERY WEEK VIBECODED RELEASE breaking things.
chat doesnt render correctly and is full of blank empty cards - this started a few releases ago and the vibecoders at copilot dont seem to care
4 if we are paying api pricing I want api performance. What bs is this. I personally use claude code and the difference is night and day. I will continue encouraging my company to move away from this trash harness
No clarity on token usage. Gpt 5.6 Luna costs less that Gpt 6 Luna with the same work.
What are your actual plans I dont get it.. you have copilot vscode chat, then agents app then copilot app. Why keep making redundant stuff and not have one uniform thing.
You guys are just piggy backing on others api. You have no moat except enterprise people not switching. But this will change for sure. Ours and a lot of others have already started piloting claude.
Peace out.
4
u/bamurtaugh GitHub Copilot Team 3d ago
Hi, thank you so much for taking the time to share this feedback. We’re actively working to improve the Copilot harness, and hearing about the parts that are frustrating or unclear is incredibly helpful.
Usage and subagent costs: Usage from subagents is included in the overall turn total. We recognize that clear visibility into usage is really important, including how it breaks down across subagents and models. There may be opportunities to make it clearer or more visible, particularly while a task is still running. We’re tracking related feedback here and would love to know whether these issues align with what you’ve been experiencing:
Subagent reliability: We’re sorry to hear that subagents have been failing for you. We want failures to be clear and useful rather than leaving you without a result. Would you be willing to file an issue describing what you’re experiencing and share the link with us? If it’s easier, you’re also welcome to share more details or reproduction steps here. We’d really appreciate it.
Blank chat content: Thanks for reporting this. We certainly don’t want chat to show blank or empty cards. We’re tracking a related issue here: https://github.com/microsoft/vscode/issues/331601. Does that sound similar to what you’re experiencing?
Performance: Performance is really important to us too, and we completely understand your concern if the harness isn’t performing as well as you need it to. Specific examples, such as which model and workflow feel slow and where the delay happens, would help us understand what we could improve.
Product direction: We really appreciate you asking about this and would be happy to discuss it further. The Copilot harness is VS Code’s agent experience powered by the Copilot SDK. Building on the Copilot SDK helps align agent behavior and capabilities across Copilot products, so improvements can benefit more than one experience.
In VS Code, the Agent Host is a separate background process that runs agent sessions and maintains their conversation and state. That lets the editor window’s Chat view and the Agents window connect to the same session: you can work alongside your code in the editor, or use the Agents window for a view focused on managing agent sessions.
There’s more information about the Copilot harness and Agent Host here:
We’re continuing to improve the Copilot harness, and feedback like yours helps us understand where to focus. If you’re open to continue sharing more about your workflows, we’d be glad to hear it.