Capabilities & requirements

Choose the capability that answers your question, then check its prerequisites. This describes the Olef 3.0.2 CLI surface; Cloud availability also depends on account access and enabled features.

Capability	What you get	Requirements and limits
UI automation	Screen tree, selectors, actions, waits, and postconditions	Connected device service; accessibility-visible UI determines what can be read
Crash triage and logs	Parsed crashes, app-scoped logs, and diagnostic verdicts	Selected device and app context; unavailable evidence is reported explicitly
Java/Kotlin debugging	Breakpoints, stacks, variables, and stepping	Debuggable app; JDWP permits one debugger per process
Native and mixed debugging	LLDB-backed native state alongside Java/Kotlin	Compatible NDK/LLDB tools and target ABI; inspect readiness before attaching
Compose inspection	Compose nodes, semantics, source mapping, recomposition information	Compatible debuggable app and runtime attachment; source mapping needs project sources
Network inspection	HTTP(S) capture, interception, rules, and replay	Traffic must use the proxy; HTTPS needs CA trust; pinning may prevent interception
Record to test	Save viewer or agent actions as a Bash test folder	An Olef session and replayable app state; inspect generated assertions and low-confidence selectors
Test runner	Repeats, sharding, JUnit, HTML, and failure artifacts	Prepared app/device and Bash for generated scripts; no model or API key needed for replay
Local app builds	Apply source changes to the device	Project build setup, JDK, Android SDK, and dependencies
Olef Cloud	Managed Android workspace, builds, and emulator	Enabled Cloud access and account limits; no local Android SDK for the managed workflow
Play Store publishing	Not yet an end-to-end Olef capability	Release signing and submission remain separate

Check the installed version

olef --version
olef doctor --json
olef commands --json --describe "debug attach"

The installed CLI’s help and catalog govern its supported flags. The website’s command reference is a versioned snapshot.

Work alongside other tools

Olef works alongside Android Studio and other editors. Avoid two JDWP debuggers on the same process. Use olef test -- <command> when an external instrumentation tool needs the device’s single UiAutomation slot.

Device actions can change app state. Debugger evaluation can have effects. Review captured logs, screenshots, and recordings before sharing them; redaction has explicit limits, especially for pixels.