dsh-session-resilience

LIMITATIONS

已知限制

- Designed for a DSH web profile with the published `@deepseek-ai/cordis` and `@deepseek-ai/dsh-tools` peer packages. - Version 0.1.2 was checked against DeepSeek Harness `0.1.7-alpha.2` and Node `24.15.0`. Its settings page uses the current Plugins page and configuration form services. - Package metadata supports DSH `>=0.1.0-rc.7 <0.2.0` and the `0.1.7-alpha.1` through `0.1.7` release line. - The replacement process uses the profile's normal DSH web launch path and configured port; the plugin does not choose a GPU, model, or port. - Restart recovery requires a root browser session that reconnects within the selected handoff window. - A process that is killed before it writes the restart marker cannot provide a session handoff. - The browser must be allowed to reconnect to the local DSH launch URL. Browser policy, an external proxy, or a host-level process manager can still prevent recovery. - Provider-specific errors may need a narrow custom retryable pattern. Broad patterns can repeat requests and should be avoided.