mobium session
This tool on every surface: CLI · MCP · Python · JavaScript · Go · Java · .NET
Start or end the session on a device
The explicit start and end of a device session. Never required: every other command opens a session on first use.
start opens it now, so the slow first start — installing UiAutomator2, building WebDriverAgent on an iPhone — happens here rather than inside your first tap. --platform ios picks wda; --app launches an app fresh once the session is up: stopped first if it was running, so the session begins at its first screen. Its data is kept.
end closes one device's session with the daemon's own teardown:
accessibility settings put back, a recording or route stopped, WebViews
detached, the device-side server stopped, and the app --app launched
stopped too — apps it did not launch are left alone. Ending a session
that is not open succeeds and says so. mobium daemon stop ends every
device's.
With no argument, or status, lists the sessions open.
Usage
mobium session [start | end | status] [flags]
Flags
| Flag | Type | Default | What it does |
|---|---|---|---|
--app | string | with start: a package name or bundle id to launch once the session is up | |
--platform | string | "android" or "ios"; with start, "ios" picks wda |
And the global flags.
Examples
Start a session and launch the app fresh
mobium session start --app com.android.settings
Printed on an Android 15 emulator:
session already open on emulator-5554 (android, uiautomator2); com.android.settings was launched fresh and is in the foreground
End it, putting back what it changed
mobium session end
Printed on an Android 15 emulator:
session ended on emulator-5554; anything it changed for the session is put back; com.android.settings, which the session launched, was stopped
More, from mobium session --help
mobium session start --device emulator-5554 --app com.android.settings
mobium session start --platform ios --app com.apple.Preferences
mobium session status
mobium session end --device emulator-5554
No screenshot: a session is the connection to the device, and the screen shows nothing of it.
The tool
session calls app_session; its arguments and what every client calls it are there.