Summary

• Both acp and acp client declared their verbose flag as "--verbose, -v" (long flag first)
• Commander.js requires short flag first: "-v, --verbose". With reversed order, the -v alias is silently dropped and the parsed option key is malformed
• Every other short-flag option in the codebase (skills-cli.ts, hooks-cli.ts, completion-cli.ts, etc.) correctly uses "-v, --verbose"

Files changed: src/cli/acp-cli.ts — lines 48 and 99

Test plan

• Run openclaw acp -v and verify it enables verbose mode (previously silently ignored)
• Run openclaw acp client -v and verify the same
• Run openclaw acp --verbose and verify it still works
• Lint/format pass

🤖 Generated with Claude Code

Greptile Summary

Fixes Commander.js option flag order for verbose flags in acp and acp client commands. Previously declared as "--verbose, -v" (long first), which causes Commander.js to silently drop the -v alias. Changed to "-v, --verbose" (short first) to match the pattern used throughout the rest of the codebase (skills-cli.ts, hooks-cli.ts, completion-cli.ts, etc.).

• Corrects src/cli/acp-cli.ts:48 for the main acp command
• Corrects src/cli/acp-cli.ts:99 for the acp client subcommand
• Enables openclaw acp -v and openclaw acp client -v to work as expected
• No functional changes to the verbose behavior itself, only fixes the CLI parsing

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The fix is straightforward and correct - it simply reorders flag declarations to match Commander.js requirements and align with the rest of the codebase. The change is minimal (2 lines), doesn't alter any logic, and fixes a real bug where -v was silently ignored. Existing tests verify the verbose flag forwarding works correctly, and the fix follows the established pattern used in all other CLI files.
• No files require special attention

_{Last reviewed commit: 68785a4}