fix: suggest close CLI commands#91345
Conversation
|
Codex review: passed. Reviewed June 19, 2026, 1:52 AM ET / 05:52 UTC. Summary PR surface: Source +104, Tests +71. Total +175 across 5 files. Reproducibility: yes. for the behavior gap: current main's formatter and early unowned-root path emit generic diagnostics without closest-command hints, and the PR proof shows the after-fix CLI output. Review metrics: none identified. Stored data model Root-cause cluster Members:
Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything. Merge readiness Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch. Next step before merge
Security Review detailsBest possible solution: Land this focused helper through the active exact-head merge/check gates, then close the linked issue once main contains the suggestion behavior. Do we have a high-confidence way to reproduce the issue? Yes for the behavior gap: current main's formatter and early unowned-root path emit generic diagnostics without closest-command hints, and the PR proof shows the after-fix CLI output. Is this the best way to solve the issue? Yes. A shared descriptor-backed helper covering both unknown-root surfaces is the narrow maintainable solution, and it avoids auto-running aliases or changing plugin-policy diagnostics. AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning high; reviewed against 82ae81f3bf1d. Label changesLabel changes:
Label justifications:
Evidence reviewedPR surface: Source +104, Tests +71. Total +175 across 5 files. View PR surface stats
What I checked:
Likely related people:
What the crustacean ranks mean
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics. How this review workflow works
|
514bf6b to
ac79843
Compare
Signed-off-by: Glenn-Agent <[email protected]>
ac79843 to
17baf7f
Compare
|
Follow-up pushed after review cleanup:
GitHub Actions is now running the broader PR matrix on the updated branch. |
|
/clownfish automerge |
|
Clownfish is on the reef for this PR. 🐠 I tagged A maintainer can call |
|
🦞✅ Source: What merged:
Automerge notes:
The automerge loop is complete. Automerge progress:
|
Summary: - The PR adds descriptor-backed CLI command suggestions for unknown root commands, wires them into Commander parse errors and early unowned-root diagnostics, and covers both paths with focused CLI tests. - PR surface: Source +104, Tests +71. Total +175 across 5 files. - Reproducibility: yes. for the behavior gap: current main's formatter and early unowned-root path emit generic diagnostics without closest-command hints, and the PR proof shows the after-fix CLI output. Automerge notes: - PR branch already contained follow-up commit before automerge: fix: suppress suggestions for plugin policy diagnostics - PR branch already contained follow-up commit before automerge: Merge remote-tracking branch 'origin/main' into fix/83999-cli-command… - PR branch already contained follow-up commit before automerge: test: align agent model expectations - PR branch already contained follow-up commit before automerge: test: restore unrelated agent test fixture Validation: - ClawSweeper review passed for head b98f5b5. - Required merge gates passed before the squash merge. Prepared head SHA: b98f5b5 Review: openclaw#91345 (comment) Co-authored-by: Glenn-Agent <[email protected]>
Summary: - The PR adds descriptor-backed CLI command suggestions for unknown root commands, wires them into Commander parse errors and early unowned-root diagnostics, and covers both paths with focused CLI tests. - PR surface: Source +104, Tests +71. Total +175 across 5 files. - Reproducibility: yes. for the behavior gap: current main's formatter and early unowned-root path emit generic diagnostics without closest-command hints, and the PR proof shows the after-fix CLI output. Automerge notes: - PR branch already contained follow-up commit before automerge: fix: suppress suggestions for plugin policy diagnostics - PR branch already contained follow-up commit before automerge: Merge remote-tracking branch 'origin/main' into fix/83999-cli-command… - PR branch already contained follow-up commit before automerge: test: align agent model expectations - PR branch already contained follow-up commit before automerge: test: restore unrelated agent test fixture Validation: - ClawSweeper review passed for head b98f5b5. - Required merge gates passed before the squash merge. Prepared head SHA: b98f5b5 Review: openclaw#91345 (comment) Co-authored-by: Glenn-Agent <[email protected]>
Summary
openclaw updatefor close typos such asupateand explicit adjacent terminology such asupgradeFixes #83999
Real behavior proof
Did you mean this?hint instead of only generic help text.fix/83999-cli-command-suggestionsafter commit96aa8d1714.node scripts/run-vitest.mjs src/cli/program/error-output.test.ts src/cli/run-main.exit.test.ts, plusgit diff --check. I also ran a real source CLI smoke with Corepack's pnpm shim onPATH:After the follow-up commit
96aa8d1714, copied local focused test output also verifies the plugin-policy guardrail remains separate from generic typo suggestions:Earlier terminal output from the after-fix focused test run:
The formatter test asserts this exact output for
upate:The dispatch test asserts the early unowned-root path rejects before proxy/plugin runtime startup while including:
Tests
node scripts/run-vitest.mjs src/cli/program/error-output.test.ts src/cli/run-main.exit.test.tsnode scripts/run-vitest.mjs src/cli/program/error-output.test.ts src/cli/run-main.exit.test.ts src/cli/run-main.test.tsgit diff --check