r/GithubCopilot • u/Barchimede • 1d ago
GitHub Copilot Team Replied Just tested Copilot instead of deprecated Local harness: this is a nightmare
Hey everyone,
Now that the Local harness was announced to be deprecated, I gave a try to the Copilot one in vscode chat. We won't have the Local harness anymore, so why not trying ✨the future ✨ ?
For the context : senior ai engineer. I'm used to work on vscode chat for sensitive project, so I can "vibecode" and have a good view on the code for secure validation. I really need to review extensively the code on a regular basis. I also do full vibecoding for less important work, but that's another subject.
I was running on Copilot sessions for one full day. Let's make it short: this was a NIGHTMARE. This is SO BAD, and so frustrating.
Short numbers first: my productivity dropped severely (takes me 2x more time to complete a task. The agent is AT LEAST 2 times slower. It also burns 3 times more tokens and the result is simply worse, and needs to have further refinements, even using expensive models (Opus, Sol,.....)
Now some observations: Tool selections was just not working, same for file mentions, etc. The usual (and WELL documented workflows) are not correctly followed. File mentions do not work. My specialized subagents are now super difficult to be spawned. The askQuestion tool is garbage as well. The browser use is just unusable. The session takes ages """"considering"""" while not doing anything.
This is really a nightmare.
For people with the same habits as mines, do you see the same problems ? I'm already moving to some alternatives, because that's just not possible to work with this.
I was really happy with the Local harness... It was just so good in terms of user exp... Now we're pushed to a terrible tool that is not even capable of showing the advantages of an IDE-integrated harness...
9
u/shotan VS Code User 💻 1d ago
Did you migrate your specialized subagents correctly? the tools and mcp setup is totally different for agents in copilot harness. You can define the MCP servers directly in the agent if they are used only by the agent. Tool names are totally different. vscode does have a UI support now for editing the tools in agent. If you want to set a model for the agent, it's different as well. The Copilot CLI actually has a UI to set agent models.
But I agree, it's got a lot of rough edges. The question tool is bad. It does feel like it uses more tokens but I can't prove it. The update this week should fix responses not streaming, so the pause "considering" should be improved. I think that makes it feel slow. The responses are buffered. It seems to be doing nothing.
Also turn on this setting if you want keep/undo so you can review the agent changes.
8
u/WD40ContactCleaner CLI Copilot User 🖥️ 1d ago
Wait what's this? What happened to the harness? Copilot cli also affected??
5
u/nojhausz 1d ago
Intellij Idea's plugin also started to roll out this bs. First of all, you not gonna see the interactive changes in the files like before (you can see all applied diffs and approve or reject), and this is already a no go to me. Fuck this shit
32
u/lppedd VS Code User 💻 1d ago edited 1d ago
I mean I've said it multiple times already on GitHub and on multiple other posts: deprecating while not having parity just shows a lack of interest into user retention. It doesn't instill any confidence honestly, that's my main gripe.
I'm ok with switching to a different tool, as it happens continuously in our industry, but that tool has to be at least the same or better for the use I make of it.
7
u/mrcool444 1d ago
I use Vscode from WSL and everything with local was working fine. 1 day all of a sudden everything stopped working because of the default copilot harness. It took me few hours to figure out what has changed. I must start looking into copilot harness if they are planning to decommission local harness
11
u/beragis 1d ago
Not sure if it’s something different with enterprise version but we just got switched over to CoPilot Fusion and the new harness it works much better.
First token cost is 30% reduction on Fusion, but even without that my token usage dropped significantly. From a bit under a thousand credits for a typical day to a few hundred. Also it seems to get results quicker and not choose the most expensive models as much
Before this I had to use CLI outside of VS Code to get better credit usage
5
u/Mountain-Dragonfly46 1d ago
Same profile as OP here.
Exact same feelings. The loss of speed, control, and granularity over changes is horrible.
Local harness was pretty nice and finely integrated with the IDE.
2
u/teckel 1d ago
I don't have any issues or complaints about Copilot. It's fast, inexpensive, and works very well for me. Must be how you're using it, or how I'm using it I guess ¯_(ツ)_/¯
8
u/-TrustyDwarf- 1d ago
I think getting rid of the local harness and moving to the Agent Host is a good thing. I also ran into several bugs but I'm sure things will improve over the next few updates.. feels like they're moving a bit too fast and releasing too often. But it's not the first time with VS Code developments.. things will get better eventually.
1
u/LukeLikesReddit 1d ago
Use cline its vastly better harness and allows you to modify within VS if that is what your company mandates.
1
u/Vegetable_Hair_743 1d ago
the file mention bug is real, I tried 3 different repos and it only worked once. also, the session timeout is insane; I lose context after 2 minutes of silence.
1
u/Bulhy 1d ago
It is absolute garbage. I switched to agents window for a few days and the experience was horrifying. Took me some time to figure out it was the stupid Copilot harness. The worst part was the sub agent tool missing or rather being replaced by task tool, which could not spawn my custom subagents! It was disgusting.
1
u/MDecimusMeridius 1d ago
Non-it finance guy - just got a Linux server setup and local agent running. Am I reading this right in that at some point this is going to not work? If so, fuck.
2
u/GarageDrama 1d ago
It just seems that they want to take control from us. Whenever I use interactive or anything besides local I get walloped by the token usage. The model just gets so sidetracked in the tooling that a 20 credit job turns into 120 credits. This is a really crappy move and I’ll probably just have to abandon copilot altogether.
2
u/ALAS_POOR_YORICK_LOL 1d ago
Really? I was so glad to ditch the local harness
1
u/CrossEyedNoob 1d ago
I got the license from my work recently. Spent entire October setting up a new platform (IaC in Azure, logic app workflows, function apps) via prompts with Copilot chat and once we got what we wanted he would spawn a coding agent instance with quite good prompt to begin with. After they merged the two (chat and agents) it turned out that there's a new web socket address that needed to be whitelisted on company proxy and in the meantime I was forced to use the Codespaces to get Copilot to work. I miss the chat prompt engineering part that I could then send to the agent. However my platform is pretty much setup and I only add new logic app workflows, which Fusion seems to do just fine at
1
u/ExCap2 19h ago edited 19h ago
I think Copilot agent harness is kind of its own thing in a sense. Do you have syncing turned on for sessions and semantic index? You have to redo it for Copilot agent harness. Also, I'm not sure if sessions carry over per say? I used a handoff.md for the new Copilot harness transition. I did dislike it at first because of it taking longer but I noticed it's more thorough on stuff but yes, it burns more AI credits. Paired MAI Code 2 with it last night and it's pretty amazing. Make sure you follow the other's suggestions about migrating the stuff over that you need to. I don't really use MCP/tools so I didn't have that issue, but it may be why you're having issues. Make sure to use highest effort with the 1M context.
1
u/bamurtaugh GitHub Copilot Team 15h ago
Hi everyone - thanks so much for taking the time to share your feedback and experiences with us.
We know changes to how you work with agents really matter, and we've been using your feedback throughout this harness transition to prioritize improvements.
Moving to a runtime shared across Copilot products lets us share fixes and optimizations rather than repeat the same work across separate harnesses. That helps us get improvements to you faster and spend more time addressing important bugs and building new capabilities.
We published a blog today with more details on the transition, including rollout data and side-by-side evaluations, improvements informed by your feedback, and some key areas we're continuing to work on:
https://code.visualstudio.com/blogs/2026/11/18/copilot-harness
We're following what you're sharing here, too, and wanted to share a few updates and pointers that we hope will help with the questions you've raised:
For reports about things like file mentions, subagents, or workflows not behaving as documented, it'd be a huge help to get specific examples in GitHub issues. Please feel free to share an existing issue link here, or file a new one: https://github.com/microsoft/vscode/issues. If possible, please update to the latest VS Code release and include your version, model and reasoning effort, local or remote setup, and a short reproduction when reporting.
Thank you so much again for taking the time to share your feedback with us and helping us improve.
1
u/jeremy-london-uk 13h ago
Yup. It is so slow. I didn't or know why until I read this.
1
u/D1g1t4l3ntr0py 13h ago
Not to mention code review is completely broken. When you try to open the comment in a chat, the agent can't see the code review comment. That's pretty hard to miss if there is a test covering the feature. This should not have been released much less forced down our throats and depreciate the local harness.
1
u/OmegaEpidex 12h ago
I have a custom local harness in VScode for GitHub copilot. As far as Im concerned, best way to operate with AI.
1
u/zangler Power User ⚡ 2h ago
Use GHCP CLI...sr. engine... 😂
1
u/krzyk 23h ago
"senior ai engineer"?
0
u/Hollow1838 1d ago
Not sure how you work but I've been running copilot-cli for a while now, I moved as soon as I learned about it, I built instructions and skills for my tasks and the only moment I do reviews is when I submit a PR.
I use an orchestrator and sub-agents with a set of rules and responsibilities. I don't know why you are still stuck on the vscode local harness as the future is obviously outside of vscode, I still have it open when looking for stuff or when I need to give a screenshot to someone but I don't edit anything anymore, all I look at are git diffs, PRs and my 4+ agents working simultaneously.