Skip to main content
An agent on your phone acts as you, in your accounts. Phones has three protections: taps that could publish, send, pay or delete wait for your approval, every phone has a rate limit, and only a signed-in person can approve.

Which taps wait for approval

Before a tap or a long press, Appeeky Desktop reads the label of the element under it. The action pauses when the label contains one of these words: Matching ignores upper and lower case and looks for whole words. Send message pauses. Sender and Postpone don’t. A tap by x and y is checked too: Appeeky Desktop looks up which element from the latest observation is under that point.
The approval gate is a safety net, not a guarantee. It does not pause:
  • A button that has only an icon and no text label, or a label that uses none of the words above.
  • A tap on a point that is not on a known element of the latest observation.
  • Typing, pressing a key, swiping or scrolling. Pressing enter in a message field can send the message.
Give agents tasks you are comfortable with them finishing, and use accounts and phones you are willing to let them act on.

How an approval works

1

The action pauses

The agent’s request stays open. Nothing is tapped.
2

You are asked

Appeeky sends an email to your account address, with a subject like Approve on Pixel_8: Tap “Send” and a link to the Phones page. A card appears under Waiting for you on /dashboard/phones.
3

You decide

The card shows the screenshot the agent was looking at, the action and label, the reason, the phone, and when the request expires. Choose Approve or Deny.
4

The agent continues or stops

After Approve, the tap runs and the agent gets the new screen. After Deny, the agent gets the error APPROVAL_DENIED and is told to stop and ask you what to do.

Expiry

A request expires 10 minutes after it was created. An expired request counts as a denial. The email tells you how many minutes are left.

Statuses

Recent decisions on the Phones page lists the latest approved, denied and expired requests.

Who can approve

Only a person signed in to the dashboard can approve or deny. An API key can list approvals but can’t decide them, so an agent can never approve its own tap. Approvals are also available over the API for your own tools. See Approvals in the API reference.

Rate limits

Each phone accepts at most:
  • 30 actions per minute
  • 600 actions per hour
Taps, long presses, swipes, scrolls, typing, key presses, opening apps and pushing media count. Observing the screen and listing apps or phones do not. Manual actions from the Phone page of Appeeky Desktop count too, because they use the same phone. Above the limit an action fails with the code RATE_LIMITED and a message that says which limit was hit. Wait and try again.

What runs where

What leaves your Mac:
  • Screenshots and element lists go to the agent that asked for them. With the phone agent, that is Appeeky’s own agent.
  • The approval screenshot is stored with the approval request. The API returns it only while the request is pending.
What stays on your Mac:
  • An action log. Appeeky Desktop writes one line per action to ~/.agentthumbs/logs/, one file per day. For typed text it records the length, not the text.

Good practice

  • Turn Share phones with Appeeky off when you are not using it.
  • Read the screenshot on the approval card before you approve. It shows what the agent saw.
  • Don’t put passwords or payment details in a task or prompt unless the agent needs them for that task. Agents are told never to enter such details on their own.
  • Use a phone and accounts set aside for this work if you run agents often.