Projekt · Open Source (MIT) · Fork von hermes-android
FlipsiBridge
FlipsiBridge runs on your Android phone and opens screen, keyboard, notifications, camera and files to your self-hosted AI agent, over an encrypted connection (wss:// with client certificate) the phone establishes back home. No port forwarding, no third-party cloud.
Was es macht
Sicherheit
FAQ
A Hermes agent on your server, an Android phone (Android 8+), plus a domain with reverse proxy if you also want to connect on the go. The complete setup including a ready-made prompt for your agent is in the repository.
The agent can only do what you enable in the app switches. Sending SMS, calls, contacts and GPS are not built in at all. The connection is encrypted and needs two factors: your client certificate and the pairing code.
Yes: the Android app talks to a small relay server (Python) that any agent software can connect to. A guide for Hermes agents (the agent sets everything up itself) is included.
Warum FlipsiBridge?
Controlling your own phone with your own AI: here is the honest comparison.
Gegen Cloud-Assistenten
Stark: komfortabel, funktioniert sofort.
Der Nachteil: Screen content, commands and voice recordings pass through third-party servers. A corporation knows what your phone displays.
FlipsiBridge: runs entirely through your own server, encrypted, without third-party cloud.
Against the upstream project (hermes-android)
Stark: a clean open-source base project that provides the idea.
Der Nachteil: Connections are unencrypted by default (ws://): fine for the home landing zone, risky for everything else.
FlipsiBridge: encrypted by default (wss + mTLS), capability gating, signed builds: the fork I use daily.
Comments (0)
Setup questions, bugs or a feature idea? Discord is the fastest way, or open an issue on GitHub.
TechFlipsi-Discord