Loading today’s stories
Product4 distinct publishers3 min readUpdated
OpenAI's new Apple Messages plugin reads, searches and sends iMessage, SMS and RCS threads from a Mac. Sending is approval-gated by default, which makes persistent approval an admin decision.
The Product Desk · Product desk
Compiled by The Product DeskSomething wrong?How this is made
OpenAI has shipped an Apple Messages plugin for the ChatGPT desktop app on macOS that can read and search a user's Messages chats and prepare or send messages, covering iMessage, SMS and RCS [1][2]. According to the release notes quoted by 9to5Mac, it is available on all plans, and it works in ChatGPT Work and Codex [3].
That last detail is the part worth reading twice. The plugin does not operate in regular ChatGPT chats, and it does not let anyone drive ChatGPT remotely by texting it [4]. So the read, search and send capability exists specifically in the work-branded and developer surfaces rather than in consumer chat [14]. For anyone running a fleet of Macs, this is not a consumer feature that happens to be nearby; it is an assistant inside the corporate tenant with a path to the message store where deal terms, on-call escalations, two-factor codes and vendor negotiations actually live.
The control OpenAI points to is approval. By default, ChatGPT sends a message only after the user approves both the text and the recipients [5]. The company's plugin guide covers the risks of persistent approval, how to revoke access, and a known issue in which tasks disable approval prompts [6]. Read plainly, that is a vendor telling you the default is safe, the opt-out of the default is not, and there is already one path where the prompt does not appear. Persistent approval is therefore a configuration question with a blast radius, not a convenience toggle: once a user grants it, an agent can send from their identity to their contacts, and the failure mode is a message that looks exactly like the human wrote it. Fleet scope is narrower than the plan scope suggests, because for now the feature runs on Apple silicon Macs and not Intel machines [7].
The same release includes other things that move data across boundaries. Pinned chats now stay in sync between the desktop app and iOS [8]. Users can share a read-only snapshot of a local Codex thread, frozen at the moment of sharing [9]. Links made from personal accounts are open to anyone holding the URL, while workspace links stay inside the workspace, and OpenAI says Codex redacts known secret patterns but advises reviewing snapshots because sensitive material can survive [10]. "Known secret patterns" is the operative limit there.
Elsewhere, Site owners can invite active members of the same workspace to co-edit, with editors able to change content and database data, save versions and publish after the owner's first publication, while owners keep access, settings, analytics and version restoration [11]. Some owners can also change a ChatGPT-hosted URL without redeploying, with the old address redirecting to the new one [12]. The Computer History feature is expanding to Pro, Business and Enterprise users in the EEA, Switzerland and the UK; it requires Memories and stays off by default [13].
What to watch: whether admins get a tenant-level control to block the Messages plugin or persistent approval outright, rather than relying on each user reading a plugin guide; how quickly the known task issue that disables approval prompts is closed [6]; and whether the personal-versus-workspace split on snapshot links [10] holds up when employees share Codex threads from personal accounts. Also watch the Intel cutoff [7], since it is the only thing currently keeping this off older corporate hardware.
Follow any of these and your For You feed starts watching them — no settings page required.
Ranked by verification strength, evidence, and original report placement.
ChatGPT's latest update adds an Apple Messages plugin for the Mac app that works with iMessage, SMS and RCS.
The Apple Messages plugin lets ChatGPT read and search chats on a Mac and prepare and send messages.
By default, ChatGPT sends messages only after the user approves the message and its recipients.
OpenAI's plugin guide details persistent-approval risks, revocation steps, and a known issue with tasks that disable approval prompts.
For now the feature only works with ChatGPT on Apple silicon Macs and not Intel machines.
OpenAI states the plugin does not let users interact with ChatGPT remotely through Messages, and it does not work in regular ChatGPT chats.
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Well-documented vendor release, no independent testing
Four independent publishers report the same launch, and the primary source quotes OpenAI's release notes and plugin guide verbatim on availability, surfaces, approval defaults and hardware limits; MacRumors adds observable install and permission mechanics. Evidence is nonetheless entirely vendor-declared or vendor-relayed: no publisher tested the feature, no one verified the local-processing or no-index assurance, and TechCrunch's clarification request was still outstanding at publication.
Generally available, zero usage signal
Adoption evidence is availability-side only: the plugin is live and listed publicly in the ChatGPT Plugins directory, stated as available on all plans, and adjacent features shipped in the same release. No source reports installs, active users, enterprise rollouts or any usage metric, and real uptake is throttled by an Apple silicon requirement, Work/Codex-only surfaces and a multi-step OS permission grant.
Headlines overstate autonomy and data reach
Framings such as ChatGPT 'controlling' iMessage or users sharing 'all of your digital conversations with OpenAI' run ahead of the documented behavior: sending requires per-message approval of content and recipients by default, the plugin is inert in consumer ChatGPT chats and cannot be driven remotely, it runs only on Apple silicon, and OpenAI says processing is local without building a message index. The gap is moderate rather than severe because the underlying capability is genuinely broad and the persistent-approval and prompt-injection concerns raised are real and vendor-acknowledged.
Vendor launch cycle inside an active Apple-OpenAI conflict
Every account originates from an OpenAI release-notes and promotional cycle, including the company's own X demo, and two of the four publishers are Apple-audience outlets whose framing and commerce-oriented tail sections favor Apple-ecosystem engagement. Overlaying that, Apple is litigating trade-secret claims against OpenAI and building competing Siri capability, giving both principals reasons to shape the narrative; Apple did not respond to Bloomberg, so only one side's account is on the record.
Facts firm, availability framing and privacy mechanics unsettled
The capability, default approval gate, surface confinement and Apple silicon limit are consistently reported across four publishers and grounded in quoted vendor documentation, so the core is reliable. Confidence is held below high because entitlement framing conflicts (all plans versus Work/Codex users only), the local-processing and no-index claims are unverified, prompt-injection exposure is asserted without technical detail, and there is no usage evidence at all.
product
Record, don't prompt: two labs converge on demonstration as the agent interface1 distinct publisher
invest
OpenAI's Computer History turns keystroke logging into a ChatGPT setting1 distinct publisher
security
OpenAI's Computer History writes a plaintext log of the workday. Decide before staff opt in.1 distinct publisher
product
Apple cuts at least 60 Vision roles, and the visionOS roadmap gets harder to underwrite1 distinct publisher
Distinct publishers with included, body-backed reporting in this cluster.
9to5mac.com
1 article · August 20, 2026
gizmodo.com
1 article · August 20, 2026
macrumors.com
1 article · August 20, 2026
techcrunch.com
1 article · August 20, 2026