otp bridge.
An illuminated glass inbox with paper envelopes floating around it. Original illustration; no live inbox data.
OPEN SOURCE / FOR YOUR BROWSER AND AGENTS

OTP BRIDGE — OPEN SOURCE

Your phone gets
the code.
You stay here.

SMS and email. One private bridge.
Matching login codes fill in Chrome.
Your agents can use the same inbox.

CONNECT ONCE. KEEP YOUR FLOW. SELF-HOSTED.

THE LAST MILE OF A LOGIN

Let the code find the workflow.

ONE INBOX, A FEW WAYS IN

Your messages.
Your next step.
One less interruption.

Connect your capture source and Chrome helper once. New arrivals appear even with the panel closed. Your saved connection survives Chrome restarts.

01 / CAPTURE

Your phone.
Off the critical path.

Bring iPhone SMS and Gmail into your own short-lived inbox. Phone capture depends on your configured trigger; Android has a Tasker recipe.

iPhone setup ↗Android recipe ↗
02 / CHROME

The right code.
Already on the page.

Grant website access once. One fresh matching login code fills on the selected page. Save site exceptions, see arrivals, or explicitly open an approved email sign-in link.

Set up Chrome autofill ↗Sign-in links ↗

USEFUL TODAY. ROOM TO GROW.

More than copying codes.
Clear choices at every step.

This broader pilot is included in the main branch. Self-host it and load the unpacked helper; there is no hosted signup or store listing.

OWNER CHOICE / AVAILABLE

Payments.
Your saved choice.

Keep payment codes manual, fill them, or fill and submit. Enable this separately. Filling alone can authorize a charge on some bank pages. Recovery, transfers and withdrawals stay manual.

Payment behavior and limits ↗
SMS AI / OBSERVATION ONLY

Understand messages.
Compare before acting.

Optional AI predicts message type and code beside the existing parser. It sends whole SMS text to OpenAI and keeps comparison totals in the bridge. It never selects a fill code. Enabled on the maintainer pilot; off by default for new installs.

AI data flow and limits ↗
MESSAGE ACTIONS / ROADMAP

A receipt today.
A useful next step tomorrow.

Receipt categories, transaction lookup and named message rules are the next direction. They are not shipped actions. A URL in a message is never permission to open it or run an automation.

See the product direction ↗

FORK IT. MAKE IT YOURS.

Not another service.
Your own little tool.

Copy the setup prompt into Codex or Claude Code. Your agent handles the computer-side setup; you handle phone taps and required consent.

Read the full deployment guide ↗
LET YOUR AGENT DO THE SETUP

Paste into Codex or Claude Code. The complete README prompt, ready to go.

Read the full prompt
OR START MANUALLYmacOS / Linux
git clone https://github.com/bnishit/otp-inbox.git
cd otp-inbox
python3 scripts/setup.py \
  --url http://127.0.0.1:8787
bun --env-file=.local/server.env run server.ts

In a second terminal: python3 scripts/smoke.py

iPhone: generated Shortcut + personal Message automation.

SMALL BY DESIGN. HONEST ABOUT THE EDGES.

A small tool.
With clear boundaries.

Short-lived copies

At most ten minutes, or sooner when validity is shorter. Originals stay in your mail and messages. Agent/provider history has its own rules.

Trust the agent you connect

Every reader key can access your captured inbox. Match before claim. Retrieval alone does not authorize a payment or security change. Payment filling is a separate saved owner choice; it defaults off.

Personal scale

One owner, one replica, memory storage. A restart resets claims. Capture can miss messages. Keep Gmail polling as backup and watch-renewal driver.

Proof, not promises

The maintainer pilot completed a Blinkit SMS login; the owner reports a successful Amazon purchase OTP test. Local coverage: 87 Bun tests plus synthetic browser checks. Android and native OS banner delivery still need live proof.

Read the security model and limits ↗

LESS FETCHING CODES. MORE GETTING THINGS DONE.

Fork it.
Keep your flow.

Get OTP Bridge on GitHub ↗

MIT licensed · No hosted service · No public inbox