@runloop/remote-agents-sdk
    Preparing search index...

    Type Alias ThreadResumeParams

    There are three ways to resume a thread:

    1. By thread_id: load the thread from disk by thread_id and resume it.
    2. By history: instantiate the thread from memory and resume it.
    3. By path: load the thread from disk by path and resume it.

    For non-running threads, the precedence is: history > non-empty path > thread_id. If using history or a non-empty path for a non-running thread, the thread_id param will be ignored.

    If thread_id identifies a running thread, app-server rejoins that thread and treats a non-empty path as a consistency check against the active rollout path. Empty string path values are treated as absent.

    Prefer using thread_id whenever possible.

    type ThreadResumeParams = {
        approvalPolicy?: AskForApproval | null;
        approvalsReviewer?: ApprovalsReviewer | null;
        baseInstructions?: string | null;
        config?: { [key in string]?: JsonValue } | null;
        cwd?: string | null;
        developerInstructions?: string | null;
        model?: string | null;
        modelProvider?: string | null;
        personality?: Personality | null;
        sandbox?: SandboxMode | null;
        serviceTier?: string | null | null;
        threadId: string;
    }
    Index

    Properties

    approvalPolicy? approvalsReviewer? baseInstructions? config? cwd? developerInstructions? model? modelProvider? personality? sandbox? serviceTier? threadId

    Properties

    approvalPolicy?: AskForApproval | null
    approvalsReviewer?: ApprovalsReviewer | null
    baseInstructions?: string | null
    config?: { [key in string]?: JsonValue } | null
    cwd?: string | null
    developerInstructions?: string | null
    model?: string | null
    modelProvider?: string | null
    personality?: Personality | null
    sandbox?: SandboxMode | null
    serviceTier?: string | null | null
    threadId: string

    Settings

    Member Visibility

    On This Page

    Properties