Install, connect,
and start safely.

01 / BEFORE YOU START

Before you start

TrueFix Studio is a desktop app for market research, strategy testing, and reviewed trading actions. It does not hold your money and it does not replace your broker or exchange. Install the official Nightly build, then connect only the services you want to use.

02 / FIRST RUN

Your first 15 minutes

1. 1

   Open or create a workspace

   A workspace remembers your selected market and panel layout. If it cannot be restored, TrueFix opens a safe default layout.

2. 2

   Check the status at the top

   You can enter the app even if one service is unavailable. Before using that service, wait for it to become ready or read the displayed error.

3. 3

   Connect one test service

   Start with one market-data or test trading connection. Search for a product, check its price source, and prepare an order without sending it.

Words used in advanced sections

Provider means a broker, exchange, data service, or AI service. A ClientInstance is one saved connection to that service. Environment means whether that connection is a test or real-money connection. The app may use these exact names, so this guide keeps them where they help you find the matching setting.

03 / CONNECT A SERVICE

Connect a broker, exchange, or data service

In Connection management, choose Open full connection centre to open Provider Centre. Use the Add monitoring ClientInstance form to enter the instance ID, Provider slug, display name, market, product scope, and actual environment. Enter connection parameters in the on-screen Connection JSON field. Select Historical/Realtime, optionally select Connect after saving, then click Save monitoring ClientInstance. This form sets up market monitoring; it does not grant trading permission.

• Provider-owned schemas validate settings before the instance is rebuilt.
• Secrets are write-only. Returning to the page reveals presence, never the original value.
• Connected does not mean tradable. Capability, entitlement, account, exact instrument mapping, environment, and health must all qualify.
• Closed market, disconnected, unauthorized, invalid configuration, and rate-limited are distinct states.

What to check before and after saving

Create separate ClientInstances for Paper and Live at the same Provider, with unmistakable names such as broker-paper-us and broker-live-us. Avoid toggling one instance back and forth between environments.

04 / MARKET CONTEXT

Select instruments and market sources

Choose a canonical Instrument from global search. TrueFix resolves Historical, Realtime, and Trading routes independently.

Keep Provider, ClientInstance, quality, and timestamps visible. When an exact mapping is absent, the route is rejected; a similar-looking symbol is never treated as the same instrument.

06 / PORTFOLIO

Accounts, positions, orders, and fills

Portfolio reads the authoritative trading projection and filters by Provider, ClientInstance, account, and environment. Application-owned orders remain separate from external or unknown orders. A normal page refresh reads the local projection; an authoritative refresh requests Provider reconciliation.

• Currencies are not added together without a consistent FX revision.
• Partial or stale valuation remains marked and is never presented as complete equity.
• After a Provider disconnect or environment switch, the old account domain no longer participates in current actions.

08 / AGENT

Configure and use Agent

Agent is a constrained operating assistant—not an autonomous trader with account authority. It reads instruments, markets, news, Signals, accounts, and Quant state through authorized TrueFix tools. Trading requests can only produce reviewable proposals. Tool availability may differ between test builds; the run timeline is the source of truth.

A. Configure a model first

Enter the API Key and model ID in the Desktop Settings → AI form and save. JSON model request parameters belong in the on-screen input field; the app saves them.

1. 1

   Open Settings → AI

   Select Add under “AI trading agents.”

2. 2

   Enter the connection

   Set a display name, Provider (OpenAI / Anthropic / Google / Custom), API Key, and model ID. Enter Base URL only for a compatible custom gateway.

3. 3

   Check extra parameters

   Model request parameters must be a JSON object, such as {"enable_thinking": false}. Keep {} when unused; never place a secret there.

4. 4

   Enable and save

   When editing an existing Agent, leave API Key blank to retain the stored key. Confirm the enabled status after saving.

B. Complete one safe session

1. 1

   Open Agent

   Use the bottom command bar in Desktop, Web Desktop, or H5. Create a session and select an enabled model.

2. 2

   State the scope

   Name the instrument, venue, time range, preferred source, and goal. For account work, state the Environment; begin with Simulator or Testnet.

3. 3

   Read the run timeline

   Check admission, model, tool, approval, and final states. Verify Provider, ClientInstance, timestamps, freshness, and evidence on tool results.

4. 4

   Review—do not rubber-stamp

   Separate facts, inference, and correlation. If data is stale, degraded, denied, or incomplete, narrow the request or repair the source first.

5. 5

   Handle a trade proposal

   Inspect instrument, side, size, account, environment, expiry, and evidence on the Approval Card. Approval still leads through Review, RiskGuard, and explicit submission; rejection or expiry places no order.

