Summary

When copying long UUIDs from OpenClaw chat responses (including fenced code blocks), spaces are inserted into the UUID. This breaks commands like openclaw cron run --id ....

Impact

Users cannot reliably copy/paste job IDs from assistant messages. CLI commands fail due to malformed IDs.

Example malformed copy from chat:

• expected: e01afbad-b2ce-4a0e-a5db-f1affdb3b806
• copied: e01afbad-b2ce-4a0e-a5db-f1affdb3 b806

Also observed in variable assignment snippets where long tokens get split with spaces.

Repro

1. In OpenClaw webchat, ask assistant for a command containing a long cron job UUID.
2. Copy command directly from rendered message/code block.
3. Paste into terminal.
4. Observe inserted spaces in UUID token and command failure.

Expected

Copy/paste should preserve exact token content with no inserted whitespace.

Actual

Whitespace appears inside long tokens (UUID), often around wrap boundaries.

Workarounds

• Use job-name lookup (openclaw cron list --json ...) instead of direct UUID copy.
• Strip spaces manually (ID="${ID// /}").

Environment

• OpenClaw: 2026.2.26
• Surface: webchat (direct chat)
• Host: macOS