SuperX 1.0.0

SuperX 1.0.0 is the first stable milestone on GitHub: automatic fact-checks while reading X, plus explicit checks of your own posts and replies before publishing.

Download the installation ZIP · Public source

What changed

• Check before posting. Use the round SuperX button beside Post/Reply. Findings stream below the editor; the draft remains the target, with available parent posts, reply ancestors and quotations as supporting context. SuperX does not publish your draft.
• Include images. Published-post pictures and relevant quoted/parent pictures reach the model as image inputs. Draft checks accept up to four PNG/JPEG images, 8 MiB total, including image-only drafts. Images are read only when you request a draft check. Unsupported or unavailable images produce an explicit error. Unpublished video attachments are excluded; a supplied video thumbnail is only a still frame.
• Choose a connection. Sign in with The X Subscription, use a Grok API Key, or connect official local Grok Build. Grok 4.3 with no reasoning is marked Recommended for quick, concise checks. Existing choices remain intact; no automatic provider fallback.
• Keep reading context. Source links, model/Token details and searchable on-device browsing history for the past 24 hours remain available. Draft contents and results are excluded from persistent history and answer caches.
• Refine the interface. Stable composer controls, clear progress and retry actions, image-change handling, twelve interface languages and thirteen concise localized package summaries, including browsing history.

Install or update

1. Extract SuperX-1.0.0.zip into a permanent folder. SuperX.zip is an identical-byte alias.
2. In Chrome or Edge Extensions, enable Developer mode and load that folder. For an existing unpacked installation, replace its files, reload the extension and refresh X.
3. Open Settings and use your preferred connection. New installations default to subscription sign-in and Grok 4.3 with no reasoning. Account availability, allowance and charges follow the selected provider.

The Chrome Web Store update is separate and has not been submitted by this GitHub release. Its last verified public version is 0.9.12. The exact installation ZIP above is the file to upload to the store; do not upload the source ZIP.

Validation and scope

• 1,191 automated checks passed in both the working source and exported public source.
• 1,631 isolated composer checks, 81 focused image checks and 126 recommendation-layout checks passed.
• Installed Windows Chrome with subscription OAuth and Grok 4.3 handled published images, parent-image reply context and an image-only draft. With no draft text or image description, it corrected an image's 37 × 8 = 306 claim to 296. Hide/show retained the result and removing the image disabled the empty-draft check. Nothing was published during testing.
• A fresh isolated Edge extension read a real X-hosted image through the production local-Build image loader without new host permissions. This is transport evidence, not a live Build model test.
• Fresh real-account API Key/Build image inference, installed macOS and OAuth natural-expiry/restart scenarios retain their documented acceptance limits. No stable label guarantees model accuracy or every account's entitlement.

See the acceptance record, privacy policy, and connection guide.

Community credit

Thank you to @0xDenji-Ai for PR #1, proposing local Grok CLI access, dwell triggers, macOS guidance and preserving started work across tab switches. Those main goals were covered through a separate implementation rather than merging the older patch. This release also adds explicit checks of the user's own unpublished draft; it does not adopt a click-only mode for browsing other posts.

安装或更新请使用上方 SuperX-1.0.0.zip。本版包含帖子与草稿核查、图片上下文、证据来源及近 24 小时浏览历史。Chrome 商店需单独上传审核；本次不会自动更新商店版本。

Source commit: 5cfa125f9000866c1719afc452d1867ef37280bf.

Installation SHA-256: 72480dd586d962e3b67004348072b6a9b4bd0c6f8fad345183bb85fc82f892fe.

SuperX v0.9.13 (Preview)

Check your own post or reply before publishing. SuperX 0.9.13 is available as a GitHub Preview; Chrome Web Store and GitHub Stable/Latest remain 0.9.12.

Download the installable ZIP · Versioned ZIP · Source ZIP

What changed

