Martty

A terminal Agent UI for DeepSeek Harness that also speaks ACP to other agents and evolves its own plugins at runtime.

Source repo
openma-ai/Martty
Stars
★ 83
Last updated
3d ago
License
MIT
Primary language
Rust

At a glance

Works with
Portable with changes
You'll need
Node.js 22.19+Rust stable (build from source only)pnpm (may be required for dsh plugin install)@deepseek-ai/dsh >=0.1.7-rc.2 (optional profile host)Shell / CLINetwork accessLocal filesystem
Typical use
Developers who want long coding sessions with streaming reasoning, tool calls and Plans inside a terminal.
Main limitation
Default experience is tied to DSH and its bundled runtime; other Harnesses mean editing agent or stream configuration.
Website
martty.sh ↗ set on GitHub
Maintenance
Commits in the last 30 dayslast commit 2026-11-18latest release v0.3.3 (2026-10-17)

What does this agent do, and when should you use it?

Martty is a terminal UI client for ACP agents. It ships an embedded ACP connection layer, starts and connects to DeepSeek Harness (DSH) by default, and can be pointed at any other ACP-compatible agent through configuration. Rendering is split: a Rust/ratatui painter owned by the Martty Client process takes exclusive control of the user TTY over fd 3/4, while ACP traffic uses the Client's stdin/stdout. The interface is not a fixed set of switches — UI, themes, slots, commands, overlays and session views are all composed from Cordis Plugins that load and unload with their lifecycle, and Client halves can register content into six named slots such as welcome.hero, chrome.right and conversation.composer.dock. A martty harness CLI plus an in-TUI /harness panel share one ACP Registry for discovering, installing and switching Harnesses. Installed as a dsh plugin (dsh --profile martty), a Host half runs in the Harness while the Client half renders, giving a two-process design.

On startup Martty performs ACP initialize and session/new against the selected Harness, which lets the welcome screen show the agent-reported model and effort before the first message. It then renders streaming replies, reasoning, tool calls, subagents, Plans, token usage and persisted sessions in the terminal. The composer supports multi-line editing, selection copy/cut, undo/redo, an optional vim mode, images via /image or /clip, and queued messages (enter sends, ctrl+enter steers, alt+↑ edits the queue). Discovery runs through martty harness find/add/use/list/remove and the /harness panel: find reads a cached or bundled registry snapshot unless --refresh is given, in which case it fetches https://cdn.agentclientprotocol.com/registry/v1/latest/registry.json; binary entries download to $MARTTY_HOME/bin/<id>/<version>/<platform> and are SHA-256 verified before configuration. For plugins, a Creator can call cordis_inspect_self to read a validated package, generate a code.host, code.client or dual package, and persist Client-only artifacts through tui_plugin_save into $MARTTY_HOME/plugins/<artifact-id>/plugin.json, while packages containing code.host must be packaged and installed with dsh plugin --profile martty add.

  1. Developers who want long coding sessions with streaming reasoning, tool calls and Plans inside a terminal.
  2. People juggling several ACP agents (DSH, Pi, Codex-style registry entries) who want to switch Harness from the TUI with /harness.
  3. Cordis plugin authors adding custom panels, navigation or token statistics to a terminal agent UI.
  4. Research or prototyping teams that want the agent to generate, validate and save new UI plugins mid-session.
  5. Automation that discovers and configures ACP Harnesses from scripts or CI via the martty harness CLI.

Key setup facts

Pulled from the install and usage notes below. The project README has the current values.

Install / run
  • npm install --global martty
  • npx --yes martty
  • npm install --global @deepseek-ai/dsh
Runtime
Node.js 22.19+

How do you install or deploy this agent?

Installation expects Node.js on the machine (22.19+) and may need pnpm when installing through dsh.

npm install --global martty
martty-cli   # first run creates the `martty` command; afterwards run `martty`

Without a global install:

npx --yes martty

Let DSH manage plugins and upgrades in a profile:

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

Building from source requires Rust stable and Node.js 22.19+:

make rust-test
node --test scripts/package-native.test.mjs
bash scripts/build-npm.sh

How do you use this agent?

Browse and configure a Harness, then launch the TUI in your working directory:

