xAI Release Notes

The world’s most intelligent voice model.

Today, we’re announcing Grok Voice 3.0, the world’s most intelligent speech-to-speech model. It sets a new record for resolving customer support calls, has class-leading latency at under one second, and costs less than other frontier models. Grok Voice powers millions of conversations a day across Tesla and SpaceX, and is available today in the API at the same price as its predecessor.

The Most Accurate Voice Model

In Artificial Analysis’s independent testing, Grok Voice 3.0 ranks #1 on the Speech-to-Speech Index, with a score of 86.9. The Index combines speech reasoning, τ-Voice, and preference and task success from blind head-to-head calls. Grok Voice 3.0 also scores 97% on Full Duplex Bench, a measure of how naturally it handles pauses, turn-taking, and interruptions.

Speech-to-speech benchmark comparison between Grok Voice 3.0 and competing models, per Artificial Analysis.

Benchmark Grok Voice 3.0 (this release) Grok Voice 2.0 GPT-Live-1 (Astra, Medium) Gemini 3.8 Live (Ext. Thinking, High) Overall AA Speech-to-Speech Index 86.9 81.3 83.2 82.6 Speech Reasoning Big Bench Audio 98.5% 97.2% 90.1% 97.7% Human Preference Speech Agent Arena Elo 1070 1011 1048 990 Task Completion Task Success Rate 94.8% 94.6% 87.4% 89.1% Conversational Dynamics Full Duplex Bench 97.0% 95.1% 94.9% 91.9%

Source: Artificial Analysis, October 13, 2026.

τ-Voice measures how well agents handle support calls with diverse accents, background noise, and interruptions. Grok Voice 3.0 scores 71.6%, comparable with GPT-Live-1 (Astra), but at 40% lower latency, setting a new frontier in agent intelligence versus responsiveness.

Agentic Performance vs. Speed

τ-Voice

τ-Voice score vs. average time to first audio for 16 speech-to-speech models, per Artificial Analysis. Grok Voice 3.0 scores 71.6% at 0.81s.

Agent Success Rate (%)

More accurate →

Time to first audio (seconds)

Faster →

• Gemini 3.8 Live (Ext. Thinking, High) 68.6%
• GPT-Live-1 (Astra, Medium) 74.5%
• Grok Voice 2.0 56.5%
• Grok Voice 3.0 71.6%

Source: Artificial Analysis

It's also cheaper to run than comparable models. Artificial Analysis measures what each model costs to complete a task in its Big Bench Audio run, and Grok Voice 3.0 comes in under both GPT-Live-1 (Astra, Medium) and GPT-Realtime-2.1.

Lower cost per task than comparable models

Average cost per task on Artificial Analysis's Big Bench Audio run, USD. Lower is better.

Average cost per task by model

Cost per task (USD)

• $0.025 Grok Voice 3.0
• $0.030 GPT-Live-1 (Astra, Medium)
• $0.055 GPT-Realtime-2.1 (High)

On EVA-Bench, ServiceNow’s benchmark for enterprise voice agents, Grok Voice 3.0 achieves the highest accuracy score at 74% and is the best-performing model when jointly scored across accuracy and customer experience.

“Grok Voice 3.0 sets a new Pareto frontier on EVA-Bench, ServiceNow’s open-source benchmark scoring voice agents on accuracy and experience across 200+ realistic enterprise scenarios. It pairs top accuracy with a natural, responsive conversation, setting a new standard for what enterprises can expect from AI on the front line of customer service.”

Nitin Aggarwal, Senior Director of Product Management, Agentic Evals and RAI, ServiceNow

Used by Millions of Customers at Tesla & SpaceX

Grok Voice 3.0 handles millions of conversations a day in Tesla vehicles. Drivers can use Connectors for simple requests like checking their calendar or answering an email, and Grok Bot for bigger tasks like ordering a coffee or booking dinner—all completely hands-free (see it on X). Grok Voice 3.0 also powers Grok Bot’s voice mode.

Starlink call centers use Grok Voice to answer 20,000 customer calls every day across multiple languages. Roughly 70% are resolved with no human in the loop, and one in four sales calls ends in a purchase before the caller hangs up. A single agent built on Grok Voice 3.0 verifies customers, troubleshoots hardware, issues credits, and ships replacement equipment.

Pricing and Availability

Grok Voice 3.0 is available today in the Voice Agent API at $0.08 / min ($4.80 / hr), the same price as Grok Voice 2.0. Agents using grok-voice-latest have already been switched over automatically, with no changes needed.

