Fix a DeepSeek Harness Session Stuck on “Running”
Official Discussion #511 reports sessions remaining permanently on “running” after a backend stops responding. Preserve logs, avoid repeated destructive clicks, restart the local service cleanly and test a new session before deciding whether persisted state is affected. This page separates verified behavior from community reports and marks the release-candidate context so you can act without mistaking an observation for a permanent guarantee.
What is verified now
Official Discussion #511 reports sessions remaining permanently on “running” after a backend stops responding. Preserve logs, avoid repeated destructive clicks, restart the local service cleanly and test a new session before deciding whether persisted state is affected.
Evidence basis: Official Discussion #511. The status was checked on 14 August 2026; re-check the linked source after any dsh release.
Safe workflow
Use the smallest reversible workflow first. Do not add community plugins or paste credentials while validating the base behavior.
- Copy the exact error and record OS, Node and dsh versions.
- Apply the narrow checks on this page in order.
- Verify with a minimal profile and escalate with sanitized logs if it persists.
Verify before moving on
A successful result should be observable: a version string, reachable local URL, valid provider response, loaded configuration, or disappearance of the exact error. If the result differs, stop and capture sanitized evidence rather than stacking unrelated fixes.
- Record the exact dsh, Node or Python version.
- State the operating system and installation method.
- Link the first-party source and include only sanitized logs.
First-party sources
Open the original source before acting on a changed version or unresolved community report.