Grok Bot 的隐藏“Elon-Only Settings”选择器列出了33个模型
处于休眠状态的桌面控制拉取了一个账户范围的目录，涵盖 Grok、GPT、Claude、Gemini、Kimi 和 GLM。
By RuntimeWire Staff · Published · Updated
RUNTIMEWIRE INVESTIGATION — Exclusive
Original reporting by RuntimeWire, based on documents, testing, reverse engineering.
Why it matters
The hidden catalog shows Grok Bot can route persistent agents across rival models, giving SpaceXAI and Cursor control of the interface, account and billing layer above the models.
Reporting record
Finding
SpaceXAI shipped Grok Bot 0.16.0 with a hidden settings card labeled “Elon-Only Settings” whose working model picker queried an authenticated, account-scoped catalog containing 33 models from xAI and competing providers.
How we verified
Methods: documents, testing, reverse engineering.
Grok Bot’s shipped renderer contains the “Elon-Only Settings” component, Model control and visibility guard. Source-mapped TypeScript documents the model-catalog request and account-scoped persistence path. Runtime testing returned 33 USER_AVAILABLE catalog entries and rendered them in the hidden picker. Screenshots, console output, original binaries, hashes and SpaceXAI’s conflicting public documentation were preserved.
RuntimeWire inspected Grok Bot’s Windows installer and app.asar, reconstructed original TypeScript from bundled source maps, and traced the settings component through its renderer guard, IPC handler and authenticated model-catalog request. The tested account was assigned to the live sand_model_selection treatment arm, which suppressed the card. RuntimeWire changed only the local renderer visibility condition, restarted the client and opened Settings → General. The unchanged shipped component requested the authenticated account’s catalog and displayed 33 entries. RuntimeWire separately recorded the experiment state, raw catalog response, current stored model and screenshots before restoring the original ASAR. Caveat / limitations The test proves that the shipped picker is functional and connected to a live account-scoped catalog. It does not prove that every listed model can serve Grok Bot turns on every account, or that Elon Musk personally uses the panel. The uploaded installer and analyzed ASAR both identify as 0.16.0, but their ASAR hashes do not match; they should be described as neighboring builds unless the installed copy is independently matched to its installer. Classification rationale RuntimeWire independently discovered and demonstrated an undisclosed shipped interface and its live backend connection. No earlier public report documenting the “Elon-Only Settings” label and 33-model catalog was identified.
Tested versions: Grok Bot 0.16.0, Windows x64; Electron 42.1.0; Chromium 148.0.7778.97.
Reproduction
Reproduction does not apply to this reporting (document-driven).
Preserve and hash the original app.asar. Open Grok Bot DevTools and call desktop.experiments.getSnapshot(). Confirm the tested account reports sandModelExperiment: {active: true, arm: "treatment"}. Call desktop.agent.getAvailableModels() and preserve the returned catalog. Change the renderer guard function not(){return cs(ct().experiments.snapshots)?.sandModelExperiment!=null} to return false, preserving byte length. Restart Grok Bot and open Settings → General. Confirm the shipped “Elon-Only Settings” card appears. Open the Model control and compare its entries with the authenticated catalog response. Restore the original ASAR.
Company response
RuntimeWire requested comment; the company had not responded by publication time.
SpaceXAI 在发布 Grok Bot 时包含了一个标注为 "Elon-Only Settings" 的隐藏模型选择器，尽管其 teams and enterprises 指南称该产品没有模型选择器，也不打算允许用户或管理员选择模型。另一份设置指南仍然记录了在“当可用时的默认模型”控制项。
RuntimeWire 发现，该休眠控制与一个经过认证、按账户范围的目录相连，该目录包含来自 xAI 和竞争性 AI 实验室的 33 个模型。
RuntimeWire 启用了桌面客户端的本地显示保护，暴露了应用程序通常隐藏的设置卡。该卡包含了一个用实时账户数据填充的 Model 控件。返回的条目包括 Grok 4.5、Claude Opus 5 和 GPT-5.6 Sol，以及来自 Google、Moonshot AI 和 Z.ai 的模型。
该目录和已交付的请求机制表明 Grok Bot 被构建为接受来自竞争模型提供商的选择。但这并不证明所选的 GPT、Claude 或其他外部模型实际上为 Bot 的一次回复提供了服务。测试账户处在 sand_model_selection treatment arm。
此计数是对被测试账户的快照，而非对每个 Grok Bot 订阅者都能使用这 33 个条目的承诺。目录内容和执行权限可能因计划、组织和灰度投放而异。检查也未证明 Elon Musk 个人使用该面板。“Elon-Only Settings” 是客户端的字面标签，其存在表明 SpaceXAI 的开发者在已交付的应用内部如何对该控制项进行分类。
SpaceXAI's guides conflict with each other and the shipped client
SpaceXAI 的公共文档对模型选择给出了两种不同说法。其 teams and enterprises guide 断言性地写道：“Grok Bot has no model picker, for members or admins. We do not plan to allow admin or user choice for models that are used with Grok Bot.” 然而其 general settings page 则记录了“Default Model, when model selection is available.”
已交付的客户端包含了设置指南有条件描述但企业指南否定的那个控件。RuntimeWire 通过更改抑制该账户设置卡的本地可见性保护来将其暴露。应用随后请求了账户的实时模型目录并用 33 个条目填充了该控件。
RuntimeWire 只更改了客户端的可见性条件。“Elon-Only Settings” 标签、Model 控件、经过认证的目录请求及返回的模型条目都已存在于已交付的应用中。
这种差异对企业买家具有重要含义，因为 SpaceXAI 的指南不仅仅说模型选择目前不可用。它写明 Grok Bot 没有选择器，并且 SpaceXAI 不打算允许管理员或用户选择该产品所使用的模型。已交付的客户端和单独的设置指南恰恰保留了这种能力，即便访问可能仍受账户、计划或灰度投放的限制。
该模型选择器也契合 Grok Bot 异常的产品架构。尽管带有 Grok 名称，该应用依赖于 Cursor 账户和基础设施。SpaceXAI 的 setup guide 指导用户使用 Cursor 登录，通过 Cursor 下载桌面客户端，并使用合格的 SuperGrok Heavy、Cursor Ultra 或 Cursor Teams Premium 计划。
SpaceXAI 的 privacy and security documentation 表示 Grok Bot 遵循 Cursor 的身份验证、账户设置和训练退出选择。其云端计算机存储浏览器会话、文件和可以在用户的 Bots 之间共享的凭据。因此该产品建立在更广泛的 Cursor 账户和模型路由基础之上，尽管 SpaceXAI 将这些代理宣介为 Grok 队友。
Grok Bot can expose multi-provider choice without changing its pitch
Cursor 已经销售来自多个提供商的前沿模型访问权限。其 pricing page 宣传前沿模型访问和云端代理，而其自身的 Grok 材料表示 Cursor 和 SpaceXAI jointly trained Grok 4.5。包含 GPT、Claude、Gemini、Kimi 和 GLM 的模型目录与该底层供应商结构一致。
对 SpaceXAI 而言，这种安排提供了更快的路径来进入带有持久计算机的代理。Grok Bot's product documentation 表示每个用户都会获得一个带有浏览器、文件系统和终端的云计算机。Bots 可以保留会话、运行例程并相互协调。模型选择可以让 SpaceXAI 或 Cursor 为这些任务分配不同的推理引擎，同时保留 Grok Bot 界面及其已保存的工作状态。
这点重要，因为代理层日益掌控客户关系。模型可以在底层改变，而用户的 Bots、文件、授权、例程和已连接账户仍然保留在位。隐藏的选择器为 Grok Bot 提供了技术表面，使这些选择对有资格的用户可见，或将其保留在自动路由之后。
SpaceXAI 的文档表示，附属于同一用户的所有 Bots 共享一个云计算机及其经过认证的会话。该持久状态是产品的主要锁定来源：改变底层模型比在别处重建 Bot 的工作环境要容易得多。
“Elon-Only Settings” 标签暴露了一个在表面上精致的测试版中的粗糙内部接缝。关键部分是其后面的实时目录以及围绕它的文档冲突。Grok Bot 随客户端和后端机制一同到达，使被选中的账户可以在多个模型提供商间进行选择，而 SpaceXAI 的企业指南则表示这种选择既不存在也不在计划之中。