Skip to content

docs: add Android AI phone bridge engineering tutorial - #3

Open
G-Raser wants to merge 4 commits into
mainfrom
tutorial/umi-mobile-ai-companion-bridge
Open

G-Raser wants to merge 4 commits into
mainfrom
tutorial/umi-mobile-ai-companion-bridge

Conversation

@G-Raser

@G-Raser G-Raser commented Oct 1, 2026 •

Copy link
Copy Markdown
Owner

What this adds

Adds a practical engineering tutorial based on the private Umi Mobile implementation:

从 MCP 到 Android:搭建一个受控的 AI 手机 Bridge

Covered

  • Android companion + outbound WSS architecture
  • device pairing and persistent device identity
  • WebSocket command/result protocol
  • DeviceHub abstraction
  • MCP tool layer
  • AccessibilityService implementation boundaries
  • UI tree + screenshot strategy
  • password/input safety guards
  • permission tiers
  • optional APK, logcat, BLE and background-call extensions
  • deployment topology
  • implementation order
  • E2E test matrix
  • public/private boundary

The tutorial is written as an engineering guide rather than a project narrative. CatTea / Home remains only as a concrete adapter example.

Public-safety pass

The tutorial excludes real domains, device identifiers, tokens, production paths, version/commit IDs, signing material and private prompts.

Also updates the repository root tutorial index.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 493031272f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".


- 由设备持有人做一次明确的开发权限 bootstrap;
- 日常运行仍然走原本的 WebSocket bridge;
- 每次读取必须带 literal filter;

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Enforce a genuinely narrow logcat filter

After the development bootstrap grants access to other applications' logs, merely requiring a caller-supplied literal does not create the narrow data boundary claimed below: an empty, one-character, or otherwise common literal can match nearly the entire buffer, while keyword redaction cannot cover arbitrary credentials or personal data. Constrain reads on the device with an allowlisted UID/package or tag plus bounded time/line limits, and reject low-selectivity filters before exposing this capability over the bridge.

Useful? React with 👍 / 👎.

@G-Raser G-Raser changed the title docs: add Umi Mobile AI companion bridge tutorial docs: add Android AI phone bridge engineering tutorial Oct 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant