youthe principal claudechief of staff your phonehears everything

Make Claude your chief of staff.

A chief of staff is only as good as what they're read into. Conduit reads Claude into the one device that already hears your whole life — texts, calls, every notification — so it can brief you, dig things up, and (with your say-so) act, while the phone stays in your pocket. And the server in the middle carries it all the way a courier carries a sealed envelope: it can't read a word.

brief me on what I missed find the code my bank just texted text Dana I'm running late who called during the meeting?

Start setup → See exactly what's shared

how a question travels

your claude

asks, over oauth

“messages from Dana?”

conduit hub

holds only sealed data

gU7tKx…J9Q== · aGxTk2…8w==

your phone

owns the only key

⚿ key · lent while connected

step 1 / 4

Claude asks. Your question arrives over OAuth, scoped to your account and nothing else.

AES-256-GCM — encrypted on the phone, before upload key never written to the server's disk lookups match HMAC fingerprints, not text

Ask, and it knows

Reading is the default, and it's the safe half — the worst a message can do is lie. Everything your phone hears becomes something you can just ask about: every app's notifications, SMS/MMS, the call log, contacts, WhatsApp.

you, from your desk

What did I miss while I was heads-down?

claude, from your phone

Actions · your phone has the final say

Give Claude hands. Keep the final say.

Conduit lets your AI actually do things with your phone. Every action starts disabled; you enable only what you want. Consequential ones land on your lock screen as a question, every time — reversible ones (ring, locate, notify) can earn an “always allow.” Watch three requests play out:

The powerless-server test: imagine every line of Conduit's server replaced by an attacker's code. What can it do? Read gibberish. Send requests your phone ignores unless you've enabled them — and even then, consequential ones still wait on your tap. That's the whole design.

2:41thursday, july 3

conduit · now

Allow: send a text to Dana?

“Running late — there in 15.”

Approve Deny

✓

Sent to Danaby your phone · receipt: send_sms · done · 2:41 PM

Setup, in minutes

What setup involves a few minutes · guided · checked at each step

Sign in ~10s

Google, or a shared access code. This spins up your isolated account — the walls that keep your data yours and nobody else's.
Install & pair the app

Sideload the Android APK — allow "unknown sources" once — then scan a pairing code the console shows you. That scan is what proves the app is really yours, and it's where your encryption key is born: on the phone, never uploaded.
Turn on capture

Flip on only what you're comfortable with — notifications, SMS, call log, contacts. Each tier is optional, and every action starts off. History back-fills on its own, already encrypted.
Connect Claude

Paste your personal MCP URL into Claude's connectors and approve once. From then on you just ask — "what did I miss while I was out?", "read me the 2FA code from my bank", "any packages today?"

Android only — sideloaded APK; iOS exposes none of these APIs. Your data exports as JSON or hard-deletes in one click, no support ticket.

Start setup →

What's shared where

Conduit is built assuming its own server will someday be hacked — so the server holds nothing readable and no authority. Don't take that on faith: here is the actual inventory, and every line of it is a behavior you can check.

	your phoneyours, in your hand	conduit hubassume it's compromised	your claudevia oauth, your account only
Your messages	plaintextWritten and read in the clear — it's your phone.	ciphertextAES-256-GCM, sealed before upload. A breach gets `gU7tKxbA…J9Q==`.	while connectedDecrypted answers, only while your phone is online.
The encryption key	born hereGenerated on-device, kept in the Android Keystore.	borrowedRides the live connection, evaporates when it closes. Never in the database, never in a backup.	neverClaude sees answers, not keys.
Who messages you	names & numbersYour contacts stay contacts.	fingerprintsAn HMAC per sender — enough to find a thread, not enough to read who it is.	while connectedNames resolve when you ask about a person.
Doing things texts · calendar · alarms	you decideOff by default. Consequential actions ask on your lock screen, every time.	relay onlyForwards the request; keeps a receipt — action, outcome, time. Never the contents.	may askCan request. Can't insist.
Photos & attachments	originalsStay on the phone.	private bucketServed only through links that expire within the hour.	expiring linkA signed URL that dies in 60 minutes.

Check it, don't trust it. Disconnect your phone and watch reads lock — the demo up top is real behavior, not an illustration. The audit receipt really is three fields. The source is open, and your data exports or hard-deletes in one click.

Messages are untrusted input. Anyone who can text you can plant instructions for your AI. Conduit marks message content as data, never instructions — and the action system above is why a planted instruction still can't hurt you.