10 / WEB GATEWAY & ACME

Configure browser access and HTTPS

Open Desktop Settings → Web Gateway and use the on-screen form. Fill in the listening, domain, and HTTPS fields needed for the local or remote access method below; enable the Gateway and click Save and apply. The app saves and applies the settings without stopping the Desktop kernel or Provider connections. Configure DNS records and firewall rules in your DNS provider or network management interface.

A. Local access: the fastest smoke test

1. 1

   Settings → Web Gateway

   Click Generate random password on this page and copy it immediately, or enter at least 12 characters in the custom access password field and click Change access password. Either action revokes existing Web/H5 sessions. Save and apply saves Gateway settings without changing the password.

2. 2

   Bind only to loopback

   Choose Local HTTP under HTTPS certificate, set Listen address to 127.0.0.1 or ::1, enter the service port, enable the Gateway, and click Save and apply. Then open the access URL shown on the page.

3. 3

   Open the displayed URL

   Enter the password. Choose “Keep me signed in” only when device persistence is wanted; it extends identity lifetime, never trading authority.

B. Remote access: prepare a domain

1. 1

   Point DNS

   Point the A/AAAA records for studio.example.com to the Gateway's public address. Remove an incorrect AAAA record if IPv6 cannot reach the service.

2. 2

   Set the public address

   Allowed domains contains DNS names only—no scheme, port, or path. Public access URL is the complete final https:// URL. Wildcard hosts are not accepted by the allowlist.

3. 3

   Choose TLS

   For an existing certificate, choose Own certificate under HTTPS certificate and fill in the certificate PEM path and private key PEM path fields. For automatic certificates, choose Let’s Encrypt, enter an ACME email, and select HTTP-01, TLS-ALPN-01, or DNS-01 in the ACME validation method field. Enter the Cloudflare Zone ID and API Token for DNS-01 in this same form.

C. Recommended ACME rollout

1. 1

   Open Settings → Web Gateway and choose Let’s Encrypt under HTTPS certificate.

2. 2

   Enter studio.example.com in Allowed domains and https://studio.example.com in Public access URL.

3. 3

   Enter https://acme-staging-v02.api.letsencrypt.org/directory in ACME Directory, then fill in the ACME email, validation method, and its required fields.

4. 4

   Enable the Gateway, click Save and apply, and check the runtime and certificate status on the page. Staging certificates are for testing and are intentionally untrusted by browsers.

5. 5

   After testing, change the same ACME Directory field to https://acme-v02.api.letsencrypt.org/directory and click Save and apply again. Check the issuer, domain names, and expiry.

A staging certificate is deliberately untrusted; use it only to rehearse issuance and renewal. HTTP-01 must preserve the public /.well-known/acme-challenge/* path. For DNS-01, create a least-privilege DNS:Edit Token for the target Zone—never use a Global API Key.

D. Sessions, devices, and workspaces

• Access Tokens are short lived. “Keep me signed in” uses a rotating HttpOnly Refresh Cookie; it never enters JavaScript, URLs, or access logs.
• Review and revoke individual Web devices from Desktop settings. Sign-out, sign-out-all, password rotation, or disabling the Gateway revokes the relevant sessions.
• A browser session accesses only its selected workspace. Use ?workspace=<id> when needed; the default is main-workspace.
• If the access password may be exposed, generate a new one. Existing Web sessions are revoked without stopping healthy market, trading, or Provider processes.

11 / OPERATIONS & AUDIT

Operations, logs, and audit

Operations answers what happened, when, who initiated it, and what scope was affected. Logs, Audit, Activity, Health, and Incidents have different meanings: logs may rotate, trading/security audit is durable, and “no new log lines” never proves health.

Before filing an issue

1. 1

   Record time and environment

   Include display timezone, Environment, Provider, and ClientInstance. Keep only a redacted account suffix.

2. 2

   Capture stable evidence

   Keep error code, correlation ID, order/client order ID, revision, and freshness. Exclude API keys, cookies, and full account numbers.

3. 3

   Describe expected vs actual

   List reproducible steps and state whether Live, an external order, or financial consequence was involved.

12 / STATUS GLOSSARY

Read state without turning unknown into zero

Read every state with its source, as-of, revision, and stable code. One stale facet does not make the whole application unavailable, and a green connection dot does not prove account, instrument, and execution-route eligibility.

13 / ARCHITECTURE

Architecture and data boundaries

The browser is not the authority for instruments, accounts, orders, market data, risk, or AI/Quant. Every entry point shares canonical contracts and retains original adapter provenance. The UI does not manufacture missing data, silently mix Providers, or hard-code capability by Provider name.

14 / TROUBLESHOOTING

Common questions