@statelyai/agent 2.0.0-alpha.11 → 2.0.0-alpha.13

package/dist/utils-BYqT_Dyv.d.cts

@@ -1,108 +0,0 @@
-import { A as UserMessage, C as StandardSchemaV1, D as ToolMessage, E as ToolCallPart, T as TextPart, k as ToolResultPart, p as AssistantMessage, r as AgentMessage, v as FilePart, w as SystemMessage, y as ImagePart } from "./types-C9QiMjre.cjs";
-import { AnyMachineSnapshot, AnyStateMachine } from "xstate";
-
-//#region src/utils.d.ts
-/**
- * Deep-clones a snapshot to a plain-JSON value via a `JSON` round-trip, the
- * shape you persist and later feed back to `runAgent({ snapshot })`. Asserts
- * JSON-serializability: functions, `undefined`, and other non-JSON values are
- * dropped or throw exactly as `JSON.stringify`/`JSON.parse` would. Returns a
- * plain-JSON deep clone, not a live snapshot.
- */
-declare function persistSnapshot<TSnapshot>(snapshot: TSnapshot): TSnapshot;
-/**
- * A stable, dependency-free structural fingerprint of a machine — a short hex
- * `djb2` hash over its **structural** config only: state ids/nesting, transition
- * event types and targets, invoke `src`s, `initial`, and any other serializable
- * config fields. Function values (context/output builders, prompts, inline
- * guards/actions) are excluded entirely, so two machines that differ only in
- * their prompts or executors hash identically; adding/removing/retargeting a
- * state or transition changes the hash.
- *
- * Used by {@link runAgent} to stamp settled snapshots with a `version` and to
- * detect a structurally-edited machine on resume. It is a change detector, not
- * a cryptographic digest — collisions are possible but unlikely for real
- * configs. Pass an explicit `machineVersion` to `runAgent` to override it.
- */
-declare function getMachineStructuralHash(machine: AnyStateMachine): string;
-/** Builds a {@link UserMessage} from a string or multimodal content parts. */
-declare function userMessage(content: string | Array<TextPart | ImagePart | FilePart>): UserMessage;
-/** Builds an {@link AssistantMessage} from a string or content parts (text, files, tool calls/results). */
-declare function assistantMessage(content: string | Array<TextPart | FilePart | ToolCallPart | ToolResultPart>): AssistantMessage;
-/** Builds a {@link SystemMessage}. */
-declare function systemMessage(content: string): SystemMessage;
-/** Builds a {@link ToolMessage} from one or more tool-result parts. */
-declare function toolMessage(content: Array<ToolResultPart>): ToolMessage;
-type MetaOfSnapshot<TSnapshot extends {
-  getMeta(): Record<string, unknown>;
-}> = NonNullable<ReturnType<TSnapshot["getMeta"]>[keyof ReturnType<TSnapshot["getMeta"]>]>;
-/**
- * Returns the merged `meta` of a snapshot's active state(s) — the typed
- * replacement for the `Object.values(snapshot.getMeta())[0]` dance.
- *
- * `snapshot.getMeta()` is keyed by state id; a leaf machine has one active
- * state, but parallel/nested machines can have several. This shallow-merges
- * every active state's meta into one object (later/deeper entries win) and
- * returns `{}` when no active state declares meta.
- *
- * The return type is recovered from the snapshot's own `getMeta()` type, so a
- * schema-typed machine (`setupAgent({ meta })`) yields the meta schema's
- * output type. Pass an explicit `TMeta` to override when the snapshot is
- * untyped (e.g. `AnyMachineSnapshot`).
- *
- * @example HITL: read the current state's interaction protocol off an idle
- * snapshot to render for a human.
- * ```ts
- * const { interaction } = getStateMeta(result.snapshot);
- * ```
- */
-declare function getStateMeta<TSnapshot extends {
-  getMeta(): Record<string, unknown>;
-} = AnyMachineSnapshot, TMeta = MetaOfSnapshot<TSnapshot>>(snapshot: TSnapshot): Partial<TMeta>;
-/**
- * Reads the run-owned message log off a snapshot settled by a `runAgent` call
- * that used `getRequests` (or `options.messages`) — the typed replacement for
- * the `(snapshot as { messages?: AgentMessage[] }).messages` cast. runAgent
- * stamps the log as a plain enumerable `messages` property (like `agentMeta`),
- * so it survives a JSON persist/resume round-trip; this accessor works on the
- * live settled snapshot and on a JSON-parsed persisted one alike. Returns `[]`
- * when no log was stamped (e.g. a default invoke-driven run).
- *
- * The write path is `runAgent(..., { messages })`: an explicit seed that
- * overrides the resume snapshot's stamped log (fold in a user reply on
- * resume, or start a run with prior history).
- */
-declare function getAgentMessages(snapshot: unknown): AgentMessage[];
-/**
- * Structural guard for a {@link StandardSchemaV1}: `true` when `value` carries
- * the `~standard` marker. Used to tell an already-schema'd tool `inputSchema`
- * (a Zod/Valibot/… schema) apart from an SDK-specific schema wrapper that core
- * can't read directly — see the `ai-sdk` tool pass-through and `openai-compat`
- * tool serialization.
- */
-declare function isStandardSchema(value: unknown): value is StandardSchemaV1;
-/**
- * Pulls the JSON Schema off a {@link StandardSchemaV1} via its optional
- * `~standard.jsonSchema.input()` extension (implemented by e.g. Zod v4's
- * `z.toJSONSchema`), awaiting it when the producer is async. Returns
- * `undefined` when the schema doesn't expose the extension. Use this to build
- * a provider request's `response_format`/tool `parameters` from a schema.
- */
-declare function getJsonSchema(schema?: StandardSchemaV1): Promise<Record<string, unknown> | undefined>;
-/**
- * Synchronous variant of {@link getJsonSchema}, for call sites that can't
- * await (building tool/event descriptors inline). An async JSON Schema
- * producer is treated as absent (returns `undefined`) — in practice Zod's
- * `z.toJSONSchema` resolves synchronously.
- */
-declare function getJsonSchemaSync(schema?: StandardSchemaV1): Record<string, unknown> | undefined;
-/**
- * Validates `value` against a {@link StandardSchemaV1}, synchronously.
- * Throws if the schema's `validate` returns a `Promise` (async validation is
- * not supported anywhere in this library) or if validation reports issues —
- * in which case the thrown `Error.message` joins every issue message with
- * `', '`.
- */
-declare function validateSchemaSync<T>(schema: StandardSchemaV1<T>, value: unknown): T;
-//#endregion
-export { getMachineStructuralHash as a, persistSnapshot as c, userMessage as d, validateSchemaSync as f, getJsonSchemaSync as i, systemMessage as l, getAgentMessages as n, getStateMeta as o, getJsonSchema as r, isStandardSchema as s, assistantMessage as t, toolMessage as u };

