explaingit

aohp-os/aohp

15Audience · researcherComplexity · 5/5ActiveLicenseSetup · hard

TLDR

Research fork of Android from Tsinghua AIR that redesigns the OS so AI agents can call services, run tasks in parallel, and handle sensitive data safely.

Mindmap

mindmap
  root((aohp))
    Inputs
      User intent
      App services
      Sensor data
    Outputs
      Task results
      Audit traces
      System memory
    Use Cases
      Agent-driven phones
      Cross-app automation
      Safe payment flows
    Tech Stack
      Android
      AOSP
      Apache 2.0

Things people build with this

USE CASE 1

Read the technical report to understand agent-native OS design

USE CASE 2

Cite the AOHP architecture in research on mobile AI agents

USE CASE 3

Track the project for source code and device images when released

Tech stack

AndroidAOSP

Getting it running

Difficulty · hard Time to first run · 1day+

Source code, build steps, and device images are not yet released, so today the repo only holds documentation.

Apache 2.0 lets you use, modify, and distribute the code commercially as long as you keep the license and notices.

In plain English

AOHP, short for Android Open Harness Project, is a research fork of Android being built at the AI Industry Research institute at Tsinghua University. The idea is that AI agents are starting to drive phones on behalf of users, but mobile operating systems still assume a human is the one tapping the screen. AOHP keeps Android's hardware support and app compatibility, then adds system features that make services easier and safer for an agent to call. The README contrasts the two approaches with a shopping example. On stock Android, finding a pair of running shoes under 80 dollars means hopping across Amazon, Temu, eBay, the browser, and Notes, with many taps, copy-paste, and app switches. On AOHP, the operating system offers one task-level entrance, the agent figures out the intent, and the system can talk to several apps in parallel before applying a safety policy and returning a result. The repository lists three main capability areas. Personalized user interaction means the OS can generate task-shaped entrances, find capabilities across apps, and keep memory that survives across app boundaries. Efficient agent interfaces include parallel background execution on virtual displays, structured UI representations for the agent to read, an OS-managed sandbox runtime, unified file handling, and a single subscription channel for events and sensor data. Secure information flow uses typed placeholders for sensitive values like payment cards, a trusted vault for secret-handling steps, and data-flow taint tracking enforced at system boundaries. Tasks flow through five stages: expressing intent, resolving it to system capabilities, picking an execution path through APIs or command-line calls or structured UI operations, passing sensitive actions through a policy layer, and recording memory and audit traces. The team reports tests with OpenClaw agents on ten mobile tasks, where AOHP raised the task completion rate from 43.3 percent to 90 percent while cutting tool calls, duration, token use, and LLM requests by 65 to 74 percent. The project is licensed under Apache 2.0. Source code, build steps, and device images are not yet released, and the repository today holds documentation and a technical report citation.

Copy-paste prompts

Prompt 1
Summarize the five task stages in AOHP and how each handles sensitive data
Prompt 2
Compare AOHP's agent-native interfaces against stock Android for a shopping task
Prompt 3
List the three core capability areas of AOHP with one example each
Prompt 4
Explain how AOHP's typed placeholders and trusted vault protect payment cards
Open on GitHub → Explain another repo

Generated 2026-05-22 · Model: sonnet-4-6 · Verify against the repo before relying on details.