case-study 2026-10-12 x-casebluetoothwechat-miniprogramcodexauthorized-device

Status-bar toilet remote: REA + Codex on a WeChat miniprogram BLE protocol

A public X post shows what “agent + REA on hardware you already own” can look like: recover the BLE control path from a WeChat miniprogram, then ship a tiny desktop remote that opens/closes the lid from the menu bar.

Source meta

— GitHub stars (snapshot)

Language: —

License: —

Updated: —

GitHub source: —

rea.run rating

5/5 — REA + Codex BLE remote (own device)

Quality. Clear REA+Codex story with demo video on authorized hardware.

Evidence. Public X post + self-hosted clip; ~30 min vibe remote claim by author.

Limits. One creator’s workflow — not a universal BLE tutorial or product endorsement.

For. Builders with own smart-home devices and authorized miniprogram assets.

Author demo: desktop status-bar remote flipping a toilet lid over BLE (self-hosted; from @thinkszyg post).

Public metrics (snapshot)

Metric	Figure	Note
Views	~10.9k	Author post at capture
Likes	52	Snapshot 2026-10-12
Bookmarks	47	Snapshot 2026-10-12
Source	@thinkszyg	Self-hosted clip on rea.run

What happened (paraphrase)

The author describes using Codex + REA to reverse the Bluetooth protocol exposed by a WeChat miniprogram that controls a smart toilet, then vibing a native status-bar remote in about half an hour so a laptop can flip the lid without opening the phone app.

Steps you can mirror (authorized device only)

Confirm the toilet / hub / miniprogram assets are yours or written-authorized.
Install REA into Codex (or another MCP host): npx rea-agents@latest setup — see /docs/install/.
Point the agent at the miniprogram package / captured BLE traffic you are allowed to keep.
Ask for Evidence: GATT services, characteristic UUIDs, write payloads for open/close — mark unknowns.
Rebuild a minimal native remote (status-bar / menu-bar) that only sends the recovered writes.
Verify on your hardware; do not publish secrets that unlock other people’s units.

Checklist

[ ] Ownership / authorization documented
[ ] REA doctor green on the host
[ ] Evidence cites concrete UUIDs / payloads (or honest unknowns)
[ ] Remote scoped to your device pairing
[ ] No DRM / account-bypass framing

Why it is on rea.run

It is a concrete, lawful “own device + agent + REA” story with a watchable demo. We host the video ourselves so the case wall does not depend on X CDN.

Compliance

Lawful RE only: reverse protocols on devices and miniprogram assets you own or are authorized to analyze. Do not attack third-party accounts, DRM, or neighbors’ hardware. Demo is the author’s own setup.

Takeaways

Own-device BLE remotes are a legitimate REA teaching shape.
Demand Evidence (UUIDs, payloads) before shipping vibes.
Self-host community clips — never hotlink X media.

Related on rea.run