Prop your phone in front of a computer, a TV or a tablet and tell it what you need. It takes over that screen's keyboard and mouse and gets on with the job, and you can take back over any time. Nothing to install on the other side.
Android today; the iPhone app is coming. Driving a TV or tablet with no extra hardware stays Android-only.
Put the phone in a holder facing the screen and talk to it. It sees what is there, does what you ask, and hands back the moment you touch anything. An assistant you carry, with no account and no tracking, and one that will be able to think with a model you run yourself.
The assistant is on Android today
The live camera picture is your monitor. No cable, no capture box, no drivers.
The whole screen is a trackpad. A key bar holds Esc, Tab, Enter, Delete, the arrows, and modifiers that stay pressed until you tap them again.
Show it the screen and say what you want. It writes a short plan, you approve it, it types. More →
Available on Android today
Photograph the screen, say what you want, and it answers with a numbered plan of keystrokes and clicks. Review it, tap Run.
BluetoothComputers, laptops, single-board computers, and the smart TVs, tablets and iPads that take a Bluetooth keyboard.
A screen that accepts no keyboard or mouse at all can be seen but not driven.
A small device, or your phone itself, that shows up to the machine as an ordinary keyboard and mouse.
USB · Android today, iPhone coming
A Raspberry Pi Zero 2 W, once our image is published. If the phone goes quiet, it lets go of every key by itself.
USB · Android today, iPhone coming
Our app turns a Flipper Zero you already own into a keyboard for the device. Keyboard only for now.
Phone support in progress
No extra hardware. The phone itself becomes a Bluetooth keyboard and mouse. Built into the Android app.
Anything that can be driven can grow a tentacle: an old CNC machine, a printer on a parallel port, an instrument with a serial console. The protocol will be published with the launch.
An open-source peer-to-peer network where every node is a small database with its own identity, sharing only what its owner allows.
Both apps carry a node. On Android it wakes when you use the assistant. On iPhone it will let an Android phone you already own be the tentacle, so an iPhone can reach screens it could not drive by itself. A Pi tentacle will be able to join too, so other services you pair can use it.
The app identifies the tentacle before it sends a single input. Until it answers, there is no control screen.
What you type goes only to the device. The keyboard never autocorrects, suggests or learns from it.
If the connection drops while a key is held, the tentacle releases it within about three seconds. A panic button, and leaving the app, release everything at once.
No login, no tracking: your phone has its own cryptographic identity rather than an account. On Android the assistant reaches our service over the Resonator network, relayed through public servers we do not run and which cannot read what passes through them.
A downscaled picture goes out for one plan, never to disk. The iPhone app sends no pictures at all. Privacy →
If it takes a Bluetooth keyboard, your Android phone becomes one. iPhone cannot act as a keyboard, so direct TV control stays Android-only.
Nothing to install: it sees an ordinary keyboard and mouse. With a tentacle it works on the login screen, as a wired keyboard does.
Under the hood, yes: a software KVM whose video is your camera. We just don't lead with that.
