I built ScriptTap because I’ve used automation tools for years, and they often fall into one of two categories: powerful but difficult to learn, or simple but too limited. ScriptTap is meant to combine both—easy to use, but capable of complex automation.
To simplify script creation, ScriptTap includes an intuitive editor and is designed to work with AI agents. For example, you can ask ChatGPT:
“I’d like a ScriptTap JSON for [your need] on my device. Use https://scripttap.com/ai/ as the source of truth.”
A compatible AI can return a .scripttap.json file that imports directly into the app. Coding agents such as Codex or Claude can also use ScriptTap’s ADB bridge to create scripts directly on an ADB-connected device, where you can inspect, run, and refine them.
One major goal is reducing unnecessary AI usage. AI agents can sometimes perform actions directly on a device, but repeating the same workflow consumes tokens and introduces opportunities for mistakes. With ScriptTap, AI can create or modify the workflow once, then reuse a reviewed script whenever needed. The script logic executes deterministically, while actual results can still depend on the device state it observes. This improves both cost efficiency and execution consistency.
Scripts can also be exposed as Android home-screen shortcuts. AI agents or other automation tools can invoke them when they support the appropriate shortcut, deep-link, intent, ADB, or device-control flow. This can integrate ScriptTap with tools such as Tasker, MacroDroid, Automate, and Samsung Routines.
ScriptTap is especially useful for screen-aware automation. Scripts can locate images and UI elements, detect pixel-color changes, work with files and variables, and perform screen capture → analysis → taps/text entry. It can also produce detailed run logs. Large scripts are supported; I’ve tested workflows containing roughly 5,000 commands.
This also makes ScriptTap useful alongside other automation tools. If another app lacks a specific screen-interaction capability, a ScriptTap shortcut or compatible intent can become one step inside the larger workflow.
ScriptTap entered Open Beta on August 20, 2026 and is currently available to everyone on Google Play.
I’d especially appreciate feedback from automation enthusiasts on the complete workflow:
AI chat/coding agent → create script → import/open it → test → edit/refine
If any part feels confusing, unreliable, or unnecessarily difficult, I’d like to know. Thanks for checking it out!
P.S. A few limitations and safeguards:
a. Not every AI can return downloadable files.
b. Some AI models may misunderstand the ScriptTap schema. ScriptTap validates imported files and reports structural or syntax errors when something is wrong.
c. Scripts imported from AI packages start disabled and require user review and enabling. Imported packages also do not create shortcuts automatically; the user must create those separately if the script is meant to be invoked by AI or another automation tool.
I built ScriptTap because I’ve used automation tools for years, and they often fall into one of two categories: powerful but difficult to learn, or simple but too limited. ScriptTap is meant to combine both—easy to use, but capable of complex automation.
To simplify script creation, ScriptTap includes an intuitive editor and is designed to work with AI agents. For example, you can ask ChatGPT:
“I’d like a ScriptTap JSON for [your need] on my device. Use https://scripttap.com/ai/ as the source of truth.”
A compatible AI can return a .scripttap.json file that imports directly into the app. Coding agents such as Codex or Claude can also use ScriptTap’s ADB bridge to create scripts directly on an ADB-connected device, where you can inspect, run, and refine them.
One major goal is reducing unnecessary AI usage. AI agents can sometimes perform actions directly on a device, but repeating the same workflow consumes tokens and introduces opportunities for mistakes. With ScriptTap, AI can create or modify the workflow once, then reuse a reviewed script whenever needed. The script logic executes deterministically, while actual results can still depend on the device state it observes. This improves both cost efficiency and execution consistency.
Scripts can also be exposed as Android home-screen shortcuts. AI agents or other automation tools can invoke them when they support the appropriate shortcut, deep-link, intent, ADB, or device-control flow. This can integrate ScriptTap with tools such as Tasker, MacroDroid, Automate, and Samsung Routines.
ScriptTap is especially useful for screen-aware automation. Scripts can locate images and UI elements, detect pixel-color changes, work with files and variables, and perform screen capture → analysis → taps/text entry. It can also produce detailed run logs. Large scripts are supported; I’ve tested workflows containing roughly 5,000 commands.
This also makes ScriptTap useful alongside other automation tools. If another app lacks a specific screen-interaction capability, a ScriptTap shortcut or compatible intent can become one step inside the larger workflow.
ScriptTap entered Open Beta on August 20, 2026 and is currently available to everyone on Google Play.
I’d especially appreciate feedback from automation enthusiasts on the complete workflow:
AI chat/coding agent → create script → import/open it → test → edit/refine
If any part feels confusing, unreliable, or unnecessarily difficult, I’d like to know. Thanks for checking it out!
P.S. A few limitations and safeguards:
a. Not every AI can return downloadable files.
b. Some AI models may misunderstand the ScriptTap schema. ScriptTap validates imported files and reports structural or syntax errors when something is wrong.
c. Scripts imported from AI packages start disabled and require user review and enabling. Imported packages also do not create shortcuts automatically; the user must create those separately if the script is meant to be invoked by AI or another automation tool.