Bring your own
<AI>

Use AI tools with your existing Claude subscription — no signup, no second bill, no data leaving your machine.

for anyone running a Claude Code CLI today · Chrome · Node ≥ 20 · macOS

↓ live runs — real wrapps, running on your own AI

adforge.app on your Claude
ran on your machine:8787
provider
model
context
data
tools it used

// what it means

Every AI app today vs. this.

every ai app today
  • Sign up again
  • Pay again
  • Reconnect tools
  • Re-explain brand
  • Data on their servers
with switchboard
  • Just open it
  • Same subscription
  • Tools already work
  • Context loads in
  • Stays on your machine
One subscriptionApps run on the AI you already pay for. No per-app pricing.
Zero setupEvery tool you've connected works instantly, everywhere.
Data stays homeApps see only what you hand them. Nothing else leaves.
Work travelsBuild a brand in one app. Use it in every other.

// how the call gets connected

Operator, patch me through

01

Install

One extension, one tiny app. They find each other.

$ switchboard
[░░░░░░░░░░░░░░] 0%
connected ✓ runs on your machine
02

It gathers what's yours

Your AI, your tools, your work — in one place.

your claude subscription
gmail · sheets · github
your projects & brands
03

Apps ask. You decide.

Looking is pre-approved. Changing anything asks first.

ad maker wants
your ai · one brand
APPROVE deny

// trust model

Approval, or
it doesn't happen.

  • One front doorEvery request passes the same checkpoint. There is no back door.
  • Look, don't touchApps can look within what you granted. Changing anything asks first, every time.
  • Choosing is the permissionHand an app one brand — it never learns the rest exist.
  • Take-backs are instantRevoke an app, a tool, or everything. One tap.
Wrapp store · runs on your own AI

Apps that bring nothing but the interface.

Every wrapp runs on your own Claude and your tools — the operator never holds a key or sees your data. Open one and it just works.

Open the store →

// who it's for

One board, two sides.

Whether you open wrapps or build them, the deal is the same — the runtime is yours.

// for you

Open it. It just runs.

Every app runs on the AI you already pay for.

  • No new signupopen a wrapp and start — nothing to create
  • No second billit runs on your existing Claude subscription
  • Your data stays homethe app sees only what you hand it
Browse wrapps → Install →

// for builders

Ship the interface. Skip the backend.

Publish a wrapp as static files. Your users bring the model, tools and data.

  • No server, no keysyou never run a backend or hold a credential
  • No inference billthe visitor's own AI runs it — free to serve
  • Port or build freshbring an open-source app, or start new
  • Earn what runsusage-based payouts for publishers — on the roadmap
Build a wrapp → The repo →

// patch yourself in · ~5 minutes

Try it today.

Two pieces: the extension in your browser, the sidekick on your machine. Then any wrapp runs on your Claude.

01

Add the extension

One click — Switchboard is on the Chrome Web Store.

chromewebstore.google.com Add to Chrome Switchboard in your toolbar
02

Run the sidekick

The local daemon that holds your Claude. It prints a pairing token.

$ git clone https://github.com/sameeeeeeep/switchboard $ cd switchboard $ npm install && npm run build $ npm run sidekick pairing token: ····-····
03

Pair & connect

Paste the token into the extension, open a wrapp, click Connect.

extension → paste token open a wrapp ↓ Connect Switchboard running on your Claude

Prefer your coding agent to set it up? Point it at the runbook — it audits the MIT source first, then installs, stopping at every step it can't take.

Install with your agent →

// the board is live

Patch yourself in.

The cloud was someone else's computer.
This one is yours.