Best possible solution:

Rebase on current main, keep the merged --message-file implementation and /compact guard, then add stdin as an additive input mode with docs, focused tests, and redacted real terminal proof.

Do we have a high-confidence way to reproduce the issue?

Not applicable as a bug reproduction; this PR adds a new CLI input mode. The review blockers are source-reproducible by comparing current main with the PR head and the merged file-only PR.

Is this the best way to solve the issue?

No. The right shape is to add stdin on top of the current main resolver, not reimplement the now-merged file-message path or bypass the current /compact guard.

Full review comments:

• [P1] Preserve the merged file-message contract — src/commands/agent-via-gateway.ts:268
  Current main already has --message-file and tests that it preserves multiline content and a trailing newline after BOM removal while rejecting invalid UTF-8. This resolver trims every source and reads files with non-fatal UTF-8 decoding, so resolving the conflict by keeping this path would regress the merged file-input contract.
  Confidence: 0.94
• [P1] Keep the /compact guard after resolving input — src/commands/agent-via-gateway.ts:925-926
  Current main rejects /compact after message-file resolution and before Gateway or embedded dispatch. This branch proceeds from resolved input into dispatch without that guard, so /compact sent through inline, file, or stdin input can return to the false-success no-op path.
  Confidence: 0.91
• [P2] Document stdin wherever agent inputs are documented — src/cli/program/register.agent-turn.ts:39
  The PR adds --message-stdin as a public openclaw agent input source, but current public docs only describe --message and --message-file. If stdin remains in scope, update the CLI and tool docs with the exact mutual-exclusion and empty-input behavior.
  Confidence: 0.9

Overall correctness: patch is incorrect
Overall confidence: 0.92

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 477b27b6f87e.

Label justifications:

• P2: This is a normal-priority public CLI feature with limited blast radius and no urgent production regression signal.
• merge-risk: 🚨 compatibility: A bad conflict resolution can break current users of the already-merged --message-file path and reintroduce the /compact false-success behavior.
• rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🧂 unranked krab and patch quality is 🧂 unranked krab.
• status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask. Needs real behavior proof before merge: The external PR needs real behavior proof before merge; the body lists commands and claimed smokes but no inspectable after-fix output or artifact for stdin/file behavior. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.

PR surface:

Source +88, Tests +57. Total +145 across 4 files.

What I checked:

• Current main input surface: Current main already registers --message-file for openclaw agent but has no --message-stdin, so the file portion is implemented while stdin remains the unique part of this PR. (src/cli/program/register.agent-turn.ts:37, 477b27b6f87e)
• Current main file-message contract: Current tests assert that --message-file removes an optional BOM, preserves multiline content and the trailing newline for Gateway and local dispatch, and rejects invalid UTF-8 before dispatch. (src/commands/agent-via-gateway.test.ts:311, 477b27b6f87e)
• Current main compact guard: Current main resolves message input, then rejects /compact CLI agent messages before Gateway or embedded dispatch to avoid the historical false-success no-op path. (src/commands/agent-via-gateway.ts:905, 477b27b6f87e)
• PR head reimplements message input: The PR head adds stdin support but also reads files with readFileSync(..., "utf8") and trims the resolved raw message, which would not preserve the merged file-message contract if used during conflict resolution. (src/commands/agent-via-gateway.ts:214, 8e58aef1685c)
• PR head dispatch path: The PR head resolves message input and proceeds to session normalization without the current-main /compact rejection in the shown path. (src/commands/agent-via-gateway.ts:925, 8e58aef1685c)
• Current docs: The public agent docs document --message and --message-file, but not --message-stdin; stdin would need docs if it remains in scope. Public docs: docs/cli/agent.md. (docs/cli/agent.md:26, 477b27b6f87e)

Likely related people:

• ooiuuii: Authored the merged file-only agent CLI PR that now owns the current --message-file behavior this branch overlaps. (role: feature introducer; confidence: high; commits: 4897f2fc2005, a0fedcfb7e53; files: src/commands/agent-via-gateway.ts, src/commands/agent-via-gateway.test.ts, src/cli/program/register.agent-turn.ts)
• Alix-007: Authored the merged sessions compact PR that added the current CLI /compact rejection this PR must preserve after message-source resolution. (role: adjacent invariant introducer; confidence: high; commits: 13b4d49fa213, e35e5f123dda; files: src/commands/agent-via-gateway.ts, src/commands/agent-via-gateway.test.ts, docs/cli/sessions.md)
• vincentkoc: Merged the file-only agent message-file PR, which makes them relevant for routing questions about preserving that public CLI contract. (role: merger/reviewer signal; confidence: medium; commits: a0fedcfb7e53; files: src/commands/agent-via-gateway.ts, docs/cli/agent.md, docs/tools/agent-send.md)
• sallyom: Merged the sessions compact PR that introduced the /compact guard now affected by this branch's stale dispatch path. (role: merger signal; confidence: medium; commits: e35e5f123dda; files: src/commands/agent-via-gateway.ts, src/commands/agent-via-gateway.test.ts)

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

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.

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.