package/dist/utils-Do5wIJrh.d.mts

@@ -1,108 +0,0 @@
-import { A as UserMessage, C as StandardSchemaV1, D as ToolMessage, E as ToolCallPart, T as TextPart, k as ToolResultPart, p as AssistantMessage, r as AgentMessage, v as FilePart, w as SystemMessage, y as ImagePart } from "./types-qm00QF91.mjs";
-import { AnyMachineSnapshot, AnyStateMachine } from "xstate";
-
-//#region src/utils.d.ts
-/**
- * Deep-clones a snapshot to a plain-JSON value via a `JSON` round-trip, the
- * shape you persist and later feed back to `runAgent({ snapshot })`. Asserts
- * JSON-serializability: functions, `undefined`, and other non-JSON values are
- * dropped or throw exactly as `JSON.stringify`/`JSON.parse` would. Returns a
- * plain-JSON deep clone, not a live snapshot.
- */
-declare function persistSnapshot<TSnapshot>(snapshot: TSnapshot): TSnapshot;
-/**
- * A stable, dependency-free structural fingerprint of a machine — a short hex
- * `djb2` hash over its **structural** config only: state ids/nesting, transition
- * event types and targets, invoke `src`s, `initial`, and any other serializable
- * config fields. Function values (context/output builders, prompts, inline
- * guards/actions) are excluded entirely, so two machines that differ only in
- * their prompts or executors hash identically; adding/removing/retargeting a
- * state or transition changes the hash.
- *
- * Used by {@link runAgent} to stamp settled snapshots with a `version` and to
- * detect a structurally-edited machine on resume. It is a change detector, not
- * a cryptographic digest — collisions are possible but unlikely for real
- * configs. Pass an explicit `machineVersion` to `runAgent` to override it.
- */
-declare function getMachineStructuralHash(machine: AnyStateMachine): string;
-/** Builds a {@link UserMessage} from a string or multimodal content parts. */
-declare function userMessage(content: string | Array<TextPart | ImagePart | FilePart>): UserMessage;
-/** Builds an {@link AssistantMessage} from a string or content parts (text, files, tool calls/results). */
-declare function assistantMessage(content: string | Array<TextPart | FilePart | ToolCallPart | ToolResultPart>): AssistantMessage;
-/** Builds a {@link SystemMessage}. */
-declare function systemMessage(content: string): SystemMessage;
-/** Builds a {@link ToolMessage} from one or more tool-result parts. */
-declare function toolMessage(content: Array<ToolResultPart>): ToolMessage;
-type MetaOfSnapshot<TSnapshot extends {
-  getMeta(): Record<string, unknown>;
-}> = NonNullable<ReturnType<TSnapshot["getMeta"]>[keyof ReturnType<TSnapshot["getMeta"]>]>;
-/**
- * Returns the merged `meta` of a snapshot's active state(s) — the typed
- * replacement for the `Object.values(snapshot.getMeta())[0]` dance.
- *
- * `snapshot.getMeta()` is keyed by state id; a leaf machine has one active
- * state, but parallel/nested machines can have several. This shallow-merges
- * every active state's meta into one object (later/deeper entries win) and
- * returns `{}` when no active state declares meta.
- *
- * The return type is recovered from the snapshot's own `getMeta()` type, so a
- * schema-typed machine (`setupAgent({ meta })`) yields the meta schema's
- * output type. Pass an explicit `TMeta` to override when the snapshot is
- * untyped (e.g. `AnyMachineSnapshot`).
- *
- * @example HITL: read the current state's interaction protocol off an idle
- * snapshot to render for a human.
- * ```ts
- * const { interaction } = getStateMeta(result.snapshot);
- * ```
- */
-declare function getStateMeta<TSnapshot extends {
-  getMeta(): Record<string, unknown>;
-} = AnyMachineSnapshot, TMeta = MetaOfSnapshot<TSnapshot>>(snapshot: TSnapshot): Partial<TMeta>;
-/**
- * Reads the run-owned message log off a snapshot settled by a `runAgent` call
- * that used `getRequests` (or `options.messages`) — the typed replacement for
- * the `(snapshot as { messages?: AgentMessage[] }).messages` cast. runAgent
- * stamps the log as a plain enumerable `messages` property (like `agentMeta`),
- * so it survives a JSON persist/resume round-trip; this accessor works on the
- * live settled snapshot and on a JSON-parsed persisted one alike. Returns `[]`
- * when no log was stamped (e.g. a default invoke-driven run).
- *
- * The write path is `runAgent(..., { messages })`: an explicit seed that
- * overrides the resume snapshot's stamped log (fold in a user reply on
- * resume, or start a run with prior history).
- */
-declare function getAgentMessages(snapshot: unknown): AgentMessage[];
-/**
- * Structural guard for a {@link StandardSchemaV1}: `true` when `value` carries
- * the `~standard` marker. Used to tell an already-schema'd tool `inputSchema`
- * (a Zod/Valibot/… schema) apart from an SDK-specific schema wrapper that core
- * can't read directly — see the `ai-sdk` tool pass-through and `openai-compat`
- * tool serialization.
- */
-declare function isStandardSchema(value: unknown): value is StandardSchemaV1;
-/**
- * Pulls the JSON Schema off a {@link StandardSchemaV1} via its optional
- * `~standard.jsonSchema.input()` extension (implemented by e.g. Zod v4's
- * `z.toJSONSchema`), awaiting it when the producer is async. Returns
- * `undefined` when the schema doesn't expose the extension. Use this to build
- * a provider request's `response_format`/tool `parameters` from a schema.
- */
-declare function getJsonSchema(schema?: StandardSchemaV1): Promise<Record<string, unknown> | undefined>;
-/**
- * Synchronous variant of {@link getJsonSchema}, for call sites that can't
- * await (building tool/event descriptors inline). An async JSON Schema
- * producer is treated as absent (returns `undefined`) — in practice Zod's
- * `z.toJSONSchema` resolves synchronously.
- */
-declare function getJsonSchemaSync(schema?: StandardSchemaV1): Record<string, unknown> | undefined;
-/**
- * Validates `value` against a {@link StandardSchemaV1}, synchronously.
- * Throws if the schema's `validate` returns a `Promise` (async validation is
- * not supported anywhere in this library) or if validation reports issues —
- * in which case the thrown `Error.message` joins every issue message with
- * `', '`.
- */
-declare function validateSchemaSync<T>(schema: StandardSchemaV1<T>, value: unknown): T;
-//#endregion
-export { getMachineStructuralHash as a, persistSnapshot as c, userMessage as d, validateSchemaSync as f, getJsonSchemaSync as i, systemMessage as l, getAgentMessages as n, getStateMeta as o, getJsonSchema as r, isStandardSchema as s, assistantMessage as t, toolMessage as u };