Start building with Grok Voice

Original source

Grok, Grok Bot, Cursor, and X Premium, all on one plan.

Today we’re introducing The X Subscription, which brings together Grok, Grok Bot, Cursor, and X Premium in one plan. Over the next few days, we’ll make it available to everyone globally.

For the first time, one AI subscription supports the full path from thinking and creating to building and sharing.

• Grok supports chat, voice, and image and video generation.
• Grok Bot gives you AI teammates that get work done.
• Cursor provides leading local and cloud coding agents.
• X adds a checkmark, creator tools, and fewer ads, with higher tiers removing ads from the timeline entirely.

Paid plans on The X Subscription include a generous pool of Grok model usage shared across Grok and Cursor. Each comparable new tier provides more usage-per-dollar than the plan it replaces.

Your shared pool covers Grok models whether you use them in the Grok apps, the Grok tab on X, or Cursor. Each X Subscription plan includes at least twice as much coding usage with our models as the comparable Cursor plan. With the new plans, third-party models are still available in Cursor on Premium and above. Usage is billed separately at API list prices, through top-ups.

The X Subscription is available to new customers starting today.

We’re also rolling out the option to switch for existing SuperGrok, Cursor, and X Premium subscribers. You’ll see it in your account billing settings when it’s available to you. You can keep your current plan, or switch and get a prorated refund for your old plan.

Plans and pricing

The X Subscription gives you Grok, Cursor, and X for roughly what a comparable standalone plan for one of those products used to cost.

Plan Price What’s Included Included Usage Free $0 Daily access to Grok, a starter allowance for Cursor's coding agents, and standard X Limited Plus $8/month More AI usage in Grok and Cursor, plus a checkmark, creator tools, and fewer ads on X Base Premium $30/month The benefits of SuperGrok, Cursor Pro, and X Premium+, previously $90/month combined 4x Plus Plan Super $100/month All of the above features 15x Plus Plan Ultra $200/month All of the above features 50x Plus Plan

For further details on pricing, included usage and eligibility see pricing page.

One subscription for Teams and Enterprises

Team users get Premium, Super, and Ultra on The X Subscription at the same per-seat prices as individual plans. That's priced lower per seat than older Cursor Teams but now includes 3x more coding usage, plus SSO, admin controls, consolidated billing, usage analytics, and SOC 2 compliance.

Enterprise customers can manage Grok and Cursor from one dashboard, with a single usage pool across both products. Our sales team is ready to help you get started.

Keep your current plans or move to The X Subscription

Nothing changes for existing SuperGrok, Cursor, or X Premium subscribers. You can keep your current plan, price, and features or move to The X Subscription.

Switching comes with limited-time offers, which you can see in your account billing settings.

Get started

Compare plans and sign up at x.ai/pricing.

If you already subscribe to SuperGrok, Cursor, or X Premium, go to your billing settings to see if switching is available for your account yet.

FAQ

Do I need The X Subscription to use X?

Can I cancel anytime?

How does the value of the new plans compare to the old ones?

What if I only use one of the products?

How do I subscribe, upgrade, or manage my plan?

What happens to my current Grok, Cursor, or X subscription?

I subscribe to more than one of these today. How can I upgrade?

Will my current plan go away?

Are third-party models still available in Cursor?

How do usage limits work?

I’m currently on an annual plan. What happens to my term?

Does The X Subscription have Team plans?

Original source

• Added support for OSC 7501 and the Rex terminal
• Expanded tool-call groups stay expanded as new calls join them, and Ctrl+E expands or collapses thinking faster in long transcripts
• Project hooks in a repository subfolder load when you launch inside that folder
• HTTP hooks to localhost work, and bad hook URLs are reported at load time
• Command status-line scripts see the current turn prompt ID and start time while the turn is active
• /model switches that fail no longer change the footer or the saved default model
• Export and copy refuse to overwrite an existing file, and show a clear message
• Shell commands no longer keep running after you quit grok, or after grok receives a signal
• Approval cards for background subagents no longer disappear when the parent turn ends
• grok worktree rm and gc no longer delete a worktree that an open session is using
• Pasted images over 50 MB are rejected with a clear message instead of being dropped silently
• grok -p --effort warns when the model ignores the flag, and refuses invalid effort levels
• Approval notifications name the session that needs approval
• grok worktree rm refuses to delete git repositories, .git folders, or any directory grok did not create
• grep and list_dir report a clear error when a search times out or fails, or the folder cannot be read, instead of returning no results
• Cancelled terminal commands show the command that was stopped
• Wrapped URLs in prompts and quotes link to the complete address
• Restarting after a model switch no longer reverts to the previous model
• Long tool turns that include PostToolUse hook output compact instead of hitting the prompt length limit
• Headless prompts that start with a byte-order mark no longer send that mark to the model, and no longer break JSON prompt files
• MCP tool replies that contain invalid characters no longer cause the call to time out
• Context overflow errors trigger automatic compaction instead of failing the turn
• Inline tags in agent replies no longer break line layout
• /workflow stop picks the correct live run
• Auto-compaction stops after three context refills in a row instead of looping
• Minimal mode shows the permission prompt instead of a hidden plan or cancel panel when both are present
• Approval cards close the block viewer so the card is visible
• The in-session resume picker matches the ungrouped layout on the welcome screen when that layout is configured

