Getting Started
Snapbug now has a browser-first setup:
- Add the Snapbug SDK to your app.
- Open the Chrome Extension and create a room code.
- Connect the app to the extension over WebRTC.
- Optionally run the local service if you want AI fix, build, and PR flows.
Recommended path
- Chrome Extension is the default product path for inspection and bug reporting.
- Local service is optional and only needed for developer automation.
- Desktop app is still available as a legacy companion, but it is no longer the primary onboarding flow.
Android install
Add the runtime artifact in debug and the no-op artifact in release:
dependencies {
debugImplementation("ai.snapbug:snapbug:1.0.0")
releaseImplementation("ai.snapbug:snapbug-no-op:1.0.0")
}Initialize the SDK in your Application:
class App : Application() {
override fun onCreate() {
super.onCreate()
Snapbug.start(this)
}
}You can also pass configuration if you need custom plugins or overlay settings:
Snapbug.start(this) {
crashReporter { catchFatalErrors = true }
debugFeedback { screenNameProvider = { "Home" } }
}Connect to the Chrome Extension
- Install the Snapbug Chrome Extension.
- Open the extension and create a room code.
- In your app, open the Snapbug overlay.
- Enter or scan the room code.
- Wait until the connection state becomes Connected.
This path does not require ADB, port forwarding, or a shared Wi-Fi network.
Optional: local service
Install the local service only if you need AI actions such as fix, build, verification, or PR creation.
brew install snapbug/tap/snapbug-cli
snapbug serveThe service exposes:
http://localhost:9090for Chrome Extension readiness and AI endpointsws://localhost:9023andhttp://localhost:9024for legacy-compatible transport
Platform notes
- Android: fully supported.
- iOS Simulator: supported for the core flow.
- Flutter and React Native: use the native SDK underneath, then bridge data into Snapbug.
- Desktop app: legacy path for teams that still depend on localhost transport.