> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://documentation.celestory.io/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# 🟦 Clear feed

# 🟦 Clear feed

![Clear feed](https://celestory-docs-illustrations.netlify.app/en/Clearfeed_EN.svg)

The Clear feed block wipes the screen of messages that are already displayed, so the story can start fresh on a "clean" page. It is mainly useful in modules where messages pile up on screen as the conversation goes on (such as a Chatbot), when you want to let the user restart a discussion from scratch without leaving the module.

## 📥 Entries

- Depending on the context (Standard Graph vs. Narrative / Menu), this block generally acts universally on its immediate environment, without the need for complex parameters: it takes the current flow and purges the "chatbot" type display states or accumulated texts.

## 📤 Outings

- Stream: The standard output which allows you to continue processing the graph once the visual interface has been deleted or cleaned.

## 💡 Example of use

Scenario: Properly relaunch a Chatbot type application

1. You simulated a chat interface where the user entered 20 questions and the bot (Celestory) responded.
1. The screen is very full and the user wants a "New Topic".
1. A “New” button activates our Clear feed block.
1. Upon passing this connection, the entire visual history magically clears, leaving a pristine area.
1. At the exit of this block, a "Hello!" initiates a new, pristine textual context, for user convenience.

## ⚙️ Technical Details

- Contextual warning: It is especially fundamental for stackable interfaces based on the addition of history (Chatbot, Terminal, Visual Novels modules). In a classic web view or a purely logical backend tree with no user interface involved, this block could be ignored.
- Variable Statistics: Clearing the visual stream does not clear persistent value (like scores, name) stored in the engine. It affects the history display, it does not operate like "Reset Variables" would.

---

*Documented version: v1*