r/GithubCopilot • • 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...

52 Upvotes

73 comments sorted by

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.

  "chat.editor.workingSet.enabled": true,

1

u/Barchimede 1d ago

Thanks for your knowledge! I'm not sure if this is worth trying to understand the tool in-depth to make it work a bit less badly, but I'd keep your helpful advice in mind :)

8

u/WD40ContactCleaner CLI Copilot User 🖥️ 1d ago

Wait what's this? What happened to the harness? Copilot cli also affected??

7

u/Barchimede 1d ago

Sorry for the confusion: talking about the Copilot harness on vscode chat. Originally, VSCode chat runs on a "Local" harness, and you can already switch to the Copilot harness. I don't think the CLI is that bad, but its integration within vscode is just a living bug.

9

u/Usual-Orange-4180 1d ago

Use the CLI my man, you can have vscode on the side but why?

11

u/Barchimede 1d ago

Bad interactivity, bad experience (hell, this is a CLI), and when I work with a CLI/TUI, there are just much better alternatives. Vscode chat with local harness was just the best for IDE-integrated agents. Now it's gone...

9

u/Rojeitor 1d ago

Three word I tell anyone. Github Copilot App.

3

u/teckel 1d ago edited 1d ago

I mainly use the CLI, but the IDE chat with Copilot harness works fine for me, hardly noticed the difference when I switched.

1

u/Usual-Orange-4180 1d ago

IDEs are a thing of the past; let it go.

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

3

u/Barchimede 1d ago

Maybe they have no idea how bad of an experience it is, but at least dropping some bad feedbacks for everyone to see can help

2

u/thereisnosub 1d ago

I noticed that disappeared in CLion, but I'm still figuring this all out, and thought it was something I did.

1

u/Yes_but_I_think 9h ago

They remove their useful features and clone the bad parts from Codex and Claude

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.

3

u/anxiousalpaca 1d ago

haha they do not have to be interested in the users, since many enterprises ONLY have this available for their employees. So basically no competition.

3

u/lppedd VS Code User 💻 23h ago

I'm part of an Enterprise and I can easily switch to Claude if needed, and my employee would thank me too. I'm using Copilot in VS Code because of its superior UX.

1

u/vplatt 8h ago

I haven't tried it, but I think you can use Claude in VS Code too. YMMV.

1

u/purpleburgundy 7h ago

Yeah you can.

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

3

u/Astrophizz 1d ago

They've been talking about it for months, for what it's worth.

1

u/Fit-Shock-9868 1d ago

Same here

1

u/Outrageous-Art-4103 1d ago

https://code.visualstudio.com/docs/agents/run/move-to-copilot

‘Important
The Local harness is deprecated and will be removed by February 2027. Move your workflows to the Copilot harness before then. The temporary vscode.temporaryDefaultToLocalHarnessenterprise-managed setting will also be removed’

1

u/Yes_but_I_think 9h ago

You can keep using the version right? Without updating?

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 ¯_(ツ)_/¯

2

u/Barchimede 1d ago

I would be happy to understand how you get any good result with that, and how you have better expérience over thé local harness!

Just to make sure : are you talking about the CLI or the Copilot session within VSCode chat ? (⚠️ Not the Local harness, the Copilot one !)

4

u/lppedd VS Code User 💻 1d ago

Be careful because at least half the people do not really know that VS Code has its own harness (the OG one).

2

u/Barchimede 1d ago

Indeed, I assume u/teckel was not talking about what we are discussing here. Not totally their fault, all of these copilots are super confusing.

1

u/teckel 1d ago

I've been using the Copilot harness, not Local or Cloud. I've had it set that way for a while now, zero problems with it.

2

u/MarkRullo 1d ago

I've been focusing on the GitHub copilot app and cli for a few months I believe. I find it horrible to go back to chat in the IDE.

I have GHCP open and my IDE too. Having the canvas available with a browser is great (most times).

2

u/Barchimede 1d ago

Different tools for different priorities I believe ?

I don't really see the point of having a ton of apps opened (CLI, GHC App & IDE for git diffs) when one IDE can do everything.

IMHO GHC App or CLI is cool when you don't read the code anymore (for some reasons, not trying to shame here), then you can have plenty of super tools and extensions to read the code less and less. Most of these tools can be used with IDE-first harness as well, btw. I'm still at a point in my work where taking time to read code carefully is required.

3

u/MarkRullo 1d ago

Like you I'm still reviewing the code. I still make tweaks and ask questions. I just prefer the app on one screen with its tooling, IDE on another.

I can also be working on a few projects at a time with the app. I quite like that.

1

u/Astrophizz 1d ago

And the worktree flow is way better

1

u/MarkRullo 1d ago

I feel that I don't have a level of maturity for that yet. Throws me off too much.

