@adcp/sdk API Reference - v7.9.0
    Preparing search index...

    Interface TaskResultIntermediate<T>

    Task is still progressing (working, submitted, input-required, deferred).

    interface TaskResultIntermediate<T> {
        metadata: TaskResultMetadata;
        governance?: GovernanceCheckResult;
        governanceOutcome?: GovernanceOutcome;
        governanceOutcomeError?: string;
        conversation?: Message[];
        debug_logs?: any[];
        match?: <R>(
            handlers: MatchHandlers<T, R> | PartialMatchHandlers<T, R>,
        ) => R;
        success: true;
        status:
            | "submitted"
            | "working"
            | "input-required"
            | "auth-required"
            | "deferred";
        data?: T;
        error?: undefined;
        adcpError?: undefined;
        errorInstance?: undefined;
        correlationId?: undefined;
        deferred?: DeferredContinuation<T>;
        submitted?: SubmittedContinuation<T>;
    }

    Type Parameters

    • T

    Hierarchy

    • TaskResultBase<T>
      • TaskResultIntermediate
    Index

    Properties

    Governance check result (present when governance is configured)

    governanceOutcome?: GovernanceOutcome

    Governance outcome (present after successful execution with governance)

    governanceOutcomeError?: string

    Error message when governance outcome reporting failed

    conversation?: Message[]

    Full conversation history

    debug_logs?: any[]

    Debug logs (if debug enabled)

    match?: <R>(handlers: MatchHandlers<T, R> | PartialMatchHandlers<T, R>) => R

    Exhaustive pattern match on the result's status. Prefer this method form — it autocompletes alongside the other TaskResult accessors.

    The free function import('./match').match is also exported for compositional use (e.g., point-free style or when the result type is not yet narrowed).

    Attached non-enumerably by the client when the result is returned from executeTask. Results constructed by hand (e.g., in test fixtures or custom middleware) will not have this method — use the free function, or call attachMatch(result) first.

    success: true
    status:
        | "submitted"
        | "working"
        | "input-required"
        | "auth-required"
        | "deferred"

    Task is progressing but not yet final. 'auth-required' and 'input-required' are paused states surfaced by the polling cycle (pollTaskCompletion) — the buyer must satisfy the paused condition (refresh auth / supply input) and retry the original tool call. Polling alone won't advance them.

    data?: T
    error?: undefined
    adcpError?: undefined
    errorInstance?: undefined
    correlationId?: undefined
    deferred?: DeferredContinuation<T>

    Deferred continuation (client needs time for input)

    submitted?: SubmittedContinuation<T>

    Submitted continuation (server needs time for processing)