> For the complete documentation index, see [llms.txt](https://no-cto.gitbook.io/ratpaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://no-cto.gitbook.io/ratpaper/the-solution/2.-telegram-hypebot-vibes-on-autopilot.md).

#   2. Telegram HypeBot: Vibes on Autopilot

**The heart of our community beats in Telegram. But dead chats = dead tokens.**

**So we built a beast: the NO CTO HypeBot.**

**🧠 Fully automatic, plugged into chat flow:**

* **Reacts to custom keywords with fire memes**<br>
* **Injects energy when chat gets quiet**<br>
* **Admin-customizable for max chaos**<br>

**24/7 degenerate meme engine**\
\
\&#xNAN;***This isn’t just utility - it’s community survival tech.***\
***No devs disappearing. No vibe collapse. Just non-stop rat energy.***

***We’re not just building a bot. We’re building a vibe algorithm.***

<br>


---

# 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:

```
GET https://no-cto.gitbook.io/ratpaper/the-solution/2.-telegram-hypebot-vibes-on-autopilot.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.