martty harness find         # browse the Registry plus local candidates
martty harness add <id>     # install / save configuration
martty harness use <id>     # make it the default for the next launch
martty                     # start the TUI in the current working directory

To look at the interface only:

martty --demo
martty --demo-skin

Point standalone mode at another ACP agent, or switch inside the TUI:

DSH_TUI_AGENT="<acp-command> [args...]" martty

Inside a running session the main entry points are /model, /agent, /harness [id], /permission (shift+tab rotates), /theme and /theme toggle, /plugins, /cordis-plugins, /auth and /status. If the shell cannot find martty, run from the repository root:

node npm/bin/martty.js harness --help

What are this agent's strengths and limitations?

Pros
  • Embedded ACP client: DSH by default, and other ACP agents via DSH_TUI_AGENT, --agent/--agent-arg or config.agent without swapping out the ACP layer.
  • The UI is composed from Cordis Plugins with six documented tuiSlots and a tui-node.v0 schema, so plugins can be created, observed, updated and rolled back while running.
  • martty harness find/add/use/remove and the /harness panel share one ACP Registry, covering npx/uvx entries and SHA-256-verified managed binary installs.
  • The published package declares no install scripts, so it installs under pnpm's strict build-scripts policy without approvals.
  • A documented migration path from @openma/deepseek-harness-tui copies old config and session data on first launch instead of deleting it.
Limitations
  • Default experience is tied to DSH and its bundled runtime; other Harnesses mean editing agent or stream configuration.
  • dsh must be >=0.1.7-rc.2; below that floor or with missing host capabilities the ACP plugin will not mount and you must fall back to the bundled npx martty mode.
  • A fresh install only provides martty-cli until it is run once, which is easy to mistake for a failed install.
  • Packages containing code.host cannot be promoted automatically; they must be repackaged as a Cordis npm package and installed with dsh plugin add.
  • Source builds need Rust stable, native binaries ship per platform, and --omit=optional installs must be redone with optional dependencies enabled.

How does this agent compare with similar options?

Key facts side by side with the most closely related agents.

Agent Source review Form / cost Stars Updated Language Full support on
Martty This agent 58 · Major gaps — ★ 83 3d ago Rust —
dsh-TUI - Terminal UI Plugin for DeepSeek Harness 72 · Some gaps CLIFree + model costs ★ 8k today TypeScript —
rpi: Rust Coding-Agent Runtime 71 · Some gaps CLIFree + model costs ★ 287 today Rust OpenAI API · Claude API
Zoetrope 86 · Good CLIFree ★ 1.2k 2mo ago Rust Claude Code

How does FollowAgents rate this agent?

FollowAgents source review · FARS-2.1
Major gaps
58/ 100 5-point scale 2.9 / 5
Trust 16/29
Reliability 9/14
Adaptability 10/18
Convention 12/18
Effectiveness 7/13
Verifiability 4/8
Why each dimension lost points
Trust16 / 29 · 2.8/5

Least privilege: plugins are explicitly denied the TTY, raw mode, kitty escapes and absolute coordinates and may only submit TuiNode trees (AGENTS.md, README), but the npm launcher creates/removes global bin links and writes $MARTTY_HOME, so the surface is not minimal — deducted to 2. User confirmation: harness remove previews and confirms, supports --dry-run and requires --yes when non-interactive, and switching after a prompt needs confirmation, but --api-key is passed as a plain CLI argument with no masking guidance — deducted 1. Data-flow transparency: README explains the Registry snapshot source, stderr progress and captured installer output, yet never systematically states where session JSONL and credentials live or how long they are kept — deducted 1. Sensitive data: --api-key is plaintext input and credentials are only vaguely 'preserved', with no encryption or permission notes — 1. Dependency security: Cargo.toml pins recent versions and CI uses --locked, but there is no audit/vulnerability-scan evidence and binary downloads verify SHA-256 only 'when provided' — deducted to 1. External effects: downloads, installs, no PATH writes, Ctrl-C staging cleanup and retaining the previous default on failure are well handled — 2. Rollback: stop/update/rollback lifecycle, previous-default retention and uninstall convergence are described — 2. Source attribution: MIT with an OpenMA copyright line is clear, but the publisher is unverified and the project went through a rename and package migration, so the chain must be reassembled by the reader — deducted to 1.

