Omniscio

Set up SMS integration with your own phone

Omniscio sends and receives your text messages through your own Android phone — no second phone number and no paid texting service to sign up for. Turn it on under Settings → Connections → Channels → SMS and choose how your texts travel: Pushbullet, which mirrors them through its cloud and handles pictures, or Native, which goes straight over your phone's own SIM. Once connected, your texts thread into the Inbox and you can read and reply from inside the app.

On this page

What it is

Your texts become one more channel inside Omniscio. They thread into the Inbox, where you can read and reply without picking up your phone, and you can start a text to anyone from the app. A text from a sender you have approved can also start a session or run an automation.

There are two ways to connect, chosen under Settings → Connections → Channels → SMS → "SMS provider":

  • Pushbullet (default) — the easiest path. Texts are mirrored through the Pushbullet cloud using the Pushbullet Android app. Supports pictures (MMS) and GIFs. Free Pushbullet accounts cap SMS at 100/month.
  • Native (my phone) — texts go straight over your phone's real SIM via a free, open-source Android app (capcom6 "SMS Gateway for Android") that runs a tiny server on your home network, with no third-party cloud in the path and no monthly cap. It is text-only for now — pictures, MMS, and GIFs aren't sent or received under Native yet, so use Pushbullet if you need those.

You can switch providers anytime; conversations and history are shared, so nothing is lost.

Where to find it

SMS lives in the Channels pane under Settings → Connections — open Settings, then Connections, then Channels, and expand the SMS card (settings search reaches it too). At the top you pick how your texts travel: Pushbullet, which mirrors them through the Pushbullet cloud, or Native, which sends straight over your own phone's SIM through a small server running on the phone. Choosing a provider reveals a short setup wizard underneath, and you can switch between them at any time without losing your conversations.

Once connected, your text threads appear in Omniscio's Inbox and you can reply from inside the app. When SMS is switched on but stops working, a single alert appears in your Inbox along with one desktop notification, and the switch that controls that alert sits on the same SMS card.

How it behaves

Set up Pushbullet (the default)

  1. Switch it on. Open Settings → Connections → Channels → SMS and turn on SMS Integration. Nothing else on the card appears until it is on.
  2. Leave the provider on Pushbullet. You'll see a three-step wizard: Token → Device → Connect.
  3. Get a Pushbullet API token. Install Pushbullet on your Android phone and sign in. Then visit pushbullet.com/account on desktop, scroll to "Access Tokens", and click "Create Access Token". You'll get a string that starts with o. — copy it.
  4. Paste the token into Settings. Click "Save & Verify". Omniscio confirms the token, encrypts it, and stores it on disk. Then it lists your Pushbullet devices — pick the Android phone marked "SMS capable".
  5. Wait for "Connected". Omniscio opens a WebSocket to Pushbullet and the status dot turns green. Send yourself a test SMS from another number — it should appear in Omniscio's Inbox within a few seconds.

Re-entering your token or re-picking your device automatically refreshes the connection, and a socket that sticks mid-handshake recovers on its own within ~15 seconds — so you rarely need to click Retry if you hit "Taking longer than expected" at Step 5. If the token is rejected, double-check you copied the whole string including the o. prefix.

Set up Native (your own phone, self-hosted)

Native runs a tiny web server on your phone that texts flow through — nothing touches anyone else's cloud.

  1. Install the app. On your Android phone, install the free SMS Gateway for Android app (from F-Droid or the project's GitHub release — it isn't on the Play Store because Google restricts SMS-forwarding apps). On Android 15+, open the app's App info → ⋮ → "Allow restricted settings" once so it can run its local server in the background.
  2. Run it in Local Server mode. The app shows a local address like http://192.168.1.5:8080 plus a username and password — that's your phone's own SMS API on your Wi-Fi.
  3. In Omniscio, Settings → Connections → Channels → SMS, turn on SMS Integration if it is off, and switch SMS provider to Native (my phone). Fill in the phone address, username, and password from the app, and set a webhook secret (any strong phrase — you'll paste the same one into the phone app).
  4. Point the phone app's webhook at Omniscio. Omniscio shows an Inbound webhook URL to copy into the app's webhook settings, and to sign each request with that shared secret. This requires Mobile Access (Settings → Remote & Sharing → Remote Access) to be on so your phone can reach Omniscio.
  5. Test it. Text yourself from another number — it should land in Omniscio's Inbox. Send a reply from Omniscio — your phone sends it over your SIM.

Off Wi-Fi: the local address only works while your phone and PC share a network. To send/receive when you're away, put both on a private tunnel like Tailscale (free) and use the tunnel address, or use the phone app's own cloud relay — see the app's docs.

If SMS goes offline

If SMS is turned on but stops working, Omniscio raises a single "SMS is offline" alert in your Inbox plus one desktop notification, rather than failing silently — for Pushbullet, that's a saved token that can no longer be read (for example after a hardware or Windows change that resets saved keys) or a connection that drops for a sustained stretch; for Native, it's missing connection settings. A missing/unreadable credential alerts right away (it won't fix itself); a dropped Pushbullet connection waits out a short grace window first, so a brief blip or a laptop sleep doesn't nag you. The alert clears itself automatically once SMS reconnects. Turn it off under Settings → Connections → Channels → SMS → "Alert me when SMS goes offline" (on by default). Omniscio checks the connection about once a minute, which is what lets a brief blip pass without a word.

Keyboard support

SMS and Telegram triage in Omniscio is deliberately mouse-first — every action in the messaging panes (archive, snooze, mark-as-read, mark-as-spam, reply) is a visible button, and none of them is keyboard-only. That's a declared decision, not an omission, for two reasons:

  • These panes are a quick pass, not a workspace. You open a thread to read it and reply, then move on — every one of those actions is a visible button, and a visible button is faster than a key you had to learn.
  • The app-wide shortcut set stays clean. Omniscio's global session shortcuts (J/K to move between sessions, R to reply in the focused session, E to archive, H to snooze) are built around the Claude session list and composer. Messaging threads deliberately don't mirror that layout, so wiring a second, conflicting shortcut set onto them would fight the app-wide keys.

This is a declared choice, not an oversight: the messaging panes are deliberately keyboard-light.

Last verified 2026-10-23