How to use Codex to inspect serial hardware
Codex inspected an ESP32-S3 through OpenBaud, captured serial bytes and built reusable commands. Logged writes and acknowledgement gates kept work auditable.
reddit.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Inspect this serial device through OpenBaud. Enumerate USB metadata, retain raw RX/TX captures, infer framing and CRC from evidence and promote only verified byte sequences into reusable commands. Log every write and request acknowledgement before any dangerous command.
Reach people exploring AI agents
See placements →What happened
A physical ESP32-S3 serial inspection was demonstrated with raw captures, telemetry and reusable commands. A replay capture is public; arbitrary-device support is not established.
Reported by OneMasterpiece1717 — RedditHow the agent did it
- Codex enumerated device metadata and captured raw serial traffic through OpenBaud.
- It inferred protocol structure and visualized telemetry from the physical ESP32-S3.
- Verified sequences became YAML commands while writes remained logged and gated.
Where a person stepped in
The author used a physical ESP32-S3 demonstration and required explicit acknowledgement for dangerous writes; raw captures and write logs remained available.
The OpenBaud author demonstrated Codex inspecting a real ESP32-S3 over serial through a Rust MCP server and plugin. The project addressed a specific gap: an agent could produce firmware but lacked a controlled way to inspect the device already sitting on the developer's desk.
In the recorded workflow, Codex enumerated USB metadata, preserved raw transmitted and received bytes, inferred a CRC-protected binary protocol and visualized telemetry. Verified byte sequences became reusable YAML commands rather than being discarded as one-off terminal experiments.
The interface retained an audit trail. Every write was logged, raw captures stayed accessible and dangerous commands required explicit acknowledgement. The repository also included a byte-exact capture so another developer could replay parser and command behavior without owning the demonstration hardware.
The concrete result is a demonstrated device-inspection loop and published tooling with reusable commands and replay evidence. It is not evidence that any unknown serial protocol can be decoded automatically. The author specifically sought feedback about installation and the write-safety boundary, so those remained review topics rather than established guarantees. Codex handled investigation through exposed tools while the surrounding system constrained and recorded device writes.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Reddit · OneMasterpiece1717
Frequently asked questions
What device was demonstrated?
A physical ESP32-S3 with a CRC-protected binary protocol.
Can the workflow be inspected without hardware?
The repository supplies a byte-exact capture for replay.
How were writes controlled?
Every write was logged and dangerous commands required explicit acknowledgement.
More details
About this account
Codex enumerated device metadata and captured raw serial traffic through OpenBaud. It inferred protocol structure and visualized telemetry from the physical ESP32-S3.
Original author showcase and README opened. The account demonstrates a serial workflow and supplies replay captures; no arbitrary-device protocol support or safety certification is inferred. Suggested prompt written by Agents In Use; no original task prompt was published in the verified account.
Credit: OneMasterpiece1717 — Reddit
Source published 25 Aug 2026
Source checked 14 Oct 2026
Tools and topics
Codex · OpenBaud · Rust · MCP · ESP32-S3
Serial inspection · Auditable commands
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.