Reliability9 / 14 · 3.2/5

Self-consistency: README, AGENTS.md and agent-install.md agree on install paths, version floor and profile names, but Node requirements appear as both >=18 and 22.19+, a visible contradiction — deducted 1. Dependency availability: engines.dsh floor, bundled ACP version, per-platform optional deps and npx/uvx fallback are documented — 2. Failure messages: the CLI rejects unknown args, missing values and misused --dsh with clear errors, the TUI error panel retries, and install failures have a troubleshooting table — 2.

Adaptability10 / 18 · 2.8/5

Audience and scenarios: covers terminal users, AI-agent installation, plugin developers and dsh users with clear scenarios — 2. Capability boundaries: states that the ACP client does not import a harness, plugins never get the TTY, Host/Client are split and dynamic plugins are not persisted — 2. Trigger precision: the SKILL.md trigger depends on loading an external cordis-plugin-development skill first and on runtime inspect results, so static evidence cannot confirm precise triggering — deducted to 1. Environment fit: macOS/Linux/Windows, static musl, Windows loopback TCP and PATHEXT are all covered — 2.

Convention12 / 18 · 3.3/5

Information architecture: bilingual README, docs directory and tested website doc routes give a clear structure — 2. Install notes: three install paths plus verification and troubleshooting tables are outstanding — 3. Naming stability: the project and package moved from DeepSeek Harness TUI to Martty, the command changed from dsh-tui to martty-cli/martty, and the Cargo package is still deepseek-harness-tui — deducted to 1. Examples and FAQ: demo, screenshots, dump-frame smoke and a troubleshooting table exist, but there is no consolidated FAQ — 2. Known limitations: README and agent-install list migration caveats, platform constraints and the absence of a clippy/fmt gate — 2. License: full MIT text consistent with Cargo and README — 3. Versioning/changelog: three files must stay in sync and CHANGELOG follows Keep-a-Changelog, but the CHANGELOG itself is not in the packet — deducted to 2. Maintenance responsibility: only 'OpenMA contributors', with no governance, contact or security-reporting channel, and the publisher is unverified — 1.

Effectiveness7 / 13 · 2.7/5

Output usability: the TUI output, headless dump-frame rendering, error panels and retry paths make results directly usable — 2. Marginal value: a plugin-based TUI with a self-evolving Creator on top of an ACP client is differentiated, but the value claim rests on a Creator loop not shown in the packet — deducted to 2. Cost-benefit: requires Node, pnpm, a Rust toolchain and the dsh ecosystem, so install and migration cost is high while benefit evidence is mostly self-asserted — 1.

Verifiability4 / 8 · 2.5/5

Claim traceability: most README claims point to docs and scripts, but key claims such as Creator self-evolution and performance have no supporting file — deducted to 1. Cross-source corroboration: CI workflows, AGENTS.md, agent-install.md and website tests corroborate the install and release flow — 2. Fact/inference separation: docs mix 'implemented' with 'long-term direction', e.g. 'Current boundary' sits beside goal statements, forcing the reader to separate them — deducted to 1.

Risks and how to mitigate them
  • The project and package migrated from DeepSeek Harness TUI to Martty and the command from dsh-tui to martty-cli/martty, while the Cargo package is still deepseek-harness-tui; scripts and docs mix old and new names, so automation should verify the actual command per version.
  • Node requirements conflict across documents (>=18 vs 22.19+); treat npm/package.json engines as authoritative before deployment.
  • --api-key is passed as a plaintext CLI argument and may leak into shell history and process listings; prefer environment variables or a credentials file.
  • The publisher is not verified by the FollowAgents registry and no security-reporting channel is documented; verify the npm package-to-repository mapping before installing.
  • Binary downloads verify SHA-256 only 'when provided', so Registry entries without a checksum lack an integrity guarantee.
  • Creator self-evolution and dynamic plugin loading are the headline claims, but the packet lacks implementation and test evidence for them; do not infer completeness from the README.
Evidence confidence: Low Reviewed Nov 11, 2026 Reviewed revision b4dbfa05a049 New commits since this review; the score may not cover them
See the full review method →
Maintain this project? Add the FARS badge to your README

