Bubble SSH
日本語Get the app

Android SSH guide

How to use SSH in an Android bubble

To use SSH in an Android bubble, allow notifications, enable bubble notifications for Bubble SSH, save a server connection, and tap it. Android opens the terminal as a floating conversation bubble that you can collapse and expand over other apps.

Updated September 7, 20264 minute read
01

What you need

Bubble SSH requires Android 11 or later because it uses Android’s native Bubble API. You also need an SSH server that you are authorized to access and either a password or a compatible private key.

  • Android 11 or later
  • Notification permission and bubbles enabled for Bubble SSH
  • SSH host, port, and username
  • Password or RSA, ED25519, or ECDSA private key
02

Set up the bubble and connect

The first-run screen checks the two Android settings that control whether a terminal can appear as a bubble. Complete both before adding your connection.

  1. Allow notifications

    Bubble terminals are delivered through Android conversation notifications. Allow notifications when prompted.

  2. Enable all Bubble SSH conversations

    Open the system bubble setting from onboarding and allow all Bubble SSH conversations to bubble.

  3. Add the server

    Enter the connection name, host, port, username, and authentication method. Add an optional startup command only when you trust and understand it.

  4. Tap the saved connection

    Bubble SSH starts the SSH session and opens its terminal bubble. Collapse it to return to the current app; tap it to resume.

03

What happens when the bubble closes?

Collapsing a bubble is not the same as disconnecting. Bubble SSH keeps the in-memory session available while the service is running. Explicitly ending the session disconnects it. Android may also retain conversation notification and shortcut history so a bubble can be restored.

A phone-side bubble does not guarantee that a remote command survives network loss, app process death, or an explicit disconnect. Use an appropriate server-side session tool when the remote process must continue independently.

04

Security checklist

Treat the phone as an SSH client endpoint. Use a dedicated account where practical, protect the device lock screen, verify the server host key prompt, and remove connections or keys that are no longer needed.

  • Never paste a private key into chat or a web form
  • Verify unexpected host-key changes before accepting them
  • Use a passphrase for imported private keys when your workflow permits
  • Keep the Android device and Bubble SSH updated

Keep the context. Keep the terminal.

Put your next SSH session one tap away.

Get Bubble SSH