agentfootprint
Version:
The explainable agent framework — backtrack a wrong answer to the exact context that caused it (evidence, not guesses). Built on footprintjs.
20 lines (19 loc) • 943 B
TypeScript
/**
* pendingAsk — what a paused run is waiting on, as data a door may hand back.
*
* ONE projection, used by every door that keeps a paused run for a later
* request (`standingAgent`, `streamHandler`): the question, never the state.
*/
import type { RunnerPauseOutcome } from '../core/pause.js';
import type { PendingAsk } from './types.js';
/**
* Project a paused run into the part that is safe to hand back: the question,
* never the state.
*
* Every field is read from what the run actually recorded — the tool name and
* question the dispatch loop stamps on `pauseData`, the typed `checkIn`, the
* middleware `ask`. A field the run did not record is simply absent. Nothing
* here infers, summarises or invents, which is why the raw `pauseData` rides
* along untouched: the tool's author chose those words.
*/
export declare function describePause(outcome: RunnerPauseOutcome, sessionId: string | undefined): PendingAsk;