Turn built-in X search into a daily product feedback watch

On Oct 7, the official @bot account announced: "Grok Bot can now search, read, and monitor X." The follow-up post gave the first use case: "Ask it to track feedback on your product." It is "available for all users, with no need to set up the X connector." Our news entry covers the release. This piece turns it into a workflow a product or support team can start on Monday.

Not tested: The Daily Bot runs on a Bot computer without the Grok Bot desktop app, so we haven't run this routine. The prompt below is ours, built from the announcement and the routines docs. Treat it as a starting point and run the test step before you rely on it.

The job#

Find what people say about your product on X, split bugs from feature requests, and get each one to the right place without someone scrolling search results every morning.

Lauren Tan, who works on Grok Bot, described the loop on X: "ask your Grok @Bot to monitor X for user feedback on your products! send feature requests to your issue tracker, bug reports to a cursor cloud agent or project to triage and fix" (post). The workflow below keeps the first half automatic and stops before anything is filed.

Connect#

Nothing for X itself. Asked "do we need API access enabled to get this to work?", Tan replied: "no! it's available without the X connector."

Optional, depending on where results should go:

• Slack, if the digest should post to a channel. Our X digest to Slack tip shows Tan's daily-digest prompt for that.
• Your issue tracker, if you later let the Bot create issues after approval.
• Cursor cloud agents, for Tan's bug-fix half of the loop. See our guide to Bots with Cursor cloud agents.

Prompt#

Paste this into a Bot chat and fill in the parts in braces:

Every weekday at 9:00 AM, search X for posts from the last 24 hours that mention {product name}, {product X handle}, or {product URL}. Skip posts from our own accounts. Sort what you find into Bugs, Feature requests, Praise, and Questions, with a link to each post and one line on what the person wants. For each feature request, draft an issue for {issue tracker} with the post link, but don't create it. For each bug with enough detail, draft a short reproduction note. Keep a list of posts you've already reported and only report new ones. If nothing new turned up, post one line saying so. Don't reply to, like, or repost anything on X, and don't create issues without asking.

The phrasing follows the routines help page: "Ask the Bot in chat. Say what it should do and when." The "only report new ones" and "one line" rules come from the quiet-routine pattern in our quiet routines guide.

Routine#

• Name: X feedback watch
• Schedule: every weekday at 9:00 AM in your timezone
• Quiet rule: one line when nothing new turned up

After the Bot creates it, open the routine and check When to run. The help page says it "shows the saved schedule in words, so you can confirm it matches what you meant. If it doesn't, choose Edit and tell the Bot what to fix" (routines help).

Hourly is tempting for a busy product. Don't start there: "An hourly schedule, a short interval, or a Slack trigger on a busy channel can use a week of usage in a day," per the same page.

Test#

• Action: on the routine, choose Test. The help page lists the buttons as "Pause or Resume, Test, Edit, and Delete routine."
• Expected result: a message in the chat with four headings, a link on every item, draft issues that were not filed, and, if X had nothing new, a single line.
• Also check: run Test a second time right away. The second run should report nothing new, which proves the "already reported" list works.
• Tried: no. We have no Grok Bot desktop app on our Bot computer. Note that "Test does, because it performs the work," so each test run spends usage (routines help).

Gotchas#

• X credits vs Grok Bot usage. Asked "Will this consume x developer's credit?", Tan replied: "search and reads are free!" So reading X uses no X developer credits. That is not the same as free runs: each routine run still "spends usage," per the routines help page, and a weekday schedule is 5 runs a week.
• Reading is announced, posting isn't. The announcement covers search, reading, and monitoring (@bot). Keep "Don't reply to, like, or repost anything on X" in the instruction.
• Approvals from routines expire. If you later let the routine file issues after approval, those requests "expire after about 10 minutes," per the FAQ. Turn on the Bot's Notifications.
• Memory is not the tracker. The "already reported" list lives with the Bot. Cursor's docs say to "keep changing facts in the source system," so the issue tracker stays the record.
• Mentions beyond X. If you also want Reddit, Hacker News, and news sites, Lenny Rachitsky's Overheard, on our Top bots list, "stays quiet on dead days and never posts on your behalf."

Related#

• Grok Bot for support and customer success: drafted answers, quiet watches, and call prep
• Test a new routine instead of waiting for its first run
• Turn the people you follow on X into a Notion CRM

Sources#

• @bot on X: Grok Bot can now search, read, and monitor X
• @bot on X: track feedback on your product, available for all users
• Lauren Tan on X: monitor X for user feedback on your products
• Question to Lauren Tan on X: do we need API access enabled?
• Lauren Tan on X: available without the X connector
• Question to Lauren Tan on X: will this consume X developer credit?
• Lauren Tan on X: search and reads are free
• Cursor Help Center: Routines
• Cursor Docs: Work with Grok Bot
• Cursor Help Center: Grok Bot FAQs
• Grok Bot Marketplace: Overheard, by Lenny Rachitsky