Run DeepSeek Harness in Headless Mode
The shipped headless profile runs one persisted session, prints the final assistant text and exits. The task is positional, no HTTP or Web runtime is mounted, and the process returns nonzero when the final turn does not complete successfully. 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.
Start with this command
This is the narrow command relevant to this page. Read the checks below before changing flags, credentials or profile patches.
dsh --profile headless "Inspect the repository and report its test command."What is verified now
The shipped headless profile runs one persisted session, prints the final assistant text and exits. The task is positional, no HTTP or Web runtime is mounted, and the process returns nonzero when the final turn does not complete successfully.
Evidence basis: Official CLI reference. 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.
- Put launcher flags before profile app arguments.
- Use --help or a dump command before changing patch layers.
- Check exit status and stderr rather than reading stdout alone.
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.