External connections
Bridge and Android integrations
ScriptTap can exchange complete scripts and selected diagnostic assets with authorized computer-side tools, and complete scripts can be started through supported Android shortcut and intent entry points.
AI ADB Bridge
The authenticated local Bridge exposes 20 exact routes for health and contract discovery, script inspection and mutation, atomic multi-script transactions, Run Logs, optional screenshot reads, and asset operations.
Complete script changes are preflighted before adoption. Rejected fields or structures leave the live script unchanged, preserving one atomic accepted result.
Current command contract
Bridge clients should follow the generated JSON command contract for exact current command names, fields, value types, nested shapes, and choices. The function reference explains their user-visible behavior.
Each published route identifies its parameter location, body policy, and encoding. Clients can distinguish query filters, bodyless operations such as Duplicate, and exact UTF-8 JSON mutations directly from contract discovery. Invalid encoding is rejected before a script or asset changes.
Current mutation requests must use the current contract. Retired compatibility forms are limited to supported read/import conversion and are not alternate writer forms; unsupported aliases, fields, and structures are rejected before the live script changes.
Script inspection returns the stored body as-is, including incomplete or older facts, so a read is not automatically a current write request. Deleting a script removes Calls to that script while preserving other authored values in its callers.
Shortcuts and external starts
ScriptTap Shortcuts launch the app, select a complete enabled script, and start Play when it is ready. Disabled scripts do not start; deleting a script revokes its shortcut and asks Android to disable the launcher entry. Authorized external starts use the normal ScriptTap validation, permission, entitlement, and Play preparation paths.
Secure local access
The Bridge binds to the device loopback interface and uses explicit user enablement, a verified ScriptTap account, an active token, ADB forwarding, and the live app access gate. It accepts contract-defined ScriptTap read and mutation operations through the published routes.