Files
deepseek-harness/docs/cordis-catalog/events.md
Tianyi Cui 56e34619d7 Merge remote-tracking branch 'origin/master' into codex/pr224-rfc-rewrite
# Conflicts:
#	docs/architecture.md
#	docs/capability-seams.md
#	docs/config-catalog.md
#	docs/cookbook/extension-cookbook.md
#	docs/cordis-catalog/events.md
#	docs/cordis-catalog/services.md
#	docs/event-producer-consumer.md
#	docs/module-graph.md
#	docs/rfc/implemented/feature/2026-06-30-interception-seams.md
#	docs/rfc/proposed/feature/2026-06-14-acp-agent-client-protocol.md
#	docs/tool-execution-pipeline.md
#	packages/cordis/tool-cordis/src/api-catalog.ts
#	packages/core/agent-core/README.md
#	packages/core/agent-loop/README.md
#	packages/core/tools/README.md
#	packages/core/tools/src/index.ts
#	packages/core/tools/tests/tools.spec.ts
#	packages/core/tools/tsconfig.json
#	packages/ui/acp/src/index.ts
#	scripts/doc-budgets.manifest.json
#	scripts/gen-cordis-catalog.ts
#	scripts/gen-doc-graphs.ts
2026-07-11 23:14:09 +08:00

36 KiB

Cordis Events Catalog

Every cordis event a plugin can listen to: exact signature, dispatch mode, and the declaration's JSDoc. This is one axis of the wiring reference a plugin author works against — the callable ctx.<key> surface is the sibling services catalog, and core-data-structures/ catalogs the data structures these signatures move around.

This file is GENERATED from source (scripts/gen-cordis-catalog.ts) and verified fresh by pnpm run verify-cordis-catalog (part of doc-sync) — do not edit it by hand. Signature blocks use a ts cordis-catalog fence (skipped by doc-typecheck, since a bare signature is not standalone-compilable). Type names in a signature link to the page that documents them.

The harness tier below (the @deepseek-ai/dsh-* packages) is the vocabulary this repo owns, grouped by scope. The inherited tier at the end is the cordis-core + loader/hmr/timer event surface a plugin also sees — pinned vendor source, summarized tersely.

Dispatch modes: emit (fire-and-forget), waterfall (each listener gets next() and may transform or veto — see waterfall semantics), parallel (awaited fan-out; all listeners run), serial (awaited in registration order until one returns a bail value — anything other than null, false, or undefined).

agent/*

agent/created — emit

An agent's fully composed scoped world was published in the AgentRegistry. Its session is already live in the session store, but concrete factories may keep driving verbs locked until the subsequent agent/session-start boundary; that event is the first supported place to inject or queue work during startup.

'agent/created'(this: Scoped<Agent>, agent: Agent): void

Types: Agent

Source: packages/core/agent/src/types.ts:298

agent/disposed — emit

An agent was removed from the registry after its driver and any in-flight turn reached quiescence. Ordered teardown may still be detaching the session and unwinding the agent's scoped registrations when this notification runs.

'agent/disposed'(this: Scoped<Agent>, agent: Agent): void

Types: Agent

Source: packages/core/agent/src/types.ts:312

agent/error — emit

A step or turn errored. The loop reports a failure here (plus the logger) even when the error has no in-turn position for a session error event.

'agent/error'(this: Scoped<Agent>, agent: Agent, turn: number, step: number, error: Error): void

Types: Agent

Source: packages/core/agent/src/types.ts:585

agent/pre-step — serial

Awaited pre-step surface-mutation checkpoint, fired once per step AFTER turn/start (and after the prior step closed) but BEFORE this step's step/start — so anything a listener appends lands OUTSIDE the step, between turn/start/step/end and the upcoming step/start. step is the number of the step about to start. The loop awaits ctx.serial('agent/pre-step', …) after assembling the system prompt, then opens the step and derives the request history ONCE from whatever the surface now holds. This is where compaction belongs: it mutates the session surface in place (shadowing an older range with a summary node) with its log-only compact/* records cleanly outside any step, and the single subsequent derive reflects the mutation — so there is no double-derive and no listener can see (or be expected to act on) an assembled messages array that does not exist yet.

Serial (awaited in registration order), not a waterfall: a listener mutates the surface as a side effect; there is nothing to transform, but the loop must wait for the mutation to complete before opening the step and deriving. Cordis serial bails early if a listener returns a bail value; this event is typed and documented as void, so listeners must not return a semantic veto value. fullSystemPrompt is the assembled prompt a listener needs to measure pressure (the system prompt counts toward the budget), and sessionPrefix is the instance's composed agent/session-prefix product for the same reason — every request carries it in front of the derived history, and it is composed BEFORE this seam fires precisely so a pressure gate counts the prefix the request will actually send (never a stale logged one). signal cancels any in-flight work a listener starts (e.g. a summarization model call). Scope-filtered dispatch (@deepseek-ai/dsh-scope): a listener registered through agent.ctx fires only for that agent's dispatches; a listener on a plain plugin context fires for every agent. The dispatch this is the scope carrier (Scoped<Agent>), built by the emitting side via scopeTarget/agentEvents.

'agent/pre-step'(this: Scoped<Agent>, agent: Agent, turn: number, step: number, fullSystemPrompt: string, sessionPrefix: readonly Message[], signal: AbortSignal): Promise<void> | void

Types: Agent · Message

Source: packages/core/agent/src/types.ts:417

agent/prompt-submit — waterfall

Waterfall: decide what happens to ONE drained queued message before it becomes a user/message — allow (optionally rewriting the prompt bytes or attaching additionalContext) or block it. Fires inside the already-open turn, per drained message. Maps onto Claude Code's UserPromptSubmit hook. Call next() to delegate to the default (allow unchanged), or return a PromptDecision without calling next() to short-circuit.

'agent/prompt-submit'(this: Scoped<Agent>, agent: Agent, content: ContentBlock[], source: MessageSource, next: () => Promise<PromptDecision>): Promise<PromptDecision>

Types: Agent · ContentBlock · MessageSource

Source: packages/core/agent/src/types.ts:435

agent/queued — emit

A message entered the agent's inbox (queued or steering). source is the resolved source (defaults applied), not the caller's raw options.

'agent/queued'(this: Scoped<Agent>, agent: Agent, content: ContentBlock[], info: { source: MessageSource; steering: boolean }): void

Types: Agent · ContentBlock · MessageSource

Source: packages/core/agent/src/types.ts:340

agent/request — waterfall

Waterfall: shape the step's call configuration — model switching, sampling overrides — by returning a replacement LlmCallConfig (the frozen seed is the config the loop would otherwise use). Config is ALL a listener shapes here: every request is a pure function of the session log (the reconstructability RFC), so model-visible content flows through the log channels — inject(), steering, prompt-submit additionalContext, prompt sections via system-prompt/assemble, or the header-logged session prefix via agent/session-prefix — never through request mutation, and the loop records whatever config the request actually uses as a request/header* event before dispatch. The step's messages are already snapshotted when this fires (the step/start boundary): an inject() from a listener here lands in the log but joins the NEXT request. For surface mutation that must precede the snapshot (compaction), use agent/pre-step. Call next() to delegate, or return an LlmCallConfig without it to short-circuit.

'agent/request'(this: Scoped<Agent>, agent: Agent, turn: number, step: number, config: LlmCallConfig, next: () => Promise<LlmCallConfig>): Promise<LlmCallConfig>

Types: Agent · LlmCallConfig

Source: packages/core/agent/src/types.ts:464

agent/session-prefix — waterfall

Waterfall: compose the SESSION PREFIX — request-only messages placed in front of the ENTIRE derived history (directly after the provider's system slot) on every request this loop instance sends. Fired ONCE per loop instance, lazily before its first step's agent/pre-step seam — BEFORE the pre-step so a token-pressure gate (compaction) counts the prefix this instance will actually send, never a previous instance's logged one. The composed result is deep-frozen, recorded as EpochHeader.messagePrefix on the instance's anchoring 'initial'/'resume' header snapshot, and reused verbatim for every subsequent request — never recomputed mid-session, so the provider prefix cache holds by construction (a process restart or ctx.agents.resume() is a new instance: it recomposes, and any drift lands attributably on the 'resume' snapshot). Composition runs outside the step, before the boundary snapshot: a composing listener's session append joins the CURRENT request's derived history. A composition interrupted by a cancel/dispose landing inside the waterfall is discarded — never cached, logged, or sent — and the next turn recomposes under a live signal, so an abort-aware listener's degraded fallback cannot leak into later requests.

This is the home for session-stable openers the model must always see but that must NOT become durable history — a skills catalog, an AGENTS.md digest, a workspace baseline: Session.deriveMessages() never returns the prefix, and the header events are its only durable record, so the request stays reconstructable from the log. Content that CHANGES mid-session belongs in the append-only history channels instead — agent.inject(), a tools/post-execute decision's additionalContext, prompt-submit additionalContext — each a durable context/message paid once and prefix-cached thereafter.

The seed is a frozen empty list; a contributing listener returns a NEW array — never an in-place push. The canonical contribution is a PREPEND, [mine, ...await next()]: the waterfall unwinds innermost-first (the LAST-registered listener's next() resolves first), so prepending yields registration order on the wire, and every plugin using it composes deterministically. The append form [...await next(), mine] is legal but places a contribution AFTER every later-registered plugin's — reverse registration order when all contributors append. Call next() to delegate, or return a list without it to short-circuit. Scope-filtered dispatch (@deepseek-ai/dsh-scope): a listener registered through agent.ctx fires only for that agent's dispatches; a listener on a plain plugin context fires for every agent. The dispatch this is the scope carrier (Scoped<Agent>), built by the emitting side via scopeTarget/agentEvents.

'agent/session-prefix'(this: Scoped<Agent>, agent: Agent, prefix: Message[], signal: AbortSignal, next: () => Promise<Message[]>): Promise<Message[]>

Types: Agent · Message

Source: packages/core/agent/src/types.ts:516

agent/session-start — emit

The agent's session lifecycle began, fired once before its first turn. source says why (SessionStartSource: fresh startup, a resumed persisted session, …). A pure NOTIFICATION (emit, not waterfall): it carries no veto — a session-start listener that wants to seed context does so via agent.inject() (a context/message the first request sees), not by returning a decision. Cannot block the session from starting; that gap is deliberate (a bridge logs/injects, it does not gate startup).

'agent/session-start'(this: Scoped<Agent>, agent: Agent, source: SessionStartSource): void

Types: Agent

Source: packages/core/agent/src/types.ts:360

agent/status — emit

Agent status changed (idlerunning, or → disposed). Drive lifecycle off this transition, never off a status you just requested — send() does not flip status to running before it returns.

'agent/status'(this: Scoped<Agent>, agent: Agent, status: AgentStatus): void

Types: Agent

Source: packages/core/agent/src/types.ts:326

agent/step-result — waterfall

Waterfall: post-process the assembled assistant Message before tool dispatch (validation, content rewriting, …).

'agent/step-result'(this: Scoped<Agent>, agent: Agent, turn: number, step: number, message: Message, next: () => Promise<Message>): Promise<Message>

Types: Agent · Message

Source: packages/core/agent/src/types.ts:531

agent/turn-continuation — waterfall

Waterfall: override the turn-continuation decision via a typed ContinuationDecision. The loop's defaultDecision is continue when the step had tool calls or steering was injected, else stop. Listeners force-continue (/goal, /loop — optionally attaching a reason recorded as next-step steering) or force-stop (budget guards). Call next() to delegate to the default, or return a decision to override.

'agent/turn-continuation'(this: Scoped<Agent>, agent: Agent, turn: number, defaultDecision: ContinuationDecision, next: () => Promise<ContinuationDecision>): Promise<ContinuationDecision>

Types: Agent

Source: packages/core/agent/src/types.ts:549

agent/turn-stop — serial

Serial terminal-stop checkpoint after the ordinary agent/turn-continuation waterfall, any continue.reason, and the pending-steering continuation override have been folded. A listener returns { action: 'stop' } to make this turn terminal, or undefined to abstain. Terminal stop is monotonic: listener order and steering cannot resume the turn, and pending steering is discarded rather than becoming another step or turn. A malformed non-undefined result fails the turn closed.

'agent/turn-stop'(this: Scoped<Agent>, agent: Agent, turn: number): Promise<ContinuationStop | undefined> | ContinuationStop | undefined

Types: Agent

Source: packages/core/agent/src/types.ts:568

approval/*

approval/request — waterfall

Waterfall asking the composed answerers to decide one approval request. Dispatched only from ApprovalService.request — callers go through the service (which owns cancellation and the audit events), never through ctx.waterfall directly. A listener that can answer for this request's agent returns an outcome WITHOUT calling next() (the decision slot is single-occupancy, first listener to answer wins); a listener that does not recognize the agent MUST call next() so another answerer — or the fail-closed default 'unavailable' — gets the question. Throwing is contained by the service and yields 'unavailable'. Scope-filtered dispatch (@deepseek-ai/dsh-scope) keys the carrier by req.agent: a listener registered through agent.ctx receives only that agent's questions, while a plain-context listener receives every agent's.

'approval/request'(this: Scoped<ApprovalService>, req: ApprovalRequest, next: () => Promise<ApprovalOutcome>): Promise<ApprovalOutcome>

Types: ApprovalOutcome · ApprovalRequest

Source: packages/ui/user-approval/src/index.ts:69

fs/*

fs/edit-intent — waterfall

Single-slot decision: produce the optional version guard for the next FileSystem.editText. The tool dispatches this as an unbound waterfall and supplies a default thunk returning undefined (unconditional edit of the current content — the bare provider; no stat). The @deepseek-ai/dsh-fs-policy policy listener returns { version: vObserved }, or throws FS_NOT_OBSERVED if the actor is unset or has not observed the target. Does NOT call next(): one decision, first-wins (see Events.'fs/write-intent').

'fs/edit-intent'(target: FsTarget, actor: object | undefined, next: () => { version: FsVersion } | undefined | Promise<{ version: FsVersion } | undefined>): Promise<{ version: FsVersion } | undefined>

Types: FsTarget · FsVersion

Source: packages/fs/fs/src/index.ts:123

fs/observed — emit

Record that an actor observed a target at a version, after a successful read/write/edit. Fire-and-forget (plain emit). A listener MUST be a synchronous, side-effect-only recorder (@deepseek-ai/dsh-fs-policy's is a WeakMap.set): the tool does not guard the emit, so a listener that throws surfaces as the tool's isError result, and cordis emit does not await listener promises — async or fallible audit/telemetry does not belong here. No listener ⇒ nothing recorded. actor is the opaque tool-execution context.

'fs/observed'(target: FsTarget, version: FsVersion, actor: object | undefined): void

Types: FsTarget · FsVersion

Source: packages/fs/fs/src/index.ts:138

fs/write-intent — waterfall

Single-slot decision: produce the write intent for the next FileSystem.writeText. The tool dispatches this as an unbound waterfall (no this) and supplies a default thunk returning undefined (unconditional create-or-overwrite — the bare provider). The @deepseek-ai/dsh-fs-policy policy listener returns createIfAbsent (unobserved actor) or { kind: 'replaceIfVersion', version: vObserved } (observed) and does NOT call next() — one decision, not a composable chain. The slot is first-wins: the first non-next() decider (registration order, or prepend) occupies it; a second decider is a misconfiguration, not layering. actor is the opaque tool-execution context, never read here.

'fs/write-intent'(target: FsTarget, actor: object | undefined, next: () => FsWriteIntent | undefined | Promise<FsWriteIntent | undefined>): Promise<FsWriteIntent | undefined>

Types: FsTarget · FsWriteIntent

Source: packages/fs/fs/src/index.ts:109

llm/*

llm/stream — waterfall

Waterfall around every streaming model call (retry, replay, routing). Bound to the LlmService; call next() to reach the resolved adapter's stream, or yield your own chunks to short-circuit.

'llm/stream'(this: LlmService, options: GenerateOptions, next: () => AsyncIterable<StreamChunk>): AsyncIterable<StreamChunk>

Types: GenerateOptions · StreamChunk

Source: packages/llm/llm/src/index.ts:39

session/*

session/created — emit

A session was created in the store. Scope-filtered dispatch (@deepseek-ai/dsh-scope): the carrier is the session's owner scope, captured when the session was ENTERED (an agent's session is entered through agent.ctx, so its events dispatch in that agent's scope; a bare sessions.create() from a plain plugin dispatches subject-less). A listener registered through agent.ctx hears only that agent's sessions; a plain plugin listener hears every session.

'session/created'(this: Scoped<Session>, session: Session): void

Source: packages/core/session/src/index.ts:47

session/event — emit

An event was appended to a session log (sync, fire-and-forget). This is the per-append feed a UI or invariant plugin tails. Scope-filtered dispatch (@deepseek-ai/dsh-scope): the carrier is the session's owner scope, captured when the session was ENTERED (an agent's session is entered through agent.ctx, so its events dispatch in that agent's scope; a bare sessions.create() from a plain plugin dispatches subject-less). A listener registered through agent.ctx hears only that agent's sessions; a plain plugin listener hears every session.

'session/event'(this: Scoped<Session>, session: Session, event: SessionEvent): void

Types: SessionEvent

Source: packages/core/session/src/index.ts:61

session/flush — parallel

Awaited durability checkpoint. The agent loop awaits ctx.sessions.flush(session) at every turn end; persistence plugins (JSONL, SQLite) drain their write-behind buffers here and on fiber dispose. Awaited (parallel), not a waterfall: every listener runs and the caller waits for all of them, but none can veto. Dispatch it through SessionStore.flush — the store owns the carrier — never via a raw ctx.parallel. Scope-filtered dispatch (@deepseek-ai/dsh-scope): the carrier is the session's owner scope, captured when the session was ENTERED (an agent's session is entered through agent.ctx, so its events dispatch in that agent's scope; a bare sessions.create() from a plain plugin dispatches subject-less). A listener registered through agent.ctx hears only that agent's sessions; a plain plugin listener hears every session.

'session/flush'(this: Scoped<Session>, session: Session): Promise<void> | void

Source: packages/core/session/src/index.ts:79

skill/*

skill/provider-added — emit

A skill provider became resolvable in the ctx.skills registry. Consumers can observe this instead of depending on Cordis plugin load order, which is concurrent for sibling plugins.

'skill/provider-added'(provider: SkillProvider): void

Source: packages/skill/skill/src/index.ts:130

skill/provider-removed — emit

A skill provider left the registry because its plugin fiber was disposed.

'skill/provider-removed'(name: string): void

Source: packages/skill/skill/src/index.ts:136

subagent/*

subagent/end — emit

A subagent run settled — emitted when SubagentRun.result resolves (any stop reason). Paired with Events['subagent/start']. Scope-filtered dispatch (@deepseek-ai/dsh-scope): the carrier is keyed by the DELEGATING PARENT — a listener registered through the parent's agent.ctx observes only its own delegations; a plain plugin listener observes every run.

'subagent/end'(this: Scoped<SubagentService>, info: SubagentRunEndInfo): void

Source: packages/subagent/subagent/src/index.ts:109

subagent/provider-added — emit

A provider became resolvable in the SubagentService registry. Consumers that derive state from a named provider (e.g. the model-facing tool wording in dsh-tool-subagent) react HERE instead of assuming load order — the cordis Loader starts sibling plugins concurrently, so "listed earlier in cordis.yml" does not mean "registered earlier".

'subagent/provider-added'(provider: SubagentProvider): void

Source: packages/subagent/subagent/src/index.ts:75

subagent/provider-removed — emit

A provider left the registry (its plugin's fiber was disposed — an unload or an HMR reload). Consumers holding provider-derived state drop it here; a reload re-fires subagent/provider-added with the fresh provider. Delivered with per-listener containment: a throwing subscriber is logged, never starves later subscribers, and never disrupts the provider's teardown.

'subagent/provider-removed'(name: string): void

Source: packages/subagent/subagent/src/index.ts:86

subagent/start — emit

A subagent run started — emitted after the provider is resolved and its capabilities validated, as the child run begins. Paired with Events['subagent/end']. Scope-filtered dispatch (@deepseek-ai/dsh-scope): the carrier is keyed by the DELEGATING PARENT — a listener registered through the parent's agent.ctx observes only its own delegations; a plain plugin listener observes every run.

'subagent/start'(this: Scoped<SubagentService>, info: SubagentRunInfo): void

Source: packages/subagent/subagent/src/index.ts:98

system-prompt/*

system-prompt/assemble — waterfall

Waterfall around prompt assembly — mutate or extend the PromptAssembly (sections + tools + variables) before it is rendered. Bound to the SystemPrompt service; call next() to delegate.

'system-prompt/assemble'(this: Scoped<SystemPrompt>, assembly: PromptAssembly, context: AssembleContext, next: () => Promise<PromptAssembly>): Promise<PromptAssembly>

Source: packages/core/system-prompt/src/index.ts:45

system-prompt/change — emit

A section, tool provider, variable provider, or protection was registered or unregistered (the assembly inputs changed — possibly for one scope only). An UNFILTERED registry-subject notification, deliberately not scope-filtered dispatch: a global change concerns every agent's next assembly, so a scoped listener subscribing here sees every change, not just its own scope's.

'system-prompt/change'(): void

Source: packages/core/system-prompt/src/index.ts:55

tools/*

tools/change — emit

A tool was registered or unregistered, or a scoped restriction changed (the available tool set changed — possibly for one scope only). An UNFILTERED registry-subject notification, deliberately not scope-filtered dispatch: a global change concerns every agent's next assembly, so a scoped listener subscribing here sees every change, not just its own scope's.

'tools/change'(): void

Source: packages/core/tools/src/index.ts:173

tools/execute — waterfall

Around-dispatch waterfall wrapping the registry's core tool dispatch, between the tools/pre-execute gate and the tools/post-execute seam. A listener receives (exec, next): call next() to delegate to dispatch (returning its ToolExecutionResult, optionally wrapped), or return a replacement result without calling next() to short-circuit dispatch. The base next() IS the dispatch-with-normalization thunk — a thrown tool (or unknown tool) is already normalized to an isError result by the time a listener's await next() returns, so a wrapper never sees a raw throw from the tool body. This is the seam a timeout/retry/metrics plugin wraps: it can set or replace the one mutable field, exec.signal (e.g. with a per-call deadline), BEFORE next(), restore/delete it afterward, and inspect the result AFTER. Call identity (token, callId, name, arguments, agent, and parent) is immutable throughout the pipeline so a wrapper cannot change which capability or scope was authorized. (Cordis next() ignores passed arguments and re-invokes downstream with the shared payload, so a wrapper changes exec.signal in place rather than passing a new object to next().) Multiple listeners compose by registration order — an outer one wraps the inner ones plus dispatch. Scope-filtered dispatch (@deepseek-ai/dsh-scope): the carrier is keyed by exec.agent — a listener registered through agent.ctx wraps only that agent's calls; a plain plugin listener wraps every call (including agent-less ones, which dispatch subject-less).

'tools/execute'(this: Scoped<ToolRegistry>, exec: ToolExecution, next: () => Promise<ToolExecutionResult>): Promise<ToolExecutionResult>

Types: ToolExecution · ToolExecutionResult

Source: packages/core/tools/src/index.ts:128

tools/post-execute — waterfall

Waterfall AFTER a tool runs — where hook plugins inspect the result and accept it (optionally REPLACING the model-facing content, and/or attaching additionalContext for the next request) or block it with corrective feedback (Claude Code's PostToolUse). Listeners receive (exec, result, next): call next() to delegate to the default (accept unchanged), or return a PostToolDecision to override. Core tool dispatch runs earlier as the base next() of the tools/execute waterfall, all inside execute's outer try/catch (and the tool body keeps its own inner try/catch, so a thrown tool still reaches post-execute as an isError result). Scope-filtered dispatch (@deepseek-ai/dsh-scope): the carrier is keyed by exec.agent — a listener registered through agent.ctx fires only for that agent's calls; a plain plugin listener fires for every call (including agent-less ones, which dispatch subject-less).

'tools/post-execute'(this: Scoped<ToolRegistry>, exec: ToolExecution, result: ToolExecutionResult, next: () => Promise<PostToolDecision>): Promise<PostToolDecision>

Types: ToolExecution · ToolExecutionResult

Source: packages/core/tools/src/index.ts:148

tools/pre-execute — waterfall

Waterfall BEFORE a tool runs — the gate where sandbox, permission, and hook plugins allow or deny a call (Claude Code's PreToolUse). Listeners receive (exec, next): call next() to delegate to the default (allow), or return a PreToolDecision without calling next() to short-circuit. A deny skips dispatch and yields an isError result; the tool body never runs. Input rewrite is deliberately NOT offered here (see PreToolDecision); ask is serviced by the ctx.approval seam when one is mounted, and degrades to deny otherwise. Scope-filtered dispatch (@deepseek-ai/dsh-scope) keys the carrier by exec.agent: a listener registered through agent.ctx fires only for that agent's calls, while a plain plugin listener fires for every call (including agent-less ones, which dispatch subject-less).

'tools/pre-execute'(this: Scoped<ToolRegistry>, exec: ToolExecution, next: () => Promise<PreToolDecision>): Promise<PreToolDecision>

Types: ToolExecution

Source: packages/core/tools/src/index.ts:101

tools/result — parallel

Awaited notification of the authoritative FINAL tool outcome, after the complete pre/execute/post pipeline, final lossless-JSON validation, and outer error normalization. Unlike the three waterfalls, this seam cannot transform the result: each listener receives the now-frozen execution object and a deep-frozen result snapshot; listener failures are contained and logged, and ToolRegistry.execute still returns the outcome. Scope-filtered dispatch (@deepseek-ai/dsh-scope): keyed by exec.agent, using the same carrier as the pipeline.

'tools/result'(this: Scoped<ToolRegistry>, exec: Readonly<ToolExecution>, result: Readonly<ToolExecutionResult>): Promise<void> | void

Types: ToolExecution · ToolExecutionResult

Source: packages/core/tools/src/index.ts:163

workflow/*

workflow/agent-end — emit

One agent() call settled (clean result, child failure, or run cancellation). Paired with Events['workflow/agent-start'] by agent.seq, exactly once per started call on every stop path — on an engine termination path (a worker killed past its grace) the end is engine-synthesized with outcome 'cancelled'.

'workflow/agent-end'(info: WorkflowRunInfo, agent: WorkflowAgentEndInfo): void

Source: packages/workflow/workflow/src/index.ts:96

workflow/agent-start — emit

One agent() call started a child run. Paired with Events['workflow/agent-end'] by agent.seq.

'workflow/agent-start'(info: WorkflowRunInfo, agent: WorkflowAgentInfo): void

Source: packages/workflow/workflow/src/index.ts:85

workflow/end — emit

A workflow run settled (any stop reason). Fired when WorkflowRun.result resolves. Paired with Events['workflow/start'].

'workflow/end'(info: WorkflowRunInfo, result: WorkflowResultInfo): void

Source: packages/workflow/workflow/src/index.ts:106

workflow/log — emit

The script emitted a narration line (a log(message) call).

'workflow/log'(info: WorkflowRunInfo, message: string): void

Source: packages/workflow/workflow/src/index.ts:77

workflow/phase — emit

The script entered a phase (a phase(title) call) — progress grouping for observers; no execution semantics.

'workflow/phase'(info: WorkflowRunInfo, title: string): void

Source: packages/workflow/workflow/src/index.ts:70

workflow/start — emit

A workflow run started — the script's meta block validated, the body about to execute. Paired with Events['workflow/end'].

'workflow/start'(info: WorkflowRunInfo): void

Source: packages/workflow/workflow/src/index.ts:62

Inherited events (cordis core + loader/hmr/timer)

The framework events every plugin also sees, beyond the harness vocabulary above. This is pinned vendor source (vendoring policy); it is summarized here so the page is a complete picture of the event bus, without elevating framework internals to the harness tier's prominence.