BRIDGIT / DEMO

The Bridgit demo

When you pair an AI agent with your phone, the agent offers to show you what it can do. This page lists every step of that demo, the questions it asks you, and the Bridgit feature each step shows off.

2scripts: a fixed first-run tour, then a menu

6items in the first-run tour, about 5 minutes

19demos in the menu, picked by 4 questions

21Bridgit features shown across both

Review: what goes wrong
How the demo starts
First-run tour
The menu
Features covered

On the phone the owner sees and taps a card In chat happens in the agent's chat only Both the phone acts, the result comes back in chat

Review: why the demo often skips the phone

Reviewed 1 November 2026 against the app source (Demos.kt, SelfDescription.kt, McpProtocol.kt) and demo/SKILL.md. The first-run tour is built on cards, but most agents never reach it.

1. Agents are given two demos and can pick the one without cards

The setup prompt ends with "Offer the owner a demo: bridgit.cc/demo/SKILL.md (or GET /v1/demo)". The first is the card-driven tour; the second is the menu, which asks its questions in chat and only mentions cards when the owner isn't in the chat.

Fix: one entry point. The setup prompt names only the first-run tour; the menu is offered at the end of it.

2. MCP agents only ever see the menu

Over MCP, the demo tool returns the menu (GET /v1/demo). The MCP instructions never mention the first-run tour, and reading it needs a web fetch of bridgit.cc that many agents can't make.

Fix: the phone serves the first-run tour itself (the demo tool returns it first), so no web access is needed.

3. The menu's results come back in chat, not on the phone

Only 4 of the 19 menu demos show the owner a card. Another 4 make the phone do something (speak, flash, ring, go quiet). The other 11 take a photo, record, or read a sensor and describe the result in chat; the owner holding the phone mostly sees a capture notification.

Fix: every demo ends with a card on the phone showing what the agent got: the photo, the transcript, the map point, with buttons to react.

4. Several menu demos are weak actions

Phone status, Where am I, Focus mode and Flashlight are a single read or toggle with nothing to react to. City tour can't be started by the agent at all. These are marked in amber in the menu table.

Fix: fold the reads into a richer demo (one card showing battery, location and heading together) and drop City tour from the menu until an agent can start it.

5. Two first-run items depend on setup or exact timing

Come when called needs the owner to add a wake word in Bridgit and maybe download a 40 MB speech model mid-demo. Rock paper scissors needs the photo to land right after the spoken "shoot", which fails on a silenced phone or a slow network.

Fix: move the wake word to the end as an optional extra, and let the owner tap a "Shoot" button on a card instead of relying on speech timing.

How the demo starts

A
The owner pairs an agent On the phone
Bridgit writes a setup prompt with the agent's own key. The owner pastes it into Claude, ChatGPT, Gemini, Grok or another agent.
Features
pairingper-agent key
B
The agent's first test In chat
The agent calls GET /v1/health, then POST /v1/me with its model name so its card in Bridgit shows it.
Features
healthme
C
The agent offers a demo In chat
"I'm connected to your phone. Want a five-minute demo? It runs on your phone." If the owner says no, it stops. An agent running in the background skips this line and sends the opening card straight away.
Then
The first-run tour for a new owner, the menu afterwards.

The first-run tour

Source: bridgit.cc/demo/SKILL.md. The phone drives it: before each item a card says what's next, and the owner taps Do itSkipEnd demo. Tapping Do it is the owner's OK for that item's photos. The six items tell one story: I can get your attention, see, ask, talk back, come when called, and play.

–
Get ready, quietly In chat
The agent reads GET /v1/capabilities and drops any item whose feature is off or not ready, so the agenda only lists what will work.
Features
capabilitiesevents
▶
The opening card On the phone
Bridgit demo: 6 things, about 5 minutes1. Flash the light · 2. Take a photo · 3. Ask and answer out loud · 4. Come when called · 5. Rock paper scissors · 6. How am I feeling?
StartNot now
Question
Start the demo now?
Calls
POST /interactions (question), then GET /interactions/{id}?wait=55 until answered
Features
interactions · questionbuttons
1
Item 1: Flash the light On the phone

Step card: "I'll blink your phone's light. Look at it." The torch blinks three times, one second each, and always switches itself off.

Owner does
Looks at the phone.
Calls
POST /flashlight {"on":true,"auto_off_seconds":1} ×3
Features
flashlightauto-off safety
No torch
Becomes "Say hello": the phone says hello out loud (speaker).
2
Item 2: Take a photo Both

