A Twitter to Discord bot posts new X posts into a channel, so your team sees them where it already talks. For a dev team that wants to know when other developers say Claude Code, Codex or Cursor has stopped working, the simplest setup is an AyeWatch X search monitor with Discord delivery: it runs your search on a schedule, lets an AI drop the jokes and hot takes, and posts the rest.
Why a dev team wants this
When a coding agent hangs mid-task, the first question in chat is whether the problem is on your side or the provider's. Posts from other developers on X are one quick signal, next to the provider's status page. Piping them into a #tooling channel saves everyone from running the same search.
There are three ways to build it.
Route 1: AyeWatch, no code (recommended)
- Create a monitor, pick X, then Search.
- Enter a query such as
("claude code" OR codex OR cursor) (down OR outage OR "not working") lang:en. - Under Only alert me about, write the rule in plain words: "developers saying one of these tools is down or failing right now". This matters here, because "cursor" and "codex" match plenty of posts that have nothing to do with coding agents. The AI reads each post and passes on only the ones that fit.
- Turn on Discord as the delivery channel and save.
Each alert carries the post text and a link, and several posts from one check arrive as one message, so a busy outage doesn't flood the channel. Discord, Slack, email and webhooks come with paid plans, which start at $9 a month; the free preview sends to the AyeWatch feed and app only.
If you want your own formatting, use the webhook instead. AyeWatch POSTs a topic.update event with an AI-written summary to your endpoint and signs it with HMAC-SHA256, so your handler can verify it and forward a custom message to Discord. Monitors can be created through the REST API too, and the MCP server lets an AI assistant add or pause them for you.
What it won't do: it reads public posts only and checks on a schedule, so it is not a seconds-fast firehose.
Route 2: RSS.app's X to Discord bot
RSS.app watches an X profile, hashtag, list or search and sends new tweets to a channel through a Discord webhook you paste in. Its filters include or exclude by keyword, hashtag or author. As of November 2026 the free plan has 2 feeds with a 24-hour refresh, and Basic costs $8.32 a month billed yearly with a 60-minute refresh. It is a good fit when you want to mirror every post from a feed rather than have each one judged.
Route 3: write your own bot
The Discord half is the easy part. Discord's docs describe webhooks as a low-effort way to post into a channel without a bot user or authentication. The X half is where the work is. The official X API is pay-per-use, at $0.005 per post read as of November 2026, with credits bought in advance. You also write the polling, the de-duplication and whatever filtering you want, and you pay for every post your query returns, relevant or not.
Compared
| AyeWatch | RSS.app bot | Your own bot | |
|---|---|---|---|
| Code needed | None (webhook optional) | None | Yes |
| Filtering | X query plus an AI rule | Keyword, hashtag, author | Whatever you write |
| Starting cost | Free preview; Discord from $9 a month | Free plan; paid from $8.32 a month yearly | $0.005 per post read, plus hosting |
| Best for | Signal over volume | Mirroring a feed | Full control and speed |
One more check when a tool stops
Outage chatter tells you a provider is having a bad day. It doesn't tell you whether you simply hit your own usage window. A desktop tracker such as UsageAtlas shows supported limits and reset times across Claude Code, Codex, Cursor and other coding tools, so you can rule that out before you blame the provider.