> For the complete documentation index, see [llms.txt](https://docs.tradesurge.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tradesurge.co/platform/terminal.md).

# Terminal

The Terminal is where you trade by hand. One order goes to every account you select, sized in R for each one.

The Terminal is where you trade by hand. You pick the accounts, enter one trade, and TradeSurge sends a correctly sized copy to each of them. This is the core of scaling one strategy across many funded accounts.

{% hint style="info" %}
**Early access.** Trading from the Terminal will open on Bybit demo accounts first, for invited traders.
{% endhint %}

## What you see

* **Chart, order book and ticker** from Bybit's public market data.
* **Account selector** for the accounts this order should go to.
* **Order ticket** where you set direction, entry, stop and target.
* **Breach panel** that shows how close each selected account is to its firm limits.
* **Positions** with close, flatten and kill switch controls.

## Every order is sized in R

You never type a quantity. You set the stop, and each account's risk dial decides how much that account risks on the trade. A 0.5% account and a 1% account take the same trade at different sizes, and both lose exactly 1R if the stop is hit.

## Nothing fires from one tap

Every entry opens a confirm card first. The card lists each account, its size and any warning. The order is sent only when you confirm.

## Every order carries a stop on the exchange

The stop rests on the exchange, not inside TradeSurge. If TradeSurge goes offline mid-trade, your protection stays in place.

## Every outcome is reported

Each account's leg comes back as executed, failed or expired, with a plain reason. One account failing never hides the others.

## Next steps

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Place an R-sized trade</strong></td><td>Your first order, step by step.</td><td><a href="/platform/terminal/place-a-trade.md">Place an R-sized trade</a></td></tr><tr><td><strong>Copy a trade across accounts</strong></td><td>How one order becomes many.</td><td><a href="/platform/terminal/copy-across-accounts.md">Copy a trade across accounts</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tradesurge.co/platform/terminal.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.