Security and control
You decide how far it goes
An agent with a phone needs limits. They are enforced by the server, not left to the model.
Never bypasses a lock
With a PIN, pattern or password set, the agent asks a human instead of trying to get around it.
Approvals
Risky actions pause and wait for your yes. Long runs ask whether to continue after a set number of actions.
Budgets and cost caps
Limit actions per run and spend per run. Unattended runs simply stop at the limit.
Audit trail
Every step is an event with its screenshots, so you can replay what happened and why.
App policy
Decide which apps the agent may open, per task. Unattended runs only get the apps you allow.
Secrets stay out
Passwords are never recorded in Flows and typed secrets are redacted from the history.
FAQ
Questions people ask first
Do I need to root my phone?
No. DuckClick uses USB debugging (adb) and a small input method that you enable once. Nothing is rooted or jailbroken.
Which phones are supported?
Android phones with USB debugging. It has been tested on Android 11. iPhone is not supported.
Which AI models can I use?
Any provider DuckClick's agent runtime supports, plus any OpenAI-compatible gateway. The model needs tool calling, and image input if you want it to read screenshots.
What does a Flow cost to run?
Nothing in model usage. A Flow is replayed by an interpreter on the phone and only goes back to the agent if a step fails.
Can it get into my accounts or bypass a login?
It uses the apps the way you do. It does not bypass lock screens, and when a login or captcha needs a person, it stops and asks.
Where does my data go?
Screens and event history stay in your console. Screenshots are sent to the model provider you chose, so pick one you trust.
Give your phone a duck to do the tapping.
Connect a phone, say what you want, and watch it get done.