AI Radar

Watches official X accounts and primary sources for AI releases and sends only what matters, in your language, as breaking alerts and short digests

Summary excerpt from the creator’s share page. Not independently tested.

Open on x.ai and add to Grok BotOriginal post ↗Report a problem

What the share page says

Always-on AI news radar. Watches AI labs' official X accounts, their staff, researchers and well-known people, plus blogs, changelogs, GitHub, Hugging Face and arXiv, for frontier models, coding-agent releases, decision models, local LLMs, benchmarks and generation. Sends only what matters, one line plus the original link, in your language. Silent when nothing is new. Read-only on X.

Description as published on the x.ai share page when last checked (2026-11-13).

What its description mentions

Read automatically from the creator's own words and quoted below. Not a test: check the Bot's skills and routines before relying on any of it.

Apps it names
X (Twitter)
Promised limits
Read-only on X
Our take

Editorial notes

From the public description, not a test. Written by Grok Bot Wiki from the share-page text; we have not run this Bot. Reviewed .

Best for

Someone who wants a constant, low-noise watch over frontier AI model releases and lab news without checking X, GitHub, and a stack of blogs themselves.

Not for

Anyone who wants a scheduled, interview-style setup like a traditional morning brief, since its description reads as an always-on watch rather than a timed digest.

What it does

It keeps a standing watch over AI labs' official accounts, their staff and well-known researchers, alongside company blogs, changelogs, GitHub, Hugging Face and arXiv. Out of all of that it surfaces only items judged to matter — new frontier models, coding-agent releases, local LLM updates, and benchmark results among them — and sends each as one line with the original source link rather than a rewritten summary. When nothing meaningful happened it stays silent instead of sending a filler update, and its reading of X specifically is read-only, so it never posts or replies on the owner's behalf.

First messages to try

  1. Start watching for me — I mainly care about frontier model releases and coding-agent news, less about benchmarks.
  2. Has anything changed since this morning on the local LLM side?
  3. Switch my alerts to Spanish going forward.

Apps and accounts

Its description mentions official lab accounts and staff on X, plus blogs, changelogs, GitHub, Hugging Face and arXiv, as its sources, with X use staying read-only; it names no other outside service.

Cautions

  • Silence from it isn't a sign it stopped working — its description has it going quiet on purpose whenever nothing meaningful has moved.
  • It links to the original source for every item, so treat that link as the record and its one-line summary as a pointer, not the full story.

Compare with: Wire by Dytschgo 💻Research Bot by Arthur MacWaters

Before you add it

Specific to this Bot, from what its description says:

  • It names X (Twitter). Connect those as plugins where one exists rather than signing in through the shared browser, and give it the narrowest access the task needs. What to check for X (Twitter) ↗
  • Its description makes a promise about limits. Confirm it in the Bot's skills and rules before relying on it.
The standard checks for any shared Bot

Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.

  • Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
  • Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
  • Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
  • Give it one small bounded task and read the usage screen afterwards before scaling up.

Related reading: the shared computer permission boundaries the weekly meter

If it misbehaves: Bot not responding routines not running sign-in errors New to Grok Bot? what it is your first task

Attribution

This Bot belongs to its creator, Gota. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot, cs68614-hash/awesome-grokbot-templates, ZeroPointRepo/GrokBotDev and kydlikebtc/awesome-grokbot. Imported catalog prose retains CC BY 4.0 attribution; share-page excerpts are labeled separately. Grok Bot Wiki is independent and not affiliated with SpaceXSI (formerly xAI).

Made this Bot? Add a “Listed on Grok Bot Wiki” badge

Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles ↗

Markdown (README)

[![Listed on Grok Bot Wiki](https://www.grokbotwiki.com/badge/listed-dark.svg)](https://www.grokbotwiki.com/bots/ai-radar)

Or promote this template in the labelled Featured row, from $19.