Save And Restore Workspaces

A workspace is a local snapshot of supported HyperionX windows and chart configuration. Use workspaces to move between trading or research layouts without rebuilding each chart by hand.

Workspace commands

Open the Workspaces menu in the main window:

Command	Result
Open	Replaces the current supported chart and tool windows with a saved workspace.
Save	Updates the active named workspace with the current state.
Save As	Creates a new workspace from the current state.
Manage	Lists saved workspaces and provides rename or delete actions.

The last non-default workspace is recorded and restored on the next launch.

What 1.1.10 saves

The current workspace format captures:

• Main-window position, size, maximized state, and lower-panel height.
• Standalone chart windows and modular multi-chart layouts.
• Each chart's connection identity, instrument, data-series settings, date/range settings, and custom bar selection.
• Indicator type, HyperionX parameters, plot appearance, and fixed pane scales.
• Supported manual drawings and drawing visibility, lock, and snap settings.
• Chart grid, price-line, bid/ask display, scale, and color settings.
• Chart Trader visibility, width, and selected account identity.
• Rion panel visibility and selected agent-profile ID.
• Whether Code Lab was open.
• Window placement for Validator, Optimizer, Trade Copier, Agent Builder, Research Lab, Rion Strategy Watchlist, Output, and Performance Database.
• Instrument context for MegaDOM and Level II.

For a modular chart workspace, HyperionX also stores the layout, active pane, linked-pane state, per-pane chart, and workspace Rion state.

What a workspace does not preserve

A restored window is not always a resumed task. In 1.1.10, a workspace does not preserve:

• Live orders, positions, connection sessions, or provider-side state.
• Running strategy instances or their in-memory fields.
• Validator or Optimizer jobs, progress, and unsaved result state.
• Trade Copier, Research Lab, or Agent Builder form contents merely because their window reopens.
• Standalone Time and Sales instrument context.
• Credentials, wallet approvals, or one-time session tokens as workspace fields.
• The exact in-memory object from a previous custom assembly.

Treat the workspace as layout and configuration, not as a trading-state checkpoint.

Verify restored trading context

A saved Chart Trader account is resolved again during restore. Before submitting an order, verify the connection, account type, instrument, size, and live/simulation environment. Playback does not change a restored account selection. The current release-candidate build rejects Broker and Server Paper order mutations while Playback is active, but the guard does not replace explicit LocalPaper selection.

Save a workspace

1. Arrange the main window, charts, and supported tools.
2. Finish or cancel work that should not be interrupted, including active research jobs.
3. Disable strategies that must not continue across a rebuild or restart.
4. Select Workspaces > Save As.
5. Enter a distinct name for the layout.
6. Change one visible item, select Save, and reopen the workspace to verify it.

Use separate names for materially different environments, for example Crypto-Sim, Futures-Research, and Live-Execution. A name is only a reminder; it does not enforce the account type.

Restore a workspace

1. Connect or auto-connect the providers needed by its charts.
2. Select Workspaces > Open and choose the workspace.
3. Allow historical chart loads and deferred indicator restoration to finish.
4. Check the Output log for skipped connections, instruments, scripts, or windows.
5. Verify every chart's provider, symbol, timeframe, and indicator output.
6. Verify account and environment again before using Chart Trader, MegaDOM, or a strategy.

HyperionX restores chart windows in stages. If a saved connection or instrument no longer resolves, the affected chart can be skipped instead of being silently pointed at a different provider.

Custom-script compatibility

Indicator state is restored by its type name and saved HyperionX parameters. Renaming or removing the class, changing a parameter type, or installing an incompatible extension version can prevent an exact restore.

After changing custom code:

1. Disable affected instances before the Code Lab build.
2. Build the complete custom project.
3. Remove and add the indicator or strategy again, or reload its owning host.
4. Save the workspace only after the new instance is visibly correct.

Storage and backup

Workspace files are readable JSON-like .workspace files under:

%USERPROFILE%\Documents\HyperionX\Workspaces

They are not encrypted. Indicator parameter values are stored with the chart, so never place API keys, wallet keys, passwords, or other secrets in a script parameter.

To back up layouts, close or save HyperionX and copy the Workspaces folder. A complete user-data backup must also include custom sources and any other product data described in Install, Update, And Uninstall.

Recovery checklist

If a workspace does not restore as expected:

1. Confirm the required connection still exists with the same identity.
2. Confirm the instrument is available from that connection.
3. Build Code Lab and resolve every compiler error.
4. Check whether a custom type or parameter was renamed.
5. Open the Output window and review [WORKSPACE] messages.
6. Recreate only the failed chart or tool, then save the workspace again.
7. If the file appears damaged, preserve a copy before deleting or replacing it.

For a support package, follow Support And Diagnostics.