Original source

• Cancel and edit-resend on long sessions no longer revert workspace files
• Memory is only an on or off switch ([memory] enabled)
• The /share command and session sharing are removed from the CLI
• Headless grok -p waits for background goals to finish and reports their outcome
• /density and the Tool call density setting control how much detail tool calls show
• Slash command completion updates live when skills change, and shows the correct name for files under commands/
• /feedback Drafts supports G/Home and End to jump to the first or last draft
• Pinned dashboard sessions stay in the order you pinned them, and survive restarts
• Shift+Enter, Ctrl+., Ctrl+/, and Ctrl+[ / ] work inside tmux when extended-keys are enabled
• grok -p --output-format json reports the worktree folder used, including after -w name collisions
• Bare hook commands such as my-guard run from PATH when they are not next to the hook file
• grok sessions list and /resume show worktree sessions started from the same subfolder, and hide sessions from a sibling submodule
• /exit in a dashboard details view closes only that session
• --background-wait-timeout also stops an active headless goal after the timeout
• /workflow lists, stops, and resumes background workflow runs, and those runs appear in the tasks pane with a stop button
• Hooks that ask about web searches or file deletes show the hook name on the approval card
• Hook load errors in /hooks can be expanded
• grok worktree works inside Jujutsu repositories
• Images pasted with skill commands such as /pr-workflow are sent to the model
• Ctrl+C on a goal pauses the goal
• grok -p runs auth_provider_command when no login is stored
• Reopening a chat with an active goal continues the goal
• --allowed-tools is accepted as an alias for --allow in headless mode
• Slash command suggestions no longer hide the text after the cursor
• Sessions that open without a model list use Auto
• Very large pasted prompts are offloaded to a file instead of being sent inline
• Sign-in failures show a clear next step instead of a raw error
• Logging out stops running turns on local sessions
• Typing, arrows, Enter, or send-now (Ctrl+Enter) no longer answers a permission, question, or MCP prompt card
• /find keeps match counts accurate while output streams, and scrolls to the wrapped row that contains the match
• Images from tools are validated so a bad file no longer breaks the turn
• Dragging images from a file manager onto a terminal attaches them
• Plan comments added while a revision runs are preserved and sent when the plan is approved
• --disallowed-tools accepts the names shown to the model, such as run_terminal_command and spawn_subagent
• Long pastes without bracketed-paste markers are read in full instead of stalling after about 1 KB
• Worktree creation no longer hangs when the repo contains named pipes or sockets
• Write approval cards show the existing file contents that will be replaced
• Ctrl+C during a turn cancels the turn even when a modal is open
• grok -w opens at the worktree root, with a note, when the original launch folder is missing
• /cd and the location picker accept quoted or escaped folder paths
• Large file writes or many screenshots no longer end the session
• /delete with extra text shows an error instead of deleting the current session
• Number-key picks in the dashboard peek no longer go to the wrong agent after Up/Down
• Worktrees created with -w stay tracked when GROK_HOME is a symlink
• grok worktree rm and gc clean up names after a folder is deleted by hand, and restore names after a db rebuild
• grok worktree list shows unfinished copies left by an interrupted create
• grok worktree rm without -f keeps worktrees when the unsaved-work check fails or times out
• grok worktree rm and gc remove worktrees whose only untracked content is empty folders
• Typing a hidden command such as /cd runs it instead of a near-match skill
• @-file completion no longer accepts a match from an earlier query when you type quickly
• MCP tool calls show hook permission prompts, and cards name the hook
• Multi-select questions let you toggle several answers with number keys before submitting
• /workflow stop and /workflow resume target the live run
• Dialogs such as /feedback stay readable on a short terminal, and failed send status wraps inside the dialog
• Headless goal runs no longer print a spurious "Goal paused" after completion
• Background shell commands fail immediately when the working directory does not exist, and no longer flip back to running when late output arrives
• Closing a session in the dashboard no longer leaves it listed under Inactive
• /compact on an empty session no longer resets the reported context window
• With goals disabled, a headless /goal line is treated as a normal prompt
• Only slash commands at the start of a message trigger skills
• --system-prompt appends rules from --append-system-prompt
• Project skills are labeled correctly for nested projects
• Opening the resume picker is faster on machines with many worktrees
• grok worktree commands start faster by skipping model catalog work at boot

