What Happens When Agent Ethan Gets Stuck
When Agent Ethan cannot finish something it already started, the short version is this: it stops in a place you can see, tells you in plain words what it was doing and where it got stuck, and hands your phone back to you. It does not keep guessing, it does not quietly loop in the background, and by default it does not push through a risky step just to mark the task done. An app that looks different than expected, a choice only you can make, a goal that turns out not to be possible, or simply running low on confidence: each of these ends the task the same safe way.
Stuck partway through is different from unsure at the start
There is a difference between Ethan not understanding a request and Ethan not being able to finish one that already began. When a request is unclear, such as a name that matches more than one contact, Ethan asks a quick question with numbered choices rather than guessing. This post is about a different moment: getting stuck inside a task that is already underway, once Ethan has already started acting on your behalf.
Picture Ethan a few steps into a task. It said "On it," opened the right app, and has already tapped and scrolled through two or three screens. Then something in front of it will not let it continue: the screen does not match what it expected, the next step needs a judgment call, the goal turns out not to exist, or it simply is not confident enough to keep going. This is what we mean by getting stuck, and it is the subject of this post.
Why a clean stop beats a guess
Ethan is built around one rule for moments like this: a task that cannot be finished safely should end with a visible stop, not a guess. Guessing past a confusing screen can tap the wrong thing. Quietly retrying the same step again and again looks, from the outside, like the app has frozen. Pushing through to mark a task finished when it is not sure is worse than simply saying so.
This is close to how AI agents are generally meant to be designed, not just how Ethan happens to work. Anthropic's own research on building agents describes pausing for human feedback at checkpoints or when an agent hits a blocker, and setting clear stopping conditions so an agent does not keep going past the point where it should stop. Ethan applies the same idea to your phone: when it hits a blocker partway through a task, it pauses for you instead of pushing on alone.
This is a different situation from the stop Ethan makes before a payment or a permanent delete, which by default is a line it holds on purpose every time, whether or not anything has gone wrong. Getting stuck is Ethan running into something it did not expect or cannot judge for you.
What you actually see when it happens
Ethan keeps you informed the whole way, not just at the stuck moment. It begins each task with a short plan ("On it"), and a small pill stays on screen the entire time with Pause and Stop, so you can take back control whenever you want, not only when it gets stuck.
When it cannot continue, that pill becomes the place it explains itself. Instead of a technical error, you get a plain sentence about what it was doing and where it stopped, something close to: "I was adding your 9am flight to the calendar, but this screen looks different from what I expected, so I've stopped here for you to finish." You are not left guessing why it stopped or how far it got.
From there, the phone is genuinely back in your hands. Nothing is left half finished in a way that hides what happened: you can see the screen Ethan was on, read its note, and decide what to do next.
The four situations that stop a task partway through
Ethan sees each screen through Android's Accessibility Service, which gives it a structured view of what is on screen, such as buttons and labels, along with a screenshot when text alone is not enough. Most stuck moments fall into one of four situations.
In every one of these four, the outcome is the same: a clean stop with an explanation, not a silent failure and not an open-ended loop.
- An app looks different than expected. Apps get redesigned, a button gets renamed, or a menu moves, and a screen no longer matches what Ethan was ready for.
- A step needs a decision only you can make. Something on screen is ambiguous in a way that is not a simple pick-one-of-several choice, so Ethan stops rather than choose for you.
- The goal turns out to be impossible. The feature might not exist in that app, the item might be unavailable, or what you asked for might not be on your phone at all.
- It runs out of confidence. Sometimes nothing on screen looks obviously wrong, but Ethan is not sure enough about the next step to keep going safely.
What to do after Ethan hands the phone back
A stop is a handoff, not a dead end. Read the note Ethan leaves, since it tells you exactly what it was doing and where it stopped. From there you usually have two simple options: finish the remaining step yourself on the screen in front of you, or start a new task once you know the detail Ethan was missing, such as the app's new menu name or the choice it could not make for you.
If you want to look back later, task history stays on your phone, and you can clear it any time from Settings. The accessibility service that lets Ethan read the screen only does so while a task you started is running, and you can turn it off at any time under Android Settings, then Accessibility, whether or not anything got stuck.
A stop is by design, not a bug
No agent that works across other people's apps will finish every task. Apps change, goals are sometimes not possible, and screens are not always clear even to a person looking at them. Ethan is not built to promise it will always succeed. It is built so that when it cannot, that moment is honest: a visible pause, a plain explanation, and your phone handed back, rather than a guess you did not ask for.
That is the trade we think is worth making. A task that sometimes ends in a clean stop is easier to trust than one that always claims to finish.
Frequently asked questions
Is getting stuck the same as Ethan asking which option I meant?
No. Ethan asking which contact or item you meant is a numbered pick-one-of-several question, and it can come early or a little way into a task. Getting stuck is different: it is not a simple pick from a list. It happens when Ethan hits something partway through a task, such as a changed screen or a goal that turns out to be impossible, that needs a judgment call only you can make rather than a numbered choice.
Will Ethan keep trying the same step over and over?
No. Ethan is built to recognize when to stop rather than keep attempting a step it is not confident about. A stop is always visible and explained, never a silent loop running in the background.
Can I see what Ethan was doing when it got stuck?
Yes. It tells you in plain words what it was doing and where it stopped, right when it happens. Task history also stays on your phone afterward, and you can clear it any time from Settings.
What should I do after Ethan hands the phone back?
Read its short explanation, then either finish the remaining step yourself or start a new task with the detail it needed, such as a renamed button or the choice only you could make.
Sources
Ready to try it? Download Agent Ethan or read how it works.