- Who it helps
- People evaluating phone assistants and developers building mobile agents.
- Availability
- Public maker report covers October 8–November 3, 2026. Opposable is an Android app; this review did not test installation or pricing.
What the log measures
Across 3,324 actions on 45 phones, the maker reports 305 failures, including 108 disconnected-phone failures. Most actions came through Claude. These are action outcomes, not completed-task success rates.
What remains uncertain
Battery management is a plausible contributor, but logs cannot distinguish it from lost signal or a powered-off phone. The app documents payment approvals and foreground-service changes; their enforcement was not independently tested.
What you can do
- Read the linked primary evidence and its access limits before planning a trial. Open reference ↗
Where the evidence stops
Small vendor sample; busy phones lost their earliest log entries. No causal comparison or device trial performed.
Sources read. Sources read November 5, 2026 UTC. No third-party project, model inference or complete product workflow was executed.
Sources & further reading
Web · paper
Opposable logs show why phone agents lose contact ↗
Primary page read November 5. Claims were checked against the page; the workflow was not executed.
Opposable · page checked 2026-11-05
Coverage note: Original YouTube demonstrations and independent cross-platform attention were not established. No end-to-end workflow was executed.
The record over time (1)
Dated source checks and published explanations. An observation date can differ from the original release date.
- · Added to Current
A small Android field log finds unreachable phones were a major cause of failed agent actions.