mirror of
https://github.com/deepseek-ai/deepseek-harness
synced 2026-08-15 21:04:50 +00:00
103 lines
5.3 KiB
TypeScript
103 lines
5.3 KiB
TypeScript
/**
|
|
* The ACP server app: the default agent spine ({@link
|
|
* @deepseek-ai/dsh-agent-core}) plus the coupled front-door cluster an ACP
|
|
* server needs — JSONL session persistence and the {@link @deepseek-ai/dsh-acp}
|
|
* bridge, and DELIBERATELY NOTHING that writes to stdout.
|
|
*
|
|
* The cluster is the OPPOSITE of {@link @deepseek-ai/dsh-stdio-agent}'s, and
|
|
* baking it in is the whole point: an ACP server speaks JSON-RPC on stdout, so
|
|
* a stray console logger would corrupt the protocol frames (the [stdout-purity
|
|
* footgun]). This package contains NO console-logger entry, NO `hmr` (the editor
|
|
* owns the subprocess), and pre-creates NO agents (ACP `session/new` creates
|
|
* them on demand) — so the default front door has no logger entry to get wrong.
|
|
* (A leaf `cordis.yml` could still add a sibling `@cordisjs/plugin-logger-console`,
|
|
* which this app does not prevent — so the rule "never add a stdout logger to an
|
|
* ACP leaf" still stands; the app just gives the leaf nothing to misconfigure.)
|
|
*
|
|
* The leaf supplies the swappable backends: the LLM adapter (`llm-deepseek` for
|
|
* the real model, `llm-replay` for keyless snapshot replay), the bash executor
|
|
* (`bash-local`), and any optional product tools it wants to expose. This app's
|
|
* {@link Config} (model, system prompt, persistence root) routes each value to
|
|
* where it is wired — model/prompt onto the bridge's per-session agent
|
|
* template, the root onto the JSONL backend.
|
|
*
|
|
* Plugin export shape: named `name`/`Config`/`apply`, NO default export — the
|
|
* cordis Loader's `unwrapExports` does `exports.default ?? exports`, so a stray
|
|
* default would collapse the module to the bare `apply` and drop the `Config`
|
|
* namespace (see docs/postmortem/0001 — the exact bug that shipped here once).
|
|
* The keyless ACP snapshot/Loader-path tests guard this end-to-end.
|
|
*
|
|
* @module @deepseek-ai/dsh-acp-agent
|
|
*/
|
|
|
|
import type { Context } from 'cordis'
|
|
import z from 'schemastery'
|
|
import * as acp from '@deepseek-ai/dsh-acp'
|
|
import * as agentCore from '@deepseek-ai/dsh-agent-core'
|
|
import ToolRegistry, { type Config as ToolsConfig } from '@deepseek-ai/dsh-tools'
|
|
import SessionPersistenceJsonl from '@deepseek-ai/dsh-session-persistence-jsonl'
|
|
import UserInteractionService from '@deepseek-ai/dsh-user-interaction'
|
|
|
|
export const name = 'acp-agent'
|
|
|
|
/**
|
|
* App config: the swappable per-deployment values. `model` configures the
|
|
* agent template the ACP bridge creates each session's agent from (NOT a
|
|
* pre-created agent — ACP creates agents at `session/new`); `persona` is the
|
|
* deployment persona (forwarded to the system-prompt plugin); `toolOrder` is
|
|
* the explicit model-facing tool order (forwarded to the system-prompt plugin);
|
|
* `tools` is the tool registry's config (its presentation `mode`, forwarded
|
|
* through agent-core); `persistenceRoot` is the JSONL backend's directory.
|
|
*/
|
|
export interface Config {
|
|
/** Model name for ACP-created agents (must have a registered adapter). */
|
|
model: string
|
|
/** Deployment persona (the system-prompt plugin's `persona` config). */
|
|
persona?: string
|
|
/** Explicit model-facing tool order (the system-prompt plugin's `toolOrder` config; see dsh-system-prompt). */
|
|
toolOrder?: string[]
|
|
/** Tool-registry config — its presentation `mode` (forwarded through agent-core; see dsh-tools). */
|
|
tools?: ToolsConfig
|
|
/** Directory the JSONL session backend writes under. Defaults to `./.sessions`. */
|
|
persistenceRoot?: string
|
|
/** Skill registry, local-provider, and model-facing consumer config forwarded to agent-core. */
|
|
skills?: agentCore.SkillConfig
|
|
}
|
|
|
|
// Each front door owns a complete, directly readable config schema; extracting
|
|
// the common fields would make two small app contracts depend on a new facade.
|
|
/* jscpd:ignore-start */
|
|
export const Config: z<Config> = z.object({
|
|
model: z.string().required(),
|
|
persona: z.string(),
|
|
// The array default is forced to undefined: ABSENT means "lexicographic
|
|
// order" (the owning dsh-system-prompt schema does the same), while
|
|
// schemastery's native [] default would read as an invalid configured list.
|
|
toolOrder: z.array(z.string()).default(undefined as unknown as string[]),
|
|
tools: ToolRegistry.Config,
|
|
// TODO(single-default-literal): share this schema default and the defensive
|
|
// apply() fallback through one named constant while retaining both boundaries.
|
|
persistenceRoot: z.string().default('./.sessions'),
|
|
skills: agentCore.SkillConfigSchema,
|
|
})
|
|
/* jscpd:ignore-end */
|
|
|
|
/**
|
|
* Compose the spine with the ACP front door. The agent-core bundle pre-creates
|
|
* NO agents (its `agents` list defaults to `[]`) and carries the deployment
|
|
* `persona`; the JSONL backend persists under `persistenceRoot`; the ACP
|
|
* bridge owns stdout for JSON-RPC and creates one agent per `session/new`
|
|
* from `model`. No logger, no `hmr` — stdout stays pure.
|
|
*/
|
|
export function apply(ctx: Context, config: Config): void {
|
|
ctx.plugin(agentCore, {
|
|
...config.persona !== undefined ? { persona: config.persona } : {},
|
|
...config.toolOrder !== undefined ? { toolOrder: config.toolOrder } : {},
|
|
...config.tools !== undefined ? { tools: config.tools } : {},
|
|
...config.skills !== undefined ? { skills: config.skills } : {},
|
|
})
|
|
ctx.plugin(UserInteractionService)
|
|
ctx.plugin(SessionPersistenceJsonl, { root: config.persistenceRoot ?? './.sessions' })
|
|
ctx.plugin(acp, { model: config.model })
|
|
}
|