openclaw - 💡(How to fix) Fix Triage bot closed #76276 against its own Codex "keep open" verdict [1 comments, 2 participants]

Filing this as a process thing, not a code bug.

I filed #76276 on Saturday — a cron-runId tracking gap with a wire-level repro and source-code citations. A couple hours later clawsweeper[bot] wrote a Codex review on it. The verdict was, verbatim:

"Keep open: current main returns a manual:... run ID from cron.run, but that ID is not carried into cron finished events, the JSONL run log, the protocol schema, or the history reader, so this is a distinct follow-up..."

Two hours after THAT, the same bot closed the issue. state_reason completed. Today openclaw-barnacle[bot] locked it.

A few things are off.

The Codex verdict (keep open) and the bot's auto-close action disagree. Both are nominally clawsweeper[bot], just running in different code paths and reaching opposite conclusions on the same issue. That's an automation defect.

state_reason completed is wrong — the bug isn't completed, it's still in main, and the Codex review on the issue says so.

The lock-after-close policy means I can't push back on #76276 itself. I'd be commenting there right now if it weren't locked.

Two things that'd probably help:

• gate the auto-close on the Codex verdict. if Codex says keep open, don't close.
• don't auto-lock issues whose closure came from a bot with state_reason: completed, at least not until a human signs off.

For what it's worth the cron-runId bug from #76276 is still real and reproducible. Happy to re-file it as a fresh issue if that's the right path. But the meta-pattern felt worth surfacing first — it probably buries other valid reports and the original reporter doesn't see any of it happen.