Array of content items that comprise the user's message.
Contains the multimodal content of the user's message, which can include various types of AutoBeUserMessageContent such as text, images, document files, and audio inputs. Each content item represents a different modality or attachment within the same message.
The array structure allows users to combine multiple content types in a single message, such as text description accompanied by reference images or documents. This multimodal approach provides rich context for the AI assistant to better understand user requirements and generate more accurate development artifacts.
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.
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.
Type discriminator indicating the specific kind of history record.
Provides type-safe discrimination between different history record types such as "analyze", "prisma", "interface", "test", "realize", "userMessage", and "assistantMessage". This enables proper type narrowing and ensures that history records are processed according to their specific characteristics and requirements.
History record generated when a user sends a message during the conversation flow.
User messages support comprehensive multimodal capabilities, allowing not only text input but also image attachments, document file uploads, and voice input. This flexibility enables users to communicate requirements, provide visual references, share existing documentation, and interact naturally through multiple input modalities.
The multimodal support enhances the vibe coding experience by allowing users to express their needs through the most appropriate medium, whether that's describing requirements in text, showing examples through images, or providing specifications through document uploads.
Author
Samchon