The official account of Grok Bot announced on October 7 that the Bot can now search, read, and monitor X. A thread reply stated that all users can use it without needing to set up an X connector.

The first version on August 29 took a different approach. Users had to bind their X account and automatically generate a developer account for the proxy to view timelines and mentions. This time, the connector requirement has been removed. Examples provided by the official announcement include tracking product feedback, following breaking news, and creating weekly industry summaries, which can be scheduled through Routines. The claim that a single prompt can analyze over 100 posts comes from product reports, but the announcement itself did not specify the number of queries.

The tool covers searching posts, reading timelines, checking mentions, and monitoring dynamics. Proxies can draft posts, but direct publishing is not yet available; posts still require a person to press the button to send. Reports indicate that there are no new pricing tiers or subscription levels this time. The announcement did not clarify quotas or whether the old developer interface is still in use. At that time, there was also no separate X page in the documentation.

Usage has thus shifted from self-browsing to monitoring. Users can have it track when a specific account resets limits, opens features, or provides failure explanations, and notify them when these occur. Posts like Codex limit resets are considered publicly updatable and not preset tasks in the announcement. Some users have it read their own posts to identify overlooked research before preparing to monitor a topic tag.

Buyers are users who want to track feedback, competitor releases, and breaking posts, while sellers continue to charge based on the developer account and connector path. This is usage driven by built-in entry, not the previously announced billing for calls. Attention has shifted from manual refreshing to scheduled monitoring. Beneficiaries are Bot users who treat X as a work input, while those who must first apply for a developer account to read posts are under pressure.

After the announcement post was made, it received over 8,000 likes and more than 800 replies. It can read and monitor, but cannot publish independently.

Source: Public Information