wednesdayai agent nudge
wednesdayai agent nudge (alias openclaw agent nudge) hands a payload to an agent’s main
persona and wakes it to decide what to do. It is the script-callable surface of the
nudge contract: a cheap check lives in your
script; the expensive persona turn runs only when you call this command.
The persona behaves silent-unless-it-decides — it receives the payload as non-user context and
sends a user-facing message only when warranted, otherwise acknowledges with no delivery (the
existing heartbeat relay semantics). The nudge honours every existing safety gate (active-hours,
main/cron/subagent/session lane busy checks, skipWhenBusy, duplicate suppression); a busy target
session defers rather than bypassing the checks.
Related:
- Nudge contract + wake-gate: Heartbeat
- Plugin-SDK nudge: Agent Signals
- Heartbeat vs cron guidance: Cron vs Heartbeat
Usage
Flags
--text <text>: nudge text (required; also accepted as a positional argument).--data <json>: structured payload as a JSON object (parsed; invalid JSON or a non-object errors).--agent <id>: target agent id (defaults to the default agent’s main session).--session <key>: target session key (overrides--agent).--reason <reason>: nudge reason (defaults tonudge).--json: print the raw result ({ ok, sessionKey, signalId }) as JSON.
0 when the nudge is queued and non-zero when it is rejected (empty text, invalid
--data, or a busy/full target), so scripts can branch on the outcome.
The Gateway method behind this command (agent.nudge) validates the same contract for CLI,
Web UI, and automation clients:
textis required and must be non-empty.data, when present, must be a JSON object.agentId,sessionKey,source, anddedupeKeymust be non-empty strings when present.ttlMs, when present, must be an integer greater than or equal to 1.priority, when present, must be one oflow,normal,high, orurgent.- Unknown fields are rejected instead of being ignored.