> For the complete documentation index, see [llms.txt](https://docs.frontrun.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frontrun.pro/trading/chart-lines.md).

# Chart Lines

Chart lines appear automatically when you create a limit order or set an auto-trade strategy (TP/SL) on a token.

<figure><img src="https://1220676459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnXSjLa4Ay52MfDqqSORe%2Fuploads%2Fl24ETVN6InV3eHV0r4xe%2FCleanShot%202026-03-16%20at%2016.51.49.gif?alt=media&amp;token=28ca65be-5182-4320-bc0f-38db028f610e" alt=""><figcaption></figcaption></figure>

* Lines are color-coded by type — limit buy, limit sell, TP, and SL each have distinct colors, with virtual and real levels differentiated
* Click any line to select, drag to adjust the target price, or delete — changes update the underlying order directly
* Toggle on/off in **Settings → Trading → Show Chart Order Lines** (enabled by default)

<div data-with-frame="true"><figure><img src="https://1220676459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnXSjLa4Ay52MfDqqSORe%2Fuploads%2F2eU00eFR0nRYNznE2MUl%2Fpublic%20(1).jpg?alt=media&amp;token=e109ebfc-6e9c-495f-a037-e11eb66e6a4e" alt=""><figcaption><p>Example chart showing active limit orders and TP/SL levels with the edit toolbar visible.</p></figcaption></figure></div>


---

# 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.frontrun.pro/trading/chart-lines.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.
