AutoBE
    Preparing search index...

    Interface AutoBeAutoViewCompleteEvent

    Event fired when an AutoView run finishes — successful or otherwise.

    Carries the assembled frontend project as a flat path → content map so the UI can offer a one-click download (ZIP) and a Sandbox deploy checklist. The same map is what the Sandbox /sandbox-server-infra-setup Slack command later builds against the operator's private GitHub repo.

    Samchon

    interface AutoBeAutoViewCompleteEvent {
        created_at: string & Format<"date-time">;
        elapsed: number;
        files: Record<string, string>;
        id: string;
        pages: number;
        source: "interface" | "shopping";
        step: number;
        type: "autoViewComplete";
    }

    Hierarchy

    • AutoBeEventBase<"autoViewComplete">
      • AutoBeAutoViewCompleteEvent
    Index

    Properties

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

    Timestamp when the event was created.

    ISO 8601 formatted date-time string indicating when this event was emitted by the system. This timestamp is crucial for event ordering, performance analysis, and debugging the agent workflow execution timeline.

    Format: "YYYY-MM-DDTHH:mm:ss.sssZ" (e.g., "2024-01-15T14:30:45.123Z")

    elapsed: number

    Total wall-clock time the run took, in milliseconds.

    files: Record<string, string>

    The assembled frontend project as a flat path → content map. Every entry sits under the repo root (Dockerfile, app/page.tsx, components/ui/button.tsx, …) ready to be zipped or pushed to a private GitHub repo for Sandbox deploy.

    id: string

    A unique identifier for the event.

    pages: number

    Total page TSX files produced.

    source: "interface" | "shopping"

    Source the run targeted. Mirrors autoViewStart.source.

    step: number

    Step counter — matches autoViewStart.step.

    type: "autoViewComplete"

    Unique identifier for the event type.

    A literal string that discriminates between different event types in the AutoBE system. This field enables TypeScript's discriminated union feature, allowing type-safe event handling through switch statements or conditional checks.

    Examples: "analyzeWrite", "databaseSchema", "interfaceOperation", "testScenario"