Introduction

In the plugin/preset ecosystem of DSH, the coding mode requires a stable command execution environment. Verified documentation indicates that the official path uses persistent bash for the minimal preset; dsh-coding-preset targets Windows, switches the shell to persistent PowerShell 7 (pwsh), and retains the official minimal coding session boundaries: only exposing pwsh and str_replace_editor.

It is worth noting: resources mark this package as DEPRECATED and point out that DSH’s official minimal mode now provides similar functionality. Below, based on verified facts, I introduce its positioning, capabilities, installation method, and limitations.

What is it

Saikel-Orado-Liu/dsh-coding-preset is a Windows-adapted DSH coding-mode agent preset. Its goal is to enable the DSH web profile to use a persistent pwsh session on Windows, rather than the persistent bash in the official minimal preset.

Key boundaries from verified documentation:

  • Retains the official minimal persona: You are a helpful software engineer assistant.
  • The coding mode session exposes only two tools: pwsh and str_replace_editor
  • Persistent shell is based on node-pty/ConPTY
  • License is MIT
  • README is marked as DEPRECATED and suggests using DSH’s official minimal mode

Core Capabilities

Persistent pwsh

Under danger-full-access, it provides persistent PTY execution. Variables, functions, aliases, and the current directory in the same session are preserved across invocations.

Under read-only and workspace-write, execution follows a one-time pwsh -Command path, with state not preserved.

Sandbox Privilege Escalation

When restricted commands are denied, one-time approval can be initiated carrying sandbox_permissions and justification, processed by ctx.approval. When rejected or justification is missing, it is treated as a failure.

This privilege escalation only applies to the single call and does not change the session mode.

Mode Switching

When an effective sandbox mode changes, it closes persistent terminals and rebuilds the shell on the next call according to the new mode.

Installation and Internationalization

When installing to a DSH web profile, postinstall deploys the preset file and internal packages; manual deployment is also supported. Documentation indicates it includes English and Simplified Chinese locale support.

Installation and Enablement

Prerequisites

The local machine must have PowerShell 7 (pwsh), not Windows PowerShell 5.1 (powershell.exe).

Install to web profile

First, install to the web profile:

npx @deepseek-ai/dsh plugin --profile web add @gamegeek-saikel/dsh-coding-agent-preset

Then start DSH:

npx @deepseek-ai/dsh web

If the DSH CLI is globally installed, you can also use dsh:

dsh plugin --profile web add @gamegeek-saikel/dsh-coding-agent-preset
dsh web

Note: The name in package.json from verified resources is @gamegeek-saikel/dsh-coding-preset, which differs from @gamegeek-saikel/dsh-coding-agent-preset in the installation command above. This article records it based on the installation command provided in the resources; before actual installation, confirm the installable package name on npm.

Manual Deployment

If you are not using npm package installation, manual deployment is possible:

  1. Copy agent.cordis.yml and preset.yml to:
~/.dsh/.agent-presets/coding/
  1. Run install.ps1 to copy the two internal packages to:
~/.dsh/profiles/node_modules

and the harness’s node_modules.

Typical Usage

Persistence Check

In a danger-full-access session, you can check persistence like this:

  1. Run:
Write-Output "hello"
  1. Run another command that reads a variable set by the previous command.

If the second command can read the state left by the first command, it indicates that the persistent shell is working.

Restricted Mode

In read-only or workspace-write sessions, commands are executed via a one-time pwsh -Command. Do not expect variables, functions, aliases, or the current directory to be preserved across commands.

One-time Privilege Escalation

If a restricted command is denied due to file access, the output will indicate that it can be retried once with sandbox_permissions. When retrying, use justification to explain the reason; after approval, only the current call takes effect, and the session mode remains unchanged.

Applicable Scenarios and Notes

Suitable for:

  • Developers on Windows using DSH coding mode who want command execution to fall on persistent pwsh
  • Users who want the coding session to expose only pwsh and str_replace_editor
  • Users needing clear behavioral boundaries between danger-full-access and restricted modes

Notes:

  • The package is marked as DEPRECATED. If DSH’s official minimal mode is available, prioritize using the official minimal mode.
  • It requires pwsh and does not require or support Windows PowerShell 5.1 (powershell.exe).
  • The plugin/preset runs with the current DSH process. Before installation, check the source code, dependencies, command wrappers, PTY backend subprocess behavior, and sandbox logic, and confirm that the MIT license meets your requirements.
  • DSH’s community directory is an independent site and is not equivalent to DeepSeek or Hypersphere’s official app store; do not treat this preset as a default component in the official app store.

Conclusion

The value of dsh-coding-preset lies in focusing the Windows path of DSH coding mode on persistent pwsh and two fixed tools. Since the resources mark it as deprecated, the current safer approach is to first confirm whether DSH’s official minimal mode already covers the needs; if you still want to install this preset, follow the steps in this article to check pwsh, installation commands, package names, and source code.

GitHub: https://github.com/Saikel-Orado-Liu/dsh-coding-preset

Directory Page: A fixed URL was not provided in the resources for this article; you can search for dsh-coding-preset in the DSH Community Directory.