Clawpilot Send

3. If only one runtime is paired on the host, run:

clawpilot send "/absolute/path/to/file"

4. If both OpenClaw and Hermes are paired on the same host, run:

clawpilot send --runtime <openclaw|hermes> "/absolute/path/to/file"

Rules

• Always use an absolute path.
• Only send files smaller than 20 MB.
• If the file is larger than 20 MB, do not call clawpilot send; tell the user it is too large for PocketClaw delivery.
• Let clawpilot handle upload, routing, and assistant-message delivery internally.
• Do not mention sessionKey, runId, relay routes, or low-level payloads.
• Do not invent clawpilot send flags or options.
• When the current PocketClaw conversation clearly identifies the runtime, always use the matching --runtime if multiple runtimes are paired.
• If multiple files should be sent, send them one by one unless the current workflow clearly supports bundling.

Fallback

If the conversation is not clearly PocketClaw / relay:

• Do not call clawpilot send.
• Reply normally for the current channel.

Incorrect Behavior

• Replying only with a local file path
• Uploading a file without delivering it through clawpilot send
• Guessing that a session is PocketClaw without confirming the session label