<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>AI Journey: xAI news</title>
    <link>https://aijourney.space/xai/news/</link>
    <description>Changes at xAI, logged from its own announcements, documentation and price pages, never from another publisher, each with what it means for you.</description>
    <language>en</language>
    <atom:link href="https://aijourney.space/xai/news/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Paper Benchmarks Grok&apos;s Voice Agent Across Five Languages</title>
      <link>https://aijourney.space/updates/2026-10-01-tau-multilingual-benchmarking-voice-agents-across-languages/</link>
      <guid isPermaLink="false">2026-10-01-tau-multilingual-benchmarking-voice-agents-across-languages</guid>
      <pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate>
      <description>What happened. On September 21, 2026, researchers published tau-Multilingual, a paper extending the tau-Voice benchmark to Spanish, Brazilian Portuguese, Hindi, Korean and Mandarin, running 4,500 full-duplex calls across five voice configurations and grading task completion, interaction handling and generation quality separately for each system tested, including xAI&apos;s Grok.

Sources. arXiv paper, tau-Multilingual: Benchmarking Voice Agents Across Languages, submitted September 21, 2026: https://arxiv.org/abs/2609.35820 (read 1 Oct 2026)

Why it matters. For a team picking a voice agent to handle calls outside English, a single English-only completion score now hides which languages actually work, so a vendor&apos;s headline number can mask a system that drops replies in Korean or talks over callers in Mandarin, and a buyer serving Asian markets has to check language specific scores before signing a contract rather than trusting one blended figure.</description>
    </item>
    <item>
      <title>xAI Changes Grok Pricing Page at grok.com</title>
      <link>https://aijourney.space/updates/2026-09-26-xai-published-pricing-changed/</link>
      <guid isPermaLink="false">2026-09-26-xai-published-pricing-changed</guid>
      <pubDate>Sat, 26 Sep 2026 00:00:00 GMT</pubDate>
      <description>What happened. On September 26, 2026, this site&apos;s automated poll of grok.com found that the subscription page xAI uses to sell Grok no longer matches the snapshot stored from the previous check, a difference that counts as a pricing event under this site&apos;s own tracking rules even though xAI has posted no separate announcement describing what moved.

Sources. Grok&apos;s public site at grok.com, the page this site polls for its pricing snapshot: https://grok.com/ (read 26 Sep 2026)

Why it matters. A reader deciding whether to keep paying for a chatbot subscription has to notice a change like this themselves unless a tracker flags it, since a vendor page can shift a tier, a limit or a button without a press release, and that gap between what changed and what got announced is exactly the kind of silent update this site exists to catch.</description>
    </item>
    <item>
      <title>arXiv Paper Finds Grok Amplifies Aggression in Synthetic Cyberbullying Data</title>
      <link>https://aijourney.space/updates/2026-09-18-do-social-patterns-hold-in-synthetic-data-analyzing-cyberbullying-dynami/</link>
      <guid isPermaLink="false">2026-09-18-do-social-patterns-hold-in-synthetic-data-analyzing-cyberbullying-dynami</guid>
      <pubDate>Fri, 18 Sep 2026 00:00:00 GMT</pubDate>
      <description>What happened. On 17 September 2026, researchers Arefeh Kazemi, Hamza Qadeer, Sinan Asci, Joachim Wagner and Brian Davis posted a paper to arXiv comparing synthetic cyberbullying dialogues generated by Grok, GPT and LLaMA against authentic conversations. The study measured turn-taking, power dynamics, repair behavior, pronoun usage, humor, profanity, toxicity and escalation patterns, then added human evaluation of realism and role plausibility.

Sources. arXiv paper, Do Social Patterns Hold in Synthetic Data?, submitted 15 July 2026, posted to cs.CL 17 September 2026: https://arxiv.org/abs/2609.17549 (read 18 Sep 2026)

Why it matters. Teams building safety classifiers or moderation benchmarks with LLM-generated training data need to know which vendor&apos;s outputs skew the resulting dataset. If Grok systematically writes harsher synthetic aggression than GPT or LLaMA, a benchmark built only from Grok transcripts will overstate how severe real cyberbullying looks, and a detector trained on it may miscalibrate against authentic conversations. That is a concrete caution for anyone choosing which model to use for data augmentation in trust and safety pipelines, not just an abstract finding about realism.</description>
    </item>
  </channel>
</rss>
