DSH community troubleshooting cases
12 original GitHub reports grouped into 11 cases, with environments, outcomes and evidence limits.
On this page
Results are attributed to original reports and replies; we have not independently reproduced them. Historical cases may not affect current versions, and closed issues do not prove a released fix. Match Desktop or CLI, runtime version, OS and the full error first.
Subagent credentials or 401
Reported environment: Older web / spawn / fork; original version and OS unspecified
Evidence status: Reporter says restart helped
The parent works after a model switch while children use the old provider. Compare parent and child routes; one reporter says a server restart restored routing. Fork patches and alternative plugins are not verified for current releases.
Web authentication fails, headless works
Reported environment: DSH 0.1.2-rc.1 · macOS · Node 24.19.0
Evidence status: Comparison reported; fix unverified
The reporter shows headless success and Web failure with the same provider and credentials. Replies discuss classification, profiles and plugins, but do not establish a successful Web fix. Record the failing entry point and redacted response before attributing it to the key.
Context overflow shown as authentication failure
Reported environment: Kimi coding API · patch base 47f9438; OS unknown
Evidence status: Author patch tests; release unconfirmed
The author reports an HTTP 401 response whose body describes a context limit, with classifier patch tests. An official release and recovery on an installed build are unconfirmed. Inspect the redacted response body as well as the status.
Empty tool name in streaming calls
Reported environment: Windows 11 · SSE · replies reference 47f943859b
Evidence status: Multiple success reports; historical patch
Several users report restoring tool calls by preventing empty SSE chunks from overwriting names. Later replies correct the original concatenation patch, which can produce repeated names or null suffixes. Applicability to current installations remains unverified.
Desktop port conflict and recovery mode
Reported environment: Desktop 2.0.5 · Windows x64
Evidence status: Single reporter success
The reporter encountered EADDRINUSE on 127.0.0.1:43152 and says setting dsh-desktop.port to 0 in settings.yaml restored startup. No maintainer confirmation is recorded. Back up configuration and distinguish Desktop settings from CLI --port arguments.
Missing dsh-settings after plugin installation
Reported environment: Desktop 2.0.4 · runtime 0.1.2-alpha.1 · Windows 11
Evidence status: Reporter confirms combined recovery
After installing dsh-theme-center, the reporter found an empty runtime package directory and recovered by removing the plugin and restoring matching package files. Neither uninstalling alone nor arbitrary replacement versions are verified. Preserve logs and profile backups.
Missing dependencies after migration
Reported environment: Desktop 2.0.5 · Windows x64 · Node 24.18.1
Evidence status: Combined recovery reported; cause unconfirmed
Startup fails to load @opentelemetry/semantic-conventions. The author reports reinstalling, resetting the profile and changing the port together, without isolated comparisons. This shares a reporter with #892. Profile resets affect user state and are not a general deletion recipe.
macOS cold-start exit and runtime directory error
Reported environment: Desktop 2.0.0 · macOS 26.5 arm64
Evidence status: Mainline fix confirmed; verify release
The runtime reports unexpected entries: dsh. The author describes temporary recovery followed by recurrence. A contributor corrects the initial shared-directory explanation; a maintainer later clarifies that v2.0.1 did not contain the fix. Mainline status alone does not identify a fixed installer.
Opening Desktop directly in a browser fails
Reported environment: desktop plugin 2.0.0 · Windows report
Evidence status: Closed; insufficient fix evidence
A normal browser reports invalid or missing dsh-desktop-mode null while the desktop window reportedly works. The issue is closed without repair comments or a successful retest. Manually adding parameters is not an established fix.
Two installations share configuration and tools crash
Reported environment: Desktop 2.0.0 + CLI 0.1.0-rc.6 · Windows
Evidence status: Maintainer reproduced and tested; no author retest
The prepare error occurs with two installations sharing DSH_HOME; the failing process in the report is CLI. A maintainer tested a fallback-link repair and required both runtimes at rc.7 or later, without specifying a Desktop installer version. This is not a fix for arbitrary single-install crashes.
New session reports preset code not found
Reported environment: Desktop 2.0.5 · Windows 10 x64; runtime unknown
Evidence status: Report only
A new session references code while the available presets are standard, ptc, minimal and cordis. There is no successful fix or fresh-profile comparison. Collect the version and preset origin; deleting sessions or rebuilding profiles is not a verified remedy.