• Check a draft without leaving the composer. A compact round SuperX button sits immediately before Post/Reply in home, new-post dialogs, reply dialogs and inline replies. Enter text to enable it. Click to check; findings and evidence links stream below the native toolbar.
• Keep the draft as the target. Published posts and drafts share the same editable fact-check core. Quoted posts, the original post and available earlier replies provide bounded supporting context. New-post and reply context instructions can be customized separately in Settings.
• Use contextual questions and short replies. Native reply/quote previews are read even when X does not expose a permalink. Unverified snapshots remain supporting context, and links are restored only when an exact unique match is available. Nested quotations are bounded; unrelated posts are excluded.
• Preserve the writing layout. The fixed-size logo button uses symmetric native spacing and matches Post/Reply's disabled appearance. Showing or hiding findings preserves the toolbar boundary and modal width; long findings remain outside sticky reply controls.
• Keep work and feedback clear. Editing marks an existing answer stale; rechecking is explicit. Switching tabs or hiding findings preserves the same started task. The header shows progress and reported tokens, with model and available search records on hover. Local Build recovery restores an explicit retry without silently resubmitting.
• Refresh all package summaries. Thirteen locale catalogs now describe post and draft checks, evidence links, 24-hour browsing history, and The X Subscription/API Key connections. Every summary fits Chrome's 132-character limit.

Draft data and current limits

Draft text is sent only when you click the check button, using the selected subscription, API Key or local Build connection and its account allowance. Available reply/quote context accompanies that request. Draft attachments are not inspected or sent. SuperX does not edit or publish your text, generate an image, or attach anything. Draft tasks stay in runtime memory and are excluded from browsing history, the answer cache and local diagnostic records. See the updated privacy notice.

• Validation: 1,143 automated checks and 1,551 isolated browser checks passed; the browser run produced 53 screenshots with no page errors or external requests.
• Recorded live checks: Windows Chrome/Grok 4.3 resolved a reply question about NASA's Apollo 17 samples and a quoted-post question about Lunar Reconnaissance Orbiter, with evidence links. Toggling findings kept the same output and usage; editing marked the result stale. No posts were published.
• The live checks used the functional candidate before the final button-only refinements. Final visual refinements have isolated-browser coverage. Fresh API Key/local Build draft inference, installed Edge/macOS and the remaining relevance cases have not been newly verified. Test coverage does not guarantee every model answer. Full details: acceptance checklist.

Install or update

1. Extract the installation ZIP into a permanent folder.
2. In Chrome or Edge Extensions, enable Developer mode and load the extracted folder. To update an existing unpacked installation, replace its files, reload the extension, then refresh X.
3. Open Settings and use Sign in · The X Subscription, your own Grok API Key, or Grok Build · Local CLI / ACP. Existing connection selections remain intact.

The versioned ZIP and SuperX.zip contain identical bytes. Installation checksums · Source checksums · Changelog · Report a problem

Built from commit 266db348f2e357af9c38cf3c9181a7e5c9a5777f. GitHub CI passed on Windows, macOS and Ubuntu. All seven GitHub-built attachments were downloaded and verified byte-for-byte against the locally validated release bundle. Installation ZIP SHA-256: cdbbffc6fe3bdbaeaab4814fd9e34e50ae685c4a77c0e43d6551aa40f2393a60.

Unpacked and Chrome Web Store installations have separate storage when their extension IDs differ. Avoid running two enabled copies at once. This GitHub release does not submit the update to the store or change the existing stable packages.

---

中文： 0.9.13 新增发帖／回复前主动核查：点击 Post／Reply 左侧的 SuperX 圆形按钮，在输入框下方查看核查和证据来源。草稿是核查目标，引用帖和回复链仅作辅助上下文；编辑后需手动重新核查，不会自动发布。按钮大小、灰态、左右间距和弹窗滚动布局已优化，全部语言概要已更新。当前为 GitHub Preview，商店稳定版仍为 0.9.12；请下载安装 ZIP 手动更新，勿使用源码 ZIP 作为商店安装包。

SuperX v0.9.12 (Stable)

SuperX 0.9.12 fixes the right-hand rail jumping down when the inline reply editor opens on an X post.

Download the installation ZIP · Source ZIP · Checksums

Fixes

• X uses role="tablist" for both page navigation and reply media controls. SuperX now distinguishes them, keeping the rail header at the top and the original answer visible when you focus or expand the inline reply editor.
• Keep the rail aligned when native navigation changes height because of fonts or CSS transitions. Discard obsolete geometry observers when navigation or overlay visibility changes.
• Preserve existing answers, citations, Token details and independent answer scrolling. Existing handling for enlarged media and compose dialogs continues to hide the rail until those windows close.

Validation

• 1,082 automated tests passed, including 263 content/overlay tests.
• 912 isolated browser checks passed across post detail, home and profile layouts, dark/light themes and two viewport widths. The old version reproduces the reported failure in the same fixture.
• Real Windows Chrome 0.9.12 passed inline reply focus, scrolling away and back, enlarged-image open/close and new-post dialog open/close. The original four completed answers remained unchanged. No reply or post was submitted.
• Exported-source validation passed, and rebuilding its installation ZIP produced the same bytes as the accepted candidate. This layout patch does not establish new provider/account, natural credential-expiry or installed macOS acceptance.

Installation and store update

This is the Stable/Latest release, published in the Chrome Web Store and verified on October 20, 2026. The SuperX.zip alias contains exactly the same bytes as SuperX-0.9.12.zip.

For a manual update, extract the installation ZIP into the same permanent extension folder, reload SuperX in Chrome/Edge Extensions, then refresh X. For Chrome-managed updates, install from the store link above. The attached installation ZIP is the same accepted candidate; source archives are not installation packages.

Installation ZIP SHA-256: c34d378b2eb37660a0d029c0e2c36b2dd4077a3548413a5a9b35ca55d293c885.

Changelog · Installation guide · Report an issue

---

中文

修复在帖子页激活“发布你的回复”后，SuperX 顶栏下移、原回答被裁掉的问题；同时修复原生导航高度变化后右栏更新不及时的问题。

已通过 1,082 项自动测试、912 项隔离浏览器检查，以及真实 Windows Chrome 的回复框、滚动返回、图片和新帖弹窗验收。原有四条已完成回答保留。源码重建安装包与验收包逐字节一致。

此版本于 2026-10-20 核验 Chrome 商店公开上架后，晋升 GitHub Stable/Latest。可通过商店安装与更新；手动安装请解压上方安装 ZIP 到原扩展目录，重载扩展后刷新 X。

Stable promotion / 稳定版晋升 — 2026-10-20

The Google-delivered 0.9.12 CRX matches all 49 ordinary files in the accepted ZIP; the only differences are Google’s update URL in the manifest and verification metadata. The original tag and all seven installation/source attachments and hashes are preserved. This promotion adds no new store-installed functional test. Current documentation is on main; tagged archives retain the original Preview-era documentation.

商店包除 Google 更新地址和验证元数据外，与验收包一致。原标签、七个附件及校验值保持不变。本次为发布渠道同步，不增加新的商店实装验收结论；当前文档在 main，标签及源码归档保留原始发布时的文档。

SuperX v0.9.11 (Stable)

SuperX 0.9.11 is the current Stable release, available from the Chrome Web Store and GitHub.

Install from the Chrome Web Store · Download the installable ZIP · Source ZIP

For Chrome-managed installation and updates, use the store link above. For manual installation:

1. Extract the installation ZIP into a permanent folder.
2. Open Chrome or Edge Extensions, enable Developer mode, and load that folder as an unpacked extension.
3. Open SuperX settings. New installations default to Sign in · The X Subscription: approve the short code yourself on the official xAI authorization page and return to SuperX. Grok API Key and Grok Build · Local CLI / ACP are optional alternatives, with Windows/macOS guidance. Existing connection choices are preserved. Save settings, enable SuperX and open X. Account eligibility, models, allowance and charges follow provider rules.

Unpacked installations update manually: replace the files in the same folder, reload the extension, then refresh X. Installing a separate Chrome Web Store copy does not automatically migrate an unpacked copy's settings or Key.

Installation files: versioned ZIP, SHA256 checksums, file inventory. SuperX.zip contains the identical ZIP bytes.
Source files: SHA256 checksums, file inventory.
Optional local mode: Windows / macOS setup guide. Install Grok from the official provider, sign in and follow the built-in guide; no separate SuperX program or Node installation is required.

Support: Report a bug or suggest a feature · Installation guide · 中文说明

The Chrome Web Store and GitHub Stable/Latest now provide 0.9.11. This promotion changes release status and notes only; the original tag, ZIPs, inventories and checksums are preserved. See release channels.

Stable promotion — 2026-10-19

