ASVTR
AR-X NEXUS

Your PC and your phone,
wirelessly one system.

AR-X NEXUS pairs a Windows laptop with an Android phone over the internet — no USB. See the phone screen on the laptop, control it, move files through end-to-end encrypted relay, and ask the AI operator to handle routine tasks. The cloud coordinates; it can never read your data.

Live now

Cloud coordination API

Published on Cloudflare's edge. Register an account, pair devices, exchange signals, relay sealed file bytes. Verified by 16/16 integration tests against this live URL.

Source ready

Nexus Client — Windows

Tauri 2 + React desktop app with 9 sections (Home, Devices, Phone Screen, Files, Hardware, Notifications, AI, Security, Settings). Build on Windows with the commands below.

Source ready

Nexus Agent — Android

Kotlin agent: screen share with system consent, remote input with your approval, files, sensors, notifications, AI tools. Build with Android Studio / Gradle.

Honest

What is proven vs. pending

The backend is live and fully tested. The two apps are complete source trees — they compile with the documented toolchains (Rust / Android SDK) which this build environment does not carry, so first builds should expect minor compile fixes.

Quick Start

Three ways in — try the live API right now, then build the two apps.

Try the live API in 30 seconds — paste into any terminal (or use the buttons in the AI demo app):
# 1. create an account → save the token from the reply
curl -s -X POST https://arx-nexus-api.ajitjaat1011.workers.dev/api/register \
  -H 'content-type: application/json' \
  -d '{"email":"you@example.com","password":"your-strong-pass"}'

# 2. list your devices (use the token you just got)
curl -s https://arx-nexus-api.ajitjaat1011.workers.dev/api/devices \
  -H "authorization: Bearer nx1.YOUR.TOKEN"

Windows client

  • Install Node 20, Rust (rustup + MSVC), WebView2 (built into Win 11)
  • cd apps/windows-client && npm install
  • npm run tauri dev — the app opens

Android agent

  • Install Android Studio (JDK 17, SDK 35), use a physical phone
  • cd apps/android-agent && ./gradlew assembleDebug
  • Install the APK, tap Start agent service

Self-host the backend (optional)

  • cd services/cloud-backend && npm install && npm run dev
  • Runs on :8787 with the same protocol
  • Or deploy the Worker yourself: cd services/cloud-worker && npx wrangler deploy

How to Use — the full walkthrough

First run, from unboxing to remote control. Every step is user-approved — nothing happens silently.

Create your account (laptop)

Open the Nexus Client → Home → enter the server URL wss://arx-nexus-api.ajitjaat1011.workers.dev/ws → create an account (or use the API above) → paste the nx1.… token → Connect & authenticate. The pill in the sidebar turns online.

Pair the phone

On the laptop: My Devices → Generate 8-char code (valid 5 minutes, single-use). In the Android agent: paste your account token + the code → accept. Both devices now see each other online. The phone proves its identity by signing a one-time challenge with a key that never leaves the phone's secure chip.

See the phone screen

Phone Screen → Request phone screen. The phone shows the official Android screen-share consent dialog — tap Start now. The live display appears on the laptop (fullscreen supported). Quality adjusts via stream controls. If the connection drops, the session recovers automatically.

Remote interaction

While the screen is live you can tap, swipe, scroll, Back and Home from the laptop. Input only flows while an approved session is active — stop sharing on the phone (or revoke on the laptop) and it stops instantly. Android's own security screens (PIN, password) always stay private.

Files

Files → browse the phone's photo/video folders → Download (or send a file to the phone). Transfers stream in sealed 32 KiB chunks through the relay with a SHA-256 checksum and resume support — the cloud stores and sees nothing.

Hardware & notifications

Hardware Bridge: battery, network, and permission-gated camera / mic / GPS — each with an explicit grant and an active indicator on the phone. Notifications: enable sync and pick which apps may forward titles; everything else never leaves the phone.

Ask the AI operator

AI Operator: try "check phone battery", "show my screen", "find yesterday's screenshots", "transfer the latest video". Read-only tools run immediately; anything that transmits or deletes data pops a confirmation card — the action executes only when you approve. There is no shell and no way for the AI to grant itself access. (v0.1 uses a rule-based intent parser — documented openly; an LLM can be plugged in later behind the same gate.)

Stay in control

Security lists every paired device with a one-click Revoke. Revocation kills live sessions immediately and blocks re-login until you re-pair. On the phone, the persistent notification always shows the agent status — stop it any time. Full audit trail at GET /api/audit.

Commands

Copy-paste ready. Full reference in the repository README and docs/API.md.

# ── Backend (self-host) ───────────────────────────────
cd services/cloud-backend
npm install && npm test          # 16/16 integration tests
npm run dev                       # http://localhost:8787

# ── Cloud Worker (same protocol, edge deployment) ────
cd services/cloud-worker
npm install
npx wrangler dev --port 8788      # local
npx wrangler deploy               # publish (needs Cloudflare auth)

# ── Windows client ───────────────────────────────────
cd apps/windows-client
npm install
npm run typecheck                 # works on any OS
npm run tauri dev                 # Windows: run
npm run tauri build               # Windows: MSI + NSIS installers

# ── Android agent ────────────────────────────────────
cd apps/android-agent
./gradlew assembleDebug           # APK -> app/build/outputs/apk/debug/
./gradlew installDebug            # USB install

Security model

Security is the product. Every claim below maps to enforced code + tests.

GuaranteeHow
Device identityECDSA P-256 key in the phone's secure chip (Keystore). Every connection is authenticated by signing a one-time server challenge — stolen tokens cannot enroll devices.
End-to-end encryptionFile/relay payloads are AES-256-GCM sealed boxes (ECDH P-256 → HKDF). The relay forwards them blind; tampering is rejected cryptographically (tested).
Pairing8-char single-use codes, 5-minute TTL, rate-limited.
RevocationOne click: live sockets closed, re-auth blocked until re-paired (tested).
No stealthPersistent visible notification; system consent dialogs for screen and input; no ADB or debug ports anywhere.
AI containmentWhitelisted tools only; destructive actions need a one-shot confirm token minted at approval time; no shell tool exists.
Abuse protectionRate limits on every endpoint (tested to return 429); full audit log.
Known gaps (honest): per-transfer forward-secret keys and TURN relay are on the roadmap; account 2FA is planned; the Windows/Android apps should be expected to need minor compile fixes on first build. See ROADMAP.md.

Build status

What runs, what compiles, what needs hardware — no inflated claims.

ComponentStatusEvidence
Shared protocol (wire format + E2E crypto)✅ testedExercised by the integration suite
Cloud backend — Node (self-host)✅ 16/16 testsReal server, real WebSockets
Cloud backend — Worker + Durable Object✅ 16/16 tests, LIVESame suite green locally AND against the deployed URL over the internet
Windows client🟡 source completetsc --noEmit clean; Tauri build needs Windows + Rust
Android agent🟡 source completeNeeds JDK 17 + Android SDK + hardware to build/run
Screen streaming / remote input E2E🟡 needs hardwareProtocol + signaling tested; media path requires a real phone

Milestone definition of done — pair securely ✅ · connect over the internet ✅ (live) · mutual status ✅ · secure file transfer ✅ · reconnect ✅ · revocation ✅ · screen + input 🟡 (code complete, needs phone hardware).