Tiber docs

The CLI reference is below. For the language itself — syntax, examples, everything else — head to the full docs.

ADB installed Device or AVD running

Not set up yet? Start on the downloads page →

Full documentation

Syntax, the alarm example walked through step by step, and the complete language reference now live at tiber-docs.oryvex.in.

Read the docs

CLI reference

Everything the tiber command supports, from tiber -h.

E:\tIBER\v1.0.0> tiber -h

usage: tiber [-h] [--version] [--device DEVICE] [--dry-run] [--verbose] [--live]
             [--live-cache SECONDS] [--start-from LABEL] [--end-before LABEL]
             [--interpret] [--write-to FILE] [--record-live FILE]
             [--input-device PATH] [--log-to FILE] [--components [FILE ...]]
             [file]

Run a .tib/.tbr/.tiber automation script, inspect UI components,
or start an interactive session.

Argument	What it does
file	Path to the .tib/.tbr/.tiber script. Omit when using --components, --interpret, or --record-live.
-h, --help	Show this help message and exit.
--version	Show the program's version number and exit.
--device DEVICE	Device serial, passed straight to uiautomator2.connect.
--dry-run	Print device actions without performing them.
--verbose	Print every device call as it runs.
--live	Treat every import(...) as live.
--live-cache SECONDS	Sets how long a live page's UI hierarchy can be reused before it is automatically refreshed from the device.
--start-from LABEL	Starts execution from the specified top-level label. Setup statements (import, live, rid, and func) defined before the label are still executed, while other statements before it are skipped.
--end-before LABEL	Stops execution immediately before the specified top-level label, allowing only the statements preceding that label to run.
--interpret	Start an interactive, line-by-line Tiber session (like the Python REPL) instead of running a script file.
--write-to FILE	With --interpret, save each accepted statement to this .tib file as you type it — a live recording of the session.
--record-live FILE	Record real taps/swipes on the connected device into a runnable .tib script at FILE. Requires a real device connection (not --dry-run). Doesn't capture typed text.
--input-device PATH	With --record-live, manually specify the touchscreen's /dev/input/eventN path if auto-detection fails.
--log-to FILE	Also write all input/output to this log file. Works alongside a normal run, --verbose, or --interpret.
--components [FILE ...]	Inspect UI components instead of running a script. With no FILE args, captures the live UI from the connected device via uiautomator2. Pass .xml/.json UI dumps to inspect those instead.

Ready to run this yourself?

Get Tiber and the tools around it on the downloads page.

Get Tiber