01. Start with a command you actually use
Run a useful command in ADB Companion, then favorite it from the result card. A favorite is a saved action, so the command is available in Actions without you having to search through old output.
Start small: your device model, a package lookup, or a storage check. A short library you recognize is more useful than a long list of commands you have never tried.
getprop ro.product.model02. Replace the part that changes
To reuse a command with different values, create an action with a placeholder. For a package lookup, save the template below and give it a clear name such as “Find a package.”
When you run this action, the app asks for query and shows the exact command. Placeholder names start with a letter and can contain letters, numbers, and underscores. Enter a value for every parameter.
pm list packages {{query}}03. Keep your favorites within reach
Pin your most-used actions from their menu. Reorder pins with a long press, or use Move up and Move down in the menu.
An action runs on the currently selected device. Check the device name before you run it. Each device has its own terminal history and draft, while the Actions library gives you reusable commands across your workflows.
04. Take your library with you
Settings includes Export actions and Import actions using Android’s file picker. Exports include your custom actions and starters you have edited, favorited, or pinned; untouched starter actions are omitted.
Imported actions get new IDs and do not run automatically. Reimporting the same file creates copies. Review imported commands before executing them, and remember that action export is not a backup of pairing credentials or command history.
One more useful thing in your toolkit.
Keep the commands you use. ADB Companion will keep them close.