● What it got: Messages, Mail, Notes, Reminders, Calendar, Contacts and Location — six Apple apps plus location, announced 12 November.
● The bigger part: you can drive your Mac from any Grok Bot client — phone, web, or a Tesla — not just from the Mac itself.
● Also this month: Grok Bot reached version 1.0, leaving beta.
● What is not documented: how permissions are granted, which plan is required, and what leaves the device. None of it has been published.
xAI’s @bot account put it in one line on 12 November: “Grok Bot on Mac can now use Messages, Mail, Notes, Reminders, Calendar, Location, and Contacts.” The app is available at x.ai/bot and reached version 1.0 this month, technically leaving beta.
The headline undersells it
Evan Bacon, who works on it at xAI, described the feature differently: “We now have built-in support for Apple apps when running Grok Bot on a Mac! You can remote control your Mac from any Grok Bot client — mobile, web, Tesla — to check your calendar, send messages, and read reminders from anywhere.”
That is a different product from what the headline describes. It is not an assistant that reads your mail while you sit at your Mac. It is a bridge that lets your phone, a browser, or a car issue instructions your Mac then carries out against Messages and Calendar — while you are not there.
Useful, obviously. Checking your calendar from the car without reaching for a phone is a real thing people want. But it changes what the permission grant means. You are not approving local access; you are approving remote access routed through xAI to a machine that may be sitting unattended in your house.
What macOS will ask you for
Apple gates every one of these behind its Transparency, Consent and Control system, so you will see individual prompts rather than one blanket approval. Worth knowing which ones you are agreeing to before they appear:
| Integration |
What macOS grants |
| Messages |
Full Disk Access, in practice — the message database sits in a protected location |
| Mail |
Access to local mail data, and Automation permission to act on it |
| Contacts |
The entire address book, not a selection from it |
| Calendar |
Read and write across all calendars on the account |
| Reminders |
Read and write |
| Notes |
Read and write |
| Location |
Location Services, which is a live position rather than a stored value |
Two of those are broader than they sound. Contacts is all-or-nothing on macOS — there is no partial grant, so approving it hands over every number and address you hold, including other people’s. And Messages access generally requires Full Disk Access, which is the widest permission a Mac app can hold.
This is how macOS works for any app, not something specific to Grok Bot. It matters here only because seven grants arriving together is easy to click through without reading.
What nobody has published yet
The coverage so far establishes what the integrations are. It does not establish how they work, and these are the questions that decide whether to enable them:
| Question |
Status |
| Are permissions granted per app or all at once? |
Not documented |
| Does message and mail content leave the device? |
Not documented |
| Is any of it retained or used for training? |
Not documented |
| Which subscription tier is required? |
Not stated |
| Can the remote bridge be disabled while keeping local use? |
Not documented |
| Is there an audit log of what the assistant did? |
Not documented |
None of that is a criticism of the feature — it is a week-old release at version 1.0 and documentation usually trails shipping. It is a reason to wait for answers before granting Full Disk Access on a machine with work mail on it.
If you are turning it on anyway
Four things worth doing, in order:
| Step |
Why |
| Grant one permission at a time and use it before adding the next |
You find out what each one actually unlocks, and you keep the ones you do not need switched off. |
| Start with Calendar and Reminders, not Messages and Mail |
Same convenience, far smaller blast radius. Most of the day-to-day value is in those two. |
| Decide about Contacts separately |
It is all-or-nothing and it contains other peoples data, not just yours. That is a different decision from the rest. |
| Check System Settings > Privacy & Security afterwards |
macOS lists every grant and revokes them individually. If you change your mind, that is where you do it. |
And if the Mac in question holds client data or work mail, treat the remote bridge as the deciding factor rather than the integrations. Local assistance and remote control of an unattended machine are different risk profiles.
Our earlier Grok Bot coverage: usage limits and the token-efficiency fix. Listing: Grok. Related reading: four ways to contain an AI agent.
Sources