> For the complete documentation index, see [llms.txt](https://docs.styleai.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.styleai.io/product-docs/product-docs-en/readme-1/26.03.25-automatic-purple-removal-in-editing.md).
# 26.03.25: Automatic Purple Removal in Editing
#### ✅ Key Improvements
* Automatic removal system: The "remove purple area" command is automatically applied to all brush operations.
* High success rate: It is generated cleanly without purple afterimages with a probability of about 88% (7 out of 8 images).
#### 💡 Why was there purple left behind?
The brush is a tool like a "sticky note" that marks the area to be edited. Sometimes the AI mistakenly treated this mark not as a guide to erase, but as part of the original image's "design," leaving it behind.
#### ✨ Tips for better results
Because of the nature of AI, purple may remain very occasionally (about 12.5%). If that happens, try this!
* Paint more broadly: If you brush slightly wider than the area to be edited, it will be removed much more effectively.
* Generate again: If you generate once more, the AI is more likely to cleanly remove the purple.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.styleai.io/product-docs/product-docs-en/readme-1/26.03.25-automatic-purple-removal-in-editing.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.