ADB & Android shell
Pick a device, open an interactive ADB shell tab, install APKs via Session → ADB → Install APK (adb install -r), and use bookmarks and shortcuts (root, remount, reboot, and more).
Adbnik is a single desktop app that keeps Android debugging, SSH, serial/COM, and local shells in one tabbed terminal, next to on-device file browsing and USB screen forwarding — so you spend less time switching windows and retyping connection details.
Many setups give you a terminal here, a file window there, and another place to start mirroring.
Adbnik is an ADB device workspace: an ADB explorer–style workflow for people who mix
phone or tablet work with SSH or serial — one consistent layout,
shared device selection, bookmarks, and session list. The name keeps ADB in view; the suffix is only a short handle.
The product name is Adbnik (PyPI: adbnik).
pip install adbnik — run adbnik.
Same captures as the GitHub README and PyPI. Files live under
docs/screenshots/ on main.
Pick a device, open an interactive ADB shell tab, install APKs via Session → ADB → Install APK (adb install -r), and use bookmarks and shortcuts (root, remount, reboot, and more).
Open SSH sessions from scratch or reuse remote file-access fields from the explorer. Uses the SSH client on your PATH (ssh).
Attach to COM ports at your chosen baud rate for boards and firmware logs — serial tabs alongside ADB and SSH in the same workspace.
Browse Android device storage and transfer files; remote host fields align with SSH when you work across device and server.
Start a live USB display session from the app so you can see and control the device on your PC. You install the display-forwarding utility yourself and configure its path in the app.
Android device features need Google’s platform-tools (ADB) and a separate USB display-forwarding install, both on your PATH.
SSH needs an ssh client on your PATH.
Serial uses COM hardware; set port and baud in the app or preferences.
Install from PyPI as adbnik, then run adbnik.