Autonomous Mobile Operating System
Phone Glasses AR
Open source · MIT

AMOS
Autonomous Mobile Operating System

AMOS is a fully open-source floating command layer for Android, built on 01 (execution) and 02 (intent bridge). No subscriptions, no paid tiers — clone the repo, run the CLI, and self-host the backend.

AMOS = Autonomous Mobile Operating System — governed by your confirmation, never silent, never hijacking other apps.

npm install -g amos-cli

Optional PC Companion on Windows pairs with your self-hosted backend — no account fees.

02 :: intent.json goal: "summarize selection" risk_level: LOW executor: COMPANION_01 01 :: docker sandbox healthz: ok
LLM interprets · 02 governs · You authorize · 01 executes

The stack

AMOS is an open-source AI command layer, automation assistant, and wearable control surface — not a hosted SaaS you subscribe to. Clone the repo, run amos-cli, and self-host the backend on your own hardware.

01

Execution layer

Sandboxed interpreter / executor. Runs only after intent validation, typically inside Docker on a companion host or supported on-device VM.

02

Intent bridge

Open-source schemas, provider interface, safety gate, verifiers. The skeleton developers extend and ship with AMOS.

AMOS

Mobile shell

Floating command UI on Android, optional PC Companion on Windows, glasses and AR previews. You run the backend; BYOK for AI providers.

Phone · Smart glasses · AR

Same governance, three surfaces. AMOS keeps clarification on the phone; glasses stay input/output first; AR shares the same plan / risk / confirm contract.

Phone

Floating command center

Bubble, quick panel, expanded plan review, execution status — designed to stay lightweight over your workflow.

Open phone mock
Glasses

HUD relay

Short status lines, confirmations, hands-free wake paths. Execution stays on the handset / companion.

Open glasses HUD
AR

Spatial canvas

Floating intent cards with risk pills, awaiting your confirm. Same open stack, wider canvas.

Open AR canvas

One contract across surfaces

The same intent JSON, the same SafetyGate, the same recycle controls — whether you tapped the bubble, said the wake phrase, shared from the browser, or spoke through your glasses.

Download & build

AMOS is free and open source. Download the CLI, clone the repo, grab releases — no subscription required.

CLI

amos-cli

npm install -g amos-cli

  • amos init — create local .env
  • amos backend start — API on :8000
  • amos doctor — check your toolchain
  • amos dev — full stack hints
Read install docs
Android

Build the app

Open source

  • Open app/ in Android Studio
  • Run on emulator or sideload debug APK
  • Pair with self-hosted backend
  • BYOK — your keys stay on device
Clone repository
Windows

PC Companion

Open source

  • apps/pc-companion — .NET 8 WPF
  • Pair with mobile via backend code
  • No entitlement fees
Install path →

Open source

AMOS, 02 App Core, and 01 Executor are open for inspection, fork, and self-host. Contribute on GitHub — no commercial gate on features.

Install path

Developer path: CLI + clone + backend. Build Android from source or sideload. PC Companion pairs through your self-hosted API.

Step 1 — CLI & backend

Install globally, clone the repo, initialize env, start the API.

npm install -g amos-cli
git clone https://github.com/tensorverse/amos.git
cd amos
amos init
cd services/backend-api && pip install -r requirements.txt && cd ../..
amos backend start

Step 2 — Android app

Open in Android Studio, run :app. Emulator API: http://10.0.2.2:8000/.

GitHub — build instructions

Step 3 — PC Companion (optional)

Build apps/pc-companion, enter pairing code from the mobile app against your backend.

PC Companion source
  1. 1npm install -g amos-cli · amos init · amos backend start
  2. 2Build & run Android app from source
  3. 3Pair PC Companion (optional)

AMOS is open source — you host the backend and bring your own AI keys. No subscription or in-app purchase in this project.

FAQ

The questions early testers ask first. Click any item to expand.

What's the difference between 01, 02, and AMOS?

01 is the sandboxed executor — typically Docker on a companion host. 02 is the open intent bridge. AMOS is the open-source mobile / glasses / AR shell on top.

Can I use my own AI key?

Yes — paste provider keys in settings. Keys stay on your device per in-app storage and privacy notices.

How do I install AMOS?

npm install -g amos-cli, clone the GitHub repo, run amos init and amos backend start, then build the Android app from app/ in Android Studio.

What devices are supported right now?

Android (the AMOS app) is the primary surface today. Glasses HUD and AR canvas previews are on this site; build from source for supported devices.

If AMOS goes weird or freezes, do I have to uninstall?

Usually no. The app exposes a Recycle control with four levels — Plan, Session, Executor, and All — that re-initialize specific layers. If a full reset is needed, uninstall and reinstall is supported and clears every setting and history; the only cost is re-pasting your API keys and re-granting overlay / foreground-service permissions. The Docker 01 executor lives on the companion host and is restarted independently with docker compose down && docker compose up -d.

Does AMOS read or control my other apps?

No. AMOS is a user-authorized floating layer. The intent-only LLM contract (enforced by IntentContractValidator) blocks any executable payloads from the model — the LLM proposes intents, you confirm, and only then does 01 execute on a sandboxed runtime.

Where does my data live?

On device by default — DataStore for settings and API keys, Room for safety-decision history. The 01 executor runs in your own Docker on your own host. No telemetry is enabled at this milestone.

I need help — who do I contact?

Open a GitHub issue or email support@tensorverse.ai.

Community

Contribute connectors, automation packs, and docs on GitHub. No marketplace fees in the open-source tree.

Star on GitHub

Support

GitHub issues for bugs and features. Email for security or partnership questions.

support@tensorverse.ai

Privacy · Terms