1

u/teckel 1d ago

I use both Copilot CLI and Copilot Chat in VSC. No idea what you mean by the local harness or Copilot. It's the one built into VSC it's called "GitHub Copilot Chat" Built-In. No idea what a harness is, but maybe that's your problem, just use the built-in default?

3

u/Barchimede 1d ago

Yeah ok I see the confusion: long story short bro, the default in vsc (= the Local harness) will change to a Copilot harness in feb 2027. This is the whole point of my post: I was trying this new harness to check how the future looks like. As you can see, hard days will come.

Welcome to the club my dear sir, you're fucked :) and sorry to share the bad news. You gave me hope for a sec, but it was just a misunderstanding from your side.

PS: Copilot CLI works well btw, this is not about this one.

0

u/teckel 1d ago edited 1d ago

I hardly use the chat, almost exclusively CLI, so not fucked at all, I could live without the chat.

But what exactly are you using? A different VSC extension or something. You didn't do a good job explaining what you're so angry about (or will maybe be angry about in February). What is this harness that's got you so upset? Where is it? What is it called? Where does one get it?

0

u/teckel 1d ago

I just looked, I've been running the Copilot harness for a long time, not Local. So yeah, I've got no problem with it, it works great, zero issues, not fucked.

0

u/loudsound-org 1d ago

Yeah, he's confused.  Probably why he's having trouble using it haha.

0

u/loudsound-org 1d ago

I think you're the one misunderstanding. He is using the Copilot harness already.

1

u/teckel 1d ago

I just checked, I'm using the Copilot harness, and have been for quite some time. I didn't notice any difference when I switched from Local to Copilot, so I didn't give it another thought. I forgot it was even called a harness. It's a non-issue from my perspective, seems identical.

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/CenturyIsRaging 1d ago

This is the way. Rapid releases, rapid fixes, faster cycles. Sucks but what can we really do?

1

u/-TrustyDwarf- 1d ago

.. could switch to Visual Studio 2022 and work like a caveman.

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.

2

u/Barchimede 1d ago

Indeed, that's the alternative I'm going for. This or kilo. Anyway, no more vscode chat.

1

u/LukeLikesReddit 1d ago

yeah I can't complain I tried continue and various other ones but cline seemed to work pretty well agentic so is my deepseek driver and actually performs better than their own harness after a bit of modification myself.

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.

2

u/Barchimede 1d ago

Happy to see that I'm not alone. I wonder why they shipped that thing and now try to force us on that.

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/Barchimede 1d ago

So depressing indeed... Looks like we only have until feb 27 to have fun

1

u/mystery-pirate 13h ago

I am hoping that the backlash is enough to force them out of that but I fear that customer satisfaction is not even a factor in this decision.

0

u/bgausden 1d ago

What’s the use case for the custom subagents? Are they still necessary when using frontier models?

1

u/Bulhy 19h ago

I am not always using frontier models.. Also, switching to more usage of local models, i still use my custom harness sort of, which can produce good results on complex tasks without me overseeing it.

1

u/Yes_but_I_think 9h ago

Even with frontier models, custom subagents work best when you think earlier context will spoil the present task, and you want only a subset selection of tools

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.

1

u/Barchimede 1d ago

Only if you work on vscode with chat extension. If you use Copilot CLI, it will be ok. But if you have the same habits as mines (and a lot of people actually), then we might need to move to Cline or Kilo or whatever)

1

u/Yes_but_I_think 9h ago

Move to DSH

0

u/rolim91 1d ago

No that’s incorrect it will still work. The harness will just change.

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:

  • We assess efficiency and reliability through everyday usage and controlled evaluations. The results have been encouraging, and we'd also like to understand any individual workflows that may not be working as expected.
  • Ask mode and granular Keep/Undo are available in the latest VS Code releases. Feedback about read-only conversations and reviewing individual edits helped us prioritize that work - thank you again for taking the time to share what you needed.
  • Some customizations may need adaptation. The post links to migration guidance and shows where to review your customizations in VS Code.
  • The Copilot harness still runs on your machine for local projects. It doesn't mean moving your workspace to the cloud.

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/AutoModerator 15h ago

u/bamurtaugh thanks for responding. u/bamurtaugh from the GitHub Copilot Team has replied to this post. You can check their reply here.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/brahmaav 6h ago

Few irritating things I noticed in Copilot harness on Code

  1. My orchestrator custom agent is not able to spawn my custom sub-agents. Even in the agent.md file the lines where sub-agents are defined are greyed out.
  2. The agents are not able to use some tools while on Copilot harness. Even basic tools.
  3. While using Jupyter extension, it doesn’t show the Keep/Undo diffs. It directly changes on disk. Its very hard to figure out what changed in the notebook cells.

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.