Skip to content
Finalist

OmniBridge

OmniBridge is an AI agent that identifies unknown serial device protocols autonomously — a workflow that didn't exist a year ago because it needs Opus 4.7's specific capabilities to work.

Core trick

Runs a Claude tool loop where a CRC16 check across byte frames validates inferred structure, then generates local extractors.

Tags

Description

OmniBridge is an AI agent that identifies unknown serial device protocols autonomously — a workflow that didn't exist a year ago because it needs Opus 4.7's specific capabilities to work. Plug in a 1980s weighing scale, a Modbus PLC, or an Arduino sensor. OmniBridge runs Claude as a multi-step agent with six purpose-built tools — for binary streams, one surgical call to analyze_binary_structure validates CRC16 across every frame and returns frame structure, enough evidence to commit with high confidence. Every reasoning step streams live. Once identified, Claude-generated regex (ASCII) or byte-offset extractors (binary) run locally at thousands of packets per second, zero ongoing API cost. Traditional protocol integration: engineer reads vendor docs, writes custom parser, ships glue code — eighteen hours median per device. OmniBridge: five minutes. For $1.2 trillion of legacy industrial hardware stranded outside the cloud, that speedup opens entire new markets. This couldn't work with a smaller model. Adaptive thinking lets Claude spend more compute on binary vs ASCII. Multi-turn tool use with preserved reasoning lets the agent pick a surgical tool and commit. Prompt caching delivers ~65% cache hit on repeat investigations, keeping cost near $0.20 per identification — roughly one-thousandth of the engineer time replaced. Open source, MIT licensed, native desktop app on macOS.
adindamochamad/omnibridge★ 00 forksSvelteMITCreated Apr 23, 2026 · last push Aug 9, 2026

README excerpt

<div align="center">

# ⬡ OmniBridge

### **An AI agent category that didn't exist a year ago.**

OmniBridge identifies any legacy serial device protocol — binary, undocumented, proprietary — in under a minute. It is what industrial integration looks like once models can reason about raw bytes.

![Claude Opus 4.7](https://img.shields.io/badge/Claude-Opus%204.7-D97706?logo=anthropic)
![Tauri](https://img.shields.io/badge/Tauri-2.0-24C8DB?logo=tauri)
![Svelte 5](https://img.shields.io/badge/Svelte-5.0-FF3E00?logo=svelte)
![Rust](https://img.shields.io/badge/Rust-stable-000000?logo=rust)
![CI](https://github.com/adindamochamad/omnibridge/actions/workflows/ci.yml/badge.svg)
![40 tests](https://img.shields.io/badge/tests-40%20passing-22c55e)

*Built for the Claude Opus 4.7 Hackathon 2026 · Problem Statement: **Build For What's Next***

<!-- Replace with real screenshot: 1400×800 capture of the app with Modbus investigation + live Dashboard + cost summary card visible -->
<!-- ![OmniBridge Hero](docs/hero.png) -->

**[▶ Watch the 2-minute demo](https://youtu.be/RX-uGdIQLLU)**

</div>

---

## Why this exists

I work as a backend engineer on IoT systems, including industrial weighing scales (*timbangan*). I have shipped the kind of custom parser OmniBridge replaces — spent days reverse-engineering vendor protocols that didn't match their own documentation, written glue code nobody else will ever touch. The legacy-hardware integration tax is real and I have paid it.

But this is not 

Team