# Feature parity: Web/Desktop vs. the CLI

This page is the honest audit of how much of the DeepSeek Harness Web/Desktop product the terminal CLI reproduces.
Two facts drive it:

1. The CLI is **not a re-implementation**. It boots the same `dsh-base` + `dsh-headless` bundles the GUI runs, so the
   agent loop, tools, sandbox, approvals, session store, compaction, goals, plans, skills, subagents, workflows and
   MCP resource plumbing are literally the same code.
2. The **surface** differs. A terminal has no sidebar, no drag-and-drop, no browser panel, and no pixel cards. Some
   GUI features map to a command; some are meaningless; a few are genuinely missing.

Legend: ✅ works · 🟡 terminal adaptation · ❌ not available in the CLI

## Chat and conversation

| Web / Desktop | CLI | Notes |
|---|---|---|
| ✅ Streaming assistant text | ✅ | Token-level via `agent/assistant-stream` |
| ✅ Markdown rendering | 🟡 | Headings, bold, inline code, fenced code; no tables/images layout |
| ✅ Stop a running turn | ✅ | Ctrl+C → `agent.cancel()` |
| ✅ Multi-turn context | ✅ | One live Agent per process; `/new` starts a fresh session |
| ✅ Resume a conversation | ✅ | `deepseek -r [id]`, `-c`, `/resume <id>`, `/sessions` |
| ✅ Session titles/list | 🟡 | `/sessions` lists ids + age; titles are generated in the log but not shown |
| ✅ Rename / delete / pin sessions | ❌ | Not exposed by any CLI surface |
| ✅ Message edit & retry | ❌ | No rewind/retry command |
| ✅ Message feedback | 🟡 | `/feedback` (native Harness command) writes the record |
| ✅ Attach images (paste/drag) | 🟡 | `/image <path>` or `@photo.png`; stored durably, model sees them |
| ✅ Attach files | 🟡 | `@path` inlines text up to 200 KB; no binary upload |
| ✅ @-file references | ✅ | `@path` resolves against the working directory |
| ✅ Token usage meter | ✅ | Per-turn `· 12.3k in / 456 out` line |

## Tools and agent control

| Web / Desktop | CLI | Notes |
|---|---|---|
| ✅ Tool cards (read/write/edit/grep/glob/pwsh/web/…) | 🟡 | One-line icons + path preview; results summarized |
| ✅ File diffs in cards | ❌ | No diff renderer (use `/diff`-style tooling or git in another shell) |
| ✅ Approval prompts | ✅ | `Allow write …? [y/N]`; `-y/--yes` auto-approves |
| ✅ Permission presets | ✅ | Native `/permission`, plus `/permissions` alias |
| ✅ Todo checklist | ✅ | Live `☑ 2/3` checklist with incremental updates |
| ✅ Subagent cards | 🟡 | `↳ subagent … started/finished` progress lines |
| ✅ Jobs panel | ✅ | `/jobs` lists id, status, label, progress |
| ✅ Workflow run view | 🟡 | Tool calls stream; no dedicated tree view |
| ✅ Deliverables / present cards | ❌ | No card surface in a terminal |
| ✅ Plan mode | ✅ | Native `/plan`, `/plan off`; plan review uses the terminal question provider |
| ✅ Goal mode | ✅ | Native `/goal set/view/pause/resume` + goal tools |
| ✅ Compaction | ✅ | Automatic, plus native `/compact` |
| ✅ Ask-user questions | ✅ | Rendered with numbered options in the terminal |
| ✅ Scheduled reminders | ❌ | Needs the Host Web session controller; not mountable in a CLI-only profile |
| ✅ Skills | 🟡 | `/skills` lists them; the model invokes them through the skill tool |

## Models, auth, settings

| Web / Desktop | CLI | Notes |
|---|---|---|
| ✅ Pick model / reasoning effort | ✅ | `/model`, `/reasoning`, `--model`, `--reasoning` |
| ✅ API key management UI | 🟡 | Reuses the key saved by the GUI; `DEEPSEEK_API_KEY` override |
| ✅ Account / balance panel | ❌ | No account surface |
| ✅ Provider list / model discovery | 🟡 | Adapter discovery runs on boot; no picker UI |
| ✅ Permission, theme, font, language settings | 🟡 | Permission via `/permission`; the rest via env vars/`$DSH_HOME` config |
| ✅ Plugin manager / marketplace | ❌ | Use `dsh plugin --profile dsh-cli add <pkg>` from a shell |
| ✅ MCP server management | ❌ | The CLI profile does not mount `mcp-client` |

## Workspace and host surface

| Web / Desktop | CLI | Notes |
|---|---|---|
| ✅ File tree / file preview | ❌ | The terminal is the workspace |
| ✅ Git changes panel | ❌ | Use git in the shell (tools can run it) |
| ✅ Integrated terminal panel | ❌ | The CLI *is* a terminal |
| ✅ Browser panel | ❌ | Desktop-only |
| ✅ Document preview / Office conversion | ❌ | Office skills still work through tools |
| ✅ Voice input | ❌ | Desktop/Web only |
| ✅ Session trajectory / outline / stats / log download | 🟡 | `/export` writes the current run as markdown; no trajectory viewer |
| ✅ Multiple tabs / concurrent sessions | 🟡 | Run several `deepseek` processes (each owns one session) |
| ✅ Notifications, tray, auto-update | ❌ | Desktop shell features |

## Commands and workflows that are identical

Because the CLI executes the shared `ctx.commands` registry, these behave exactly like the GUI:

- `/compact` — compact older history
- `/goal …` — set/view/pause/resume a long-running goal
- `/plan …` — enter/leave plan mode
- `/permission …` — switch the sandbox + approval preset
- `/feedback` — record session feedback
- Any command added by a third-party plugin in the profile

Run `/help` inside a session to see the live list.

## What is deliberately different

- **No GUI chrome.** No sidebar, cards, drag-and-drop, browser, or settings screens.
- **One session per process.** The Web app multiplexes many sessions in one host; the CLI keeps one live Agent (spawn
  another terminal for another conversation).
- **stdout is scriptable.** One-shot mode prints only the final answer on stdout, all progress on stderr.
- **Local paths only.** Attachments come from the filesystem (`@path`, `/image`), never from a browser upload.

## Bottom line

Roughly **four fifths of the agent-facing product is shared by construction** (tools, policies, sessions, plans, goals,
compaction, skills, subagents, workflows). The CLI adds terminal equivalents for most user-facing controls
(`/plan`, `/goal`, `/permission`, `/compact`, `/jobs`, `/todos`, `/skills`, `/image`, `/export`). What remains
Web/Desktop-only is the **visual host**: sidebar and cards, file/browser/terminal panels, diff viewer, drag-and-drop,
voice, account and plugin-management screens, and scheduled reminders (which require the Host session controller).

If you need one of those in the terminal, the practical path is a thin client over the same Host API rather than a
second implementation — that would be a separate project.
