Agent Send
openclaw agent runs a single agent turn from the command line without needing an inbound chat message. Use it for scripted workflows, testing, and programmatic delivery. Quick start
Flags
| Flag | Description |
|---|---|
--message \<text\> | Message to send (required) |
--to \<dest\> | Derive session key from a target (phone, chat id) |
--agent \<id\> | Target a configured agent (uses its main session) |
--session-id \<id\> | Reuse an existing session by id |
--local | Force local embedded runtime (skip Gateway) |
--deliver | Send the reply to a chat channel |
--channel \<name\> | Delivery channel (whatsapp, telegram, discord, slack, etc.) |
--reply-to \<target\> | Delivery target override |
--reply-channel \<name\> | Delivery channel override |
--reply-account \<id\> | Delivery account id override |
--thinking \<level\> | Set thinking level (off, minimal, low, medium, high, xhigh) |
--verbose \<on|full|off\> | Set verbose level |
--timeout \<seconds\> | Override agent timeout |
--json | Output structured JSON |
Behavior
- By default, the CLI goes through the Gateway. Add
--localto force the embedded runtime on the current machine. - If the Gateway is unreachable, the CLI falls back to the local embedded run.
- Session selection:
--toderives the session key (group/channel targets preserve isolation; direct chats collapse tomain). - Thinking and verbose flags persist into the session store.
- Output: plain text by default, or
--jsonfor structured payload + metadata.
Examples
Related
- Agent CLI reference
- Sub-agents — background sub-agent spawning
- Sessions — how session keys work