Device Tunnel overview
Direct-access CLI for BrowserStack dedicated devices without Appium dependency
Device Tunnel CLI provides direct-access tunnels to BrowserStack dedicated devices with a standalone device-based workflow. Use --device-id and --device-name flags for device targeting, plus new discovery commands (devices, plans) for fleet management.
Key features
Here are the key features of Device Tunnel CLI:
| Area | Before | After |
|---|---|---|
| Connecting | Required a pre-existing --session-id
|
Can connect directly with --device-id or --device-name
|
| Session lifecycle | Manual by user | Fully managed by CLI |
| Disconnect | Stopped the entire session | Disconnects the tunnel only; the device stays allocated, the session remains running |
| Stop | Not implemented | Per-device stop or stop-all |
| Device discovery | Not available |
devices command lists your dedicated fleet |
| Auto-reconnect | Not available | Re-running connect --device-id reconnects the existing session’s tunnel |
| Multi-device | Not available | Comma-separated device IDs/names in a single command |
| Integrated start | Separate steps required |
start --device-id auto-connects after orchestrator is ready |
Binary usage
The Device Tunnel binary is available for macOS (ARM64 and x64) and Linux (ARM64 and x64). You can use the CLI directly via the downloaded binary, or through the BrowserStack SDK for your language. See Get the Device Tunnel binary for direct-download links and SDK install commands.
Commands use ./binary-macos-arm64 prefix when using the shared binary directly:
When using the SDK binary, use browserstack-sdk instead:
Next steps
- Set up and authenticate the Device Tunnel CLI
- Command reference for syntax and options
- Known constraints and restrictions
- Troubleshoot common issues
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
Thank you for your valuable feedback!