agentSessionKey?: string;

agentChannel?: GatewayMessageChannel;

agentAccountId?: string;

/** Delivery target (e.g. telegram:group:123:topic:456) for topic/thread routing. */

/** Delivery target for topic/thread routing. */

agentTo?: string;

/** Thread/topic identifier for routing replies to the originating thread. */

agentThreadId?: string | number;

sandboxed?: boolean;

config?: OpenClawConfig;

pluginToolAllowlist?: string[];

/** Current channel ID for auto-threading (Slack). */

/** Current channel ID for auto-threading. */

currentChannelId?: string;

/** Current thread timestamp for auto-threading (Slack). */

/** Current thread timestamp for auto-threading. */

currentThreadTs?: string;

/** Current inbound message id for action fallbacks (e.g. Telegram react). */

/** Current inbound message id for action fallbacks. */

currentMessageId?: string | number;

/** Reply-to mode for Slack auto-threading. */

/** Reply-to mode for auto-threading. */

replyToMode?: "off" | "first" | "all" | "batched";

/** Mutable ref to track if a reply was sent (for "first" mode). */

hasRepliedRef?: { value: boolean };

* Node's Buffer.from silently drops invalid base64 characters rather than

* throwing. A material size discrepancy means the source string contained

* embedded garbage that was silently stripped, which would produce a corrupted

* file on disk. ±3 bytes of slack accounts for base64 padding rounding.

* file on disk. ±3 bytes of leeway accounts for base64 padding rounding.

*

* IMPORTANT: this is an input-validation check (4xx client error).

* It MUST be called OUTSIDE the MediaOffloadError try/catch so that

const deliveryFields = normalizeSessionDeliveryFields(entry);

// When the session has no delivery context yet (e.g. a freshly-spawned subagent

// with deliver: false), seed it from the request's channel/to/threadId params.

// Without this, subagent sessions end up with deliveryContext: {channel: "slack"}

// Without this, subagent sessions end up with a channel-only deliveryContext

// and no `to`/`threadId`, which causes announce delivery to either target the

// wrong channel (when the parent's lastTo drifts) or fail entirely.

const requestDeliveryHint = normalizeDeliveryContext({

/**

* Resolve heartbeat visibility settings for a channel.

* Supports both deliverable channels (telegram, signal, etc.) and webchat.

* Supports both deliverable channels and webchat.

* For webchat, uses channels.defaults.heartbeat since webchat doesn't have per-channel config.

*/

export function resolveHeartbeatVisibility(params: {