#[non_exhaustive]pub struct ToolCallMembers {Show 29 fields
pub tool: Option<String>,
pub call_id: Option<String>,
pub args: Option<String>,
pub failure_reason: Option<String>,
pub failure_kind: Option<String>,
pub visible_output: Option<String>,
pub output_ref: Option<OutputRef>,
pub tool_receipt: Option<Box<ToolReceipt>>,
pub patch_summary: Option<PatchSummary>,
pub patch_ref: Option<OutputRef>,
pub model_visible_content: Option<Vec<ModelVisibleContent>>,
pub approval_id: Option<String>,
pub held: Option<bool>,
pub held_for: Option<HeldFor>,
pub background: Option<bool>,
pub background_initiator: Option<BackgroundInitiator>,
pub background_status: Option<BackgroundStatus>,
pub status_line: Option<String>,
pub status_phase: Option<String>,
pub status_progress: Option<StatusProgress>,
pub status_step: Option<StatusStep>,
pub status_attempt: Option<StatusAttempt>,
pub status_health: Option<StatusHealth>,
pub status_children: Option<StatusChildren>,
pub display_label: Option<Box<ToolDisplayLabel>>,
pub bash_title: Option<String>,
pub work_id: Option<String>,
pub background_target: Option<BackgroundTarget>,
pub node: Option<String>,
}Expand description
toolCall members, flattened into the item row.
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.tool: Option<String>toolCall: tool name.
call_id: Option<String>toolCall: the provider call id (call_...), opaque.
args: Option<String>toolCall: the model-authored argument JSON, verbatim; clients
parse. Verbatim keeps the fold byte-deterministic and survives
model-emitted almost-JSON.
failure_reason: Option<String>toolCall/subagent: Failed/Rejected/Cancelled reason text,
verbatim.
failure_kind: Option<String>toolCall: machine-readable failure class.
visible_output: Option<String>toolCall/userShell: bounded transcript-visible result text; streams
via item/delta field "output".
output_ref: Option<OutputRef>toolCall/userShell: stored-output reference; fetch the full bytes
via item/readOutput.
tool_receipt: Option<Box<ToolReceipt>>toolCall: the shared semantic receipt — what the operation did, as
machine-readable fact. Optional and additive: absence is always valid
and is never an error. When present, a server serves the same
receipt on every item path — item/completed, view/page, seeded
snapshots and resume. Observation only; carries no control authority,
and no field in it enters model-visible content.
patch_summary: Option<PatchSummary>toolCall: server-authored edit-family diff summary — always beside
patchRef; absent = no diff available.
patch_ref: Option<OutputRef>toolCall: stored structured-patch reference (kind: "tool_patch",
mediaType: "application/json"); the body is fetched via
item/readOutput with patchRef.id, and the ref survives the
elided-snapshot rung exactly like outputRef without ever being an
elision trigger.
model_visible_content: Option<Vec<ModelVisibleContent>>toolCall: rich content the model saw beyond text; base64 is not
inlined on the view.
approval_id: Option<String>toolCall: the approval that gated this call; join key for the approval
view events.
held: Option<bool>toolCall: true while the call is held before it is admitted to
execute. Present on an item started at hold time, cleared by the release
item/updated, absent on calls never held.
held_for: Option<HeldFor>toolCall: what holds the call; present exactly when held is.
background: Option<bool>toolCall: true once the task was durably backgrounded; delivered
via item/updated.
background_initiator: Option<BackgroundInitiator>toolCall: who backgrounded the task; absent on pre-split records —
never inferred.
background_status: Option<BackgroundStatus>toolCall: the backgrounded-row payload for a running backgrounded item
— auto-yield or an explicit user/timeout background; may appear with or
without background/backgroundInitiator. Experimental, delivered via
item/updated. Presentation only — never a durability claim.
status_line: Option<String>toolCall: the task’s visible latest-status line — the latest Status
message through the shared detail normalization; absent when no status
folded or nothing displayable remains.
status_phase: Option<String>toolCall: the latest detail’s phase row, verbatim; absent when the
latest detail carries none.
status_progress: Option<StatusProgress>toolCall: the latest progress facet, field-for-field; absent when the
latest detail carries none.
status_step: Option<StatusStep>toolCall: the latest active-step facet, field-for-field; absent when
the latest detail carries none.
status_attempt: Option<StatusAttempt>toolCall: the latest external-attempt facet, field-for-field —
countdown inputs the client renders the tick from; absent when the
latest detail carries none.
status_health: Option<StatusHealth>toolCall: the latest health facet, field-for-field; absent when the
latest detail carries none.
status_children: Option<StatusChildren>toolCall: the latest child-summary facet, field-for-field; absent when
the latest detail carries none.
display_label: Option<Box<ToolDisplayLabel>>toolCall: the tool’s own words for this call; absent = none.
bash_title: Option<String>toolCall: the call’s Bash Title — its description argument through
the shared Bash Title normalizer, for a managed Bash call, served only
while the host’s bash_titles gate is on. The host adds it when it
serves the item and never stores it; absent for any other call. Old
clients ignore it.
work_id: Option<String>toolCall: the task’s registered Work ID, verbatim
(work.v2.managed_bash.sha256.…); present only when the task registered
a ManagedBash id, absent otherwise. Stable from day one: no
x-msp-stability marker. The host serves it at the later of the task
terminal and the inbox admission; absence keeps the client’s v1
derivation.
background_target: Option<BackgroundTarget>toolCall: this call’s live background-target record. Set when the
foreground tool starts, refreshed by whole-item item/updated when the
facts change, omitted once the call settles or unregisters — present
means a live candidate. Absent (pre-feature hosts, unregistered calls)
keeps the client’s derived behavior, never an error. Old clients ignore
it.
node: Option<String>toolCall: the name of the remote node this call is dispatched to.
Experimental (Item.node). Present once a dispatch to that node is
recorded for the call. Absent while none is: a call on the host’s own
machine (in a session that never had a remote node this keeps today’s
bytes), or a remote call that is not dispatched yet, or was refused or
failed before its dispatch; its approval request, when one was made,
names the node. Never local, and absence never means the default node.