Preflight checklists for common OpenClaw operations.
Browser preflight: - Can web_fetch do it? If yes, don’t automate UI. - If using Chrome relay: confirm tab is attached (badge ON). - Use snapshot + stable refs (aria) before clicking. - Avoid blind waits; wait on a specific UI state. - After action: re-snapshot to confirm result.
exec preflight: - Confirm working directory. - Print the exact command. - Prefer non-destructive flags first. - If deleting/resetting: ask for confirmation. - Capture errors and paste the key lines.
Messaging preflight: - Show the exact message text. - Confirm destination (channel/user). - If it’s a group: keep it short and non-spammy. - After send: return NO_REPLY to avoid duplication.
Secrets checklist: - Search for tokens/keys in recent output. - Ensure .gitignore covers key files and build artifacts. - Don’t paste gateway tokens or API keys into chats. - If a secret was pasted: rotate it.