If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
### 💡 Codex Review
Here are some automated review suggestions for this pull request.
**Reviewed commit:** `d0d67307c2`
<details> <summary>ℹ️ About Codex in GitHub</summary>
<br/>
[Your team has set up Codex to review pull requests in this repo](http://chatgpt.com/codex/settings/general). Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
</details>
Remove unsupported --local-only invocation from acceptance criteria
The AC here requires tools/ai/zeroclaw_dual_chat.sh <repo> --local-only --provider-check, but tools/ai/zeroclaw_dual_chat.sh does not implement a --local-only flag (usage only lists --hardware, --provider-check, --cheap, and the parser falls back to usage/error for unknown first options). As written, operators following this spec cannot reproduce the claimed check and will hit a failure path instead of enforcing local-provider-only behavior.
Useful? React with 👍 / 👎.
**<sub><sub></sub></sub> Remove unsupported --local-only invocation from acceptance criteria**
The AC here requires `tools/ai/zeroclaw_dual_chat.sh <repo> --local-only --provider-check`, but `tools/ai/zeroclaw_dual_chat.sh` does not implement a `--local-only` flag (usage only lists `--hardware`, `--provider-check`, `--cheap`, and the parser falls back to usage/error for unknown first options). As written, operators following this spec cannot reproduce the claimed check and will hit a failure path instead of enforcing local-provider-only behavior.
Useful? React with 👍 / 👎.
Replace ineffective port-hint vars with supported upload settings
These evidence commands rely on ZEROCLAW_ZACUS_UPLOAD_PORT_HINT and ZEROCLAW_RTC_UPLOAD_PORT_HINT to lock board-to-port mapping, but tools/ai/zeroclaw_hw_firmware_loop.sh only reads ZEROCLAW_UPLOAD_PORT (or --port) and otherwise auto-detects from pio device list; it never consumes either hint variable. That means the documented procedure does not actually enforce the claimed mapping fix and can still select the wrong serial device during hardware loops.
Useful? React with 👍 / 👎.
**<sub><sub></sub></sub> Replace ineffective port-hint vars with supported upload settings**
These evidence commands rely on `ZEROCLAW_ZACUS_UPLOAD_PORT_HINT` and `ZEROCLAW_RTC_UPLOAD_PORT_HINT` to lock board-to-port mapping, but `tools/ai/zeroclaw_hw_firmware_loop.sh` only reads `ZEROCLAW_UPLOAD_PORT` (or `--port`) and otherwise auto-detects from `pio device list`; it never consumes either hint variable. That means the documented procedure does not actually enforce the claimed mapping fix and can still select the wrong serial device during hardware loops.
Useful? React with 👍 / 👎.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
watcher 1min + realtime log
spec_kit sync
ai-agentic-embedded-base/specs/04_tasks.mdai-agentic-embedded-base/specs/zeroclaw_dual_hw_todo.mdValidation context
bash -n+shellcheckon watcher/stack/webhook/chat scripts already green.3000/health,8788/,8788/realtime_1min.log,9090/-/ready.💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:
d0d67307c2ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
@@ -29,0 +66,4 @@- Status: `2026-02-21` done.- [x] T-103 - Upload + monitor RTC (forced default)- AC: `pio run -e esp32dev -t upload` puis monitor 60s executes.The AC here requires
tools/ai/zeroclaw_dual_chat.sh <repo> --local-only --provider-check, buttools/ai/zeroclaw_dual_chat.shdoes not implement a--local-onlyflag (usage only lists--hardware,--provider-check,--cheap, and the parser falls back to usage/error for unknown first options). As written, operators following this spec cannot reproduce the claimed check and will hit a failure path instead of enforcing local-provider-only behavior.Useful? React with 👍 / 👎.
@@ -29,0 +79,4 @@- [x] T-201 - Discover hardware Zacus- AC: au moins un port detecte pour carte Zacus.- Evidence: `tools/ai/zeroclaw_dual_chat.sh zacus --hardware`These evidence commands rely on
ZEROCLAW_ZACUS_UPLOAD_PORT_HINTandZEROCLAW_RTC_UPLOAD_PORT_HINTto lock board-to-port mapping, buttools/ai/zeroclaw_hw_firmware_loop.shonly readsZEROCLAW_UPLOAD_PORT(or--port) and otherwise auto-detects frompio device list; it never consumes either hint variable. That means the documented procedure does not actually enforce the claimed mapping fix and can still select the wrong serial device during hardware loops.Useful? React with 👍 / 👎.