Configuring dsh-our-free-model
DeepSeek Harness loads the plugin in the selected profile, with llm as a hard dependency. The settings page exposes these documented options:
- A master enable switch
- Whether to show
region-limited models
- The availability-probe interval
- The default per-call output limit
- The local forwarding switch, address and port
- The forwarding API key, including display, copy and rotation actions
- File watching and hot reload
The forwarding service is disabled by default. When enabled, it provides GET /v1/models, POST /v1/chat/completions and POST /v1/responses. The local dashboard records usage data on the machine and does not upload it.
Commands and files used by dsh-our-free-model
The README documents dsh plugin --profile web add for adding the package to a profile, with the actual profile name substituted for web. It also documents dsh --profile <name> --dump-config for checking the bundle configuration. A desktop self-check can load /sidecar/dist/lib/profile-upgrade.js with node and call planProfileUpgrade and assertProfileStartup.
For a real-directory desktop installation, the package is placed at node_modules/dsh-our-free-model/; dsh.profile.bundles must contain dsh-our-free-model, and dependencies must contain the current package version. The README identifies that version as 1.4.4.
How dsh-our-free-model behaves
The model collection, context length and capabilities are refreshed from the upstream gateway rather than stored as a static snapshot. A model rejected as unavailable or returning 404 is removed from the selector; gateway errors, rate limits, timeouts and network failures do not make that determination. Region-blocked models are grouped separately. Light, Balanced and Deep apply output budgets of 2,048, 8,192 and the model maximum, with doubled lower budgets for models whose reasoning cannot be disabled.
Known limits
The upstream source is OpenCode’s Zen gateway, so requests depend on the local network route and may be region-limited. Desktop profile startup rejects arbitrary symlinks and junctions. Managed bundles must set distribution: 'managed'; this disables in-app upgrades, announcements and hot reload. The EAC channel exists only in the specified desktop hosts, not in command-line hosts.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub