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

# Colored Candles

Instant directional bias from the candle color alone

The candle color is set by where price closes relative to the Sniper Bands.

### Green candles

Price closed above the bands. Bullish momentum. Look only for longs.

### Red candles

Price closed below the bands. Bearish momentum. Look only for shorts.

### How to use it

#### Bias filter

If the candles are green, don't short. If they're red, don't long. That single rule removes most counter-trend losses.

#### Confirmation

A color flip on its own is not an entry. Wait for the Sniper Cloud midline and Super Trend to agree, as described in the AlgoSniper Strategy page.

### Tips

Alternating green and red candles with no follow-through means the market is ranging. Sit out until one color holds for several closes.

***

***

<figure><img src="https://3541426626-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaJ7Vv6oQJL7Ywy4bmbsR%2Fuploads%2FHEr7vaxKCXoWmFe55YzJ%2FPEPEUSDT_2025-06-29_21-13-42.png?alt=media&amp;token=ea0d9c62-1a41-4856-987f-5ece12c721e9" alt=""><figcaption></figcaption></figure>


---

# 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.algosniper.com/colored-candles.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.