Original source

grok worktree rm without -f refuses to delete worktrees that are in use or have unsaved changes, and exits with an error

Compact mode collapses recaps and keeps inner spacing on tall terminals

Clicking the git branch in the header copies the full branch name

Long branch names abbreviate on narrow terminals and stay copyable

A targeted cancel stops only the response the client asked to stop

Compact mode hides the dock, or the tasks pane, the same way Ctrl+G does

A timestamps setting offers off, minimal, and on in Settings and /timestamps

Shell command output shows "Running …" while a command executes and "Ran …" when it finishes

Live preview pins include whether an app was observed behind the URL

The command palette (Ctrl+P) and the model picker open at the same width as the settings modal

Tables show copy buttons that export TSV, CSV, or Markdown for spreadsheets

The dashboard shows which worktree each session belongs to, shows the -m model in the new-agent box, and lets you toggle worktree mode in the folder picker

Shell permission decisions prompt or approve commands that match the permission manager

Cancelled turns mark unanswered tool calls as cancelled instead of succeeded

Long error messages in the /usage and /session-info modals wrap instead of being cut off

Status messages and subagent rows no longer use em dashes

A stalled model call during a turn retries before the turn fails

The queue pane and Ctrl+; still appear and work when the dock is hidden with Ctrl+G

Long sessions stay connected when the conversation is larger than 4 MiB

Permission rules accept native tool names such as run_terminal_command and Shell

/re-wind places the text cursor at the end of the restored prompt

A failed file write leaves the previous contents in place instead of an empty file

/loop and scheduler_create accept non-ASCII intervals such as 5分 without crashing the session

Naming only one scheduler tool in --disallowed-tools no longer makes the other two fail startup

Closing a busy tab no longer sends its queued prompts to the model

grok --cwd a stays in a instead of running inside a/a

The terminal title shows "Action Required" when any background session is waiting on approval

Headless grok accepts a prompt on piped stdin instead of trying to open the UI

[features] title_refresh = false in requirements.toml disables title refresh even when GROK_TITLE_REFRESH is set

Custom notification commands under [[ui.notifications.hooks]] run when their events match

An admin pin of [cli] use_leader = false keeps --leader from starting a leader process

When several MCP servers expose a tool with the same name, search_tool returns all of them

Grok windows editing settings at the same time no longer drop or corrupt config.toml entries such as MCP servers or permission rules

web_fetch rejects a huge file before downloading it into memory

memory_get no longer returns a file that exceeds the read limit

Continue to run no longer kills commands that are running inside background subagents

memory_search finds Japanese, Chinese, and Korean words inside longer notes

Drafts the model saves show up under their real titles in /feedback

Imagine replies that are not valid images are rejected instead of being saved as .jpg files

A workflow file that fails to parse reports that file and the parse error, instead of "unknown workflow"

Re-encoded images keep the orientation from their EXIF tags

Image and log paths reported after /fork --worktree point at real files

Tab characters in terminal command output are kept when the output is shown to the model

Transparent images stay PNG when they are re-encoded, instead of turning black

The bundled ripgrep is available to terminal commands, even on images that do not install it

Request bodies stay under a configured max_request_bytes limit

The effort level stays the same after a bare /model switch, instead of jumping to the new model default

Ctrl+\ and other modified digits no longer select an option on a permission or cancel card

Feedback submissions report success or failure accurately, without an early thanks or a repeated prefix

grok doctor names the config file or setting that prevents Grok from starting, instead of reporting zero issues

Recap summaries show up on screen without scrolling

grok doctor fix opens its confirmation on Cancel, so it does not edit shell or tmux config by accident

Slash commands run in any case, such as /COMPACT or /Compact

/context legend shows accurate percentages that always add up to 100%

Agent text stops redrawing the pager when a tool call interrupts the sentence

CLI tool calls no longer fail or overflow when the workspace directory is gone or the output is huge