The badge shows the current review score and verdict and links back to this page. It refreshes about once an hour after a re-review.

FARS

[![FARS review](https://followagents.com/badge/martty.svg)](https://followagents.com/en/agents/martty)
<a href="https://followagents.com/en/agents/martty"><img src="https://followagents.com/badge/martty.svg" alt="FARS review"></a>

Recent releases

Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.

  1. v0.3.3
    Release notes excerpt
    Compatibility - Supported @deepseek-ai/dsh is now a floor, >=0.1.7-rc.2, declared as engines.dsh (read by dsh's plugin compatibility check); the exact-version dsh.supported list is gone. Newer dsh releases are attempted; a dsh newer than the newest tested (0.2.1-rc.2) only warns. - Bundles @openma/deepseek-harness-acp 0.4.39, which applies the same floor and feature-detects dsh 0.2.1's subagent teardown API. Added - martty --dsh <profile> (also npx martty --dsh <profile>) attaches to the …
    View on GitHub ↗
  2. v0.3.2
    Release notes excerpt
    Compatibility - Bundles @openma/deepseek-harness-acp 0.4.38 (compatible range >=0.4.38 <0.5.0). - Supported @deepseek-ai/dsh: 0.1.7-rc.2 || 0.2.0-rc.1 || 0.2.0-rc.2. - Pi harness launches @openma/pi-acp@latest (0.1.8 at release time). Known issues - #168 ACP auth: choosing another method while an agent auth is pending does nothing; a typed key falls into the prompt queue. What's Changed * Bump @openma/deepseek-harness-acp to 0.4.36 by @hrhrng in https://github.com/openma-ai/Martty/pull/137 …
    View on GitHub ↗
  3. v0.3.1

FAQ

Do I need DSH installed first?
No. Default mode uses the bundled @openma/deepseek-harness-acp and its dsh runtime. To use a different ACP agent, supply a launch command through DSH_TUI_AGENT, --agent/--agent-arg or config.agent.
Does switching Harness disturb the running session?
CLI add/use only write settings, and the change applies on the next standalone launch. In the TUI, /harness replaces the standalone ACP child process; if the session has already sent a prompt or was restored via /session you are asked to confirm, and the old session remains reachable from /session. defaultHarness is only updated after initialize and session/new both succeed.
Do dynamic plugins survive a restart?
Plugins created in Cordis mode belong to the current process by default. Client-only plugins can be saved with tui_plugin_save into $MARTTY_HOME/plugins and rediscovered on the next launch; packages with code.host must be packaged and installed via dsh plugin --profile martty add, and there is no one-step promote command.
Do binary Harnesses get added to my PATH?
No. Binary registry entries require confirmation, download into $MARTTY_HOME/bin/<id>/<version>/<platform>, and are checked with SHA-256 before configuration. harness remove --cleanup only deletes the private install directory and leaves global programs and shared npx/uvx caches alone.
I have the old @openma/deepseek-harness-tui installed — what now?
Just run npm install --global martty; the first launch removes martty/dsh-tui/dsb links that belong to the old package and strips its bin declarations. Inside a dsh profile, remove the old package and add martty@latest; existing config and session data are copied, not deleted.
Is Martty open source?
Yes. The source code is on GitHub (openma-ai/Martty) under the MIT licence.
Is Martty safe to use?
FollowAgents' FARS review (Nov 11, 2026) scored Martty 16/29 on trust and safety. None of the eight safety controls the review checks for was missing outright. The repository has changed since that review.
Is Martty still maintained?
Yes. The latest commit on GitHub is from 2026-11-18, within the last 30 days. The latest release is v0.3.3 (2026-10-17).
Who makes Martty?
Martty is published on GitHub by the account openma-ai. FollowAgents has not verified which person or company is behind that account.
What is Martty's official website?
The project's GitHub repository lists https://martty.sh as its website. That link is set by the repository owner; the source code itself is on GitHub (openma-ai/Martty).
Was this page helpful?
View on GitHub ↗ Install ↓

Compare agents like this one

The same FARS review applied across the shortlist this agent qualifies for.

Related concepts