loopengine 0.0.17 → 0.0.20

package/dist/run-agent.d.ts

@@ -1,92 +0,0 @@
-import { RuleSet } from 'actauth';
-import type { AgentConfig, ToolDefinition, ToolSchema } from '#agent-config.js';
-export interface ModelContentBlock {
-    type: string;
-    /** text blocks. */
-    text?: string;
-    /** tool_use blocks: this call's own id (referenced by a later tool_result). */
-    id?: string;
-    /** tool_use blocks. */
-    name?: string;
-    /** tool_use blocks. */
-    input?: Record<string, unknown>;
-    /** tool_result blocks: id of the tool_use block this result answers. */
-    tool_use_id?: string;
-    /** tool_result blocks: the tool's output (or denial/error message). */
-    content?: string;
-    /** tool_result blocks: true if the tool call failed or was denied. */
-    is_error?: boolean;
-}
-export interface ModelResponse {
-    stop_reason: string;
-    content: ModelContentBlock[];
-}
-/** loopengine's own conversation-message type — a superset of
- * ContextClip's `{role, content: string}`: `content` can also be a
- * `ModelContentBlock[]`, the same block shape `ModelResponse.content`
- * already used, so a model's tool_use requests and this loop's
- * tool_result replies round-trip with real per-call identity
- * (`tool_use_id`) instead of being flattened into prose. Plain-string
- * content (a user's message, a skill's injected body, a synthetic
- * compaction note) is just as valid — nothing requires every message to
- * be block-structured. */
-export interface Message {
-    role: string;
-    content: string | ModelContentBlock[];
-}
-/** Swap the Anthropic SDK in here — this is the only seam a real API call needs. */
-export type ModelCall = (messages: Message[], system: string, tools: ToolSchema[]) => Promise<ModelResponse>;
-export interface RunAgentOptions {
-    /** Emitted at each loop step for callers that want visibility (logging, UI, tests). Default: no-op. */
-    onEvent?: (event: string, detail: unknown) => void;
-    /** The ActAuth tenant this call runs as — feeds the Gate's scope, so it
-     * governs which rules apply. runAgent() never sees a request, so it
-     * can't call AgentConfig.tenantFor itself; adapters/http.ts resolves it
-     * per request and passes the result here. Default `'default'`, same as
-     * omitting it — every standalone/CLI caller (which never has a request
-     * to resolve tenantFor from) gets that default automatically. */
-    tenant?: string;
-}
-export interface RunAgentResult {
-    /** Final assistant text for this turn. */
-    text: string;
-    /** Full conversation so far, including this turn — pass back in as
-     * `history` on the next call to continue the conversation. Opaque to
-     * the caller: store/transmit it, don't inspect or mutate it. */
-    history: Message[];
-    /** Exactly what this turn added — safe to durably append regardless of
-     * whether ContextClip recovery reshaped `history` mid-turn. A caller
-     * that persists conversations (see session-store.ts) should use this
-     * instead of diffing `history` by length against what it loaded: that
-     * only works if `history` only ever grows, which stops being true the
-     * moment recovery can shrink/rewrite it, not just extend it. */
-    newMessages: Message[];
-    /** Set to 'max_turns' if the loop stopped because it hit
-     * config.maxTurns, not because the model produced a final answer with
-     * no more tool_use blocks — `text` in that case is a synthetic notice,
-     * not something the model said. Absent on a normal finish. */
-    stopReason?: 'max_turns';
-}
-/** Resolves AgentConfig.rules the same way skillsDirs resolves its own
- * default: an inline array is used as-is (full 3-segment scopePattern,
- * unchanged — see loadYamlRules for why only the YAML form gets the
- * agent segment auto-appended); omitted entirely defaults to
- * `agents/<name>/actauth.yml`, this repo's own folder-form convention.
- * Unlike skillsDirs, a missing *default* file falls back to an empty
- * ruleset rather than propagating the raw ENOENT — permissions failing
- * shouldn't crash the whole call. That fallback defaults to `'deny'`, not
- * the inline-array form's `'ask'`: no `actauth.yml` at all means this
- * agent's permission story was never actually written, which is a
- * stricter unknown than "written, but this one tool has no rule" — 'ask'
- * still runs an Approver that could auto-approve, while 'deny' refuses
- * outright until real rules exist. `defaultDecision`, if set, still wins
- * over that. An *explicitly* given path that doesn't exist is a real
- * configuration bug, though, and still throws — only the silent, implicit
- * default gets this forgiveness.
- *
- * Exported (alongside loadDefaultTools below) so adapters/http.ts's
- * GET /agents/:name/config route can show the same rules runAgent() would
- * actually enforce, not a re-derived guess at them. */
-export declare function loadRules(config: AgentConfig): RuleSet;
-export declare function loadDefaultTools(config: AgentConfig): Promise<ToolDefinition[]>;
-export declare function runAgent(config: AgentConfig, modelCall: ModelCall, userMessage: string, history?: Message[], options?: RunAgentOptions): Promise<RunAgentResult>;