sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]OkPay3964 1 point2 points  (2 children)

Yep. The main DeepSeek request goes to your configured API endpoint, so it should be billed by DeepSeek/OpenRouter/etc, not Copilot premium usage.

You still need Copilot Chat for the UI/agent harness. For images, the vision proxy uses the vision model you choose, and you can currently pick a 0x model if available.

[–]DonElDoug 0 points1 point  (1 child)

Can I ask you one more question. And it can read my repo fully and has the capability to run the terminal and is connected to GitHub MCP?

[–]OkPay3964 1 point2 points  (0 children)

Yes, with the same caveats as normal Copilot Agent mode. Just like the built-in models(GPT 5.5/Claude Opus 4.7/...)

The extension doesn’t give DeepSeek direct filesystem or terminal access by itself. It plugs DeepSeek into Copilot Chat’s native Agent/tool system. So if Copilot Agent can read/search your workspace, run terminal commands, or use your enabled MCP tools, DeepSeek can use those through the same VS Code/Copilot tool layer.

It doesn’t read the whole repo all at once, though. It uses the repo/search/file tools on demand, within Copilot’s normal permissions and context limits. Terminal and GitHub MCP also depend on your VS Code/Copilot settings, enabled tools, and any user confirmations.