What Agent Ethan Will Never Touch

Agent Ethan is built to skip your password fields, PIN entry boxes, and one-time verification codes entirely: not a setting you switch on, but a rule built into how the app works. It will also not change critical settings, such as doing a factory reset or removing an account from the phone, even if you ask it directly. This goes further than its everyday habit of asking before it sends a message or places a call, which you can adjust in Settings. The lines below are not adjustable at all.

The two things Ethan will not cross

There are two separate rules here, and it helps to keep them apart. The first is about the fields themselves: password boxes, PIN pads, and the short codes sent by text message or an authenticator app. Ethan is built to pass over these while it works through a task, the same way you would want someone looking over your shoulder to glance away while you type a PIN.

The second rule covers a short list of settings that are hard or impossible to undo: a factory reset, or removing an account from the phone. Even if you ask Ethan directly to do either of these, it will not. The app's own onboarding describes this as a deliberate limit, not something you discover is simply missing.

Both rules sit underneath everything else Ethan does. A short plan, a pause button, and a gold ring around the next tap are all visible proof of what it is about to do. The password and critical-settings rule works differently: you do not see it happen, because the step never happens at all.

• Password fields, PIN pads and one-time codes: passed over entirely, every time.
• Critical settings such as a factory reset or removing an account: not changed, even on request.

Why a one-time code is worth protecting this much

A one-time code exists because a password alone is not always enough. The FTC's consumer advice compares the two to the lock on a doorknob and a deadbolt: the password gets someone to the door, and the code is the second lock that proves it is really you. That is exactly why people who want into your account ask for it by name.

The FTC describes a common pattern: someone poses as your bank or another contact you trust, claims there is a problem with your account, and then asks for the one-time code that was just sent to you by text or email. Google's own help page for Google Voice says much the same: do not reply to any request for your verification code, and Google employees will never ask you for one. Anyone asking is not who they claim to be, whether the ask comes from a caller on the phone or a program sitting on your screen.

That last point matters for a phone agent. If handing a code to a stranger on a call is a mistake, handing it to software that is also reading your screen deserves the same caution. That is why Ethan is built to pass over that field rather than read it and promise to behave.

What Android hands over when you turn Ethan on

Ethan works through Android's Accessibility Service, the same system door used by screen readers and other assistive tools. Android's own developer documentation describes what that service can do: it can inspect the content on screen, and it can perform actions such as clicking a button or scrolling a list, on the user's behalf. That is a meaningful amount of access, which is why Android requires a strict system-level permission check before any app can use it, and why you are the one who turns it on, in Settings, under Accessibility.

Android's documentation is direct about the scope of this tool: it calls an accessibility service a specialized tool, not a standard way to make an app accessible, and says to only build one if you are creating a general-purpose assistive tool. Ethan uses that access only while a task you started is running, and it stops looking once the task ends.

Because an accessibility service can technically see most of what is on a screen, having a narrower rule on top of that matters. Ethan's rule is to pass over password fields, PIN pads and one-time codes as a matter of how it is built, instead of relying on judgment in the moment about what looks safe to read.

A stronger line than its everyday confirm-before-send

Most of what Ethan does can be undone, so its everyday habit is to ask first and let you decide. By default, it asks before it sends a message or places a call, and it shows you the plan before it moves. In Settings, you can choose to let it press Send or Call on its own once it is confident about who the message or call is going to, if you want the convenience.

Passwords, PINs, one-time codes, and critical settings like a factory reset or removing an account sit outside that choice. There is no setting that makes these easier to skip past. They are a fixed rule, not a preference you adjust.

The same thinking shows up at the strongest stop of all: Ethan will fill in a form or get you to the final screen of a payment, a purchase, a booking, or a permanent delete, and then hand the phone back rather than press the last button itself.

What you can still see while it works

Ethan keeps its safeguards visible rather than quiet. It opens with a short plan ("On it"), a small pill stays on screen with Pause and Stop, and a hollow gold ring marks the exact control it is about to press next, so you always know what is coming.

If a request is unclear, it offers numbered choices instead of guessing. Screen content is read only while a task you started is actively running, not in the background and not afterward.

Because Ethan runs as an accessibility service, the switch is always within reach. You can turn it off at any moment under Android Settings, Accessibility, the same place you turned it on.

Frequently asked questions

Sources

• What's a verification code and why would someone ask me for it? (FTC Consumer Advice)
• Protect your verification code (Google Voice Help)
• Create an accessibility service (Android Developers)

Ready to try it? Download Agent Ethan or read how it works.