Step card: "Unlock your phone and point the back camera at something near you: your desk, a plant, a mug." The agent takes the photo and names one detail the owner won't expect it to catch: a brand, the time on a clock, a label.

Owner does
Points the phone, taps Do it.
Calls
POST /camera/snapshot {"camera":"rear"}
Features
cameracapture notification
3
Item 3: Ask and answer out loud On the phone
Did I see that right?"I think this is a blue mug on a wooden desk." [the photo]
Spot onNot quite What is it really? [text box]
The phone reads the question aloud as it arrives. The agent answers out loud to exactly what the owner tapped or typed: "A cactus, not a pine tree. Got it."

Question
Did I see that right? (with an optional typed correction). If the photo was skipped: "What's next for you today?" as a choice.
Calls
POST /interactions with image, "speak":true, buttons and a text field; POST /speaker/say
Features
interactions · questionimage on cardtext replyspeak aloudspeaker
4
Item 4: Come when called On the phone

Step card: "Say 'hey bridgit, lights on' and watch what happens." If no wake word is set: "Open Bridgit › Features › Wake words, add 'hey bridgit' for me, then tap Do it." The owner says the phrase; the torch comes on and the phone says "Lights on. Off again in five seconds."

Owner does
Maybe adds a wake word and downloads the speech model, then speaks.
Calls
GET /listen, GET /events?types=listen.heard&wait=55, then POST /flashlight and POST /speaker/say
Features
wakewordson-device speecheventsflashlightspeakermute button
5
Item 5: Rock paper scissors Both

Step card: "Best of three. Stand the phone up facing you at arm's length, and throw on 'shoot'." Each round the agent writes its move to the Activity log first, so it can't cheat, then counts down out loud and takes a selfie on "shoot". It ends with a result card showing the deciding photo.

Owner does
Throws a hand at the camera, three times.
Calls
POST /log, POST /speaker/say, GET /speaker (wait for the line to finish), POST /camera/snapshot {"camera":"front"}, POST /interactions (notice)
Features
camera · frontspeakeractivity loginteractions · notice
6
Item 6: How am I feeling? On the phone
You look surprised![the selfie]
How were you really feeling? ( surprised · amused · confused · something else )
Send
Step card: "Make a face: happy, surprised, grumpy, sleepy, anything." The phone counts "three, two, one", takes a selfie, and the agent's guess arrives read aloud. It then says the verdict: "Got it in one!"

Question
How were you really feeling? (choice of four)
Calls
POST /speaker/say, POST /camera/snapshot {"camera":"front"}, POST /interactions with a choice control and "speak":true
Features
camera · frontinteractions · choicespeak aloudspeaker
✓
Wrap-up On the phone

A notice card, with the first line said out loud: "I flashed your light, saw your desk, asked you on your phone, heard your answer, came when you called and played a game, all over your private Tailscale network." Then two or three ideas tied to what the owner said, an offer of the full menu, and an offer to set one idea up for real.

Ideas offered
Approvals on the go · Show me anything · Read and translate · Watch me work · Hear the room · A mini app for you · Phone as a sentry · Find my phone · Help with what's on screen
Features
interactions · noticespeaker

The menu (`GET /v1/demo`)

Built live on the phone for each agent. It lists every demo and marks the ones that can't run right now (feature off, not allowed for this agent, or not ready). The agent asks four questions, then runs the demos that fit.

The four questions In chat

Where's the phone?
In your handOn the desk next to youSomewhere else in the room
In hand: anything. On the desk: camera, screen, speaker and cards first. Across the room: speaker, flashlight and find my phone first.
What would help you most?
Quick decisions and approvalsSeeing and reading thingsHands-free voice and soundKnowing what the phone is doing
Matched to each demo's "Good for" column below.
How long?
A quick taste (3 demos)The full tour
Quick taste includes one question card if cards are on.
Anything on your plate today?An open question, for example a decision, a trip or a task. Used as the content of the demos, so they're about the owner's day, not placeholders.

These are asked in chat. Only an agent running in the background is told to ask them as choice cards on the phone.

The 19 demos

Amber rows are the weak actions from finding 4.

