You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: add selectable context window (200K/1M) in model picker
Adds a "Context Window" dropdown in the Copilot Chat model
configuration panel, letting users switch between 200K and
1M token context windows per model.
- Combine reasoningEffort and contextSize into a single
configurationSchema so both controls appear in the
model picker dropdown (non-public VS Code API, same
mechanism used by Copilot for thinking effort).
- maxInputTokens raised from 656K to 1,000,000 to support
1M mode.
- maxOutputTokens set to 128,000 — a conservative middle
ground that keeps the displayed context window reasonable
(200K input + 128K output = 328K, 1M input + 128K output
= ~1.1M) without sacrificing DeepSeek's actual generation
headroom. This does NOT affect API-level max_tokens, which
is controlled by a separate VS Code setting.
- Sync dropdown choice back to workspace setting
(deepseek-copilot.contextSize) after each request so
the value persists across sessions.
- Both DeepSeek V4 Flash and Pro supported.
- English and Chinese i18n for dropdown labels and descriptions.
Why: the default 656K input window was too small for long
sessions, while always reserving 1M adds latency and cost.
Giving users control lets them pick the right trade-off between
speed/cost (200K) and capacity (1M).
"deepseek-copilot.config.baseUrl.description": "DeepSeek API base URL. Defaults to official DeepSeek API endpoint.",
19
19
"deepseek-copilot.config.maxTokens.description": "Maximum number of output tokens per request. Set to 0 to use the API default (no limit). Useful for controlling costs.",
20
+
"deepseek-copilot.config.contextSize.description": "Input context window size reported to VS Code. Larger context allows longer conversations without compaction but may increase cost.",
"deepseek-copilot.config.contextSize.1m.description": "1M tokens — longer sessions without compaction.",
20
25
"deepseek-copilot.config.experimental.stabilizeToolList.description": "**Experimental**: improve DeepSeek context-cache hit rate by pre-activating available tools.\n- When the enabled tools list changes across turns, this may improve DeepSeek context-cache hit rate.\n- Requests will include more function definitions, so input tokens may increase. Cache-hit input tokens are billed at a lower price, but still count toward usage.\n- This may add internal preflight tool calls to the current Copilot chat history. If you switch to another model in the same conversation, that model provider may reject or mishandle the replayed history. Start a new chat if model switching behaves unexpectedly.\n\nUse [Configure Tools](command:workbench.action.chat.configureTools) to **view and manage** your tool list:\n\n- 64 or fewer enabled tools: usually no need to enable this unless the tool list still changes across turns.\n- More than 128 enabled tools: not recommended. DeepSeek supports at most 128 functions in one `tools` request. Consider disabling tools you rarely use.",
21
26
"deepseek-copilot.config.debugMode.description": "Controls what diagnostic information DeepSeek Copilot writes. Token usage is always reported to Copilot regardless of this setting.\n\n- **Minimal** — Token usage only. No diagnostic logs or request dumps.\n- **Metadata** — Privacy-safe diagnostic metadata (request hashes, prefix overlap, tool schema changes). Does not contain prompt text — safe to share in public issue reports. View with [`DeepSeek: Show Logs`](command:deepseek-copilot.showLogs).\n- **Verbose** — Complete request payloads written to disk for local debugging. **Warning: contains sensitive prompt content.** View with [`DeepSeek: Open Request Dumps Folder`](command:deepseek-copilot.openRequestDumpsFolder).",
0 commit comments