AI Agent

The HyperionX chart AI is a desktop assistant attached to the active chart. Its purpose is to help users understand chart state, explain indicators, review strategy context, diagnose platform behavior, and assist with Code Lab workflows.

The AI assistant is not designed as an uncontrolled trading bot. The current architecture is read-only by default.

What The Chart AI Can See

The chart AI can receive a safe local snapshot of the active chart.

The snapshot can include:

• Symbol.
• Timeframe.
• Total candle count.
• Recent candles.
• Visible candles.
• Loaded indicator names and safe parameters.
• Loaded strategy names and safe parameters.
• Chart Trader state.
• Account label.
• Order type.
• Order size display.
• Last price, bid, and ask.
• Leverage.
• Position text.
• Entry text.
• PnL text.

What The Chart AI Cannot See By Default

The chart AI should not receive:

• API keys.
• Broker secrets.
• Wallet private keys.
• Passwords.
• Raw filesystem access.
• Hidden platform internals.
• Direct order submission tools.
• Direct wallet signing tools.

Secret-like parameter names should be filtered before any context is sent to a model.

Providers

Current or planned provider surfaces include:

Provider	Purpose
OpenAI	Cloud LLM provider.
Claude / Anthropic	Cloud LLM provider.
Ollama	Local model provider.
Azure OpenAI	Planned enterprise/provider option.
Microsoft Foundry	Planned provider option.
GitHub Copilot	Planned developer assistant surface.
Custom OpenAI-compatible endpoints	Planned advanced configuration.

Provider availability depends on installed packages, credentials, model access, and application settings.

Model Display

The AI chat UI should display the model that is actually connected. If the configured provider is gpt-4o-mini, the chat should not display a different model name such as Sonnet 4.6.

The displayed model should come from the active provider settings, not from a hard-coded UI label.

Useful Prompts

Examples:

Explain what changed on this chart over the visible range.

Review the loaded indicators and tell me what each one is contributing.

Why did this strategy enter here based on its visible parameters?

Help me write a HyperionX indicator that plots volume percentile caps.

Review this Code Lab compile error and tell me what API I used incorrectly.

Code Lab Assistance

The AI can help with Code Lab, but every generated script must be compiled and reviewed.

AI should follow these rules:

• Use HyperionX namespaces.
• Use HyperionX base classes.
• Use OnStateChanged() and OnBarUpdate().
• Use [HyperionXProperty].
• Use Series<double> and AddSeries(...).
• Use HyperionX Draw APIs.
• Use SubmitOrder(...) for strategies.
• Avoid other-platform APIs unless HyperionX implements them.

Chart Assistant UI

Expected chart assistant behavior:

• The AI avatar remains available on the chart.
• Clicking the avatar opens the chat.
• Closing the chat does not remove the avatar.
• The avatar stays anchored to the active chart area.
• The avatar resizes appropriately in multi-chart layouts.
• The chat panel should avoid covering Chart Trader where possible.
• The chat input should resize when the chat panel is resized.
• Theme colors should match the platform.

Agent Roadmap

The chart AI is the first step. The larger direction is user-created agents.

Future agents can specialize in:

• Code Lab development.
• Backtest review.
• Strategy validation.
• Chart explanation.
• Risk monitoring.
• Trade journaling.
• Multi-account monitoring.
• Support and onboarding.

See Agent Builder for the planned creation system.

Safe Trade Automation Path

The safe path for AI trade automation is staged:

1. Read-only chart context.
2. Code Lab script drafting.
3. Code Lab compile diagnostics.
4. Simulation-only strategy review.
5. Draft order suggestions.
6. Confirmed chart trader actions.
7. Live actions only with explicit permissions, confirmations, risk limits, and audit logs.

Do not skip directly from chart chat to live order submission.