NativeBridge CLI
Connect to cloud Android devices via ADB — as if they were plugged in locally.
NativeBridge CLI authenticates with your API key, authorizes your IP, and establishes an ADB connection to cloud-hosted Android devices through a secure TCP proxy.
Installation
pip install nativebridge
Prerequisite: Android SDK Platform Tools must be installed and adb available on your PATH.
Quick Start
# 1. Save your API key (one-time)
nativebridge login --api-key YOUR_API_KEY
# 2. Connect to a cloud device
nativebridge connect --device SESSION_ID
# 3. Use ADB as usual
nativebridge adb -s host:port shell
Commands
login — Save API key
nativebridge login --api-key nb_live_abc123
nativebridge login --api-key nb_live_abc123 --api-base https://custom.api.com
Saves your API key to ~/.nativebridge/config.json so you don't need to pass it every time.
logout — Remove saved API key
nativebridge logout
connect — Connect to a cloud device
nativebridge connect --device SESSION_ID
nativebridge connect -d SESSION_ID --api-key nb_live_abc123
This command:
- Validates your API key with the NativeBridge backend
- Authorizes your IP address for ADB access
- Runs
adb connectto the cloud device
On success, you'll see the connection details and quick-start commands.
disconnect — Disconnect from a cloud device
nativebridge disconnect --device SESSION_ID
nativebridge disconnect -d SESSION_ID
devices — List connected ADB devices
nativebridge devices
Runs adb devices -l and displays the output.
status — Show CLI configuration
nativebridge status
Displays your current API base URL, masked API key, and connected ADB devices.
adb — ADB passthrough
nativebridge adb devices
nativebridge adb -s host:port shell
nativebridge adb -s host:port install app.apk
nativebridge adb -s host:port push local.txt /sdcard/
nativebridge adb -s host:port logcat
nativebridge adb -s host:port shell pm list packages
Passes any arguments directly to adb. This is a convenience wrapper so you can use a single tool for all device interactions.
Configuration
NativeBridge CLI reads configuration in the following order (first match wins):
| Setting | Environment Variable | Config File Key | Default |
|---|---|---|---|
| API Key | NATIVEBRIDGE_API_KEY |
api_key |
— |
| API Base | NATIVEBRIDGE_API_BASE |
api_base |
https://api.nativebridge.io |
Config file location: ~/.nativebridge/config.json
Requirements
- Python 3.8+
adb(Android SDK Platform Tools) on your PATH- A NativeBridge API key
License
MIT License. See LICENSE for details.
Metadata
Release files for nativebridge 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| nativebridge-0.1.0.tar.gz | 9.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nativebridge-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 19.7 kB
Release files / nativebridge-0.1.0.tar.gz
| Download URL | nativebridge-0.1.0.tar.gz |
|---|---|
| Size | 9.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0acd33fa0b158257d16d55bed3cb780951c857cc5f5ff982411006d07174e76f
|
|
BLAKE2b-256 checksum How to use checksums |
c24222477dd62bffd3144d61c90d969ea74b9dce165dc2e1c5415b539bae0c73
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Release files / nativebridge-0.1.0-py3-none-any.whl
| Download URL | nativebridge-0.1.0-py3-none-any.whl |
|---|---|
| Size | 10.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f0b6c5361ca2a84d3c1e1c8aadc3c0e2d6559364f780dd12a88b87bf0805b1bb
|
|
BLAKE2b-256 checksum How to use checksums |
2e8af45d9c5549153bf1bd3487b84c67129c55f575706e33f544cf8734d3fbe4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|