Message
Owned text, optional structured content and source metadata. SDK objects remain outside.
import type { Message } from '@threadplane/angular/chat';Declaration
export interface Message {
readonly blocks?: readonly ContentBlock[];
readonly citations?: readonly Citation[];
readonly content: string;
readonly delivery: MessageDelivery;
readonly extra?: Readonly<Record<string, PlainValue>>;
readonly id: string;
readonly name?: string;
readonly reasoning?: string;
readonly reasoningDurationMs?: number;
readonly role: Role;
readonly toolCallId?: string;
readonly toolCallIds?: readonly string[];
}Members
blocks
The message as structured blocks, when the backend sent or the caller
submitted more than text. content then holds the text of its text
blocks, so a view that renders text only needs no second path.
readonly blocks?: readonly ContentBlock[];citations
readonly citations?: readonly Citation[];content
The message as text. Always present, also when blocks is.
readonly content: string;delivery
readonly delivery: MessageDelivery;extra
Backend-specific extras as frozen plain data, such as a raw tool-call list or a response format. Portable code does not rely on its shape.
readonly extra?: Readonly<Record<string, PlainValue>>;id
readonly id: string;name
readonly name?: string;reasoning
Backend-supplied reasoning display text.
readonly reasoning?: string;reasoningDurationMs
How long the reasoning took, in milliseconds, when the backend or runtime measured it. Absent means unknown, not zero.
readonly reasoningDurationMs?: number;role
readonly role: Role;toolCallId
readonly toolCallId?: string;toolCallIds
readonly toolCallIds?: readonly string[];