Demo	What the owner sees	Good for	Where	Feature · calls
Ask me with buttons	A yes/no question from their day; one tap answers it. They can reopen it and change the answer.	Decisions	Phone	interactions POST /interactions, GET /interactions/{id}
Pick from a list, or type a reply	"Where should we eat?" with three options and a "Something else?" box.	Decisions	Phone	interactions choice + text controls
A card you design	The agent's own HTML: a packing checklist, a mood slider, a chart.	Decisions, seeing	Phone	interactions kind html
Live text panel	Text scrolls on the phone as the agent works on a real task.	Decisions, seeing	Phone	interactions kind text, POST /text/stream
Talk out loud	The phone speaks a short line, or reads a question aloud.	Voice	Phone	speaker POST /speaker/say
Camera control	Photos at 0.5×, 1×, 2× zoom, front lens or flash; the agent says what changed.	Seeing	Both	camera POST /camera/snapshot
Show me something	They take a photo or screenshot the usual way; the agent sees it as soon as it's saved.	Seeing	Both	gallery GET /image/last
Read the text in a photo	A sign, label or page read on the phone itself, then summarised or translated.	Seeing	Chat	ocr POST /ocr
A short video	Five seconds of video; the agent describes what moved.	Seeing	Both	video POST /camera/video
Listen and transcribe	Ten seconds of audio, transcribed on the phone; the agent reads back a reminder they said.	Voice	Both	mic POST /mic/record
Say the wake word	"Hey bridget, remind me to water the plants" reaches the agent hands-free.	Voice	Both	wakewords GET /listen, GET /events
Hear the room	A clap or a knock reaches the agent with a short clip; it guesses what made the sound.	Voice, phone	Both	sounds GET /sounds, GET /events
What's on my screen	One look at the open screen, kept in memory and never saved.	Seeing	Both	screen POST /screen/capture
Where am I	Nothing on the phone; a sentence in chat about heading, altitude, landmark.	Phone	Chat	location GET /location
Flashlight	The torch on for ten seconds.	Phone	Phone	flashlight POST /flashlight
Find my phone	The phone rings for five seconds.	Phone, voice	Phone	ring POST /phone/ring
Focus mode	Do Not Disturb on for one minute, then back off.	Phone	Phone	controls POST /phone/dnd
How's the phone doing	Nothing on the phone; one sentence in chat on battery, network, sound.	Phone	Chat	phone GET /phone/status
City tour	Explained only; the owner has to start it from Bridgit's Tour screen.	Seeing, voice	Chat	tour GET /tour

Menu wrap-up In chat

Two or three ideas for the owner's routine based on their answers, which switch to turn on for any demo they wanted that was off, and an offer to set one idea up for real.

Features covered

Which Bridgit features each script shows. See all of them on the features page.

Feature	First-run tour	Menu
Question cards (buttons, text, choice)	Opening card, items 3, 6	2 demos
Notice cards	Item 5, wrap-up	—
HTML cards	Wrap-up idea	1 demo
Live text panel	Wrap-up idea	1 demo
Speaker, and reading cards aloud	Items 3–6, wrap-up	1 demo
Flashlight	Items 1, 4	1 demo
Camera (rear, front, zoom)	Items 2, 5, 6	1 demo
Wake words	Item 4	1 demo
Activity log	Item 5	—
Events (listening for the phone)	Item 4	2 demos
Gallery (photos the owner takes)	Wrap-up idea	1 demo
Text recognition (OCR)	Wrap-up idea	1 demo
Video	—	1 demo
Microphone and transcription	—	1 demo
Sound detection	Wrap-up idea	1 demo
Screen capture	Wrap-up idea	1 demo
Location	—	1 demo
Phone status	—	1 demo
Find my phone (ring)	Wrap-up idea	1 demo
Do Not Disturb	—	1 demo
City tour	—	1 demo

For agents: the script itself is at bridgit.cc/demo/SKILL.md, and the menu is GET /v1/demo on the paired phone.

The Bridgit demo

Review: why the demo often skips the phone

1. Agents are given two demos and can pick the one without cards

2. MCP agents only ever see the menu

3. The menu's results come back in chat, not on the phone

4. Several menu demos are weak actions

5. Two first-run items depend on setup or exact timing

How the demo starts

The owner pairs an agent On the phone

The agent's first test In chat

The agent offers a demo In chat

The first-run tour

Get ready, quietly In chat

The opening card On the phone

Item 1: Flash the light On the phone

Item 2: Take a photo Both

Item 3: Ask and answer out loud On the phone

Item 4: Come when called On the phone

Item 5: Rock paper scissors Both

Item 6: How am I feeling? On the phone

Wrap-up On the phone

The menu (GET /v1/demo)

The four questions In chat

The 19 demos

Menu wrap-up In chat

Features covered

The menu (`GET /v1/demo`)