DeepSeek Harness Plugin

riesbri/dshline#dshline

Stars ★ 20 Downloads (30d) 2,244 Category UI Enhancements Added 2026-08-27 npm @dshline/dshline

Terminal-native TUI frontend for DeepSeek Harness that presents sessions, models, plugins, jobs, subagents, todos, and provider configuration through Harness capabilities while preserving real terminal scrollback.

Install

# from npm (prebuilt)

dsh plugin --profile web add @dshline/dshline

# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)

dsh plugin --profile web add github:riesbri/dshline#path:/packages/dshline

Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).

README

A terminal-native frontend for DeepSeek Harness.

dshline is an in-process Harness presentation adapter, not a separate client or agent runtime. Finished output stays in the terminal's real scrollback while only a bounded live region is redrawn.

Harness plugin → standard capability → dshline presentation adapter → native terminal UI

Harness owns capabilities, state, runtime, and policy; dshline presents supported Harness capabilities natively in the terminal. It prefers generic capability contracts over provider-specific integrations, so a provider that participates in a supported Harness seam can share the same terminal presentation.

npm install -g @deepseek-ai/dsh @dshline/dshline
dshline

The first run asks once before letting Harness create the dshline profile and install this package into it; dshline --setup does that install explicitly, for a script or a source checkout. pnpm has to be on your PATH for either, because the harness installs profile plugins with pnpm — dshline checks first and says so rather than leaving a half-made profile behind.

dshline supports one Harness generation at a time. If installation reports a dependency conflict, do not bypass it with --force or --legacy-peer-deps; see the repository's installation guide.

The presentation core is small and dependency-light; its renderer has no runtime dependencies and knows nothing about agents or providers.

For installation requirements, usage, architecture, security guidance, and the canonical roadmap, see the dshline repository.

License

MIT

Content from the project README on GitHub ↗

Links

More in this category

View the whole category →

Community comments

Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.