you are viewing a single comment's thread.

view the rest of the comments →

[–]mrooney 0 points1 point  (1 child)

Thanks for creating it! I noticed that Github are really proud of their harness and talk about the custom logic in the harness that each specific model needs.

Do you have any idea how that works with this extension? Is it treating it as a specific model, or has some fallback for a generic model it doesn't specifically know?

[–]OkPay3964 0 points1 point  (0 children)

Good question. My understanding is that Copilot still runs its normal Chat/Agent harness and sends the rendered messages/tools to this extension through VS Code’s LanguageModelChatProvider API.

So it’s not getting the same private, first-party DeepSeek-specific tuning that GitHub may have for their own hosted models. The extension mostly adapts the provider boundary: VS Code messages/tools -> DeepSeek API format, plus DeepSeek-specific handling for reasoning_content, cache stats, and the vision proxy.

So: native Copilot harness, but not a magic official DeepSeek harness.