ChatGPT Dots in your texts: convenient, but the border must be visible

What is the most intimate screen on your phone? For many people it's the messages app: the place where your family, your bank and your dentist all talk to you in the same visual language. OpenAI has just decided that's the ideal place for an AI agent to move in.

According to 9to5Mac and a wave of other outlets, you can now text your ChatGPT dot through iMessage on iPhone or RCS on Android, including Google Messages. As Digit reports, you can send text, photos or voice notes, and the dot can write first with updates. It's a preview for Pro users in the US, and you enable it from the dot's profile by choosing "Texting".

The convenience is real, and that's the problem

Let's be fair: this is a good idea. Nobody wants to open yet another app to be told that a price dropped or that a pending request needs an answer. A thread that sits next to everything else you read is the natural home for proactive notifications. And the dot carries over its context and plugins, so you can start planning something in ChatGPT and continue by text without re-explaining anything.

But convenience is precisely what dissolves boundaries. A contact called "Iggy" in your message list looks like any other contact. Same bubbles, same keyboard, same notification sound. The interface says "conversation between two parties", while the reality is a company's servers, a model and a stack of connected plugins on the other end. In our view, that visual disguise is the real design question here, more than any specific feature.

OpenAI's promises are reasonable, but they are promises

To its credit, OpenAI is clear on some points. Per the company's post, only you can text your dot and your dot can only text you, and enabling it "doesn't give your dot or OpenAI access to your other text conversations." That matters, and it's the right limit to draw.

But notice what it doesn't say. AndroidPure notes that OpenAI warns texting uses a third-party provider. So there is at least one more link in the chain between your phone and the model. We don't know from the documentation how that provider handles the content, and we won't guess. What we can say is that "private" and "end-to-end between you and a person" are different things, and a green or blue bubble doesn't tell you which one you're in.

Also consider what you'd be handing over. Photos and voice notes are richer than typed text, and a dot built to "keep an eye on things" and message you proactively is, by design, always listening for its next cue. We think that's fine if you chose it knowingly. It's less fine if the thread feels as casual as a chat with your sister.

What Apple and Google should do about it

This is where we'd push the platforms, not just OpenAI. If AI agents are going to live in the messages app, Messages on Android and iMessage on iPhone should mark them unmistakably: a persistent label, a distinct look, a clear note on where the content goes and who processes it. Something you can't miss in the thread, not buried in settings.

Today the burden falls on the user, who must remember that this one contact is different. That's a weak safeguard. Phishing already works because things that look familiar get trusted, and a world where some "contacts" are corporate AI services and others are people is a gift to anyone who wants to blur the difference.

Our verdict

If you're a Pro user in the US, try it, but treat the thread as what it is: a chat with a service. Don't send what you wouldn't type into the ChatGPT app, and check the setup screen before enabling it. For everyone else, there's no rush; the wider rollout is only reported as expected soon, so watch how it plays out. And for Apple, Google and OpenAI, the message is simple: make the boundary obvious before it becomes a habit.