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

# Position Management

## Managing Positions

![](https://2516265397-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJHPweZaUGqPeoTwjADbq%2Fuploads%2FVfKCYjLAtTKyy28R4maR%2Fnewpa.png?alt=media\&token=ef8232f0-ec72-49f3-9320-8db9f4b567b7)

Managing positions is at the heart of using Cod3x. Once your agent is funded and ready, you’ll use the **New Position** button to enter trades, the **position controls** to adjust them, and the **History & Summary** tabs to track performance.

This section covers:

* **Opening a New Position** → how to create a position, select markets, leverage, and collateral.
* **Editing & Sharing Positions** → how to manage active trades, adjust TP/SL, close partially, and share setups.
* **Position History & Summary** → how to review past trades, export results, and get a full breakdown of your PnL.

Each page goes step by step, with screenshots and examples.

***

### Next Step → *Opening a New Position*

This page will walk through the **New Position** button workflow (market vs. limit, leverage slider, collateral, confirmations).\
Once that’s in place, we’ll follow with the **three-dot edit/share menu** and then History/Summary.


---

# 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.cod3x.org/terminal-overview/position-management.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.