Discussion

Grok Bot Can Read Your X Timeline. The Shared Computer Is the Real Permission Boundary

In Model Chat

xAI Watch
xAI WatchParticipantOpening post
#1929

xAI Watch · connector launch · 29 August 2026. xAI has connected Grok Bot to X. Sign in through the new connector and the company says it will create an X developer account if you need one. Paid Grok Bot users also get free API credits to start. The first advertised jobs are on the reading side: search posts, read a timeline, check mentions and pull together what is happening.

xAI Watch analysis

That is a short launch note with a fairly large permission boundary hiding underneath it. Grok Bot is not merely a chat window asking a public search engine about X. It is an always-on cloud agent being handed access to the parts of X shaped by a particular account.

The connector does less, and reaches further, than the headline

xAI does not say in the launch note that the first connector can publish posts, send messages or manage an account. It also does not state the credit amount, how long the credit lasts, the API tier, the exact OAuth scopes or the rate limits attached to the automatically created developer account. Those gaps matter because the difference between reading public posts and acting as a user is the whole safety case.

Even as a read-side tool, the integration could be useful. A research Bot can watch mentions, compare a timeline with a topic search and turn a morning trawl into a brief. Creating the developer account in the same flow removes a piece of setup that normally sends users wandering through a dashboard with the expression of someone renewing a parking permit.

One login, every Bot

The more consequential detail sits in xAI’s own Grok Bot documentation. Every Bot on a user’s account shares one persistent cloud computer. Browser cookies, signed-in sessions, files and command-line credentials are shared across the roster. Bots get separate screens, but xAI explicitly says those screens are work surfaces, not security boundaries.

Connectors are account-wide too. The documentation says their availability is not isolated to one Bot, although connector tools can be enabled or disabled individually. Connecting X for a researcher therefore should be treated as granting an account capability, not as handing one disposable assistant a private key. A writer, operator or chief-of-staff Bot lives on the same underlying computer.

The controls are real, but they need inspection

xAI advises users to put sending, publishing, deletion and other consequential changes behind approval. Its Auto Review rules can force matching actions to stop for permission, and explicit request boundaries remain useful. The company also warns that Auto Review is model-based and should not replace least privilege.

There are two less cheerful pieces of small print. Grok Bot requires data storage and does not support Cursor’s Legacy Privacy Mode. Deleting a Bot does not remove shared-computer files or browser sessions. Removing access means uninstalling the connector, revoking it in the source service, signing out and clearing sensitive working data. The launch note does not yet translate those general controls into an X-specific permissions screen that outsiders can inspect.

What the next version should make visible

The integration earns attention because it could turn a personalized social feed into useful agent work with almost no setup. Trust will depend on showing the plumbing: exact scopes before connection, read-only by default, per-Bot grants, a durable action log, clear retention controls and a hard approval boundary before any future posting capability.

An agent remembering the mentions is handy. An entire roster inheriting the same key is where convenience becomes architecture.

Sources and evidence

xAI Watch is an independent WittyWires-operated tracker and is not affiliated with or endorsed by xAI, SpaceXAI, SpaceX, X Corp. or Cursor.

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.