SuperCodex installer
Install SuperCodex from the dashboard, not from random files.
The dashboard creates the OS-specific installer path for the signed-in workspace. SuperCodex runs beside official Codex, keeps the user's native tools, and routes model work through Luma Cloud.
Recommended path
Use the installer block in Luma Cloud App. It issues a short-lived ticket and builds the command or package link for that account.
Prerequisites
Keep the setup small. Do not ask customers to edit JSON or download unpublished artifacts by hand.
Installer lanes
Three command endpoints, one ticketed flow.
The raw endpoints are shown so support and docs stay precise. Customers normally copy these from the dashboard because the real command contains a one-time scit_ ticket.
macOS Apple Silicon
Terminal / zsh
Use this for M1, M2, M3, and M4 Macs.
https://app.lumaos.cloud/api/downloads/supercodex/install-command?arch=arm64macOS Intel
Terminal / zsh
Use only when the dashboard offers the Intel option for the current release.
https://app.lumaos.cloud/api/downloads/supercodex/install-command?arch=x64Windows x64
PowerShell 5.1+
The installer keeps PowerShell open on failure and prints the log folder.
https://app.lumaos.cloud/api/downloads/supercodex/install-command?platform=windows&arch=x64Boundary
What SuperCodex installs and what it leaves alone.
The installer is a Luma Cloud product path. It must not reroute official Codex, Codex OmniRoute, private shard URLs, or unrelated local bridge traffic.
Local runtime
Provider profile
Local bridge
Battery
Launch helpers
Logs
Platform notes
macOS and Windows have different first-run prompts.
These are expected OS prompts for a beta installer. The dashboard guide should keep them visible so users do not stop halfway through setup.
macOS
Apple Silicon is the primary Mac path; Intel is available only when the dashboard offers the current x64 artifact.
Recommended
Download the .pkg from the dashboard, open it, and follow the installer prompts.
Gatekeeper
If macOS blocks the package, open System Settings -> Privacy & Security and choose Open Anyway for SuperCodex.
Keychain
On first launch, macOS may ask for the Mac login password. Choose Always Allow when reusing the official Codex sign-in.
Logs
Collect ~/.supercodex/logs, especially one-command-install.log, installer-runtime.log, bridge/, battery/, and launch-supercodex.log.
Intel
Use the x64 lane only when the current dashboard release offers it. Apple Silicon is the primary macOS path.
Repair
Re-run the current dashboard installer command. It refreshes the runtime and preserves the local Node runtime where possible.
Windows
Windows x64 uses a separate SuperCodex Electron duplicate and leaves the official Microsoft Store Codex package alone.
Recommended
Download the Windows setup from the dashboard or copy the PowerShell command from Advanced.
Official Codex
Install official Codex from the Microsoft Store first. SuperCodex duplicates and patches its own copy; it does not patch the Store package.
SmartScreen
If Windows shows a blue warning, choose More info, then Run anyway.
Paths
Default logs live under %LOCALAPPDATA%\LumaCloud\SuperCodex\logs. Profiles with spaces may use a printed ProgramData path.
Shortcuts
The installer creates SuperCodex desktop/start-menu launchers and a startup shortcut for the battery indicator.
Status
Windows x64 is documented as the beta lane. Keep the PowerShell window and logs if a setup step fails.
After install
Confirm the bridge, battery, and model path.
A successful install should make the user-visible state boring: app opens, battery shows quota, local bridge responds, and model requests enter Luma Cloud through the public gateway.
Quota battery
Official boundary
Provider
Updates
Troubleshooting
Fast checks before escalating.
Most install failures are session, ticket, OS prompt, or local bridge state. Collect logs before changing account or runtime state.
Install command returns 401
Sign in to the dashboard again, then copy a fresh command. The command endpoint is session-gated.
Ticket expired or already used
Copy a new command. The scit_ ticket is short-lived and single-use by design.
Package is blocked by macOS or Windows
Use Open Anyway on macOS or More info -> Run anyway on Windows, or use the terminal command path.
Bridge is not responding
Restart SuperCodex. On macOS, the bridge LaunchAgent keeps retrying; logs are under ~/.supercodex/logs/bridge.
Quota battery is missing
Open SuperCodex once, then check the menu bar or tray overflow. The battery starts separately from the desktop app.
Wrong endpoint in a client
Use https://api.lumaos.cloud/v1. Do not paste localhost, bridge, shard, VPS, or OmniRoute URLs into customer tools.
Windows profile path has spaces
Use the printed installer root and log folder. Do not move files manually after setup.
Support request
Send OS, architecture, app version, the visible request id if any, and the log folder. Do not send API keys or cookies.
Truth gate
Do not claim a platform lane is ready if the dashboard does not currently expose its artifact or command.
The installer command depends on a valid session, download entitlement, ticket store, and release artifact availability.
Windows x64 has scripts and customer docs, but support should still request logs and avoid promising full parity until the current build is smoke-tested on a clean Windows machine.
Related setup docs
Use these when the user wants external CLI/IDE keys instead of the managed SuperCodex desktop path.
Need a command shape without a real ticket?
The macOS command pipes the dashboard script into zsh with LUMA_CLOUD_INSTALL_TICKET, arch, app URL, and API base URL. Windows sets the same variables in PowerShell before running the installer script.