Logs written to a file, or written when NO_COLOR is set, are plain text

A prompt fails immediately, with a clear message, when the session working directory is gone, instead of failing later or recreating it

grok -w works in repositories that use a separate git dir, and shows a clear error outside a git repo or on an empty repo

Shell tool descriptions state the real output truncation limit, and grep respects globs relative to the session directory

Compaction messages scroll into view instead of sitting below the bottom of the screen after a turn

Git-mode worktrees created with -w keep uncommitted changes

Worktrees created with --worktree-ref no longer contain the wrong submodule contents or LFS pointer text

Worktree creation shows the same clear error on every path

A failed worktree create shows a clear error on the home screen

Merge and rebase conflicts show up in the changes list

Starting a new session with durable rewind checkpoints on no longer crashes

A managed permission file with one bad key keeps its valid rules

Two worktree creates with the same label at the same time both succeed, instead of one failing with "already exists"

grok worktree rm without -f no longer deletes a folder that only shares a name with a removed worktree

Discard changes only the files you select, not similarly named files

One bad permission-rule entry no longer drops the other rules in that section

Chat Completions streams that end without a finish reason are retried instead of returning partial output

grok worktree rm by label refuses when that label exists in more than one repo

grep respects Read deny rules that use a leading ./

Command hooks no longer spike memory when they print a lot of output

Retry waits differ between processes

Original source

• /rewind lists only prompts you typed, and skips automatic runtime turns

• Custom model tables in config.toml keep the original model notice banner

• read_file, search_replace, and grep handle large files, special files, and binary content more reliably, and surface clearer errors

• Ask rules for WebSearch and WebFetch show a prompt instead of running on their own

• Cancelling one tool call no longer kills commands started by other parallel calls

• After login, a refused prompt is not retried on its own; the sign-in block needs a manual resend

Original source

grok inspect and the MCP doctor report MCP server sources correctly

Tool search activity folds as "Ran N tool searches" instead of claiming MCP tool results

Client rules supplied at session start are preserved when the system prompt is rebuilt later

Permission rules with relative paths apply even when the working directory contains symlinks

The context-compacted line shows the token count from right after compaction, instead of the count at the end of a long turn

Pressing Enter on a video card no longer tries to play it in a terminal that cannot show video or that lacks ffmpeg

Video cards open the file in the default player on Enter when the terminal has no inline playback, and no longer get stuck extracting posters without ffmpeg

list_dir on network or virtual filesystems skips slow subtree counts and prints a notice

Session startup is faster when loading skills from large directories, and shows what it is doing instead of a generic spinner

Original source

Sandbox enforcement on macOS uses the system Seatbelt (sandbox-exec) backend

New /context-window slash command lets you pick a context window size for the current session when the model offers choices

/model selection offers context window choices (when the model supports them) before the effort level

Plan comments can be deleted by clicking the [✗] button that appears on hover

Shortcuts panel search finds entries when you type any of the words in the label, keys, description or help text

Pasting on Windows no longer crashes from overlapping clipboard operations

Parallel tool calls that edit the same file run safely in sequence; unrelated tools stay concurrent

Original source

Give a Grok Bot the files, apps, and expertise it needs, then share it so your whole team can work from the same context.

Today we’re launching Team Bots, Grok Bots that work and learn alongside your team. Give one access to the files, apps, and expertise it needs, then share it so everyone can work from the same context.

At SpaceXAI, Team Bots brief account teams each morning, coordinate engineering projects, and answer data questions across the company. Here’s how they work, how we use them, and how to build one for your own workflow.

Team Bots bring context, tools, and memory together

You build a Team Bot around a role or workflow your team shares. Everyone gets access to the same Bot and its expertise, while still being able to work with it individually.

Every Team Bot brings together four things that help it do its job:

• Context gives it the relevant files, instructions, and skills, from brand guides to internal documentation.
• Plugins let it work in applications such as Salesforce, Notion, and GitHub. They can be connected by each person or configured for the whole team.
• Credentials let it securely access third-party APIs that do not have a plugin.
• Memories help it retain what it learns and improve at its role over time.

Although the Bot is shared, each person’s conversations with it remain private. The Bot keeps separate context and memories for each user while drawing on the skills shared across the team.

Teams can also collaborate with a Team Bot in Slack. Each Team Bot has its own handle, so you can invite it to a channel where everyone can ask questions, contribute context, and see its responses.

Team Bots take on work across SpaceXAI

