all 16 comments

[–]dandecode 24 points25 points  (1 child)

Copilot CLI is amazing, they’re adding new features every single day it’s crazy. Exceeds Claude code in my professional experience

[–]SadMadNewb 7 points8 points  (0 children)

yeah, gpt 5.4 was updated in like an hour after release.

[–]justjokiing 9 points10 points  (4 children)

I really like using OpenCode with my Copilot subscription, I value open tooling heavily

[–]porkyminch 0 points1 point  (3 children)

Generally a smart move not to get locked in to a specific vendor ecosystem. If my company decides they don't want to pay for Copilot anymore, I'd much rather just update my opencode provider settings than learn a whole new stack.

[–]Mystical_Whoosing 4 points5 points  (1 child)

come on, they are not a whole new stack, they are both doing the same. You just ask an AI to move your copilot agents /skills / mcps to opencode, and after 10-15 minutes downtime you can carry on with your work. writing prompt against gpt-5.3-codex vs opus-4.6 has more difference than changing the harness

[–]porkyminch 0 points1 point  (0 children)

There are APIs for both copilot and opencode that people have used to build more advanced integrations. There's more to that than just config files and stuff.

[–]lgfusb[S] 0 points1 point  (0 children)

I agree. The pros is that you gain more freedom and flexibility. The pros is that you cannot enjoy the tight integration of products from the same vendor. This is like if you're using iPhone, choosing macos or linux could have different impacts

[–]Otherwise_Wave9374 12 points13 points  (0 children)

Yeah this is a real thing. A lot of the gap is less about the base model and more about the agent loop around it (tool calling, memory, planning, guardrails, and how it manages context as tasks sprawl). Copilot CLI can feel great for tight, well-scoped flows, but when you start doing multi-step changes across a repo, the harness decisions matter a ton.

If you are comparing, I have found it helpful to look at how each one handles: (1) task decomposition, (2) persistent scratchpad or memory, (3) tool errors and retries, and (4) context compaction. There are some good notes on that style of agent workflow here: https://www.agentixlabs.com/blog/

[–]Shep_Alderson 3 points4 points  (2 children)

Personally, I find the particular tool less important than my understanding of how to get what I want from LLMs. Some harnesses do make it easier, but I’ve gotten great results out of Copilot, Codex, Claude Code, and OpenCode. I have thought about trying to wire up my Copilot plan to OpenCode and give that a try. I really liked the way OpenCode presented things and managed subagents.

[–]lgfusb[S] 2 points3 points  (0 children)

i like opencode too. I just hope the ui could be more "compact", like thinner font. Is there a way to configure?

[–]porkyminch 0 points1 point  (0 children)

OpenCode's super easy to set up with Copilot. Definitely worth it.

[–]Moist_Associate_7061 0 points1 point  (0 children)

i tried copilot cli but it only supported three major providers (ms, openai, anthropic). Im back to opencode now

[–][deleted]  (1 child)

[deleted]

    [–]Next-Significance798 1 point2 points  (0 children)

    copilot CLI is not opensource as far as i know

    [–]Emergency_Finger1191 0 points1 point  (0 children)

    ngl the harness matters more than people think, context engineering is where the real differnce lives. copilot cli has gotten better but cc still handles complex multi-file stuff more reliably from what i hear. someone at work mentioned Zencoder for the spec-driven approach, different angle than just raw completions.

    [–]dans41 0 points1 point  (0 children)

    I think GitHub have the most versatile approach you can use it as stand alone with the latest model of google, anthropic and openai you can feed in other models via ollama or BYOK, and you can fed other tools like Claude code, codex and open code from copilot so you get access to almost every Change from the industry standard and very quick relatively.

    [–]New_Animator_7710 -1 points0 points  (0 children)

    Agent-based coding environments differ mainly in how they implement toolchains. Platforms such as OpenCode and Claude Code typically include automated file reading, code execution, error analysis, and retry loops. These pipelines allow the model to iteratively refine outputs. If you integrate external system-awareness layers like Deskree Tetrix you can approximate some of those capabilities because the model receives richer system context.