AC status-bar remote: high-reach vibe demo (REA not named in source)
Not every viral reverse-and-vibe remote was built with REA. This card keeps the attribution honest: a popular status-bar air-conditioner control demo, hosted here as a parallel scene beside REA-named cases.
Attribution honesty (read first)
The source post does not name REA. rea.run must not fabricate “built with REA.” We present it as community RE / vibe-remote inspiration in the same product shape as other own-device status-bar remotes.
Public metrics (snapshot)
| Metric | Figure | Note |
|---|---|---|
| Views | ~1.07M | Author post at capture |
| Likes | ~18.8k | Snapshot 2026-10-12 |
| Bookmarks | ~5.9k | Snapshot 2026-10-12 |
| Source | @icanberk | Self-hosted clip; no REA claim |
What you can learn anyway
- Status-bar / menu-bar remotes are a sticky UX for home devices.
- Short silent clips travel far as social proof.
- When you *do* use REA on your own AC bridge / app, follow the same legal boundary as our toilet BLE case: own device, Evidence first, no third-party attacks.
If you want a REA-named twin
See @thinkszyg toilet BLE remote where the author does name Codex + REA.
Compliance reminder
Control only equipment you own or are authorized to automate. Do not scrape or attack vendor clouds without permission.
Compliance
Own or authorized HVAC / IoT only. This card is social-proof of the status-bar remote pattern, not an REA success claim and not a guide to attack third-party systems.
Takeaways
- High reach ≠ REA attribution — label sources honestly.
- Useful as parallel inspiration next to REA-named cases.
- Own-device remotes still need authorization discipline.
Related on rea.run
More on-site cases