At SpaceXAI, we’re using Team Bots in some of our most context-heavy workflows. Here are four examples from Sales and Customer Success, Product and Engineering, Marketing, and Data Analytics.

Sales and Customer Success

At SpaceXAI, every major sales account has a dedicated Team Bot. Each Bot is shared by the account executive, customer success manager, solutions architect, and sales leader.

Every night, the Bot reviews company news, recent Gong calls, Notion docs, and relevant Slack threads. Each morning, it posts a briefing in the account’s Slack channel with what changed and what each person should do next, including drafts tailored to their role.

Throughout the day, account teams use the Bot in Slack to assess strategy, check its thinking against account data, and plan next steps. The Bot remembers the decisions teams make and builds rich context over time. As people rotate on and off the account, it becomes the system of record and can quickly bring new team members up to speed.

Harper, an insurance company serving small businesses, built a Team Bot to identify customers with lapsed policies and help them reinstate their coverage, reducing manual work for its team and recovering substantial savings for customers.

“We initially had to manually check every customer through three platforms, get their balance details, and send them personalized emails. We built a Team Bot in 24 hours to automate this, saving our customers over $120,000 from hundreds of policies. This is now an ongoing engine for us, saving us time and our customers' money.”

Dakotah Rice, CEO, Harper

Customer Bot
A shared bot for one customer account. It keeps the AE, CSM, SA, and Sales Leader on the same page, posts a weekday morning brief, and drafts each person's next move.

Product and Engineering

Our Engineering Team Bot works from a project’s Slack channel and connects to Notion, Linear, Hex, Datadog, and Cursor. It follows product decisions, triages bug reports, creates tickets, and launches Cloud Agents to handle well-defined fixes.

We taught the Bot our shipping process through skills. It knows how to handle PR reviews, when to ask the team for help, and what evidence a change needs before it is complete. It coordinates the work across tools and agents, then reports progress and blockers in Slack.

We used this setup while building Team Bots. The Bot steered a Cursor Project that orchestrated hundreds of Cloud Agents, helping a five-person team ship more than 100 PRs a day and launch Team Bots in a few weeks.

EPD Teammate
The coordinator for your EPD team's project or feature. It keeps up with the project's Slack channels, files clear bugs in Linear, and runs Cursor cloud agents that return green, verified PRs, so the whole team stays in sync.

Marketing

Large marketing teams spend considerable time keeping their brand, messaging, and voice consistent. We built Marketing Bot to make that work easier.

We gave the Bot access to our brand guidelines, blog posts, and social copy. Whenever someone shares a draft for approval in Slack, it reviews the work against our voice and latest messaging. Regional teams can get feedback and keep moving in their own time zones without waiting for an approval cycle at HQ.

For website and SEO changes, Marketing Bot carries the work from review to launch. Once a content update passes review, the Bot makes the change and posts a preview link in Slack for final sign-off. Anyone on the marketing team can ship website updates without filing a ticket or waiting on engineering, and every change goes through the same brand and SEO checks.

“We’re building toward Team Bots for every marketing function. These Bots help us dig into market and customer intel, show up in AI answers, review launches, and tell us what’s working.”

Angela Ferrante, Head of Marketing, Amplitude

Marketing Bot
Keeps your marketing team on-brand. Reviews any artifact against your brand guidelines and latest messaging, and takes approved website and SEO changes from review to preview and sign-off, so every region can ship on its own schedule.

Data Analytics

Our data analytics team receives dozens of requests each day for one-off analyses. It built Data Bot so anyone at SpaceXAI can get answers without waiting for an analyst or setting up warehouse access.

Data Bot uses shared, read-only credentials to query approved tables in Databricks. It also connects to Datadog, Hex, and Statsig to investigate questions and present the results.

The data analytics team had already spent two years building a library of skills for working with more than 45,000 tables. It gave that existing library to Data Bot, including instructions for finding the right data, analyzing feature usage for fraud, following SpaceXAI’s chart standards, and safely updating company-wide dashboards. Data Bot also remembers corrections to its queries, so what it learns from one person improves the answers it gives everyone.

Data Bot
Answers your team's one-off data questions from your warehouse with read-only queries, clear metric definitions, and charts. It remembers every correction and confirmation, so answers get better for everyone over time.

Get started with Team Bots

Team Bots is available today in public beta on Teams and Enterprise plans. Take your favorite Grok Bots and share them with your team. To get started, try one of our pre-built Team Bots for sales, product management, marketing, or data analytics.

Try Team Bots today

Download for Windows
Contact sales

Original source