2026-07-09 16:07:58 +08:00
|
|
|
|
# 第一个插件
|
|
|
|
|
|
|
2026-07-15 18:08:28 +08:00
|
|
|
|
[English](index.md) | 中文
|
|
|
|
|
|
|
2026-08-12 10:59:06 +08:00
|
|
|
|
本教程会创建一个最小的 Harness 插件,并将其加载到 Web UI 中。请从已完成[从源码运行路径](../../../../README.md#run-from-source)的仓库检出开始。
|
2026-08-05 12:46:38 +08:00
|
|
|
|
|
|
|
|
|
|
## 创建本地项目
|
|
|
|
|
|
|
|
|
|
|
|
在仓库根目录创建本教程使用的临时项目:
|
|
|
|
|
|
|
|
|
|
|
|
```sh
|
|
|
|
|
|
mkdir -p scratch-plugin/src
|
|
|
|
|
|
```
|
2026-07-09 16:07:58 +08:00
|
|
|
|
|
|
|
|
|
|
## 插件是什么
|
|
|
|
|
|
|
|
|
|
|
|
在 Harness 中,插件是一个导出 `apply` 函数的 TypeScript 模块。框架在加载时调用 `apply`,传入一个 `ctx`(上下文对象),你通过 `ctx` 注册能力:
|
|
|
|
|
|
|
2026-07-15 18:08:28 +08:00
|
|
|
|
```ts
|
build(vendor): rescope the vendored Cordis packages into @deepseek-ai
Machine-produced by `pnpm run rescope-vendor --apply` plus the regeneration it
prints: `pnpm install` for the lockfile, `pnpm run gen-third-party-notices`,
`verify-translation-pairing --write` for the touched bilingual pairs,
`gen-doc-graphs`, and one typert snapshot whose ids embed character offsets.
`pnpm run rescope-vendor --check` verifies the result.
Renames nine vendored packages (cordis, cosmokit, schemastery and the six
@cordisjs plugins) and every reference that resolves them: manifest names and
dependency keys, module specifiers including declare-module merges, cordis.yml
plugin names, tsconfig paths, every Markdown fence, and `docs/` prose.
Directory names, upstream versions, and dependency ranges are unchanged, so
vendor/README.md still reads as an upstream snapshot; its manifest table gains
an upstream-name column so THIRD_PARTY_NOTICES keeps MIT attribution pointed
at each fork's origin.
The tutorial tier follows the rename end to end: its yaml fences named plugins
the Loader can no longer resolve, its `ts ignore-check` fences disagreed with
the compiled fences beside them, and its prose quoted both. The contracts that
told readers to keep upstream names — the root convention and the vendoring
cookbook's tree comment and manifest invariant — now say to rescope instead.
Two rules read `@deepseek-ai/` as "another workspace plugin": the client bundle
purity gate now names the vendored libraries a browser bundle inlines, and the
files where a bare `cordis` is an agent-preset id keep that product data.
2026-08-10 22:04:06 +08:00
|
|
|
|
import type { Context } from '@deepseek-ai/cordis'
|
2026-07-09 16:07:58 +08:00
|
|
|
|
|
|
|
|
|
|
export const name = 'my-plugin'
|
|
|
|
|
|
|
|
|
|
|
|
export function apply(ctx: Context) {
|
2026-07-15 18:08:28 +08:00
|
|
|
|
// Register capabilities here.
|
2026-07-09 16:07:58 +08:00
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
2026-08-09 15:27:21 +08:00
|
|
|
|
这就是完整配置。
|
2026-07-09 16:07:58 +08:00
|
|
|
|
|
|
|
|
|
|
## 创建插件文件
|
|
|
|
|
|
|
2026-08-05 12:46:38 +08:00
|
|
|
|
创建 `scratch-plugin/src/my-plugin.ts`:
|
2026-07-09 16:07:58 +08:00
|
|
|
|
|
2026-07-15 18:08:28 +08:00
|
|
|
|
```ts
|
build(vendor): rescope the vendored Cordis packages into @deepseek-ai
Machine-produced by `pnpm run rescope-vendor --apply` plus the regeneration it
prints: `pnpm install` for the lockfile, `pnpm run gen-third-party-notices`,
`verify-translation-pairing --write` for the touched bilingual pairs,
`gen-doc-graphs`, and one typert snapshot whose ids embed character offsets.
`pnpm run rescope-vendor --check` verifies the result.
Renames nine vendored packages (cordis, cosmokit, schemastery and the six
@cordisjs plugins) and every reference that resolves them: manifest names and
dependency keys, module specifiers including declare-module merges, cordis.yml
plugin names, tsconfig paths, every Markdown fence, and `docs/` prose.
Directory names, upstream versions, and dependency ranges are unchanged, so
vendor/README.md still reads as an upstream snapshot; its manifest table gains
an upstream-name column so THIRD_PARTY_NOTICES keeps MIT attribution pointed
at each fork's origin.
The tutorial tier follows the rename end to end: its yaml fences named plugins
the Loader can no longer resolve, its `ts ignore-check` fences disagreed with
the compiled fences beside them, and its prose quoted both. The contracts that
told readers to keep upstream names — the root convention and the vendoring
cookbook's tree comment and manifest invariant — now say to rescope instead.
Two rules read `@deepseek-ai/` as "another workspace plugin": the client bundle
purity gate now names the vendored libraries a browser bundle inlines, and the
files where a bare `cordis` is an agent-preset id keep that product data.
2026-08-10 22:04:06 +08:00
|
|
|
|
import type { Context } from '@deepseek-ai/cordis'
|
2026-07-09 16:07:58 +08:00
|
|
|
|
|
|
|
|
|
|
export const name = 'hello-plugin'
|
|
|
|
|
|
|
|
|
|
|
|
export function apply(ctx: Context) {
|
2026-07-15 18:08:28 +08:00
|
|
|
|
// Required dependencies are ready before apply runs.
|
|
|
|
|
|
console.log('[hello-plugin] plugin loaded!')
|
2026-07-09 16:07:58 +08:00
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
## 注册到 cordis.yml
|
|
|
|
|
|
|
2026-08-05 12:46:38 +08:00
|
|
|
|
创建 `scratch-plugin/cordis.yml`,作为插入本地插件的 Web 覆盖层:
|
2026-07-09 16:07:58 +08:00
|
|
|
|
|
|
|
|
|
|
```yaml
|
2026-08-05 12:46:38 +08:00
|
|
|
|
- insert:
|
|
|
|
|
|
- id: hello
|
|
|
|
|
|
name: './src/my-plugin.ts'
|
2026-07-09 16:07:58 +08:00
|
|
|
|
```
|
|
|
|
|
|
|
2026-08-05 12:46:38 +08:00
|
|
|
|
使用该覆盖层启动 Web UI:
|
|
|
|
|
|
|
|
|
|
|
|
```sh
|
2026-08-10 16:01:12 +08:00
|
|
|
|
pnpm dsh web --patch ./scratch-plugin/cordis.yml
|
2026-08-05 12:46:38 +08:00
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
打开 `http://127.0.0.1:3080`。启动期间,终端会打印 `[hello-plugin] plugin loaded!`。
|
2026-07-09 16:07:58 +08:00
|
|
|
|
|
|
|
|
|
|
## 自动清理
|
|
|
|
|
|
|
2026-08-04 17:36:14 +08:00
|
|
|
|
通过 `ctx` 注册的任何东西——事件监听、工具、定时器——在插件卸载时都会被自动清理。你不需要手动 removeListener 或 clearInterval。
|
2026-07-09 16:07:58 +08:00
|
|
|
|
|
|
|
|
|
|
如果你有需要手动清理的资源(比如一个网络连接),用 `ctx.effect()` 告诉框架怎么清理:
|
|
|
|
|
|
|
2026-07-15 18:08:28 +08:00
|
|
|
|
```ts
|
build(vendor): rescope the vendored Cordis packages into @deepseek-ai
Machine-produced by `pnpm run rescope-vendor --apply` plus the regeneration it
prints: `pnpm install` for the lockfile, `pnpm run gen-third-party-notices`,
`verify-translation-pairing --write` for the touched bilingual pairs,
`gen-doc-graphs`, and one typert snapshot whose ids embed character offsets.
`pnpm run rescope-vendor --check` verifies the result.
Renames nine vendored packages (cordis, cosmokit, schemastery and the six
@cordisjs plugins) and every reference that resolves them: manifest names and
dependency keys, module specifiers including declare-module merges, cordis.yml
plugin names, tsconfig paths, every Markdown fence, and `docs/` prose.
Directory names, upstream versions, and dependency ranges are unchanged, so
vendor/README.md still reads as an upstream snapshot; its manifest table gains
an upstream-name column so THIRD_PARTY_NOTICES keeps MIT attribution pointed
at each fork's origin.
The tutorial tier follows the rename end to end: its yaml fences named plugins
the Loader can no longer resolve, its `ts ignore-check` fences disagreed with
the compiled fences beside them, and its prose quoted both. The contracts that
told readers to keep upstream names — the root convention and the vendoring
cookbook's tree comment and manifest invariant — now say to rescope instead.
Two rules read `@deepseek-ai/` as "another workspace plugin": the client bundle
purity gate now names the vendored libraries a browser bundle inlines, and the
files where a bare `cordis` is an agent-preset id keep that product data.
2026-08-10 22:04:06 +08:00
|
|
|
|
import type { Context } from '@deepseek-ai/cordis'
|
2026-07-15 18:08:28 +08:00
|
|
|
|
|
2026-07-09 16:07:58 +08:00
|
|
|
|
export function apply(ctx: Context) {
|
|
|
|
|
|
ctx.effect(() => {
|
|
|
|
|
|
const timer = setInterval(() => {
|
|
|
|
|
|
console.log('heartbeat')
|
|
|
|
|
|
}, 5000)
|
|
|
|
|
|
|
2026-07-15 18:08:28 +08:00
|
|
|
|
// The returned function runs when the plugin unloads.
|
2026-07-09 16:07:58 +08:00
|
|
|
|
return () => clearInterval(timer)
|
|
|
|
|
|
})
|
|
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
## 声明依赖
|
|
|
|
|
|
|
|
|
|
|
|
如果你的插件需要使用其他服务(如 `tools`、`llm`),需要声明 `inject`:
|
|
|
|
|
|
|
2026-07-15 18:08:28 +08:00
|
|
|
|
```ts ignore-check
|
build(vendor): rescope the vendored Cordis packages into @deepseek-ai
Machine-produced by `pnpm run rescope-vendor --apply` plus the regeneration it
prints: `pnpm install` for the lockfile, `pnpm run gen-third-party-notices`,
`verify-translation-pairing --write` for the touched bilingual pairs,
`gen-doc-graphs`, and one typert snapshot whose ids embed character offsets.
`pnpm run rescope-vendor --check` verifies the result.
Renames nine vendored packages (cordis, cosmokit, schemastery and the six
@cordisjs plugins) and every reference that resolves them: manifest names and
dependency keys, module specifiers including declare-module merges, cordis.yml
plugin names, tsconfig paths, every Markdown fence, and `docs/` prose.
Directory names, upstream versions, and dependency ranges are unchanged, so
vendor/README.md still reads as an upstream snapshot; its manifest table gains
an upstream-name column so THIRD_PARTY_NOTICES keeps MIT attribution pointed
at each fork's origin.
The tutorial tier follows the rename end to end: its yaml fences named plugins
the Loader can no longer resolve, its `ts ignore-check` fences disagreed with
the compiled fences beside them, and its prose quoted both. The contracts that
told readers to keep upstream names — the root convention and the vendoring
cookbook's tree comment and manifest invariant — now say to rescope instead.
Two rules read `@deepseek-ai/` as "another workspace plugin": the client bundle
purity gate now names the vendored libraries a browser bundle inlines, and the
files where a bare `cordis` is an agent-preset id keep that product data.
2026-08-10 22:04:06 +08:00
|
|
|
|
import type { Context } from '@deepseek-ai/cordis'
|
2026-07-15 18:08:28 +08:00
|
|
|
|
|
2026-07-09 16:07:58 +08:00
|
|
|
|
export const name = 'my-tool-plugin'
|
|
|
|
|
|
export const inject = ['tools']
|
|
|
|
|
|
|
|
|
|
|
|
export function apply(ctx: Context) {
|
2026-07-15 18:08:28 +08:00
|
|
|
|
// ctx.tools is ready here.
|
2026-07-09 16:07:58 +08:00
|
|
|
|
ctx.tools.register(/* ... */)
|
|
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
框架会确保依赖的服务就绪后才加载你的插件。
|
|
|
|
|
|
|
|
|
|
|
|
## 插件的三种形态
|
|
|
|
|
|
|
|
|
|
|
|
除了函数形式,插件还支持对象形式和类形式:
|
|
|
|
|
|
|
|
|
|
|
|
### 对象形式
|
|
|
|
|
|
|
2026-07-15 18:08:28 +08:00
|
|
|
|
```ts
|
build(vendor): rescope the vendored Cordis packages into @deepseek-ai
Machine-produced by `pnpm run rescope-vendor --apply` plus the regeneration it
prints: `pnpm install` for the lockfile, `pnpm run gen-third-party-notices`,
`verify-translation-pairing --write` for the touched bilingual pairs,
`gen-doc-graphs`, and one typert snapshot whose ids embed character offsets.
`pnpm run rescope-vendor --check` verifies the result.
Renames nine vendored packages (cordis, cosmokit, schemastery and the six
@cordisjs plugins) and every reference that resolves them: manifest names and
dependency keys, module specifiers including declare-module merges, cordis.yml
plugin names, tsconfig paths, every Markdown fence, and `docs/` prose.
Directory names, upstream versions, and dependency ranges are unchanged, so
vendor/README.md still reads as an upstream snapshot; its manifest table gains
an upstream-name column so THIRD_PARTY_NOTICES keeps MIT attribution pointed
at each fork's origin.
The tutorial tier follows the rename end to end: its yaml fences named plugins
the Loader can no longer resolve, its `ts ignore-check` fences disagreed with
the compiled fences beside them, and its prose quoted both. The contracts that
told readers to keep upstream names — the root convention and the vendoring
cookbook's tree comment and manifest invariant — now say to rescope instead.
Two rules read `@deepseek-ai/` as "another workspace plugin": the client bundle
purity gate now names the vendored libraries a browser bundle inlines, and the
files where a bare `cordis` is an agent-preset id keep that product data.
2026-08-10 22:04:06 +08:00
|
|
|
|
import type { Context } from '@deepseek-ai/cordis'
|
2026-07-15 18:08:28 +08:00
|
|
|
|
|
2026-07-09 16:07:58 +08:00
|
|
|
|
export default {
|
|
|
|
|
|
name: 'my-plugin',
|
|
|
|
|
|
inject: ['tools'],
|
|
|
|
|
|
apply(ctx: Context) {
|
|
|
|
|
|
// ...
|
|
|
|
|
|
},
|
|
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
### 类形式
|
|
|
|
|
|
|
2026-07-15 18:08:28 +08:00
|
|
|
|
```ts
|
build(vendor): rescope the vendored Cordis packages into @deepseek-ai
Machine-produced by `pnpm run rescope-vendor --apply` plus the regeneration it
prints: `pnpm install` for the lockfile, `pnpm run gen-third-party-notices`,
`verify-translation-pairing --write` for the touched bilingual pairs,
`gen-doc-graphs`, and one typert snapshot whose ids embed character offsets.
`pnpm run rescope-vendor --check` verifies the result.
Renames nine vendored packages (cordis, cosmokit, schemastery and the six
@cordisjs plugins) and every reference that resolves them: manifest names and
dependency keys, module specifiers including declare-module merges, cordis.yml
plugin names, tsconfig paths, every Markdown fence, and `docs/` prose.
Directory names, upstream versions, and dependency ranges are unchanged, so
vendor/README.md still reads as an upstream snapshot; its manifest table gains
an upstream-name column so THIRD_PARTY_NOTICES keeps MIT attribution pointed
at each fork's origin.
The tutorial tier follows the rename end to end: its yaml fences named plugins
the Loader can no longer resolve, its `ts ignore-check` fences disagreed with
the compiled fences beside them, and its prose quoted both. The contracts that
told readers to keep upstream names — the root convention and the vendoring
cookbook's tree comment and manifest invariant — now say to rescope instead.
Two rules read `@deepseek-ai/` as "another workspace plugin": the client bundle
purity gate now names the vendored libraries a browser bundle inlines, and the
files where a bare `cordis` is an agent-preset id keep that product data.
2026-08-10 22:04:06 +08:00
|
|
|
|
import { Service, type Context } from '@deepseek-ai/cordis'
|
2026-07-09 16:07:58 +08:00
|
|
|
|
|
|
|
|
|
|
export default class MyService extends Service {
|
|
|
|
|
|
static inject = ['tools']
|
|
|
|
|
|
|
|
|
|
|
|
constructor(ctx: Context) {
|
|
|
|
|
|
super(ctx, 'myService')
|
2026-07-15 18:08:28 +08:00
|
|
|
|
// Perform synchronous initialization in the constructor.
|
2026-07-09 16:07:58 +08:00
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
2026-08-04 17:36:14 +08:00
|
|
|
|
大多数情况下,函数形式足够了。当插件需要向其他插件提供服务时,可使用类形式(见 [服务与依赖](../framework/service.md))。
|
2026-07-09 16:07:58 +08:00
|
|
|
|
|
|
|
|
|
|
## 下一步
|
|
|
|
|
|
|
2026-08-12 12:30:19 +08:00
|
|
|
|
- [开发一个工具](./tool.md) — 了解工具定义 DSL
|
2026-07-13 15:38:47 +08:00
|
|
|
|
- [插件配置](./config.md) — 让插件接受用户配置
|
2026-08-12 13:52:27 +08:00
|
|
|
|
- [Cordis 框架教程](../../../cordis-tutorial/index.md) — 底层的插件框架,在临时目录中动手构建,无需 API 密钥
|