Expand description
Conversation messages.
The message data model implements serde serialization / deserialization: session persistence and cross-process transport (tool definitions and messages) serialize these types directly, no manual mapping needed.
A full conversation history is expressed as a Message sequence; each
message consists of content blocks (text / images, or
vendor-shaped blocks passed through verbatim via ContentBlock::Wire).
The structured entry point of the content model is ContentBlock — the
shape of Message stays unchanged, and consumers just match the new
variant.
Structs§
- Image
Content - Raw image data carried in a
ContentBlock::Image. - Tool
Call - A tool call requested by the model.
Enums§
- Content
Block - A content block within a message.
- Message
- A single message in a conversation.