---
title: Copy a verification code from a text
---
# Copy a verification code from a text

## What it is

A bank, a delivery service, an app — they all text you a code you then have to read, memorise
and retype somewhere else. Omniscio spots those codes in your texts and hands them back to you
in one click, so the read-and-retype step disappears.

There are two places it shows up, and they cover the two different situations:

- **A text arrives with a code** → a **toast** pops up naming the code, with a **Copy code**
  button. You do not have to go looking for the message.
- **A conversation that is nothing but codes** → a large **Most recent code** panel sits at the
  top of the thread, always showing the newest code with one big Copy button. No scrolling back
  through the bubble list to find it.

Everything is detected on your own machine from messages you already receive. Nothing is sent
anywhere.

## Where to find it

- **The toast** appears on its own, anywhere in Omniscio, the moment a code text arrives.
- **The panel** is at the top of the conversation, above the messages, in the SMS panel.

## How it behaves

### When a code text arrives

A toast appears naming the sender and the code — for example *"Capital One code: 044664"*, or
*"Verification code: 483192"* when the sender cannot be identified. Click **Copy code** and the
digits are on your clipboard.

- Codes from the **same sender** refresh the one toast rather than stacking up, so a service that
  re-sends does not fill your screen.
- The toast stays up longer than an ordinary notification would — long enough to switch to
  Omniscio and click Copy.
- If the copy cannot be made for any reason, Omniscio tells you rather than going quiet.

### The "Most recent code" panel

A conversation counts as a **verification-code thread** when at least **80% of everything in it**
is an incoming text carrying a code. That single rule covers the cases that matter:

| What the conversation looks like | Panel |
| --- | --- |
| A brand-new conversation whose only message is a code | shown |
| A pure two-factor conversation (four codes, nothing else) | shown |
| Ten codes and one "Reply STOP to opt out" line | shown |
| Ten codes and two of your own replies | shown |
| Ten codes and twenty of your own replies | hidden |
| One stray code inside a normal conversation | hidden |
| One code and twenty of your own texts | hidden |

The panel shows the code in large type, who sent it, and when. Click **Copy code** and the digits
are on your clipboard; the button confirms with **Copied!**

## What counts as a code

Omniscio matches the shapes real services actually use:

- *"Your Acme code is 123456"* and *"<#>Your Acme code is 123456"*
- *"123456 is your Acme verification code"*
- *"Acme code: 123456"*
- *"Google code: 482910"*
- Any 4–8 digit number inside a message that mentions **code**, **verify**, **verification**,
  **OTP**, **PIN**, or **passcode**

A number longer than 8 digits is treated as an order or reference number, not a code. So are
years such as *"since 2024"*.

## Good to know

- **Incoming only.** A code you typed yourself is never offered for copying, in the panel or the
  per-message button.
- **Only the digits are copied** — never the whole message, never the formatting. A code written
  as `123-456` lands on your clipboard as `123456`.
- **Each message keeps its own small Copy button.** The per-message pill is still there for a code
  inside an ordinary conversation; the panel is the extra help for a thread that is all codes.
- **You can turn the toast off.** Settings → Notifications → *Verification codes*. It is on by
  default. Turning it off leaves the panel and the per-message button working.
- **Pushbullet and the native phone bridge both work** — anything that reaches Omniscio as a text.