• The official Chrome Web Store listing reports 0.9.11, updated October 19, 2026, item clcflilaihhnnglfamdblhopokpnlioo.
• The Google HTTPS-delivered CRX contains 51 files versus 50 in the accepted ZIP. All 49 ordinary files are byte-identical. The manifest adds only Google's update_url, and the only extra file is _metadata/verified_contents.json. No other payload difference was found.
• CRX SHA-256: 80abbbe205bb8664639fdc8771167ab7bd5f191d351aac5ad678f10788a3873d. CRX and ZIP use different formats, so whole-package hashes are not expected to match. This was an HTTPS payload comparison, not installation or independent signature verification.
• The existing v0.9.11 source commit, seven release assets and their digests remain unchanged. GitHub Latest now points to this version; 0.7.26 remains available as an older release.
• Functional acceptance below belongs to the installed Windows Chrome candidate tested on October 18. A new store-installed functional run was not performed during this promotion. The remaining four-scope full restart, natural expiry and other browser/account checks remain open.
• Current channel and acceptance documentation is on main; tagged source and source ZIPs retain their original Preview-era documentation as an immutable release snapshot.

Final build verification — 2026-10-18

• Reviewed source commit: 151985851dd6555e62864b9f2fb6d2568e9b4d77.
• Windows / macOS / Linux CI and release packaging passed on Node 22. Local and independently exported public-source validation each passed 1,057 tests.
• Sixteen isolated MV3 locale-selection cases passed. These are metadata checks, not installed Edge/macOS service acceptance.
• The Windows test harness resolves 8.3 short and long names to the same real directory; environment restoration, credential isolation and cleanup assertions remain enabled. This test-only correction does not change the installation ZIP.
• Public source contains 111 allowlisted files. Website code, store submission materials, temporary probes and credentials are excluded. Rebuilding the exported source gives the identical installation ZIP.
• All seven GitHub-built asset digests match the accepted local package, inventories and checksums.
• Installation ZIP SHA-256: cc77b5b1c3f2aa0fcc679127f53003ceac562f3b35ba54af14ec34761d1789bc.
• Public source ZIP SHA-256: 62064c03dacfe4f62209871ca837be180160d2a271946430be0b195a5f17f89e.
• At the original October 18 Preview publication, Chrome Web Store submission was still separate. The October 19 promotion below supersedes that channel status. Version 0.7.26 and its original assets remain a historical archive.

What changed since Stable 0.7.26

• Go deeper with Fact Check only. Run one streamed fact check instead of an explanation followed by a second check. Investigate explicit claims, implied factual premises and relevant details without repeating the original post. Keep tool commands and intermediate output out of the final answer; mark missing final answers as incomplete.
• Sign in with The X Subscription directly in the browser. New installations default to this route; Grok API Key and official local Grok Build / CLI / ACP remain independent options. Browser sign-in needs no Key, terminal or extra SuperX program. The official authorization page may show Grok Build because this flow uses the shared public client, not a separately registered SuperX identity.
• Choose model and reasoning separately. All three connections start at Grok 4.3 / None and offer the same curated 4.3 / 4.5 / 4.6 / 4.7 menu, subject to account availability. Preserve saved settings, show unavailable choices explicitly and never silently change source, model, account budget or service tier.
• Wait for reading. Automatic work starts after scrolling stops and a post remains visible for 1 second; Settings supports 0-30 seconds, including fractions. Default shared API concurrency is 3, configurable from 1 to 8. Started work retains its slot through local cancellation cleanup; local CLI work runs serially.
• Keep started work when browsing. Preserve fact checks, comments and retry progress when scrolling away, when X temporarily unmounts a post, or when switching browser tabs. Returning reuses the same task. New automatic work pauses while the feed is hidden. Actual navigation, tab closure and BFCache suspension safely interrupt work, retain available partial output and require manual retry.
• Let X dialogs and media take precedence. Temporarily hide the entire SuperX interaction layer for compose/reply dialogs, enlarged media and fullscreen content. Restore it after closing, and use consistent blue answer/source links in both themes.
• Keep failures local to the task. API Key and local CLI transient failures wait 3 seconds and retry up to 5 additional times without freezing other posts; partial findings and reported usage accumulate. OAuth does not replay generation after an accepted HTTP 200 response, stream failure, incomplete output or timeout. An initial HTTP 401 rejection may refresh once and make one recovery request. Retries can use additional allowance or incur charges.
• Simplify Settings and troubleshooting. Improve connection guidance, local model/search validation, disabled-state saving, compact preset/custom prompt controls and collapsible maintenance. Align Settings and history layout, keep history navigation last and localize extension metadata across the twelve interface languages.
• Retain the reading tools. Stream Markdown with clickable sources and Token/model details, offer three copy-only comment drafts, retain independent answer/interface languages and keep searchable on-device 24-hour history available without a Grok login or Key. History text is stored locally without encryption; credentials are handled separately.
• Minimize and isolate credentials. New sign-ins request only openid, offline_access, grok-cli:access and api:access; no profile/email scopes or profile lookup. Remembered refresh tokens are encrypted locally, access tokens remain session-only, and credentials stay out of the feed page. Existing connected grants remain valid without claiming retroactive scope reduction. Upgrading may require approval of the additional auth.x.ai site access.