package/dist/zod.cjs

@@ -1,31 +0,0 @@
-Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
-let zod = require("zod");
-//#region src/zod/index.ts
-/**
-* A zod schema for an `AgentMessage[]` context/input field — the typed,
-* dependency-light replacement for the hand-rolled
-* `z.custom<AgentMessage[]>((value) => Array.isArray(value))` recipe repeated
-* across machines that carry a message transcript in context.
-*
-* `AgentMessage` is a structural union (see `src/types.ts`), not something to
-* re-declare as a zod object, so this stays a `z.custom` under the hood while
-* exposing the precise `z.ZodType<AgentMessage[]>` type. Validation checks that
-* the value is an array; element shape is trusted (the library's own message
-* builders and adapters produce well-formed `AgentMessage`s).
-*
-* `zod` is an optional peer of `@statelyai/agent` — this subpath is the only
-* place it's imported, mirroring how `./ai-sdk` gates on `ai`.
-*
-* @example
-* ```ts
-* import { z } from 'zod';
-* import { zodAgentMessages } from '@statelyai/agent/zod';
-*
-* const context = z.object({ messages: zodAgentMessages() });
-* ```
-*/
-function zodAgentMessages() {
-	return zod.z.custom((value) => Array.isArray(value));
-}
-//#endregion
-exports.zodAgentMessages = zodAgentMessages;

