adb-agent-bridge 0.1.0__tar.gz

adb_agent_bridge-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

adb_agent_bridge-0.1.0/NOTICE

@@ -0,0 +1,11 @@
+ADB Agent Bridge
+Copyright 2026 Kelvin Lee
+
+Developed by Kelvin Lee (https://github.com/kelvincushman/adb-agent-bridge).
+Redistributions of this software must retain this attribution in accordance
+with the Apache License, Version 2.0.
+
+The unicode text-input approach was inspired by ADBKeyboard
+(https://github.com/senzhk/ADBKeyBoard). No ADBKeyboard source code is
+included in this project; it is used only as an optional on-device IME,
+driven via its documented broadcast intents.

adb_agent_bridge-0.1.0/PKG-INFO

@@ -0,0 +1,203 @@
+Metadata-Version: 2.4
+Name: adb-agent-bridge
+Version: 0.1.0
+Summary: Fast, accurate agent-to-Android control over plain ADB: semantic UI addressing via uiautomator, no on-device install
+Author: Kelvin Lee
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/kelvincushman/adb-agent-bridge
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: Pillow>=10.1
+Dynamic: license-file
+
+# ADB Agent Bridge
+
+Fast, accurate agent→Android control over plain ADB. Nothing to install on the
+device: the accessibility tree Android already exposes via `uiautomator dump`
+gives every element's text, resource-id, content-desc, and bounds — so an AI
+agent taps element centers instead of guessing pixels from screenshots.
+
+**Developed by [Kelvin Lee](https://github.com/kelvincushman)** · Apache-2.0
+
+## Why this exists
+
+This tool came out of running a real fleet of Android phones driven by AI
+agents — [ContentSwarm](https://github.com/kelvincushman/ContentSwarm), an
+open phone-agent framework for content automation, with
+[Orphus](https://github.com/kelvincushman/orphus) as the agent harness
+driving it. The stack we inherited was built the way most phone automation
+is: **for humans watching a screen, not for agents**. Two things made it
+slow and unreliable:
+
+- **The blind pixel loop.** Every action meant: capture a 1–2 MB screenshot,
+  send it to a vision model, have the model guess an (x, y) coordinate, then
+  `input tap` and hope. 2–5 seconds per action, and vision models regress raw
+  pixel coordinates poorly — taps missed, flows derailed, retries compounded.
+- **The text dance.** Typing one caption meant swapping the IME with four
+  1-second sleeps (~4s per field), and the on-screen keyboard hid the app's
+  media picker at exactly the wrong moment.
+
+The fix turned out to require almost nothing new. Android already ships the
+whole answer over plain ADB, on every device, with zero on-device install:
+`uiautomator dump` returns the full view hierarchy — the same tree an
+accessibility service sees — as XML. Parse it host-side, find the element by
+its text or id, tap its bounds center. **Element-center taps can't miss.**
+Text goes through a broadcast to [ADBKeyboard](https://github.com/senzhk/ADBKeyBoard)
+in ~100ms, with the IME switched once per session instead of once per field.
+
+The guiding principle throughout: *the laziest solution that actually works*.
+No custom accessibility service, no signed APKs, no on-device daemon — until
+measured latency proves one is needed. Every dump is timed
+(`Bridge.device.last_dump_ms`) so that decision is made with data, not vibes.
+
+## The three addressing tiers
+
+1. **Semantic** (default): `find(text="Post")` → tap the element's center.
+   Exact, layout-robust, no vision model in the loop.
+2. **Set-of-Marks / grid** (vision fallback): when the tree is thin (games,
+   canvas, some WebViews), `marks()` draws numbered boxes on a screenshot —
+   the model picks a number, you tap that element. Or address a 10-column
+   grid cell like `"C7"`.
+3. **Raw coordinates**: `tap((x, y))` still works when you need it.
+
+## Install
+
+```sh
+pip install "adb-agent-bridge @ git+https://github.com/kelvincushman/adb-agent-bridge"
+# or from a checkout: pip install -e .
+```
+
+(Not yet on PyPI — install from git. Pin a commit SHA with `@<sha>` for
+reproducible installs.)
+
+Requirements:
+
+- `adb` on the host PATH, device with USB debugging enabled.
+- [ADBKeyboard](https://github.com/senzhk/ADBKeyBoard) on the device for fast
+  and unicode text input (recommended). Without it, plain-ASCII text still
+  works via `input text`.
+
+## Quick start
+
+```python
+from adb_agent_bridge import Bridge
+
+b = Bridge()                      # or Bridge("SERIAL") with multiple devices
+b.ui()                            # -> [Element(text=..., id=..., bounds=...), ...]
+b.find(text="Post")               # first element whose text matches
+b.tap(b.find(text="Post"))        # taps the element's center — can't miss
+b.tap((540, 1200))                # raw coordinates
+b.tap("C7")                       # grid cell (10 square columns A-J, rows from 1)
+b.text("hello world")             # ~100ms, no IME dance
+b.text("héllo 👋", clear=True)    # unicode/emoji; clear empties the field first
+b.swipe(540, 1600, 540, 400)      # scroll
+b.key(66)                         # keyevent (66 = ENTER)
+b.screenshot("screen.png")
+
+path, legend = b.marks()          # numbered Set-of-Marks screenshot; the
+b.tap(legend[3])                  # vision model picks a number, you tap it
+
+b.prefetch_ui()                   # start the next dump in the background
+# ... do other work (e.g. the model decides the next action) ...
+b.ui()                            # returns the prefetched result instantly
+```
+
+CLI (installed as `aab`):
+
+```sh
+aab ui                    # dump elements, one per line (dump latency on stderr)
+aab tap --text Post       # tap by text / --id / --desc
+aab tap --grid C7         # or grid cell, or: aab tap 540 1200
+aab text "a caption"      # --clear to empty the field first
+aab marks annotated.png   # numbered overlay + legend for the vision fallback
+aab screenshot out.png
+aab swipe 540 1600 540 400
+aab key 66                # keyevent (66 = ENTER)
+aab -s SERIAL ...         # pick a device when several are connected
+```
+
+After a session, restore the device's normal keyboard with
+`adb shell ime reset` (the bridge leaves ADBKeyboard active for speed).
+
+## Measured performance
+
+All numbers measured live on a Samsung SM-S721B (Galaxy S24 FE), host on USB:
+
+| Operation | Cost | Notes |
+|---|---|---|
+| `tap` / `swipe` / `key` | ~0.1s | `input` is cheap on modern Android |
+| `text()` via ADBKeyboard | ~0.1s | any length, any unicode |
+| first `text()` of a session | ~1.5s | one-time IME switch + settle wait |
+| `screenshot()` | ~0.8s | `screencap -p` over exec-out |
+| `ui()` — `uiautomator dump` | **2.1–3.0s** | the bottleneck: fresh uiautomator process per call |
+| `ui()` on very heavy screens | up to ~6s | seen on Facebook Marketplace's tree |
+| old vision loop (replaced) | 2–5s/action | plus missed taps and retries |
+| old IME text dance (replaced) | ~4s/field | now ~0.1s |
+
+Two findings worth knowing:
+
+- `input text` costs ~35ms **per character** (key events are injected one by
+  one), so a 60-char caption takes ~2s. The ADBKeyboard broadcast commits the
+  whole string at once — that's why it's the primary text path.
+- Switching the IME and broadcasting immediately drops the text: the IME
+  hasn't bound to the field yet. One settle wait after the once-per-session
+  switch fixes what the old stack worked around with four sleeps per field.
+
+An agent action cycle (dump → find → tap) is therefore ~2.5s, ~95% of it the
+dump. Two ways to attack that, both built in:
+
+- **Prefetch** (`prefetch_ui()`): start the next dump right after an action so
+  it overlaps the caller's own work — in an agent loop the model's 1–3s of
+  thinking hides most of the dump for free. Roughly 2× on real flows, no
+  device changes.
+- **The optional fast backend** below: ~5–8× flat, one APK install per device.
+
+## Optional fast backend (fleet phones)
+
+Plain devices need nothing and keep working unchanged. For sub-second action
+cycles, install [openatx/android-uiautomator-server](https://github.com/openatx/android-uiautomator-server)
+(MIT) on the device and keep its instrumentation running:
+
+```sh
+adb install app-uiautomator.apk
+adb install app-uiautomator-test.apk
+adb shell am instrument -w com.github.uiautomator.test/androidx.test.runner.AndroidJUnitRunner
+```
+
+It keeps uiautomator alive and serves the same hierarchy XML over HTTP —
+Bridge probes for it once per session (`adb forward` + `/ping`) and uses it
+automatically; `aab ui` reports which backend served the dump, and if the
+server dies mid-session the bridge falls back to plain dumps. Expected dumps:
+~0.1–0.3s instead of 2–3s. **Not yet verified against real hardware** — the
+plain-ADB path remains the default and the regression baseline.
+
+## Limitations
+
+- Thin or absent view trees (games, canvas-drawn UIs, some WebViews) — use
+  the Set-of-Marks / grid fallback tier.
+- `FLAG_SECURE` screens refuse screenshots (banking apps, private modes).
+- `uiautomator dump` can fail mid-animation; the bridge retries once, then
+  raises so callers can fall back to the vision tier.
+- Unicode text, `clear=`, and fast typing need ADBKeyboard installed.
+
+## Roadmap
+
+- **Fleet-phone verification of the fast backend** — the HTTP backend ships
+  mock-tested; its first live run happens on a fleet device, not a personal
+  phone.
+- **[ContentSwarm](https://github.com/kelvincushman/ContentSwarm)
+  integration** — element-target taps, layout-robust flow recording with
+  per-replay run reports, a `/ui` endpoint, and prefetch-during-model-thinking
+  — lives downstream of this library, driven by
+  [Orphus](https://github.com/kelvincushman/orphus) agents.
+
+## License & credits
+
+Apache-2.0, © 2026 Kelvin Lee. See `LICENSE` and `NOTICE` — redistributions
+must retain the attribution notice.
+
+ADBKeyboard by [senzhk](https://github.com/senzhk/ADBKeyBoard) inspired the
+unicode input approach and is driven via its documented broadcast intents.
+This project contains no ADBKeyboard code.

adb_agent_bridge-0.1.0/README.md

@@ -0,0 +1,189 @@
+# ADB Agent Bridge
+
+Fast, accurate agent→Android control over plain ADB. Nothing to install on the
+device: the accessibility tree Android already exposes via `uiautomator dump`
+gives every element's text, resource-id, content-desc, and bounds — so an AI
+agent taps element centers instead of guessing pixels from screenshots.
+
+**Developed by [Kelvin Lee](https://github.com/kelvincushman)** · Apache-2.0
+
+## Why this exists
+
+This tool came out of running a real fleet of Android phones driven by AI
+agents — [ContentSwarm](https://github.com/kelvincushman/ContentSwarm), an
+open phone-agent framework for content automation, with
+[Orphus](https://github.com/kelvincushman/orphus) as the agent harness
+driving it. The stack we inherited was built the way most phone automation
+is: **for humans watching a screen, not for agents**. Two things made it
+slow and unreliable:
+
+- **The blind pixel loop.** Every action meant: capture a 1–2 MB screenshot,
+  send it to a vision model, have the model guess an (x, y) coordinate, then
+  `input tap` and hope. 2–5 seconds per action, and vision models regress raw
+  pixel coordinates poorly — taps missed, flows derailed, retries compounded.
+- **The text dance.** Typing one caption meant swapping the IME with four
+  1-second sleeps (~4s per field), and the on-screen keyboard hid the app's
+  media picker at exactly the wrong moment.
+
+The fix turned out to require almost nothing new. Android already ships the
+whole answer over plain ADB, on every device, with zero on-device install:
+`uiautomator dump` returns the full view hierarchy — the same tree an
+accessibility service sees — as XML. Parse it host-side, find the element by
+its text or id, tap its bounds center. **Element-center taps can't miss.**
+Text goes through a broadcast to [ADBKeyboard](https://github.com/senzhk/ADBKeyBoard)
+in ~100ms, with the IME switched once per session instead of once per field.
+
+The guiding principle throughout: *the laziest solution that actually works*.
+No custom accessibility service, no signed APKs, no on-device daemon — until
+measured latency proves one is needed. Every dump is timed
+(`Bridge.device.last_dump_ms`) so that decision is made with data, not vibes.
+
+## The three addressing tiers
+
+1. **Semantic** (default): `find(text="Post")` → tap the element's center.
+   Exact, layout-robust, no vision model in the loop.
+2. **Set-of-Marks / grid** (vision fallback): when the tree is thin (games,
+   canvas, some WebViews), `marks()` draws numbered boxes on a screenshot —
+   the model picks a number, you tap that element. Or address a 10-column
+   grid cell like `"C7"`.
+3. **Raw coordinates**: `tap((x, y))` still works when you need it.
+
+## Install
+
+```sh
+pip install "adb-agent-bridge @ git+https://github.com/kelvincushman/adb-agent-bridge"
+# or from a checkout: pip install -e .
+```
+
+(Not yet on PyPI — install from git. Pin a commit SHA with `@<sha>` for
+reproducible installs.)
+
+Requirements:
+
+- `adb` on the host PATH, device with USB debugging enabled.
+- [ADBKeyboard](https://github.com/senzhk/ADBKeyBoard) on the device for fast
+  and unicode text input (recommended). Without it, plain-ASCII text still
+  works via `input text`.
+
+## Quick start
+
+```python
+from adb_agent_bridge import Bridge
+
+b = Bridge()                      # or Bridge("SERIAL") with multiple devices
+b.ui()                            # -> [Element(text=..., id=..., bounds=...), ...]
+b.find(text="Post")               # first element whose text matches
+b.tap(b.find(text="Post"))        # taps the element's center — can't miss
+b.tap((540, 1200))                # raw coordinates
+b.tap("C7")                       # grid cell (10 square columns A-J, rows from 1)
+b.text("hello world")             # ~100ms, no IME dance
+b.text("héllo 👋", clear=True)    # unicode/emoji; clear empties the field first
+b.swipe(540, 1600, 540, 400)      # scroll
+b.key(66)                         # keyevent (66 = ENTER)
+b.screenshot("screen.png")
+
+path, legend = b.marks()          # numbered Set-of-Marks screenshot; the
+b.tap(legend[3])                  # vision model picks a number, you tap it
+
+b.prefetch_ui()                   # start the next dump in the background
+# ... do other work (e.g. the model decides the next action) ...
+b.ui()                            # returns the prefetched result instantly
+```
+
+CLI (installed as `aab`):
+
+```sh
+aab ui                    # dump elements, one per line (dump latency on stderr)
+aab tap --text Post       # tap by text / --id / --desc
+aab tap --grid C7         # or grid cell, or: aab tap 540 1200
+aab text "a caption"      # --clear to empty the field first
+aab marks annotated.png   # numbered overlay + legend for the vision fallback
+aab screenshot out.png
+aab swipe 540 1600 540 400
+aab key 66                # keyevent (66 = ENTER)
+aab -s SERIAL ...         # pick a device when several are connected
+```
+
+After a session, restore the device's normal keyboard with
+`adb shell ime reset` (the bridge leaves ADBKeyboard active for speed).
+
+## Measured performance
+
+All numbers measured live on a Samsung SM-S721B (Galaxy S24 FE), host on USB:
+
+| Operation | Cost | Notes |
+|---|---|---|
+| `tap` / `swipe` / `key` | ~0.1s | `input` is cheap on modern Android |
+| `text()` via ADBKeyboard | ~0.1s | any length, any unicode |
+| first `text()` of a session | ~1.5s | one-time IME switch + settle wait |
+| `screenshot()` | ~0.8s | `screencap -p` over exec-out |
+| `ui()` — `uiautomator dump` | **2.1–3.0s** | the bottleneck: fresh uiautomator process per call |
+| `ui()` on very heavy screens | up to ~6s | seen on Facebook Marketplace's tree |
+| old vision loop (replaced) | 2–5s/action | plus missed taps and retries |
+| old IME text dance (replaced) | ~4s/field | now ~0.1s |
+
+Two findings worth knowing:
+
+- `input text` costs ~35ms **per character** (key events are injected one by
+  one), so a 60-char caption takes ~2s. The ADBKeyboard broadcast commits the
+  whole string at once — that's why it's the primary text path.
+- Switching the IME and broadcasting immediately drops the text: the IME
+  hasn't bound to the field yet. One settle wait after the once-per-session
+  switch fixes what the old stack worked around with four sleeps per field.
+
+An agent action cycle (dump → find → tap) is therefore ~2.5s, ~95% of it the
+dump. Two ways to attack that, both built in:
+
+- **Prefetch** (`prefetch_ui()`): start the next dump right after an action so
+  it overlaps the caller's own work — in an agent loop the model's 1–3s of
+  thinking hides most of the dump for free. Roughly 2× on real flows, no
+  device changes.
+- **The optional fast backend** below: ~5–8× flat, one APK install per device.
+
+## Optional fast backend (fleet phones)
+
+Plain devices need nothing and keep working unchanged. For sub-second action
+cycles, install [openatx/android-uiautomator-server](https://github.com/openatx/android-uiautomator-server)
+(MIT) on the device and keep its instrumentation running:
+
+```sh
+adb install app-uiautomator.apk
+adb install app-uiautomator-test.apk
+adb shell am instrument -w com.github.uiautomator.test/androidx.test.runner.AndroidJUnitRunner
+```
+
+It keeps uiautomator alive and serves the same hierarchy XML over HTTP —
+Bridge probes for it once per session (`adb forward` + `/ping`) and uses it
+automatically; `aab ui` reports which backend served the dump, and if the
+server dies mid-session the bridge falls back to plain dumps. Expected dumps:
+~0.1–0.3s instead of 2–3s. **Not yet verified against real hardware** — the
+plain-ADB path remains the default and the regression baseline.
+
+## Limitations
+
+- Thin or absent view trees (games, canvas-drawn UIs, some WebViews) — use
+  the Set-of-Marks / grid fallback tier.
+- `FLAG_SECURE` screens refuse screenshots (banking apps, private modes).
+- `uiautomator dump` can fail mid-animation; the bridge retries once, then
+  raises so callers can fall back to the vision tier.
+- Unicode text, `clear=`, and fast typing need ADBKeyboard installed.
+
+## Roadmap
+
+- **Fleet-phone verification of the fast backend** — the HTTP backend ships
+  mock-tested; its first live run happens on a fleet device, not a personal
+  phone.
+- **[ContentSwarm](https://github.com/kelvincushman/ContentSwarm)
+  integration** — element-target taps, layout-robust flow recording with
+  per-replay run reports, a `/ui` endpoint, and prefetch-during-model-thinking
+  — lives downstream of this library, driven by
+  [Orphus](https://github.com/kelvincushman/orphus) agents.
+
+## License & credits
+
+Apache-2.0, © 2026 Kelvin Lee. See `LICENSE` and `NOTICE` — redistributions
+must retain the attribution notice.
+
+ADBKeyboard by [senzhk](https://github.com/senzhk/ADBKeyBoard) inspired the
+unicode input approach and is driven via its documented broadcast intents.
+This project contains no ADBKeyboard code.