Acceptance and current limits

• Installed Windows Chrome has passed fresh user-approved four-scope authorization, login restoration after extension reload, a new Grok 4.3 Fact Check (30,226 tokens; six linked sources) and exactly three new comments (1,373 tokens). The copy button reported Copied; independent clipboard readback was not verified. The user confirmed that switching tabs during generation preserved the same running answer without restarting it.
• Four-scope full-browser restart restoration and natural token expiry still require separate recorded acceptance. Earlier six-scope checks exercised copying, cache reuse and generation after fully restarting Chrome; those are historic...

SuperX v0.7.26

SuperX 0.7.26

Understand X. Fact-check as you scroll.

The first Stable release is now available from the Chrome Web Store. Chrome manages updates for store installations. This existing GitHub release was promoted from Preview; its tag, installation ZIPs and source archive were preserved.

• Stream explanations and background Fact Checks beside visible X posts, using your own xAI API Key.
• Follow the displayed post language or select a fixed answer language; configure the SuperX interface language separately.
• Read Markdown answers, inspect Token/model usage, and generate three optional one-line comments to copy.
• Revisit locally saved posts and answers from the past 24 hours, including posts seen without an API Key.
• Remember the Key with automatic local encryption and restore it after restart, without a password setup step.

Install and update

Chrome: Install from the Chrome Web Store, open SuperX Settings, enter your own xAI API Key and save. API usage is billed by xAI.

Manual installation: download SuperX.zip, extract it to a permanent folder, and load that folder as an unpacked extension in Chrome or Edge Developer mode. Edge installed-extension acceptance remains pending.

Manual installations update by replacing files in the same folder, reloading the extension and refreshing X. Switching from an unpacked copy to the store is a separate installation; settings and the Key do not migrate automatically. Disable the old copy to avoid duplicate analysis, then configure the store copy.

Files and integrity

Latest stable ZIP · Versioned installation ZIP · Installation checksums · Public source ZIP · Source checksums.

Release source commit: 254cade96e210e3faef4ca7e08fb67f6bc8c8e90. Installation ZIP SHA-256: 23711b6b3349428ad7374e4e409a8a96241794f1820889f7dfdbf3d0e15040b2. SuperX.zip and the versioned ZIP contain identical bytes. The store's 0.7.26 runtime files match this package; Google adds its update address and verification metadata when producing the signed CRX, so the CRX and ZIP have different package hashes.

Validation and remaining checks

Local and exported-source validation passed 642 automated checks and reproduced identical installation ZIPs. GitHub CI passed on Windows and Linux. The user previously confirmed upgrade behavior, restart Key restoration, fresh-install defaults, no-Key history, explanations and Fact Check, independent language switching, Auto translation-following and comment generation/copy in Windows 11 Chrome. After installing from the Chrome Web Store, the user also confirmed explanations, Fact Check, Key saving and restart restoration work normally.

Edge installed-extension acceptance and advanced manual failure-path scenarios remain pending. Store publication and Stable status do not guarantee model accuracy; check sources and configure your own xAI account's model and API access.

Installation guide · 中文说明 · Report an issue · Privacy.

The website is maintained separately and is excluded from the public source.