ChatGPTClaudeGrok / X / CursorGemini

dsh startup flags: port, host, public URL, patches

Configuration & UsagePublished 2026-11-02Author: DeepSeek Plugin Market
dsh startupflagsdsh webportreverse proxy
The launcher parses its own flags and hands everything else to the web app. Where --port belongs, why --host rejects 0.0.0.0, and how flags beat patch layers.

dsh has two sets of startup flags: the launcher's own, written first, and the web app's, which must follow the profile selection. Miss that boundary and flags are silently ignored.

dsh flags: launcher flags and web app flags

The launcher parses its own flags and stops at the first token it does not recognize, handing the rest to the application.

FormParsed byResult
dsh --helpLauncherLauncher help
dsh --profile web --helpWeb appWeb flags, no start
dsh --profile web --port 8080Web appStarts on 8080
dsh --port 8080LauncherUnintended usage

dsh web is shorthand for dsh --profile web. The name must follow dsh directly, so when you also pass application flags, the long form is easier to get right.

With ownership clear, look at what the web app actually accepts.

Seven flags, and anything not on the list is not a web flag.

  1. --host: bind one concrete local address;
  2. --port: listen port, 3080 by default;
  3. --no-open: skip the browser handoff for this run;
  4. --public-url: announce the externally visible root;
  5. --trusted-host: repeatable, declares trusted browser authorities;
  6. --tls-cert and --tls-key: a certificate chain and an unencrypted key, always together.

To confirm what your build supports, run dsh --profile web --help. That output comes from the installed version, not from a webpage.

dsh web: changing the port

Write dsh --profile web --port 8080, with the flag after the profile.

  1. Check the target port with lsof -i :8080;
  2. Start with the flag in place;
  3. Read the bound address in the output and confirm 8080;
  4. Verify with curl -I http://127.0.0.1:8080;
  5. Put the full command into a script rather than trusting memory.

The port affects listening only, not stored data. Sessions stay in DSH_HOME and are not tied to a port.

dsh web: --host limits and running behind a proxy

--host takes one concrete local address and rejects wildcards; --host 0.0.0.0 exits with a usage error.

  1. Find local addresses with hostname -i or the platform equivalent;
  2. If several are printed, pass exactly one;
  3. Self-test with curl -I http://<that address>:<port>;
  4. Confirm the source network and firewall rules before sharing it.

Binding is not authorization. Exposing an address only lets connections arrive; authentication and Host/Origin checks still apply, so do not confuse reachability with public availability.

Serving other machines usually also means putting a reverse proxy in front.

--public-url tells the browser where the app lives; --trusted-host authorizes that name. They are not interchangeable.

  1. Set --public-url to the externally visible HTTPS root, including any proxy prefix;
  2. Set --trusted-host to the hostname that appears in the browser;
  3. If the proxy terminates TLS, do not also pass the certificate pair;
  4. Access once from the external address to confirm no origin rejection.

Certificate flags must be paired. One without the other is invalid configuration, and missing, unreadable, empty, or invalid files fail startup with no fallback to plain HTTP.

dsh flags versus patches

A flag beats a value written in a config row; between config rows, the later patch layer wins. The order is:

  1. Bundle-supplied patches;
  2. The profile's own cordis.patch.yml;
  3. The home-level patch under DSH_HOME;
  4. Each --patch passed on the command line, in argv order.

Two details cause most surprises. A patch replaces the entire config value for that row instead of deep-merging it, and a flag's precedence depends on a runtime expression in that row. Replace the row wholesale and the flag stops being read.

dsh startup logs and four common pitfalls

Normal starts are read in the terminal; failed starts have a file.

  1. When a required plugin fails to activate, the CLI prints the plugin and its stack first;
  2. It then lists plugins still waiting and the services they need;
  3. A full report lands under the DSH_HOME logs directory as startup-<timestamp>-<uuid>.log;
  4. The process exits with status 1 even if handles remain open;
  5. The report is not redacted and may include configuration or credential fragments.

DSH_HOME defaults to ~/.dsh. If you moved it, the logs moved with it.

The log handles individual cases; the four pitfalls below cover most flag misuse.

Flag problems cluster around position, wildcards, patch overrides, and pairing.

SymptomCauseFix
--port ignoredPlaced before the profile boundaryMove it after --profile web
Usage error on start--host 0.0.0.0Pass a concrete local address
Proxy rejects requestspublic-url without trusted-hostAdd --trusted-host
HTTPS fails to startOnly one certificate flagSupply both

Change one variable per retest. Altering port and host together makes a rejection impossible to attribute.

dsh next steps

Confirm flag placement before discussing binding and proxies. For layered startup triage, read the dsh startup decision tree. For LAN access options, read dsh web on a local network. For command lookup, read the dsh command cheatsheet. For custom profiles, read configuring a custom profile.

Sources: dsh CLI reference, dsh CLI README, DeepSeek Harness docs

ChatGPTClaudeGrok / X / CursorGemini

FAQ

Why does `dsh --port 8080` do nothing while `--profile web --port 8080` works?

The dsh launcher only parses flags it recognizes, so --port belongs after the profile selection. The first unrecognized token starts application arguments, which are handed to the profile. Ahead of the profile, the launcher never parses --port.

Why is binding dsh web to 0.0.0.0 rejected as a usage error?

The dsh web --host flag accepts one concrete local address and refuses wildcard addresses. To serve other machines, bind the specific interface address that clients reach, or keep loopback and terminate traffic at a reverse proxy.

I passed --port but the server still uses 3080. What overrode it?

A dsh flag is overridden when it sits before the profile boundary or when a patch writes a literal into that config row. Confirm the flag position first, then check whether that config row was replaced with a literal. Patches replace the whole config value rather than deep-merging it, which can remove the runtime expression that reads the flag.

Where is the detailed startup failure report?

When a required plugin fails to activate, the CLI prints the plugin and stack, then writes a full report to a single startup-<timestamp>-<uuid>.log under the logs directory in DSH_HOME, exiting with status 1. The report is not redacted.

Related Terms

launcher flag
A launcher flag is parsed by dsh itself, must appear near the start of the command, and selects a profile or a management mode such as plugin operations.— dsh CLI reference
application argument
An application argument is everything from the first unrecognized token onward, handed unchanged to the profile application that parses it.— dsh CLI reference
patch layer
A patch layer is an overlay applied to the config tree after bundle patches, profile patches, and home patches, with later layers taking precedence.— dsh CLI reference
public-url
public-url is the application root announced to browsers, possibly behind a proxy prefix, but it grants no trust by itself.— dsh CLI reference

Sources