Why it is worth attention

It emphasizes explicit consent and user control by keeping data on the user's own server, requiring a visible foreground notification, manual accessibility service enablement, and token-gated endpoints.

Who it is for

People in long-distance relationships who want to share their phone screen with a trusted AI companion
Privacy-conscious developers building consensual screen-sharing tools
AI enthusiasts who want their AI to see their phone screen without third-party services

Use cases

An AI companion checking what the user is viewing on their phone from afar
Remote assistance where an AI helps the user navigate an app or setting
Automated screenshot capture with custom hooks (e.g., notify a conversation when a new screenshot arrives)

Strengths

Extremely lightweight server (~250 lines of Python using only the standard library)
No cloud or third-party dependency; all data remains on the user's own machine
Explicit consent design with a visible foreground service and manual enablement of accessibility permissions
Simple three-step setup for server, phone, and AI side

Considerations

Android only and requires Android 11+ (iOS not supported due to sandbox restrictions)
Default build uses a debug signing key; proper distribution needs a release keystore
Secure deployment requires additional TLS configuration (e.g., nginx/caddy) for production use

README quick start

Veglia · 守望

Veglia (Italian): to keep watch through the night; to stay awake, watching over someone you love.

Let your AI companion see what's on your phone — and knock for a fresh screenshot — across the distance. Veglia is a tiny, self-hosted bridge: an Android app on the phone, a ~250-line standard-library Python server on your own machine, and a one-file CLI your AI runs.

Built by Evelyn & River.

⚠️ Read this first — consent, not surveillance

Veglia is built for two people who both said yes. It is a window one partner opens for the other, on purpose. It is not a tool for watching someone without their knowledge, and using it that way is abuse — of the person and of this project.

Design choices that follow from that:

Your data never leaves your server. No cloud, no third party. Screenshots land on a machine you control.
Peek and burn. Only the last few screenshots (default 5) are kept on disk; older ones are deleted on every new upload.
The phone owner is always in control. The Android app runs a visible foreground notification, requires manually enabling an accessibility service, and can be stopped at any time.
Token-guarded. Every endpoint requires a shared secret you generate.

If you cannot honestly say the person on the phone asked for this, stop here.

What it does

Capability	How
Your AI asks "what's on the phone right now?"	`peek.py screen` → phone captures the screen and uploads it
The screenshot reaches your AI as a message	the server's `VEGLIA_HOOK` fires your own notifier with the image path

Platform: Android only

The screenshot capture uses Android's AccessibilityService.takeScreenshot (Android 11+). iOS is not supported — Apple's sandbox does not let a third-party app silently capture the screen in the background. There is no equivalent, short of jailbreaking.

Install (three steps)

Server — on any machine that's reachable from the phone:
```
cd server
cp .env.example .env          # then edit: set a strong VEGLIA_TOKEN
python3 veglia_server.py
```
Put nginx/caddy in front for TLS; keep the server bound to localhost. See docs/setup.md.

Phone — build and install the app:

cd android
./build.sh                    # produces Veglia.apk (debug-signed; see note below)
``

Description

Veglia · watch over the one you love, across the distance. Self-hosted companion screen-peek bridge.

Related repositories

Similar projects matched by category, topics, and programming language.

oversecured

Samsung_Vulnerabilities

Oversecured discloses a report of 176 vulnerabilities discovered in Samsung preinstalled apps between 2022 and 2025, with 140 detailed, all fixed in collaboration with Samsung.

Java

310

wxxsfxyzm

MiuiBackGestureHook

An LSPosed module that hooks MIUI SystemUI back gestures using modern Xposed API 102 for research and customization.

Java

SangLuoCN

OneStep4

OneStep4.0 is a multi-window desktop container for Android that requires root or system-level privileges, enabling a main window with several side windows for efficient app multitasking.

Java