Number of LLM attempts spent on this page including the final one (1 means it passed on the first try).
Number of items completed.
Tracks how many items have been successfully processed so far in the current operation. This value increments as each item is completed, providing real-time progress indication.
The ratio of completed to total gives the completion percentage:
progress = (completed / total) * 100
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")
A unique identifier for the event.
Function calling trial statistics (total, success, failure counts).
true if the produced TSX cleared the TypeScript parser without fallback.
false if the agent gave up and shipped an error placeholder so the wider
build still succeeds.
Path inside the Next.js app router, e.g. /catalog, /orders/[id].
Step counter — matches autoViewStart.step.
Token consumption breakdown (input, output, cache hits).
Total number of items to process.
Represents the complete count of operations, files, endpoints, or other entities that need to be processed in the current workflow step. This value is typically determined at the beginning of an operation and remains constant throughout the process.
Used together with the completed field to calculate progress percentage
and estimate time to completion.
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"
UI pattern the agent picked for this page (table, card, form, etc.).
Event fired for each page as phase 4 (Render) generates it.
One render attempt may include LLM retries when the TypeScript parser rejects the produced TSX. The event reports the final state — whether the page parsed cleanly or was replaced with an error placeholder.
Author
Samchon