blue (blue)

1. 安装并启动 DeepSeek Harness：npx @deepseek-ai/dsh web
2. 在终端执行上面的安装命令（CLI 会解析插件并核验来源）
3. 用 dsh plugins list 确认已安装，必要时重启 Harness 生效

插件以当前 dsh 进程的权限运行，安装时可能执行代码。请先通读仓库源码与许可证，确认无破坏性命令与越权访问；本站只做索引，不对第三方插件安全性作担保。

事实信息来自公开插件目录快照（2026-10-01），介绍文案由本站再加工。

以下为插件仓库 README 全文（原始内容，由公开目录抓取整理）。

# Blue

[![CI](https://github.com/dsh-blue/blue/actions/workflows/ci.yml/badge.svg)](https://github.com/dsh-blue/blue/actions/workflows/ci.yml)
[![Node](https://img.shields.io/badge/node-%5E22.19%20%7C%7C%20%3E%3D24-339933)](#usage)
[![pnpm](https://img.shields.io/badge/pnpm-11-F69220)](#usage)
[![License: MIT](https://img.shields.io/badge/license-MIT-blue)](LICENSE)
[![Docs](https://img.shields.io/badge/docs-dsh--blue.dev-8B5CF6)](https://dsh-blue.dev/en/)
[![Chat](https://img.shields.io/badge/chat-Feishu%20group-3370FF)](https://github.com/dsh-blue/blue/issues/106)

English | [中文](README.zh.md)

Blue is an interactive terminal UI for
[DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) (`dsh`).
It is an out-of-tree Cordis bundle over `dsh-base`, built against Harness
`0.1.2-alpha.3`. Blue `0.2.0-alpha.1` deliberately uses the same plugin
model as dsh Web: plugins are ordinary Cordis siblings and consume native dsh
services directly.

Blue renders Markdown tables, closed Mermaid fences in assistant messages,
and renderer-neutral line, point, bar, sparkline, and heatmap nodes directly in
the terminal, with width-safe source or text fallbacks.

  [图片: Blue demo: streaming transcript, tool cards, and panes]

## Plugin model

A plugin declares the services it needs with `inject`, then uses them from its
Cordis context:

- `ctx.commands`, `ctx.sessionProjections`, `ctx.tools`, and the rest of
  the documented dsh services are used directly.
- `ctx.bluePanes`, `ctx.blueStatus`, `ctx.blueOverlays`, and
  `ctx.blueEditorExtensions` are the only Blue-specific UI contribution
  services.
- `ctx.blueCurrentAgent.current()` returns the exact Agent selected by this
  Blue frontend when an Agent-scoped native service needs it.
- Every registration belongs to the caller's Cordis Fiber. Unloading the
  plugin removes its commands and UI contributions.

There is no Blue plugin manifest, capability negotiation, adapter facade,
private plugin realm, or separate plugin-author CLI. Blue's own features and
external plugins register through the same services.

Plugins always return ordinary renderer-neutral nodes. Blue automatically
windows large `list` nodes and delays hidden responsive branches, so plugins
do not manage viewport ranges, overscan, renderer caches, or scroll
controllers. Plugins still own database and network fetching.

```ts
import type { Context } from '@deepseek-ai/cordis'
import type {} from '@deepseek-ai/dsh-commands'
import type {} from '@dsh-blue/blue-api'
import { ui } from '@dsh-blue/blue-ui'

export const name = '@acme/build-health'
export const inject = ['commands', 'bluePanes']

export function apply(ctx: Context): void {
  ctx.commands.register({
    name: 'health',
    description: 'Show build health',
    handler: () => ({ kind: 'success', text: 'healthy' }),
  })
  ctx.bluePanes.register({
    id: 'acme.build-health',
    placement: 'right',
    narrow: 'bottom',
    render: () => ui.text('healthy'),
  })
}
```

## Usage

Prerequisites are Node `^22.19 || >=24` and pnpm 11.

```sh
npm i -g @deepseek-ai/dsh
dsh plugin --profile blue add @dsh-blue/blue@alpha
dsh --profile blue
```

Or install the standalone launcher, which includes the tested dsh runtime:

```sh
npm i -g @dsh-blue/blue-cli@alpha
blue
```

Set `DEEPSEEK_API_KEY` before first run. `/help` lists the active commands
and key bindings.

## Architecture

```mermaid
flowchart TB
    ROOT["one dsh process · one Cordis service graph"]
    DSH["native dsh services
commands · sessionProjections · tools · agents"]
    PLUGIN["ordinary Cordis plugins
official Blue rows and external siblings"]
    AGENT["blueCurrentAgent
exact selected Agent"]
    UI["direct Blue UI services
bluePanes · blueStatus
blueOverlays · blueEditorExtensions"]
    CORE["blue-core renderer
only pi-tui and raw-terminal owner"]
    TERM["terminal"]

    ROOT --> DSH
    ROOT --> PLUGIN
    DSH --> PLUGIN
    AGENT --> PLUGIN
    PLUGIN --> UI
    UI --> CORE
    CORE --> TERM
```

Only `packages/core` imports pi-tui or owns raw terminal behavior. The API and
UI packages define renderer-neutral nodes and direct registries. App selects
the current Agent and coordinates startup, while transcript and interaction
consume native dsh services and publish UI contributions.

See [the architecture](docs/blue-architecture.md), [the service seams](docs/blue-seams.md),
and the [developer manual](https://dsh-blue.dev/en/plugins/).

## Community

Questions, feedback, or feature ideas? Join the official Blue group on Feishu (primarily Chinese). Invite links expire every 7 days — grab the current one from the latest comment of the pinned [group issue](https://github.com/dsh-blue/blue/issues/106). Bug reports still belong in [issues](https://github.com/dsh-blue/blue/issues).

## License

[MIT](LICENSE).