README
dsh-shell-surfaces
English | 简体中文
https://github.com/Nesarf/dsh-shell-surfaces -- a DSH plugin.
dsh plugin --profile <profile> add github:Nesarf/dsh-shell-surfaces # the tip of main
dsh plugin --profile <profile> add github:Nesarf/dsh-shell-surfaces#v1.0.0 # a tag
The tag is the version that can be named. Installing from main gets whatever it holds
today; installing a tag gets the commit that was decided on -- which is what "install the
same thing again tomorrow" and "go back to what worked" both need. v1.0.0 is the first
such point: thirty-five faces, two views of the same rows, and sizes a reader can drag.
The badge is the whole test workflow: the pure self-test, and a live check that runs one real command on every surface the runner has -- on Windows and on Linux -- then feeds those answers into the same table a person reads. A green badge means "the table and the argv shape still hold, and both platforms still answered", not just "the linter passed".
One DSH tool for the execution surfaces this machine has -- thirty-five faces at the last measurement: a WSL Linux userland and the ten shells inside it, the MSYS2 userland's six, four interpreters, both PowerShells, four window hosts, two container runtimes, a remote destination, a real console, and nushell.
It exists because a rule that is only written down is not a capability. The selection rules for these surfaces have been recorded for a while, but a session could only act on them by composing a command string for pwsh and hoping the quoting survived the trip. Here they are callable.
shell_surfaces(action="surfaces") what exists here, and where each was looked for
shell_surfaces(action="run", surface="wsl", command="grep -P '(?<=Linux )[0-9.]+' /proc/version")
shell_surfaces(action="run", surface="nu", command="open data.json | where n > 3 | to json")
shell_surfaces(action="run", surface="msys", command="pacman -Q | wc -l")
shell_surfaces(action="run", surface="pwsh", command="Get-CimInstance Win32_OperatingSystem | Select-Object Caption")
shell_surfaces(action="run", surface="pty", command="powershell -File install.ps1", send=["y\n"])
Contents
The file is long because each section answers a question a person actually asked while using this, and the answer is not one sentence. The map below is the short version: read the section you need, skip the rest.
| What you want to know | Where |
|---|---|
| is PowerShell still the fallback? | PowerShell is a surface here |
| can a command outlive the call? | Background work stays here too |
| does confinement apply here? | The same sandbox as the built-in shell tools |
| can state survive between calls? | Persistent sessions |
| what else is installed on this machine? | Finding this machine's shells |
| which version is each shell? | Which version |
| what can each face actually do? | What each face can do |
| run Python, Perl, JS, VBScript | Interpreters are faces too |
| reach another machine | An ssh destination is a surface |
| run it in a container | A container is a face too |
| what does the list look like? | The list is a tree |
| which faces work together? | Who works with whom |
| why one tool instead of many? | Why one tool and not seven |
| what does a call render as? | The row a call renders as |
| a surface refuses to answer | Opening a path instead of refusing it |
| what is deliberately not supported? | What it is not |
| why are the arguments shaped that way? | The facts behind the argument lists |
| how do I run the checks? | Verification |
| what is still unverified? | Honest boundaries |
PowerShell is a surface here
"Fall back to pwsh" used to mean "leave this tool and use the other one". The
pwsh surface closes that gap: a PowerShell command is an ordinary call here,
the same shape as every other surface, so a session that hits an awkward surface
does not have to change its tool to get a PowerShell job done. Background jobs,
timeout promotion, escalation approval and persistent sessions work on it as
well -- they are surface features here, not privileges of one tool.
Both PowerShells are addressable, and that took two entries rather than one. pwsh
is PowerShell 7 and is the better default; powershell is the 5.1 that ships
with Windows. Keeping them behind a single DSH_PWSH variable meant a machine
holding both could reach only one of them, while "does this script still work on
5.1" is a question two surfaces answer and one variable cannot.
The one shape this tool does not carry is a terminal session that keeps a drawn
prompt or a cursor. That is where the built-in pwsh tool still earns its place;
"the command is PowerShell" is not a reason to go there.
A surface-level failure is also not a reason to change tools. When a surface is
absent, cannot spawn, or times out, the tool says so and names the next call
(action="surfaces") that stays inside this plugin; the failure is about the
surface, not about the tool.
Background work stays here too
更多「命令列與終端機」外掛
deepseek-harness-docker
作者 runzhliu
社群 Docker 與 Kubernetes 打包,含加固映象、Compose、Helm、Web UI 與無頭 CLI。
deepseek-harness-android
作者 dphmoblie
dsh安卓版:整合 DeepSeek Harness、Ubuntu 執行環境、外掛與檔案管理,以及使用者授權的 Shizuku 和無障礙自動化。
dsh-subagent-codex
作者 mjylfz
讓 DeepSeek Harness 以 Codex CLI 作為子代理的外掛,在對話中複用 Codex 的編碼與推理能力。
mnemon
作者 mnemon-dev
LLM 監督的持久記憶系統,基於圖結構召回、跨會話知識共享,單個二進位制檔案,相容 DeepSeek Harness 等執行時。
