AutoBE
    Preparing search index...

    Interface AutoBeAnalyzeRunCheckpointHistory

    Durable checkpoint for in-flight analyze phase recovery.

    Dispatched at each stage boundary (scenario, module, unit, section, cross_file_review). Persisted to agent histories so that a restart after crash can reconstruct AnalyzeRunView and skip completed stages.

    Multiple checkpoints may exist for the same (step, stage, fileIndex) tuple; the one with the latest created_at is authoritative.

    Juntak

    interface AutoBeAnalyzeRunCheckpointHistory {
        created_at: string & Format<"date-time">;
        fileIndex: number | null;
        id: string & Format<"uuid">;
        payload: AnalyzeCheckpointPayload;
        stage: AnalyzeCheckpointStage;
        step: number;
        type: "analyzeRunCheckpoint";
    }

    Hierarchy

    • AutoBeAgentHistoryBase<"analyzeRunCheckpoint">
      • AutoBeAnalyzeRunCheckpointHistory
    Index

    Properties

    created_at fileIndex id payload stage step type

    Properties

    created_at: string & Format<"date-time">

    ISO 8601 timestamp indicating when this history record was created.

    Marks the exact moment when this history entry was initiated or when the corresponding agent activity began. This timestamp is fundamental for maintaining chronological order, tracking development progress, and understanding the temporal relationships between different phases of the vibe coding process.

    fileIndex: number | null

    File index (matches AutoBeAnalyzeScenarioEvent.files[] order).

    • null for scenario and cross_file_review stages (run-level)
    • Required for module, unit, section stages (file-level)
    id: string & Format<"uuid">

    Unique identifier for this history record.

    A UUID that uniquely identifies this specific history entry within the system. This identifier enables precise referencing, cross-linking between related history records, and maintaining referential integrity across the development timeline and different agent activities.

    payload: AnalyzeCheckpointPayload

    Stage-specific recovery payload.

    stage: AnalyzeCheckpointStage

    Stage boundary this checkpoint represents.

    step: number

    Analyze run's step number.

    type: "analyzeRunCheckpoint"

    Type discriminator indicating the specific kind of history record.

    Provides type-safe discrimination between different history record types such as "analyze", "database", "interface", "realize", "test", "userMessage", and "assistantMessage". This enables proper type narrowing and ensures that history records are processed according to their specific characteristics and requirements.

    Settings

    Member Visibility

    On This Page

    Properties