> 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/risk/kill-switch.md).
# Close, flatten and the kill switch
Close one position, flatten an account, or flatten everything. Exits are never blocked.
There are three ways out of a trade, from the smallest to the largest. Each one only reduces your position, so none of them can be blocked by a cap, a breaker or Breach Guard. Exits take one tap, while entries always need a confirm step.
{% hint style="warning" %}
Multi-account flatten and the kill switch are still being completed. After using either one, confirm on the venue that every position on every account is closed.
{% endhint %}
## Three exits
| Name | What it means |
| --------------- | ----------------------------------------------- |
| **Close** | Closes one position on one account. |
| **Flatten** | Closes every position on the selected accounts. |
| **Kill switch** | Flattens every position on every account. |
## Exits are never vetoed
Every exit is sent as reduce-only, so it can only shrink a position, never open a new one. Because it cannot add risk, no safety check stands in its way. The kill switch works even when an account is frozen for being out of sync.
## Use it from the Terminal
You reach every exit from the web Terminal. Using the kill switch from Telegram is coming soon.
## Every outcome is shown
Each exit reports what happened: executed, failed or expired, with a reason. Every step is written to the audit log.
## Next steps
---
# 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/risk/kill-switch.md?ask=&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.