The help text has always shown --query as the way to pass a search term:

openclaw memory search --query "deployment notes"

But the subcommand only registered a positional argument, so anyone following the docs got:

error: unknown option '--query'

This change makes both forms work:

• openclaw memory search "deployment notes" (positional — unchanged, still works)
• openclaw memory search --query "deployment notes" (flag — now accepted)

If neither is provided, a clear error message is emitted. The implementation resolves the query with queryArg ?? opts.query, so the two forms are fully equivalent.

Closes #25857

Greptile Summary

Adds support for the --query flag in the openclaw memory search command, matching the documented help text. The implementation correctly makes both forms equivalent: positional argument (openclaw memory search "term") and flag-based (openclaw memory search --query "term"). The code properly validates that at least one form is provided.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The change is minimal, focused, and correctly implements the documented behavior. The logic properly handles both positional and flag forms with appropriate error handling. Import reordering follows TypeScript conventions. No breaking changes or security concerns.
• No files require special attention

_{Last reviewed commit: 81e9c87}