Grox: the LLM that reads every post
Grox = X's LLM (Grok VLM) content-understanding layer, open-sourced as orchestration code with every prompt template and model config withheld (grox.prompts.template / grox.config imports don't exist in the repo). We know WHAT it scores, not HOW it decides. Verified 2026-07-31.
"Banger" quality screening
An LLM pass that screens posts for quality — X literally runs a 'is this a banger' classifier over content. Output feeds quality/slop scoring used in content understanding.
Implication: Content quality is machine-read by a language model, not inferred from engagement counts alone. Slop is detectable and detected.
Spam detection
LLM spam classification including reply/comment spam — the reply-guy economy is machine-screened.
Implication: Template replies, copypasta, and AI-generated reply-farming are exactly what an LLM classifier catches that keyword rules never could.
Safety screens
Multi-tier safety screening (including a 'deluxe' pass and PTOS policy screening) whose verdicts feed the withheld visibility-filtering layer.
Implication: The enforcement thresholds are not public; no external tool can tell you your safety verdict.
Reply ranking
Replies under a post are themselves ranked by an LLM pass — reply visibility is a judged competition, not chronological.
Implication: A thoughtful reply can outrank earlier/louder ones; low-effort first-replies are demotable on content alone.
Multimodal post embeddings
Posts (text + media, with ASR for audio) are embedded and summarized by the VLM — this is the ONLY path by which your content's meaning reaches the recommendation system.
Implication: The system reads what your post is about, including what's inside images and video audio. Alt-text games and keyword stuffing don't reach the ranker; meaning does.
Why this matters more than any weight
The 2023 algorithm counted engagements. The 2026 stack reads content — a Grok VLM embeds and summarizes every post (including what’s inside images and video audio) and screens for spam, safety and quality before ranking ever happens. Optimization theater aimed at counters (pods, bait, tag-stuffing) now runs head-first into a language model. The checker’s slop and bait flags exist because of this layer.