Struct DockNodeView 

pub struct DockNodeView {
    pub node_id: String,
    pub tool_name: String,
    pub status: String,
    pub age_ms: i64,
    pub stuck: bool,
    pub run_in_background: Option<bool>,
}

Fields

node_id: String

tool_name: String

status: String

age_ms: i64

stuck: bool

true when status == "running", past DOCK_STUCK_THRESHOLD_MS, AND the block’s own ProcessBroker lifecycle is not Running — i.e. nothing srv-side is actively backing this block’s turn at all. Coarse: this is block-level, not node-level, liveness (a block mid-turn on a LATER tool call would still read Running and suppress the flag for an earlier stuck node in the same block) — see spec §3.1’s own framing of this as “the same signal a human would manually cross-reference today, automated,” not a perfect per-node liveness oracle.

Does NOT cover a backgrounded call stuck in the actual dock UI (issue #2518): status here is the RAW ToolNode status, which is terminal (“success”) for an accepted background launch within ~a second — this field can never go true for that case no matter how long the real dock row has been showing running, because the server has no visibility into whether a <task-notification> ever arrived (that reclassification is entirely client-side, in tool-adapter.ts). See run_in_background below: a true there combined with a long age_ms is worth checking by hand even when stuck reads false.

run_in_background: Option<bool>

params.run_in_background === true on the pushing client’s own ToolNode, if it’s a Bash call and the renderer reported it. None for every non-Bash tool and for older clients that predate this field. See stuck’s doc comment above for why this exists.

Trait Implementations

impl Serialize for DockNodeView

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.