Top Repos· Jev-Based· Harness· Last updated

CaiZongyuan / mobile-agent

“基于 Mobilerun Portal、ADB 与 Jev 的 Android 真机 AI Agent:通过无障碍树感知界面、自主决策并执行操作,附可复现代码、真实场景评测与脚本自动化对照实验。”

Jev-Based rank #307In Harness #112

TL;DR

CaiZongyuan/mobile-agent showed up as Jev / System One related work: Verified TypeSafe Jev / System One work — Jev or System One is the core idea.

The author describes it as: “基于 Mobilerun Portal、ADB 与 Jev 的 Android 真机 AI Agent:通过无障碍树感知界面、自主决策并执行操作,附可复现代码、真实场景评测与脚本自动化对照实验。” That is their claim, not a bench this site ran.

Who it’s for

What’s inside

Top-level entries on GitHub at generation time: .gitignore, AGENTS.md, README.md, artifacts, docs, scripts. Read those before you trust a one-line install.

How to use

  1. Clone and follow the author’s Python toolchain. Do not invent a package name.
git clone https://github.com/CaiZongyuan/mobile-agent.git
cd mobile-agent
  1. If the project calls hosted Jev, you still need a TypeSafe console key or a documented gateway.
  2. Send a complete state and typed questions. Code owns control flow after the probabilities.

Hosted Jev still looks like a function call — wrapper or not:

{
  model: "jev-1.13.0",
  state: { source: "CaiZongyuan/mobile-agent", brief: "..." },
  questions: {
    gate: { type: "noul", instructions: "Should we act on this state?" },
    route: { type: "choice", instructions: "Pick one next system.", criteria: ["code", "review", "human"] },
  },
}

Try this

Put Jev on one real brief

Wire CaiZongyuan/mobile-agent so one real state (ticket, diff, or utterance) becomes a Choice plus a Noul. Do not ask Jev to write the user-facing reply.

Schema-safe ≠ correct

On a case CaiZongyuan/mobile-agent gets wrong, write down the schema-legal answer it returned and the human label. Do not “fix” it by asking Jev to generate an explanation.

FAQ

Does this replace the TypeSafe SDK?

Only if the author implemented a full client. Most harnesses still call the vendor SDK or raw HTTP.

Are the star chips live?

Star, fork, and watcher chips refresh from the public GitHub API via a scheduled job. The prose on this page is editorial.

Sources

Public repository metadata and TypeSafe documentation. No private claims.