deepseek-harness-tui-openmaai

<p align="center"> <img src="https://raw.githubusercontent.com/openma-ai/Martty/main/assets/martty-lockup.svg" width="650" alt="Martty terminal lockup" /> </p>

<h1 align="center">Martty</h1>

<p align="center"> A DSH-first terminal with the same Cordis plugin model, plus support for other ACP agents. </p>

---

Native binaries are packaged for macOS arm64, macOS x64, Linux x64, and Windows x64. Requires Node.js 18+.

> Rename note: the project and recommended npm package have moved from > DeepSeek Harness TUI / @openma/deepseek-harness-tui to Martty / martty. > The dsh-tui command, configuration, and session data remain compatible. > The production profile is now martty; legacy tui profiles > continue to work.

Global Agent TUI

npm install --global martty
martty

Martty directly depends on our @openma/deepseek-harness-acp implementation. It resolves this built-in ACP from its own dependency graph, connects DSH by default, and requires no separate ACP installation. For another ACP server, configure DSH_TUI_AGENT; Cordis embedding can instead provide config.agent or config.stream. --agent is only the standalone CLI override for the same connection configuration.

Recommended

npm install --global @deepseek-ai/dsh
dsh plugin --profile martty add martty@latest
dsh --profile martty

The profile command is the recommended install and upgrade path. It creates a missing profile and installs the TUI plus its ACP dependency; no global martty installation is required.

Migrating from DeepSeek Harness TUI / the scoped package

martty is the recommended package name. Starting with 0.2.13, it and the legacy @openma/deepseek-harness-tui package are published by the same CI run with identical versions and artifacts. Existing scoped-package installs remain supported. To switch package names:

dsh plugin --profile tui remove @openma/deepseek-harness-tui
dsh plugin --profile martty add martty@latest

The recommended profile changes from tui to martty; runtime behavior, config, and session data remain unchanged. dsh-tui and legacy tui profiles remain compatible.

The profile Host mounts the ACP plugin on Base, then starts a separate TUI Client process over standard ACP stdin/stdout. For standalone use, run martty and use --agent <cmd> plus repeated --agent-arg <arg> for another ACP server. The Node Client process owns a Cordis tree and starts the Rust painter. A sibling tui-cordis-client-runner publishes TUI Client capabilities and evaluates approved code.client packages from dsh-tool-cordis against that client tree.

ACP is a runtime dependency of this package. On a profile that already carries a different version through the standard ACP bundle, the package manager may retain both copies, but the TUI bundle replaces that surface's rows and mounts only the plugin resolved from TUI's own dependency graph. The supported profile shape never runs two ACP surfaces for one TUI.

The package carries ACP as a runtime dependency and exports its Creator Host overlay internally. The profile bundle mounts both on the Host Base tree; neither enters the Client tree. Creator adds TUI plugin guidance to the existing cordis preset and does not use ACP for skill registration. Creator-authored UI Presets and Theme Plugins preview as process-local dynamic Packages, then persist explicitly under $MARTTY_HOME/plugins through tui_plugin_save; tui_plugin_read resumes authoring after restart.

MARTTY_HOME resolves explicitly first, then to $DSH_HOME/.martty, then to ~/.martty. UI choices live in $MARTTY_HOME/settings.json. On first use, legacy Creator artifacts and settings are copied forward without deleting or overwriting the old files.

Third-party TUI plugins remain ordinary installed packages. Their Host-side registrar contributes an absolute Client module entry to tuiClientPlugins; the Host runner serializes only that directory into the separate Client process. Package entries and Creator artifacts share one Client lifecycle manager, with installed packages winning same-id conflicts.

Node and Rust use inherited pipes on Unix and an authenticated loopback TCP socket on Windows. This compositor channel carries theme/render data only; agent traffic remains ACP.

Demo

martty --demo
martty --demo-skin

Without a global installation:

npx --yes martty --demo

The profile path remains recommended for an existing DSH installation that wants standard plugin management and a durable martty profile. martty is the primary command; dsh-tui remains a compatibility alias.

Highlights

• Streamed reasoning, replies, tool activity, subagents, run state, and

token/cache metrics in one terminal timeline.

• Agent-advertised models, compositions, permissions, authentication methods,

and invocable skills in one searchable slash menu.

• Up to eight editable image chips per prompt, with clipboard/file staging and

metadata previews on kitty-capable terminals.

• Terminal-aware Markdown for headings, lists, quotes, code, emphasis, links,

and mixed CJK/Latin text.

• Durable sessions, queued follow-ups, immediate steering, readline editing,

platform-native modifier bindings, mouse selection, and inline-expanded tools.

• Dark/light themes, clipboard routing for local, tmux, and SSH sessions, plus

the optional /liang pixel companion.

• Persistent UI Presets selected with the native /ui picker (or /ui <id>): builtin Martty and the classic

DeepSeek Harness composition, both assembled from independent welcome Hero and information slots without writing to the transcript.

• A root chrome.right plugin rail for validated TuiNode trees, with live

update/unload and Client inspect support for Creator-authored plugins.

• Lifecycle-owned local commands and native slider overlays, plus transactions

over the current Session's standard ACP configOptions.

• Dynamic code.host + code.client Packages with inspect/run lifecycle and

package-private Host/Client RPC over a negotiated _dsh/cordis/* ACP extension. Ordinary ACP agents remain usable when they do not advertise it.

Plugin surface

TUI extensions are ordinary Cordis plugins on the Node Client tree. A single plugin may register a theme, chrome.right nodes, slash commands, overlays, timers, Session config transactions, and Host/Client RPC; all contributions leave together when its fiber stops or /theme replaces the selected Theme Plugin. Plugins submit semantic data and never receive the TTY, Ratatui, absolute coordinates, compositor fds, or private transport methods.

The versioned contract and examples live in the repository's plugin API.

The demo needs no API key or agent. Run martty --help for agent, model, credential, session, theme, and demo options.

Supported platforms

If installation succeeds but launch reports no native binary for ..., confirm that you installed the latest version and that your platform appears above.

Uninstall

npm uninstall --global martty

Use npm uninstall --global @openma/deepseek-harness-tui instead for a legacy global installation.

Source, screenshots, development commands, and architecture notes live in the GitHub repository.

MIT.