Mobile Jev
Mobilerun Android agent: Jev picks OPEN_APP, TAP, TYPE_TEXT, and scroll ops from observations; React studio, CLI traces, verified dark-theme demo.
Overview
mobile-jev (github.com/droidrun/mobile-jev) is Droidrun's standalone agent for Mobilerun Android devices. Each loop observes accessibility state and installed apps, sends one TypeSafe request with operation plus speculative target heads, validates the winning branch, then executes through the Mobilerun API. A React studio on port 3040 streams the device, surfaces per-step latency, and keeps API keys server-side. The packaged dark-theme demo verifies the real Settings switch; the README Uber clip shows about 21 seconds for nine actions without claiming a completed booking.
Problem: Desktop browser and macOS computer-use demos dominate the Jev directory, while real Android automation still gets treated like a remote ADB script with no typed action menu.
Built for: Mobilerun operators who want a localhost React studio or CLI where Jev picks bounded mobile UI actions from device observations, not prose plans.
First indexed on Jev Directory: 2026-09-26
Creator and team
- Name
- Droidrun
- Organization
- Mobilerun
- Handle
- @droidrun
How Jev is used
- Role in the product flow
- Per-step mobile control routing (operation plus compatible target selection over observed UI)
- Primitives
- Choice
- State in
- Indexed controls, installed-app inventory (up to 200 apps when not name-filtered), goal text, and prior executed actions from Mobilerun observations.
- Decision out
- OPEN_APP, TAP, TYPE_TEXT, scroll, navigation, WAIT, DONE, or BLOCKED with validated target indices; text spans are copied verbatim from the goal, not generated.
- Observe device UI and app list through Mobilerun
- One Jev request chooses operation and speculative targets
- Executor rejects stale targets and records actions before the next read
- Mobilerun mutates the device; loop continues until stop, failure, or cancellation
- Demo runner re-observes to verify state (DONE alone is not proof)
Mobile Jev mirrors the Browser Use ultrafast split on a phone: finite operations over structured observations, with TYPE_TEXT fed from exact goal spans instead of a second generative model. Mobilerun owns transport and gestures; Jev owns which legal branch fires. The executor never retries a device mutation after an uncertain transport failure and treats Jev DONE as a hint, not QA. docs/DEMO.md documents why clock and travel flows need independent verifiers before you quote speed wins. Compare browser-use-jev-ultrafast for DOM tables in Chromium, awlevin-typesafe-computer-use for macOS accessibility loops, and moritzkremb-jev-voice-browser when the input is partial speech instead of a typed goal.
Sourced performance claims
- README Uber recording: about 21 seconds for 9 actions from SFO airport to Golden Gate Bridge payment screen; completed booking not demonstrated.Source: github.com/droidrun/mobile-jev README
- docs/DEMO.md exploratory dark-theme run: 8.685 seconds with three executed actions, five Jev calls, one stale decision rejected.Source: github.com/droidrun/mobile-jev docs/DEMO.md
- Public GitHub repo droidrun/mobile-jev had about 402 stars and 50 forks when this listing was drafted.Source: GitHub API September 2026
Features and stack
Features
- React studio with @mobilerun/react stream, stop control, and in-memory run history
- CLI agent run, observe, screenshot, profile, and direct tap or type debug commands
- pnpm demo dark-theme with optional --reset baseline and --repeat batches
- Connection reuse, brief device readiness cache, and split request timing in traces
- Optional --confidence cutoff; MOBILERUN_TEXT_COMPLETION_MODE for field verification
Stack
- Node.js 22.16+ (24 recommended)
- pnpm 10.30.1
- Mobilerun API and React SDK
- TypeSafe Jev
Pricing: Open source studio and agent; Mobilerun device usage and TypeSafe Jev calls bill to your keys.
Links
FAQ
- Does Mobile Jev require ADB?
- No. README states Mobilerun API control with no ADB connection required.
- Does Jev DONE mean the task succeeded?
- README and docs/DEMO.md say DONE is not independent proof. The dark-theme demo re-reads the switch state; Uber demo stops before purchase.
- Can Jev invent passenger names or payment details?
- No. README: text comes from exact spans in the goal or --text overrides; the agent does not generate arbitrary prose.
- Is the studio safe to expose on the public internet?
- README binds to localhost and expects a single local operator. Public hosting needs your own auth and device authorization.
Related learn guides
Original Jev guidance that pairs with this product pattern.
- Jev use cases
The patterns builders actually search for: moderation, routing, triage, RAG verify, and agent gates.
- Jev vs LLM classification
When to gate with System One probabilities instead of asking a chat model to label things.
Related products
Hand-picked neighbors with rich profiles or overlapping tags.