Autonomous Mobile Operating System
Phone Glasses AR
Voice-first agent control

AMOS
Autonomous Mobile Operating System

AMOS is a paid mobile command layer for Android, PC companions, smart glasses, watches, browser surfaces, and agentic systems. It keeps a persistent connection to your narrator/bridge, turns requests into approval cards, and routes your voice to the right tool.

AMOS = Autonomous Mobile Operating System - governed by your confirmation, server-authorized by entitlement, and designed for agents that need human approval before meaningful action.

Phone app + PC narrator + LiveKit bridge + wearable adapters.

Founder access is reserved for awakengiovanni3000@gmail.com. Public access starts behind the AMOS entitlement gate.

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 AI command layer, automation assistant, and wearable control surface. The paid product is the app, narrator, bridge, billing gate, and adapters that make your agents usable from phone, PC, glasses, watches, and browser surfaces.

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

Shared card contract, provider interface, safety gate, verifiers, and approvals. Developers extend adapters without breaking the voice-first control loop.

AMOS

Mobile shell

Android hub, entitlement gate, foreground reconnect service, floating AMOS ball, glasses/watch surfaces, and PC narrator bridge.

Phone · Smart glasses · AR

Same governance across surfaces. AMOS keeps rich controls on the phone; glasses and watches stay lightweight for status, approval, voice, and fast interruption.

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, narration, and band or tap approval where hardware supports it. Execution stays on the handset, PC companion, or managed workspace.

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 card contract, entitlement state, reconnect loop, and approval controls whether you tapped the bubble, spoke to the phone, used a watch, or approved from glasses.

Plans & access

AMOS has no free tier. Unpaid accounts see the pay screen. Founder, Pro, Developer/Premium, and Enterprise access all resolve through the same backend entitlement system.

Founder

Founder access

Full personal access

  • Reserved for the founder login
  • Unlocks tester simulation tools
  • Supports dev builds and all surfaces
  • Used to test unpaid, pro, and expired states
Founder support
Pro

AMOS Pro

$19.99 base

  • Phone app and floating AMOS ball
  • PC narrator and LiveKit bridge
  • Persistent reconnect and approval cards
  • Bring your own AI where supported
Request access
Developer

Premium / Enterprise

Higher-capacity agents

  • Hosted GCP / Veo style workflows
  • Higher model and adapter capacity
  • Enterprise governance and audit path
  • Pay-as-you-go provider usage with margin
Talk to TensorVerse

Developer ecosystem

AMOS is built for adapters: Terminal/Git, GitHub, Gmail, Drive, Calendar, gcloud, Slack, Stripe, Chrome, Perplexity, and agent systems such as Codex, Claude Code, OpenClaw, and future enterprise workspaces.

Install path

Developer path: install the app, sign in, pass entitlement, then pair the PC narrator/companion. Founder builds can sideload during development; public users go through the app store or installer flow.

Step 1 - Account & entitlement

Sign in. The backend resolves founder, pro, enterprise, or unpaid. Unpaid accounts stay on the pay screen.

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 hub

AMOS runs as the phone hub: splash/passphrase gate, auth, billing, paywall, foreground reconnect service, and floating ball.

See surfaces

Step 3 - Narrator / companion

The PC narrator bridges Claude Code, Codex, and agent systems to the phone through LiveKit and the shared approval-card contract.

Request setup help
  1. 1Sign in and pass entitlement
  2. 2Run the Android hub and floating AMOS ball
  3. 3Pair the PC narrator, glasses, watch, and browser surfaces

AMOS fails closed when license status is inactive. Founder/developer builds can expose tester controls, but real public access is server-authoritative.

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 on a companion host. 02 is the intent bridge and card contract. AMOS is the paid mobile, glasses, watch, browser, and PC control layer 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?

Public users install the AMOS app, sign in, and unlock access through the backend entitlement gate. Founder/developer builds can also sideload Android and run local backend/narrator components for testing.

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?

Email support@tensorverse.ai.

Adapter ecosystem

AMOS grows through adapters, app-specific voice wiring, browser extensions, glasses surfaces, watch surfaces, and governed enterprise agent workspaces.

Build an adapter

Support

Email for access, setup, security, app adapters, enterprise workspaces, or partner questions.

support@tensorverse.ai

Privacy · Terms