> For the complete documentation index, see [llms.txt](https://docs.degenarena.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.degenarena.app/modifying-and-closing-positions.md).
# Modifying and Closing Positions
Once you've opened a position, you can view it at any time by messaging the bot `/positions`.
There, you can click on a specific trading pair, and modify your position.
You will see your current unrealized PNL, along with options to increase position size, close position (either partially or in whole), increase margin, or create new orders such as take profit or stop loss orders.
Let's increase our position size. Click `Increase Position`.
Now, choose leverage. Let's stick with 25x, because why not.
Enter the margin you wish to use to increase your position size, in this case another 25 USDT.
Double check your trade details, and click `Confirm`.
The add-on position has been opened. Now let's say I want to close. Type `/positions`, and click on the desired pair. Then click `Close Position`.
In this case, I'll choose to close 100% of my position.
I'll click `Confirm`, and see a transaction success, with a sharing card including my realized PNL sent to me and my clan.
---
# 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.degenarena.app/modifying-and-closing-positions.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.
