AI Agent

The HyperionX chart AI is an assistant for the active chart. Use it to explain price and indicator state, inspect strategy context, troubleshoot the desktop, and prepare Code Lab work.

Feature status

Chart chat and its read-only context are Current. Structured desktop actions are Preview and simulation-first. Live Hyperliquid and KuCoin actions are available only in a release-enabled build that reports the matching provider capability and passes its local gates. The managed Rion cloud desktop bridge is Internal and is not a third-party integration API.

Rion Autopilot and Strategy Discovery are separate Preview workflows. Strategy Discovery is not ready for unrestricted public-release use because its default ML path can upload the full research CSV and metadata without a dedicated consent prompt. See Rion Autopilot And Strategy Discovery.

Choose A Provider

Open the AI settings and select the provider, model, and endpoint that should process the conversation.

Provider	Status	Current default	Configuration
HyperionX Cloud	Current and default	Rion	Uses the HyperionX license and cloud session; no customer model API key is required.
OpenAI	Current	gpt-4o-mini	Requires an OpenAI API key.
Claude / Anthropic	Current	claude-sonnet-4-6	Requires an Anthropic API key.
Ollama	Current	llama3.2	Uses http://localhost:11434 by default and does not require an API key. Tool support depends on the selected local model.
Azure OpenAI	Roadmap	—	Not enabled in the current provider registry.
Azure AI Foundry	Roadmap	—	Not enabled.
Foundry Local	Roadmap	—	Not enabled.
GitHub Copilot	Roadmap	—	Not enabled.
Copilot Studio	Roadmap	—	Not enabled.
Agent-to-Agent (A2A)	Roadmap	—	Not enabled.
Custom OpenAI-compatible	Roadmap	—	Not enabled.

Provider availability can also depend on the installed build, license entitlements, credentials, and model access. The chat header should identify the provider/model actually selected; verify it before sending sensitive market or strategy context.

Ollama is local only while its endpoint resolves to the local machine. If you configure a remote Ollama endpoint, prompts and context leave the desktop.

Understand The Active-Chart Context

The assistant can build a snapshot containing:

• symbol and timeframe
• total, recent, and visible candles
• loaded indicator names, plots, signals, and selected parameters
• loaded strategy names, state, account label, positions, and selected parameters
• Chart Trader visibility and connection state
• displayed order type, size, prices, leverage, position, entry, and PnL text
• Validator, Optimizer, or Research Lab state when requested and allowed
• local chart-memory summaries

The snapshot follows the active chart. It does not currently target an arbitrary chart by public chart ID.

Keep Secrets Out Of AI Context

The current parameter filter omits names containing key, secret, password, or token. This is a defensive filter, not a guarantee that arbitrary custom text is safe.

Never place these values in a prompt, script parameter, profile instruction, prompt file, or feedback note:

• API or broker credentials
• passwords or bearer tokens
• wallet private keys
• seed or mnemonic phrases
• private customer or account information that the selected model provider should not process

HyperionX does not intentionally read broker credential fields into chart context. User-created parameter names and values can still contain sensitive information. See AI Data and Privacy for provider destinations, local paths, and retention.

Ask Read-Only Questions First

Useful requests include:

Explain what changed over the visible chart range and cite the candle or indicator evidence.

List the loaded indicators and explain what each contributes.

Explain the selected strategy state without placing or modifying an order.

Review this Code Lab compiler diagnostic and suggest a HyperionX-native correction.

Treat model output as a draft. It can misread context, invent APIs, or produce unsafe trading logic.

Use AI With Code Lab

The assistant can draft or explain source in conversation and can invoke the Preview Code Lab actions to open Code Lab, list custom scripts, compile the custom project, and report compile state.

The Local Desktop API does not currently create or edit a source file and does not validate one arbitrary file. Copy or review drafted code in Code Lab, then compile it against the installed HyperionX version.

That Local Desktop API boundary does not describe the separate Rion Autopilot and Strategy Discovery workflow. When explicitly invoked, that Preview workflow can write Rion-owned Code Lab scripts, compile them, run Validator or Optimizer stages, and use cloud ML by default. Review its trigger phrases, generated artifacts, opt-outs, and consent limitation before using it. Use local only or no ml whenever research data must stay on the workstation.

For generated code:

• use the documented HyperionX.Custom namespace and base for the extension type
• use OnStateChanged() and OnBarUpdate() where required
• expose settings with [HyperionXProperty]
• guard early bars and every added series
• prefer managed strategy-order helpers for normal order flow
• review direct SubmitOrder(...) use for cancellation, OCO, partial fills, and state transitions
• test in historical validation, playback, and Hyperion Sim before considering a live workflow

Start with the Developer Center for supported extension contracts.

Trading Actions

The permissioned Rion action path in the 1.1.10 baseline can place, cancel, modify, close, or flatten orders only for Hyperion Sim when all required settings and entitlements are present.

Newer release-enabled builds can expose guarded Hyperliquid and KuCoin live actions. A caller-provided confirmed or executeTrading field records the caller's approval decision; it does not create an independent desktop confirmation prompt for a direct HTTP request. The client must also pass the provider-specific capability, setting, entitlement, active account/instrument, connection, and exchange-permission checks.

Use this progression:

1. Inspect read-only context.
2. Draft and review code or an order idea.
3. Compile and validate scripts.
4. Run in historical testing or playback.
5. Use Hyperion Sim with an explicit account and user decision.
6. Check the returned action status and authoritative account state.
7. Consider live Hyperliquid or KuCoin only in a release-enabled build and follow the Local Agent Live Trading API checklist.

See Local Desktop API for the Preview route and permission boundary.

Use A Specialized Profile

Agent Builder creates specialized profiles with selected context and tools. Some profile toggles are enforced for non-baseline specialized agents; many displayed trading-risk fields are currently advisory metadata. Agent Builder profiles also do not scope the global Local Desktop API token.

Review Agent Builder API before treating a profile setting as a security boundary.

Clear Conversation History

Use Clear Chat to remove the saved conversation from the local protected chat-history file. Chart memory is stored separately in the application database and currently has no dedicated purge control in the AI UI.