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

# Strategies

Save sell rules such as take profit and stop loss, and attach them to tasks.

Click **Strategies** in the header. A strategy is a saved set of sell rules, each a **limit order** that Bloom creates after a buy ([Limit Orders](https://docs.bloombot.app/manager/manager-pages/tasks/limit-orders.md)). A strategy belongs to a task type and a chain:

* **Spot**: one per chain. No attaching needed: its rules apply to your trading panel buys and to your limit buys once they fill.
* **Copy Trade**, **AFK**, **Social**: as many as you like. Attach each to tasks of that type.

## Tabs and Toolbar

Click a strategy row to see its limit orders.

<div align="left"><figure><img src="https://373591576-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMnkwltEDWRRlh7lLk05b%2Fuploads%2FIaMESLGYczjmWkFcXnE2%2Fstrategies-spot-expanded-row.png?alt=media&amp;token=2c2df487-7309-42f6-bb40-c2e05c9fd394" alt="Strategies page, Spot tab, expanded strategy row"><figcaption></figcaption></figure></div>

| Control                                       | Description                                                              |
| --------------------------------------------- | ------------------------------------------------------------------------ |
| **Spot**, **Copy Trade**, **AFK**, **Social** | Show that type's strategies and set the type of the next one you create. |
| **Chain selector and chips**                  | Choose which chains' strategies the list shows.                          |

## Create a Strategy

Click **Create Strategy** on the open tab, and pick a chain if several are shown.

<div align="left"><figure><img src="https://373591576-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMnkwltEDWRRlh7lLk05b%2Fuploads%2Fo91sE6n077ryOyMdi16L%2Fstrategies-create-strategy-dialog.png?alt=media&amp;token=dd0bfb0c-71b7-4603-9e4e-416a793bf07e" alt="Create Strategy dialog"><figcaption></figcaption></figure></div>

| Field             | Description                                   |
| ----------------- | --------------------------------------------- |
| **Emoji button**  | Picks the strategy's emoji.                   |
| **Strategy Name** | Names the strategy, from 1 to 100 characters. |

## Create a Limit Order

Click **Create Limit Order** on a strategy row.

| Field                         | Description                                                                                  |
| ----------------------------- | -------------------------------------------------------------------------------------------- |
| **Target Type**               | Picks the rule. See [Rule Types](#rule-types).                                               |
| **Sell Amount**               | Percent of the token to sell, up to 100.                                                     |
| **Slippage**                  | The most the price may move against you, in percent.                                         |
| **Sell Protection**           | Turns Anti-MEV on or off for this sell.                                                      |
| **High Impact (Expert Only)** | Allows a higher price impact than usual. Solana only.                                        |
| **Tip**                       | Optional extra payment to get your trade into the next block. Solana, Ethereum and BSC only. |
| **Priority Fee**              | Extra you pay for faster processing.                                                         |

Click **Create limit order** to save it.

## Edit and Delete

Click the pencil icon on a strategy or limit order row to edit it, or the bin icon to delete it. Deleting cannot be undone.

## Rule Types

Every rule sells **Sell Amount** percent of the token you bought.

<div align="left"><figure><img src="https://373591576-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMnkwltEDWRRlh7lLk05b%2Fuploads%2FwncEIG7wa7e7YjZcfX07%2Fstrategies-target-type-flow.gif?alt=media&amp;token=aaa61961-c6fc-42fa-979a-f1b3dafc487d" alt="Create Limit Order dialog cycling through rule types" width="526"><figcaption></figcaption></figure></div>

| Rule                     | Value                                         | Description                                                                                                  |
| ------------------------ | --------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| **Dev Sell**             | **Any Amount** or **Whole Amount**            | Sells when the token's creator sells: **Any Amount** for any sale, **Whole Amount** for their whole holding. |
| **Time**                 | **Sell after**: a number and a unit           | Sells that long after the buy.                                                                               |
| **Trailing**             | **Trailing Value** in percent                 | A stop loss that sells when the price falls that percent from its peak.                                      |
| **Profit/Loss**          | **Sell at** in percent                        | Positive values set a take profit, negative values a stop loss.                                              |
| **Fixed Market Cap**     | **Sell at** in dollars, such as `250k`        | Sells when the market cap reaches that value.                                                                |
| **Market Cap Variation** | **Sell at** in dollars, which may be negative | Sells when the market cap moves that amount from your buy.                                                   |

On EVM chains, an order made from a rule leaves the **Limit Order** list 7 days after the buy. An order from a **Time** rule stays at least until its time.

## Attach a Strategy to Tasks

<div align="left"><figure><img src="https://373591576-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMnkwltEDWRRlh7lLk05b%2Fuploads%2FVssoAszYJdQbRtibtF0N%2Fstrategies-afk-create-sheet-strategies.png?alt=media&amp;token=d9479ff3-b6f0-4c3f-9620-c9f5a9de10a5" alt="Strategies section of the Create AFK Task sheet"><figcaption></figcaption></figure></div>

* **New task**: tick a strategy in the create sheet.
* **Existing tasks**: tick rows on **Tasks** and click **Apply strategy** in the mass actions bar.
* **Quick create**: the **Auto sell** step picks a strategy or makes one.
* **One task**: change its own rules in the **Edit** sheet and save with **Update Task**.

{% hint style="warning" %}
A task keeps the rules it copied, so apply a strategy again after you change it.
{% endhint %}


---

# 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.bloombot.app/manager/manager-pages/strategies.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.
