Sessions

A session is a running trading desk. It owns the broker connections, the order book, the stops and the journal. Clients attach to it and can detach without stopping it.

Session modes

Mode	Needs an account	What it does
Mock	No	A simulated market and broker. Works at any hour; nothing leaves the session.
Data	Yes	Streams your broker’s data, with trading disabled.
Trade	Yes	Streams data and trades on the account: paper or live, as the account is set up.

Hosted sessions

Create a session in the app with New session. It runs in its own private environment, with its own storage, in a cloud about 2 ms from major brokerages, and only you can connect to it. Stopping a session keeps its records; restarting resumes it.

Because the session runs in the same cloud region as your broker, its data is fresh and its stops and trailing react in milliseconds, however far away you are. Your screen is a window onto it: closing your laptop doesn’t stop your protection.

If a node fails

Each session runs as exactly one copy. If the node running it fails, the session is rescheduled to a healthy node with its journal and settings intact. Recovery time depends on the failure, so there is no fixed guarantee. Your screens reconnect on their own and the engine reconciles its book with your broker. Resting stop orders stay at the broker the whole time, but engine-managed protection such as trailing is paused until the session is back.

Open it in the browser

Open trading terminal opens the web client: the full terminal interface in a browser tab. Keys and mouse work as in a native terminal; Ctrl and Cmd combinations stay with the browser.

Attach from the command line

The tradeshell client attaches a native terminal to a session.

1. Run tradeshell peer-id on your machine. It prints an identity for this device.
2. In the app, choose Connect with CLI on the session, paste the identity, and create the connection.
3. Run the command the app shows you.

The connection is a direct, encrypted peer-to-peer link to your session; when your network doesn’t allow one, a secure fallback route is used. It reconnects on its own and resumes from the last event it saw.

How connecting works

1. Your session starts in its own isolated container in TradeShell Cloud, in the same cloud region as your broker, and checks in with the TradeShell relay.
2. Your screen signs in through the TradeShell relay, a secure meeting point that checks your access before anything reaches your session.
3. TradeShell goes direct: your screen and your session reach out to each other at the same moment and meet at the edge of TradeShell Cloud. Once they meet, an end-to-end encrypted peer-to-peer link opens between them and the relay stays on standby.
4. If your connection drops, your session keeps running: it keeps streaming, keeps your stops in place and follows your rules.
5. When you’re back, your screen reconnects on its own, goes direct again, and picks up exactly where it left off, with your positions checked against your broker.
6. If a server fails, your session is restarted on a healthy one with all its data, checks in with the relay again, and your screen reconnects.

Several clients at once

Any number of clients can attach to one session. They all see the same desk, and settings changes reach all of them. A client on a slow link gets the newest quotes rather than a growing backlog, and never slows the others down.