Frequently Asked Questions
Where should I start?
Install the Windows desktop application, then complete the simulation-first workflow in Getting Started. Use Desktop And Main Menu when you need to find a window or command.
How do I know whether a feature is ready for public use?
Use Feature And Provider Status. The knowledge base uses these labels consistently:
- Current — implemented in the reviewed build, subject to the documented provider and entitlement limits.
- Preview — available for evaluation, not approved as a production live-trading dependency.
- Beta — functional but still undergoing safety or compatibility validation.
- Internal — present in development code but not a supported public surface.
- Unavailable — not usable even if a name or placeholder is visible.
Which providers can I connect?
The reviewed build exposes supported workflows for KuCoin, Rithmic, and Hyperliquid market data. Binance is locked for clean setup and remains Unavailable / Coming Soon; legacy preconfigured state is not release-certified. Capabilities are not identical: a provider may supply charts without exposing a live order route. Check the matrix in Connections before entering credentials or selecting an account.
Is Playback a paper-trading account?
No. Playback is a replay-data clock, not an account type, and it does not automatically select LocalPaper. In the current release-candidate build, HyperionX rejects submissions, changes, and cancellations for selected Broker and Server Paper accounts while Playback is active. Select and verify LocalPaper explicitly rather than relying on that guard. See Accounts And Trading Environments.
How realistic is Hyperion Sim?
LocalPaper is a simplified full-fill simulator. It does not model queue position, order-book liquidity, partial fills, configurable slippage, buying-power rejection, margin calls, or liquidation. Use it to test workflow and logic, not to predict provider execution precisely.
Does Chart Trader ask for confirmation before submitting?
Not generally. Once its local checks pass, Chart Trader submits to the selected account. Confirm the account, instrument, size mode, quantity, order type, and bracket before pressing an action. A Broker account can affect real capital.
What is Code Lab?
Code Lab is the C# extension environment included with HyperionX. It builds custom indicators, strategies, add-ons, bar types, optimizers, fitness modules, money-management modules, and commission models into a shared custom assembly. Start with the Developer Center.
Where are custom extensions stored?
The default source root is:
%USERPROFILE%\Documents\HyperionX\Bin\Custom
Keep a separate backup of source files you cannot replace.
Why did a rebuilt indicator or strategy keep its old behavior?
An enabled instance can continue using the assembly it was created from. Disable affected running strategies before building. After a build, remove and add the extension again—or reload its owning host—to create an instance from the new assembly. Toggling the same existing instance off and on is not a reliable reload. See Build, Test, And Debug.
Can I paste NinjaScript or another platform's script into Code Lab?
Not directly. Port the script to HyperionX namespaces, lifecycle methods, series types, drawing calls, and managed order helpers. The NinjaScript Migration Guide maps common concepts and calls.
Why did an imported extension appear under Add-ons?
The import preview's source classifier recognizes direct low-level base types more reliably than the normal generated Indicator and Strategy aliases. Runtime discovery uses the compiled type, so a preview label does not necessarily determine where a successfully built extension loads. For predictable results, inspect the bundle and place source files in the documented folders. See Share And Deploy Extensions.
Why are Validator or Optimizer unavailable on a fresh installation?
The last reviewed clean 1.1.10 candidate installer did not provide every required default. The active candidate source now contains product-owned defaults and installer-manifest entries intended to fix that gap, but the exact clean, signed installer has not completed installation and workflow smoke validation. Treat Validator and Optimizer as unavailable on a fresh public installation until that validation passes. Do not download untrusted modules as a workaround. Follow Install, Update, And Uninstall, Backtesting, and Optimization.
Which AI providers are available?
The reviewed settings and runtime support HyperionX Cloud/Rion, OpenAI, Anthropic Claude, and a local Ollama endpoint. Other names are roadmap items unless AI Agent says otherwise. Never put provider keys, trading credentials, or wallet secrets in a prompt.
Is the local desktop API a public network API?
No. It is a loopback-only Preview surface intended for supported local integrations. It uses a generated bearer token, and the current public desktop does not expose a complete external token-onboarding flow. Do not bind or proxy it onto a network. See Local Desktop API.
What does a workspace save?
A workspace records the main window, chart windows, modular chart layouts, and supported tool windows. It does not snapshot provider sessions, live orders, positions, in-memory chart bars, Rion conversation history, or an executing strategy object. Read Save And Restore Workspaces before relying on restore behavior.
How do I update HyperionX?
The desktop update notice opens the release page in a browser; it does not install an update in place. Back up Documents\HyperionX, close HyperionX processes, download the signed installer from the official release location, and verify its Windows signature. See Install, Update, And Uninstall.
What should I send to support?
Include the version from Help > About, provider and environment, instrument, exact time with time zone, steps to reproduce, and the expected and observed result. Redact credentials, tokens, private keys, and sensitive account data. Support And Diagnostics lists the relevant logs and safe collection steps.