Skip to content

AICore Plus Bridge

Jump to bottom
thejaustin edited this page Sep 19, 2026 · 2 revisions

AICore+ Automation Bridge

The AICore+ Automation Bridge is a Shizuku+ exclusive feature designed to facilitate advanced, rootless UI automation and intelligent screen context extraction. It achieves this by providing a privileged, proxied AccessibilityService.

The Problem

Modern AI-driven automation tools (like Tasker integrating with LLMs, or local AI assistants) need to understand what is on the screen and interact with it. Traditionally, this required:

  1. Accessibility Services: Which users are hesitant to grant to every new app, and which can cause significant system lag if poorly written.
  2. Root Access: To simulate physical taps/swipes at the hardware level.

The Shizuku+ Solution

Shizuku+ introduces AICorePlusService, a single, highly optimized Accessibility Service. Once enabled by the user, authorized Shizuku apps can request the bridge to perform actions on their behalf, eliminating the need for multiple apps to request their own accessibility permissions.

Capabilities

The bridge exposes powerful, low-latency methods to authorized clients:

  • dumpHierarchy(): Dumps the active window's UI hierarchy into a structured XML format. This is significantly faster than using the traditional uiautomator dump command and provides immediate context for AI agents to parse.
  • performTap(x, y): Simulates a physical screen tap at specific coordinates.
  • performSwipe(startX, startY, endX, endY, durationMs): Simulates a physical swipe gesture, mimicking human interaction.

Enablement & feature flags

The bridge is off by default for its automation actions and layered behind three cascading toggles (Settings → Shizuku+ features → Intelligence Bridge). Each depends on the one above it:

Toggle (UI name) Feature key Default Gates
Intelligence Bridge ai_core_plus On The bridge binder itself. With this off, the server returns no AICore+ interface at all.
AI Core (Master) ai_core_master Off Privileged screen-context reads — dumpHierarchy/native window crawler and NPU scheduling (also requires npu_acceleration).
Experimental AI Automation ai_core_experimental Off The input-injection actions — performTap, performSwipe, gesture dispatch.

Both the server (AICorePlusImpl) and the manager-side AICorePlusService re-check these flags on every call, so a client can't reach tap/swipe/dump unless the user has explicitly opted into the experimental tier. Because ai_core_master and ai_core_experimental both depend on ai_core_plus, turning the master Intelligence Bridge toggle off force-disables everything beneath it.

Experimental status: the tap/swipe/hierarchy actions are gated behind Experimental AI Automation precisely because they're still maturing. Expect behaviour to change, and don't build a production automation flow on them without the toggle enabled and tested on your device.

Privacy & Security

The AICore+ Bridge is designed with security in mind:

  • No Passive Observation: Unlike many accessibility services that constantly monitor the screen for changes, the AICore+ Bridge acts primarily as a responder. It only dumps the hierarchy or performs an action when explicitly requested by an authorized app.
  • Strict Authorization: Only apps that the user has explicitly granted Shizuku permissions can utilize the bridge.
  • Data Protection: It respects standard Android security flags (like FLAG_SECURE) and does not observe passwords or personal data within secure fields.

Clone this wiki locally