How to install and use the TUI profile?

[2xmncvcx92-dotcom]

Background

The DSH CLI documentation mentions the tui profile in several places:

• README.md shows dsh --profile tui --resume <id> as an example
• The help text describes TUI as a terminal interactive interface with --resume support

However, when attempting to install the TUI profile, we encounter:

$ dsh plugin --profile tui add @deepseek-ai/dsh-base
# Error: @deepseek-ai/dsh-compact-basic is not in the npm registry

Questions

1. Is the TUI profile publicly available? If yes, what is the correct installation method?
2. Are the required packages published to npm? We notice @deepseek-ai/dsh-compact-basic and potentially other TUI-related packages are not found in the public npm registry.
3. Are there any prerequisites or access requirements (e.g., private registry, early access program)?

Use Case

We'd like to integrate DSH session resume functionality into OpenClaw's terminal interface, allowing users to continue DSH conversations from the command line. The TUI profile seems like the natural fit for this workflow.

Environment

• DSH version: 0.1.1-rc.2
• Platform: macOS
• Existing profiles: web and headless work correctly

Any guidance would be appreciated. Thanks!

[m0hamadazzam]

I looked into this because there seem to be two separate issues here: the availability of a TUI itself, and the @deepseek-ai/dsh-compact-basic error you hit while creating the profile.

1. The TUI is not a first-party shipped profile in 0.1.1-rc.2

For 0.1.1-rc.2, the shipped CLI profiles are web and headless. A profile such as tui has to be assembled from an external plugin/bundle; simply creating a profile named tui does not give it a terminal UI.

More importantly, DeepSeek Harness previously had an in-repository TUI package, but it was deliberately removed. The repository's implementation note says that DeepSeek Harness no longer ships a terminal UI package and that Web remains the shipped interactive surface.

That also explains why the documentation is confusing here.

There is an earlier discussion about the exact github:deepseek-harness/turtle-ui reference: #871. A maintainer clarified there that the referenced TUI was in a private repository at the time and that the role of the TUI would be reconsidered.

So I would not interpret the tui examples in the 0.1.1-rc.2 CLI docs as meaning that an official, publicly installable TUI profile was included with that release.

2. The @deepseek-ai/dsh-compact-basic error looks like a separate package-version problem

This part is important because I don't think that error means you are missing access to some private TUI dependency.

@deepseek-ai/dsh-compact-basic is an older package name. It was renamed to:

@deepseek-ai/dsh-compaction-basic

There has also been a reported npm dist-tag/version skew in the 0.1.1-rc.2 release line; see #4434.

The CLI itself resolves to 0.1.1-rc.2, while an unversioned:

dsh plugin --profile <name> add @deepseek-ai/dsh-...

could resolve some plugin packages from an older release train. That can produce dependency trees referring to old or unpublished package names.

So this:

dsh plugin --profile tui add @deepseek-ai/dsh-base

may be mixing your 0.1.1-rc.2 CLI with an older dsh-base package.

If you want to verify that independently, compare:

npm view @deepseek-ai/dsh-base version
npm view @deepseek-ai/dsh-base versions

and try explicitly pinning the same release train:

dsh plugin --profile tui add @deepseek-ai/dsh-base@0.1.1-rc.2

However, even if that installs successfully, dsh-base by itself is only the base Harness bundle. It still does not provide a TUI.

3. For the OpenClaw integration

For the use case you described — selecting/resuming an existing DSH session from a terminal interface — I would not build against the old tui documentation as though it were a supported first-party interface in 0.1.1-rc.2.

There are now public out-of-tree TUI implementations, including turtle1999/turtle-ui and other community plugins, and some of them implement --resume.

But because Harness is still in developer preview and its plugin APIs are changing, I would verify compatibility with the exact DSH version you want to support rather than assuming a current TUI plugin works with 0.1.1-rc.2.

If OpenClaw only needs session discovery/resume rather than the complete TUI rendering layer, integrating with DSH's session interface directly may also be a cleaner boundary than depending on a particular third-party terminal frontend.

So, in short:

• tui was not a shipped first-party interactive profile in 0.1.1-rc.2.
• The old documentation/reference was misleading; 有bug, 还是说文档描述不准确? 添加tui plugin失败了 #871 confirms the referenced TUI repository was private at the time.
• @deepseek-ai/dsh-compact-basic is most likely a version/dependency mismatch, not evidence that you need private-registry access.
• Pinning @deepseek-ai/dsh-base@0.1.1-rc.2 may fix that specific dependency error, but it will not create a TUI by itself.
• For OpenClaw, I would either use a compatible public TUI plugin or integrate the session/resume functionality directly.