package/dist/zod.d.cts

@@ -1,30 +0,0 @@
-import { r as AgentMessage } from "./types-C9QiMjre.cjs";
-import { z } from "zod";
-
-//#region src/zod/index.d.ts
-/**
- * A zod schema for an `AgentMessage[]` context/input field — the typed,
- * dependency-light replacement for the hand-rolled
- * `z.custom<AgentMessage[]>((value) => Array.isArray(value))` recipe repeated
- * across machines that carry a message transcript in context.
- *
- * `AgentMessage` is a structural union (see `src/types.ts`), not something to
- * re-declare as a zod object, so this stays a `z.custom` under the hood while
- * exposing the precise `z.ZodType<AgentMessage[]>` type. Validation checks that
- * the value is an array; element shape is trusted (the library's own message
- * builders and adapters produce well-formed `AgentMessage`s).
- *
- * `zod` is an optional peer of `@statelyai/agent` — this subpath is the only
- * place it's imported, mirroring how `./ai-sdk` gates on `ai`.
- *
- * @example
- * ```ts
- * import { z } from 'zod';
- * import { zodAgentMessages } from '@statelyai/agent/zod';
- *
- * const context = z.object({ messages: zodAgentMessages() });
- * ```
- */
-declare function zodAgentMessages(): z.ZodType<AgentMessage[]>;
-//#endregion
-export { zodAgentMessages };

package/dist/zod.d.mts

@@ -1,30 +0,0 @@
-import { r as AgentMessage } from "./types-qm00QF91.mjs";
-import { z } from "zod";
-
-//#region src/zod/index.d.ts
-/**
- * A zod schema for an `AgentMessage[]` context/input field — the typed,
- * dependency-light replacement for the hand-rolled
- * `z.custom<AgentMessage[]>((value) => Array.isArray(value))` recipe repeated
- * across machines that carry a message transcript in context.
- *
- * `AgentMessage` is a structural union (see `src/types.ts`), not something to
- * re-declare as a zod object, so this stays a `z.custom` under the hood while
- * exposing the precise `z.ZodType<AgentMessage[]>` type. Validation checks that
- * the value is an array; element shape is trusted (the library's own message
- * builders and adapters produce well-formed `AgentMessage`s).
- *
- * `zod` is an optional peer of `@statelyai/agent` — this subpath is the only
- * place it's imported, mirroring how `./ai-sdk` gates on `ai`.
- *
- * @example
- * ```ts
- * import { z } from 'zod';
- * import { zodAgentMessages } from '@statelyai/agent/zod';
- *
- * const context = z.object({ messages: zodAgentMessages() });
- * ```
- */
-declare function zodAgentMessages(): z.ZodType<AgentMessage[]>;
-//#endregion
-export { zodAgentMessages };

package/dist/zod.mjs

@@ -1,30 +0,0 @@
-import { z } from "zod";
-//#region src/zod/index.ts
-/**
-* A zod schema for an `AgentMessage[]` context/input field — the typed,
-* dependency-light replacement for the hand-rolled
-* `z.custom<AgentMessage[]>((value) => Array.isArray(value))` recipe repeated
-* across machines that carry a message transcript in context.
-*
-* `AgentMessage` is a structural union (see `src/types.ts`), not something to
-* re-declare as a zod object, so this stays a `z.custom` under the hood while
-* exposing the precise `z.ZodType<AgentMessage[]>` type. Validation checks that
-* the value is an array; element shape is trusted (the library's own message
-* builders and adapters produce well-formed `AgentMessage`s).
-*
-* `zod` is an optional peer of `@statelyai/agent` — this subpath is the only
-* place it's imported, mirroring how `./ai-sdk` gates on `ai`.
-*
-* @example
-* ```ts
-* import { z } from 'zod';
-* import { zodAgentMessages } from '@statelyai/agent/zod';
-*
-* const context = z.object({ messages: zodAgentMessages() });
-* ```
-*/
-function zodAgentMessages() {
-	return z.custom((value) => Array.isArray(value));
-}
-//#endregion
-export { zodAgentMessages };