Configuring dsh-deepseek-web-login
DeepSeek Harness exposes a settings panel for the provider. It can show login status and the current account, capture a login from Microsoft Edge or another logged-in browser window, accept a manually pasted token, test connectivity, manage multiple accounts, and clear the current browser profile when signing out. The panel also controls request throttling, session cleanup, transport testing, context mode and the built-in browser. The README does not specify a separate configuration file or stable defaults for these controls.
How dsh-deepseek-web-login behaves
At login time, Electron registers webRequest.onBeforeSendHeaders and reads request headers from the login window. The callback removes Electron branding from the user agent and UA-CH headers, then the window can close. Subsequent calls are made by the plugin to DeepSeek's private web endpoints rather than through a reverse proxy or DOM automation.
DeepSeek Harness sends requests through a real Edge or Chrome network context by default. The plugin obtains a challenge from create_pow_challenge, solves it with DeepSeek's sha3_wasm_bg.*.wasm, and sends the result in x-ds-pow-response. It parses SSE response/fragments and direct thinking/content streams, and uploads images through /api/v0/file/upload_file.
Commands and endpoints
The provider is selected in the model picker as DeepSeek 网页 · 快速模式. The settings panel exposes host HTTP API routes under /deepseek-web-login/api/*. The environment variable DSH_NO_BROWSER_TRANSPORT=1 disables browser transport, but the README states that 0.7.0 and later require Edge or Chrome for PoW and will not silently use Node-side solving.
Known limits
Tool calls are prompting-based rather than native function calls. The plugin depends on private web endpoints, captured login credentials and browser behaviour that may change. The README warns that these adjustments reduce, but do not remove, the possibility of rate limiting or account penalties, and describes the approach as unofficial and potentially contrary to the service terms.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub