@dudousxd/nestjs-agent 0.12.0 → 0.13.0

package/dist/{agent-deps.factory-EROMcBNh.d.cts → agent-deps.factory-y2hvoQ6U.d.cts}

@@ -223,11 +223,19 @@ interface AgentModuleOptions {
     durable?: boolean;
     /**
      * Dispatch the turn's model call and tool executions as routed durable steps
-     * (`AgentRunSteps.llm` / `AgentRunSteps.tool`) instead of in-process `ctx.localStep`s.
-     * DEFAULT `true` under `durable: true` — dispatching moves the run off its pod during the two
-     * long steps (the correct production posture), and `AgentRunSteps` is always registered so the
-     * routed groups are never unserved. Set `false` to keep the turn's steps in-process localSteps.
-     * `true` without `durable: true` throws at module build.
+     * (`AgentRunSteps.llm` / `AgentRunSteps.tool`) instead of in-process `ctx.localStep`s. OMITTED
+     * keeps them in-process; `true` without `durable: true` throws at module build.
+     *
+     * WHAT IT BUYS: the run is not pinned to one pod for the two long parts of a turn, so a fleet can
+     * scale the model call and tool execution separately from the workflow itself.
+     *
+     * WHY IT IS NOT A DEFAULT. It relocates the HOST's own code. A tool handler no longer runs inside
+     * the turn's workflow body but inside whichever worker serves the routed group, and the `llm`
+     * step re-runs the host's tool-visibility callbacks there to rebuild its tool list. A handler
+     * that resolves anything per invocation from its caller's execution context — a request-scoped
+     * ORM EntityManager, an AsyncLocalStorage tenant, a CLS transaction — finds nothing in that
+     * worker, and the library has no way to know which handlers do that. Turn this on once the tools
+     * this deployment registers establish whatever context they need themselves.
      *
      * The cross-process-sink requirement is a property of `durable: true` itself, not of this flag:
      * the turn already runs on whichever worker takes `agent.run`, which may not be the pod holding
@@ -383,12 +391,11 @@ interface AgentModuleAsyncOptions extends Pick<ModuleMetadata, 'imports'> {
      */
     durable?: boolean;
     /**
-     * Dispatch the turn's model call and tool executions as routed durable steps. DEFAULT `true`
-     * under `durable: true`; set `false` to keep the turn's steps in-process localSteps. Same
-     * static-wiring reasoning as `durable` above — it lives here (not in the async factory result)
-     * because it decides how `AgentRunWorkflow` builds its hooks at module build time. `true` without
-     * `durable: true` throws at module build. See `AgentModuleOptions.dispatchedSteps` for the full
-     * contract.
+     * Dispatch the turn's model call and tool executions as routed durable steps. Omitted keeps the
+     * turn's steps in-process localSteps. Same static-wiring reasoning as `durable` above — it lives
+     * here (not in the async factory result) because it decides how `AgentRunWorkflow` builds its
+     * hooks at module build time. `true` without `durable: true` throws at module build. See
+     * `AgentModuleOptions.dispatchedSteps` for the full contract.
      */
     dispatchedSteps?: boolean;
     /**

package/dist/{agent-deps.factory-EROMcBNh.d.ts → agent-deps.factory-y2hvoQ6U.d.ts}

@@ -223,11 +223,19 @@ interface AgentModuleOptions {
     durable?: boolean;
     /**
      * Dispatch the turn's model call and tool executions as routed durable steps
-     * (`AgentRunSteps.llm` / `AgentRunSteps.tool`) instead of in-process `ctx.localStep`s.
-     * DEFAULT `true` under `durable: true` — dispatching moves the run off its pod during the two
-     * long steps (the correct production posture), and `AgentRunSteps` is always registered so the
-     * routed groups are never unserved. Set `false` to keep the turn's steps in-process localSteps.
-     * `true` without `durable: true` throws at module build.
+     * (`AgentRunSteps.llm` / `AgentRunSteps.tool`) instead of in-process `ctx.localStep`s. OMITTED
+     * keeps them in-process; `true` without `durable: true` throws at module build.
+     *
+     * WHAT IT BUYS: the run is not pinned to one pod for the two long parts of a turn, so a fleet can
+     * scale the model call and tool execution separately from the workflow itself.
+     *
+     * WHY IT IS NOT A DEFAULT. It relocates the HOST's own code. A tool handler no longer runs inside
+     * the turn's workflow body but inside whichever worker serves the routed group, and the `llm`
+     * step re-runs the host's tool-visibility callbacks there to rebuild its tool list. A handler
+     * that resolves anything per invocation from its caller's execution context — a request-scoped
+     * ORM EntityManager, an AsyncLocalStorage tenant, a CLS transaction — finds nothing in that
+     * worker, and the library has no way to know which handlers do that. Turn this on once the tools
+     * this deployment registers establish whatever context they need themselves.
      *
      * The cross-process-sink requirement is a property of `durable: true` itself, not of this flag:
      * the turn already runs on whichever worker takes `agent.run`, which may not be the pod holding
@@ -383,12 +391,11 @@ interface AgentModuleAsyncOptions extends Pick<ModuleMetadata, 'imports'> {
      */
     durable?: boolean;
     /**
-     * Dispatch the turn's model call and tool executions as routed durable steps. DEFAULT `true`
-     * under `durable: true`; set `false` to keep the turn's steps in-process localSteps. Same
-     * static-wiring reasoning as `durable` above — it lives here (not in the async factory result)
-     * because it decides how `AgentRunWorkflow` builds its hooks at module build time. `true` without
-     * `durable: true` throws at module build. See `AgentModuleOptions.dispatchedSteps` for the full
-     * contract.
+     * Dispatch the turn's model call and tool executions as routed durable steps. Omitted keeps the
+     * turn's steps in-process localSteps. Same static-wiring reasoning as `durable` above — it lives
+     * here (not in the async factory result) because it decides how `AgentRunWorkflow` builds its
+     * hooks at module build time. `true` without `durable: true` throws at module build. See
+     * `AgentModuleOptions.dispatchedSteps` for the full contract.
      */
     dispatchedSteps?: boolean;
     /**

package/dist/durable/index.cjs

@@ -662,9 +662,9 @@ function runnerProviders() {
     {
       provide: AGENT_DISPATCHED_STEPS,
       useFactory: /* @__PURE__ */ __name((options, sink) => {
-        const enabled = options.durable === true && options.dispatchedSteps !== false;
+        const enabled = options.durable === true && options.dispatchedSteps === true;
         if (enabled && sink instanceof InProcessTokenStreamSink) {
-          logger.warn("Dispatched steps are active (the default under durable: true) with the default InProcessTokenStreamSink, which only buffers tokens in-process. A dispatched `llm` step served by a different worker cannot stream into this buffer. Wire a cross-process TokenStreamSink (e.g. a Redis pub/sub sink) via AgentModule.forRoot({ sink }) before running multi-pod, or set dispatchedSteps: false to keep the turn in-process localSteps.");
+          logger.warn("dispatchedSteps: true with the default InProcessTokenStreamSink, which only buffers tokens in-process. A dispatched `llm` step served by a different worker cannot stream into this buffer. Wire a cross-process TokenStreamSink (e.g. a Redis pub/sub sink) via AgentModule.forRoot({ sink }) before running multi-pod, or drop dispatchedSteps to keep the turn in-process localSteps.");
         }
         return enabled;
       }, "useFactory"),