Yichen Jiang
fe221be572
The vendored Cordis rescope (`cordis` -> `@deepseek-ai/cordis`, `@cordisjs/plugin-*` -> `@deepseek-ai/cordis-plugin-*`) collided with this branch's two added edges. Resolved by taking master's package names and keeping this branch's additions: `@deepseek-ai/dsh-agent` and `@deepseek-ai/dsh-system-prompt` peers, the `scopeChainOf` import, and the `agent/created` type-only edge. `docs/event-producer-consumer.*` is generated; regenerated after the merge rather than hand-resolved.
73 lines
3.0 KiB
TypeScript
73 lines
3.0 KiB
TypeScript
/**
|
|
* Agent-plane presentation selector: the row an agent preset carries to say
|
|
* which form of its tools the model sees.
|
|
*
|
|
* The tool registry itself stays on the host plane — the agent loop's
|
|
* scheduler, the API proxy's presenters, and every tool plugin are all its
|
|
* consumers, so it cannot move into a preset. What a preset CAN own is the
|
|
* presentation: `ctx.tools.presentAs()` declares it for the mounting SCOPE,
|
|
* which is the preset's standing mount, so the declaration covers every agent
|
|
* joined to that preset and a Code Mode preset runs beside native ones in one
|
|
* process. One row per composition, not one per session.
|
|
*
|
|
* A code mode needs a TypeScript code runtime, which is a host-plane service
|
|
* ([`dsh-code-runtime-worker`](../../code-runtime/code-runtime-worker/README.md)).
|
|
* This row therefore waits for it rather than assuming it: a preset selecting
|
|
* Code Mode against a deployment that composes no runtime fails at mount, named
|
|
* in the preset's own activation audit, instead of at the first prompt.
|
|
* @module @deepseek-ai/dsh-agent-tool-mode
|
|
*/
|
|
|
|
import type { Context } from '@deepseek-ai/cordis'
|
|
import z from '@deepseek-ai/schemastery'
|
|
import type { ToolPresentationMode } from '@deepseek-ai/dsh-tools'
|
|
// Type-only: brings the `ctx.tools` Context merge into this program.
|
|
import type {} from '@deepseek-ai/dsh-tools'
|
|
|
|
/** Cordis plugin name. */
|
|
export const name = 'tool-mode'
|
|
|
|
/**
|
|
* Required services. `codeRuntime` is NOT listed: a `native` row must mount in
|
|
* a deployment that composes no runtime, and the mode-dependent wait is
|
|
* declared inside {@link apply} instead.
|
|
*/
|
|
export const inject = ['tools']
|
|
|
|
/** Plugin config. */
|
|
export interface Config {
|
|
/**
|
|
* The form this agent's model sees. `native` sends every visible schema,
|
|
* `code` sends only `run_code` plus a generated SDK, `both` sends both.
|
|
* Required rather than defaulted: the deployment default is what a preset
|
|
* without this row already gets, so an omitted value would mean the row was
|
|
* composed for nothing.
|
|
*/
|
|
mode: ToolPresentationMode
|
|
}
|
|
|
|
/** Runtime schema. */
|
|
export const Config: z<Config> = z.object({
|
|
mode: z.union(['native', 'code', 'both'] as const).required(),
|
|
})
|
|
|
|
/**
|
|
* Declare the tool presentation for every agent this composition covers.
|
|
* @param ctx - the mounting composition's scope context (a preset's standing scope).
|
|
* @param config - the selected presentation.
|
|
*/
|
|
export function apply(ctx: Context, config: Config): void {
|
|
// `presentAs` is itself the effect — it registers through the calling
|
|
// context and hands back that exact disposer — so the declaration unwinds
|
|
// with this row without a second wrapper owning it.
|
|
if (config.mode === 'native') {
|
|
ctx.tools.presentAs('native')
|
|
return
|
|
}
|
|
// The wait is the loud failure: an entry still pending on `codeRuntime` is
|
|
// what `dsh-agent-presets` reports as an unusable row, naming this id.
|
|
ctx.inject(['codeRuntime'], (runtimeCtx: Context) => {
|
|
runtimeCtx.tools.presentAs(config.mode)
|
|
})
|
|
}
|