pub struct BridgePendingTaskInput {
pub message: String,
pub conversation_history: Option<Vec<BridgePendingTaskInputConversationHistoryItem>>,
pub files: Option<Vec<String>>,
pub attachments: Option<Vec<BridgePendingTaskInputAttachment>>,
}Expand description
BridgePendingTaskInput model.
Fields§
§message: String§conversation_history: Option<Vec<BridgePendingTaskInputConversationHistoryItem>>§files: Option<Vec<String>>Attachment ids the user added to this message. Fetch each with GET /files/{fileId}/content (scope files:read). Absent when the message had no attachment.
attachments: Option<Vec<BridgePendingTaskInputAttachment>>The attachments, in the same order as files, with what a client needs BEFORE it spends a
fetch: a 40 MB video and a 2 KB note are not the same decision, and an error that cannot
name the file leaves the model answering about a document it never opened. This is the
SUBSET of files whose artifact record still exists when the task is enqueued — a run
dispatched from a schedule was written earlier and the file may have been deleted since. An
id present in files with no entry here means the file is gone, not that its metadata was
omitted; fetching it will 404, which is how the client reports the attachment as not
delivered.
Trait Implementations§
Source§impl Clone for BridgePendingTaskInput
impl Clone for BridgePendingTaskInput
Source§fn clone(&self) -> BridgePendingTaskInput
fn clone(&self) -> BridgePendingTaskInput
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more