Settings

The Settings workspace controls application-level preferences and local connection configuration. These settings affect how AQS looks, how it starts new runs, which local services it can reach, and how account-related links behave.

Open Settings from the left sidebar, then choose a settings section from the settings navigation.

Appearance

Use Appearance to control workspace presentation.

• Theme switches between dark mode, light mode, or system sync.
• Language changes static workspace text between English and French.

Change the application language

1. Open Settings from the left sidebar.
2. Select Appearance.
3. Find Language.
4. Choose English or French.
5. AQS updates supported workspace text immediately.

What is not translated

The language setting applies to static AQS workspace text. It does not translate strategy names, project names, broker messages, exchange messages, runtime logs, or data returned by external services.

On first launch, AQS checks the operating system language. If the locale is supported, AQS uses it automatically. If it is not supported, AQS defaults to English.

Configurations

Use Configurations for application refresh intervals and development-only paths.

• Active price refresh controls how often AQS refreshes current prices for live insight rows.
• Live health check controls how often AQS checks whether live strategy data is still updating.
• Live stale timeout controls when a live strategy is marked stale.
• Development builds can also expose local website and AQE source path overrides.

Execution Defaults

Use Execution Defaults to set default behaviour for new strategy runs.

• Default runtime mode.
• Preferred local or remote server node.
• Log retention for editor run logs.
• Compile target and default log level.
• Safeguards such as prompting before live deploy.

Backtests always use paper execution, even if a live broker is selected. The selected datafeed can still be used to load market data for a backtest.

Fee configuration for a specific strategy lives in the Strategy Editor runtime/backtest configuration. Those per-strategy brokerFees values are what AQS passes to AQE’s PaperBroker for backtests. Use the editor when you need broker-specific commission, long/short fee differences, or swap assumptions for a particular historical run.

Live MT5 execution is different: swaps are read from MT5 symbol information, while commissions are recorded from executed MT5 deals. Paper broker fee settings do not override live MT5 deal commission.

Data Feeds

Use Data Feeds to configure market data and execution integrations.

• Add or edit local datafeed providers.
• Configure MT5 bridge details, including token and bridge bind address.
• Test datafeed connectivity.
• Select datafeeds later from charts, editor runtime config, or strategy detail market data settings.

AQS Cloud

Use AQS Cloud when signed in to manage cloud-linked strategy records, live session secrets, and membership status.

This section is only available for authenticated users. Local-only strategy runs do not require AQS Cloud.

Updates

Use Updates to manually check whether a newer AQ Studio desktop release is available.

• Current version shows the desktop version currently installed.
• Check for Updates asks the AQS website updater endpoint for the latest release metadata.
• When an update is available, AQS shows the target version, release notes, and an install action.
• Installing an update downloads the signed updater package, applies it, and restarts AQ Studio.

AQS also checks for updates automatically on startup. The manual settings screen uses the same updater endpoint as the startup update prompt.

Privacy Settings

Use Privacy Settings to review account identity, session state, and legal links.

Legal links open on the AQS website. When the application language is French, supported website links open under the French route where available.

Account restoration in the current desktop

The 0.2.0 development version renews eligible account sessions and can restore sign-in after restarting. Credentials are stored in an encrypted local vault protected by your operating system’s credential store. Your account password is not saved.

If the operating system asks for access to its credential store, allow it for the installed AQS application. If that store is locked or unavailable, unlock it and try again. Revoked or expired credentials require a fresh sign-in. Temporary connection failures can leave visible data in place while AQS retries; check its age before acting.

Signing in to AQS and authorising an AQE live session are separate operations. Account renewal does not extend a subscription entitlement or an expired strategy session.

Subscription payments and cancellation

Open Billing on the AQS website to choose monthly or yearly Pro billing, view invoices, update your payment method, or cancel your subscription. Payments are handled on the website through Stripe, not inside the desktop application.

A scheduled cancellation keeps Pro available until the paid period ends. You can reverse it in Stripe before that date. If a renewal fails, Pro access is suspended: resolve the existing invoice in Manage billing in Stripe rather than purchasing a second subscription. Once payment is confirmed, Pro is restored. After a subscription has ended, you can subscribe again from the billing page.

New purchases remain pending until payment is confirmed. An existing customer’s renewal may have a short processing window while Stripe finalises the invoice; a failed payment does not receive that window.

Expired live-session credentials are not reactivated by a payment. Issue new credentials in AQS when access is restored, and manage any running strategy deliberately. Cancelling a subscription does not close positions at your broker.

Live event gateway

In the current development version, AQS Cloud → Live event gateway lets you configure the delivery service used by desktop live views.

Use the trusted HTTPS address supplied for your deployment. Both AQS and a remote execution server need to reach it. Local HTTP addresses are intended for loopback development only.

Saving reconnects the desktop readers, but does not confirm a successful connection. Existing strategies keep their launch-time destination; restart or redeploy them in a controlled way to adopt a new address. Leaving the field empty uses the configured environment default, or direct database synchronisation when no default is set.