What is Jev-PhoneControl?

A v0.0.1 source-visible Android vision control prototype: give it a task, and it observes screenshots, plans a step, has JEV pick among candidate actions, and executes through ADB — with a local web console and backend API.

How does JEV participate in the loop?

The JEV agent calls the official TypeSafe endpoint (jev-1.13.0 in the sample config), uses Choice to select among candidate actions the vision agent proposed, and Noul to cross-check completion evidence. The endpoint is not configurable to alternative services.

What do I need to run it?

Python 3.10+, Android platform tools with an authorized USB-debugging device, a text model and a vision model (providers include OpenAI-compatible, OpenRouter, MiniMax, Anthropic and Gemini), plus a TypeSafe JEV API key.

How are risky actions handled?

Sensitive actions pause in awaiting_confirmation until you POST an approve or deny decision; the system re-screenshots and verifies before executing. Non-high-risk clicks may tolerate off-target changes, but payment, send and delete require whole-screen consistency.

How do I start the service?

Install into a venv with pip install -e ., set CONTROLPHONE_ADMIN_TOKEN, and run uvicorn controlphone.api:create_app --factory --host 127.0.0.1 --port 8000. Then open http://127.0.0.1:8000/, paste the token and configure models. It binds to localhost only.

What error handling does it have for JEV calls?

Each JEV request times out after 30 seconds and retries at most twice on 429, 500, 502, 503, 504, 529 or network timeouts, honoring Retry-After up to 30 seconds. Config errors like 401 and 422 are not retried; retry state appears in execution records.

Is it open source, and what are its limits?

No — it uses PolyForm Noncommercial 1.0.0, which the README says is not OSI open source; commercial use needs the maintainer's permission. It is v0.0.1, mainly tested on Windows, and screenshots and task text go to third-party model providers and TypeSafe.

Jev directory

CommunityJev Tools & CLIs

Jev-PhoneControl

A source-visible Android vision control prototype where a vision agent reads screenshots, a text-only supervisor plans, and TypeSafe JEV chooses among candidate actions; an ADB executor runs them under a local web console.

See highlights Open github.com

Stars: 5
Language: Python
Reading time: 2 min
Published by: Community
Author: ztrrtuo
Last verified: Oct 2026

ztrrtuo/jev-phonecontrol

User repository on GitHub

View on GitHub

Visual Android automation powered by three agents: vision, a text-only supervisor, and TypeSafe JEV. Executes actions through ADB with a local web console.

Forks: 2
Last pushed: Updated Sep 2026

Repo stats from the GitHub API, cached Oct 2026.

Tagscommunity catalog-import logicrw android agents

Works forJev for Realtime control Jev for Verification

Used inJev for Software & DevTools

Languages: Python
Platforms: API CLI
Capabilities: Self-hostedRuns locallyRequires API key

Highlights

Three roles: a vision agent proposes candidates from screenshots, a text-only supervisor plans, and JEV picks actions with Choice and Noul.
The ADB executor taps, long-presses (a same-coordinate swipe held at least 650ms), swipes, goes back and types; models cannot run arbitrary commands.
Sensitive actions pause at awaiting_confirmation for an explicit approve or deny call; payment, send or delete need whole-screen consistency.
A local web console and API on 127.0.0.1:8000 with WebSocket screenshot preview of up to about 4fps — not scrcpy-style mirroring.
Licensed PolyForm Noncommercial 1.0.0: source-visible, non-commercial only, and explicitly not OSI open source.

Quickstart

bash

git clone https://github.com/ZTRRTUO/Jev-PhoneControl.git
cd Jev-PhoneControl
python -m venv .venv
.\.venv\Scripts\python.exe -m pip install -e .

Watch out

Copy reviewed against the truncated repo README on 2026-10-15; the capture ends inside the MiniMax provider paragraph, so the rest of the provider configuration notes were not reviewed. The project is v0.0.1, developed and tested mainly on Windows, and its README notes the license is not OSI open source.

Questions about this entry

Short answers drawn from the linked project or page.

From the Jev guides

Original write-ups on what this entry is for.

Jev at home: voice pipelines, Assist routing, and sentinels

Oct 16, 2026

How Home Assistant conversation agents, macOS voice pipelines, and an advisory sentinel put a fast typed decision in the loop — one call per utterance, thresholds in code, and a daily token budget.

Jev Tools & CLIs#home-assistant#voice#automation

Read article

Search visibility, audited by decisions

Oct 16, 2026

Jev-based SEO tools split the crawl from the call: deterministic crawlers count and parse, while typed judgments rank fixes, place internal links, score search results, and track AI-answer mentions — with costs and caveats attached.

Jev Tools & CLIs#seo#search-visibility#audits

Read article

Jev on the Gateways: Vercel, Workers AI, and OpenRouter

Oct 12, 2026

The request shape barely changes across surfaces; the surrounding contract does. When to call the API directly and when a gateway, a Worker binding, or a router entry earns its extra hop.

Jev Tools & CLIs#gateway#vercel#cloudflare

Read article

From the Jev AI model community

Posts from builders shipping with Jev right now.

Follow @typesafeai

Jev-PhoneControl

Highlights

Quickstart

Questions about this entry

What is Jev-PhoneControl?

How does JEV participate in the loop?

What do I need to run it?

How are risky actions handled?

How do I start the service?

What error handling does it have for JEV calls?

Is it open source, and what are its limits?

More Jev resources like this

From the Jev guides

From the Jev AI model community