← News archive

News record

SpaceXAI launched Grok Bot in early beta on August 11, 2026 as always-on AI teammates that can work across apps and continue cloud work when the user steps away.

Evidence state

developing

A later SpaceXAI product notice, stable Grok Bot documentation, registered-outlet coverage, or first-party clarification of beta access and the shared cloud-computer model.

Reported vs. the record

Reported

Grok Bot Launches as Persistent AI Agents with Cloud Computers

The record

The official launch page retains the August 11 launch, early-beta status, always-on agent framing, and cloud-computer description.

Primary-source receipt

Receipts

  1. captured headline

    Grok Bot Launches as Persistent AI Agents with Cloud Computers

  2. screenshot timestamp

    screenshot timestamp

  3. subject identity

    subject identity

    The directly fetched SpaceXAI launch page is titled 'Introducing Grok Bot' and names the product throughout.

    Open source receipt
  4. originating speaker

    SpaceXAI's official site published the August 11 early-beta launch notice.

    The canonical x.ai page returned HTTP 200, carries SpaceXAI branding, and states that the company is launching Grok Bot.

    Open source receipt
  5. reporter publication

    The launch notice is a byline-less first-party SpaceXAI publication dated August 11, 2026.

    The directly fetched page exposes its title, publication date, company footer, and official domain but no individual byline.

    Open source receipt
  6. atomic claim

    SpaceXAI launched Grok Bot in early beta on August 11, 2026 as always-on AI teammates that can work across apps and continue cloud work when the user steps away.

    The launch date, beta status, product description, and cloud-work behavior appear directly on the official announcement.

    Open source receipt
  7. atomic claim

    SpaceXAI documentation describes each Grok Bot as a persistent named agent with a browser, filesystem, terminal, memory, files, sessions, and preferences that persist across turns.

    The directly fetched official documentation states these capabilities and persistence properties explicitly.

    Open source receipt
  8. primary source evidence

    The official launch page retains the August 11 launch, early-beta status, always-on agent framing, and cloud-computer description.

    The canonical page and official documentation were directly fetched; the hash covers the URL, title, and retained launch and cloud-computer statements.

    Open source receipt
  9. response correction

    The current documentation says all Bots on one account share one user-scoped cloud computer, with separate screens but not separate security boundaries.

    The official computer-and-apps page directly clarifies the account-level sharing model behind the launch page's 'computer of their own' wording.

    Open source receipt
  10. resolution evidence status

    The launch and documented persistence model are retained; the product remains an early beta and no registered-outlet coverage was directly retained in this window.

    First-party launch material is available, while registered-source search did not yield a directly fetchable qualifying coverage page.

    Open source receipt

This page is a source-linked record. It does not score a person, infer motive, or replace the preserved source material.