# Telegram HQ: Turn One Chat Into an AI Command Center (OpenClaw)

*Exponential Logs, Documenting what we are building with OpenClaw*

By [🚀 Exponential TOM 🚀](https://paragraph.com/@exponentialtom) · 2026-02-09

openclaw, clawdbot

---

[![](https://paragraph.com/editor/youtube/play.png)](https://www.youtube.com/watch?v=tNELYRQwSlc)

What we built
-------------

We turned Telegram into a structured command center for an AI agent (Atlas running on OpenClaw). Instead of one endless chat feed, we created a single Telegram group (Atlas HQ) and enabled Topics (Forum mode) so each workflow has its own dedicated thread.

This gives us:

*   A clean separation between workflows (journals, content, ops)
    
*   A faster feedback loop with the agent
    
*   A scalable structure where new workflows can be added without chaos
    
*   A predictable routing surface for automations (post into the right topic every time)
    
    ![](https://storage.googleapis.com/papyrus_images/8dac7b98610f4afd4b3a70aa634a5c012793190d7eb5dc2edd7a21714d536fc7.png)
    

Why Topics matter (the core insight)
------------------------------------

Most chat apps are a single infinite feed. That is fine for human conversation, but it breaks down when:

*   you are running multiple parallel workflows
    
*   you want to retrieve information later
    
*   your agent is producing outputs (reports, briefs, drafts) every day
    

Topics turn Telegram into something closer to

a lightweight operations console.

The workflow map (example)
--------------------------

*   Morning Journal -> chaotic brain-dump -> Atlas extracts priorities + tasks
    
*   Content Workflow -> transcripts in -> articles / threads / clips out
    
*   Open Loops -> nightly scan of Notion -> list of unfinished items for the next day
    
*   Morning Brief -> daily web research -> use cases + how they apply to our projects
    

Step-by-step (how to replicate)
-------------------------------

1.  Create a dedicated Telegram group (separate from your personal DMs)
    
    ![](https://storage.googleapis.com/papyrus_images/06a2de02cf3495ad2d97113691fd8f4468b7330aa9dccb454e66646a5fc7060e.png)
    
2.  Enable Topics / Forum mode in group settings
    
    ![](https://storage.googleapis.com/papyrus_images/323b8a125486a3e878e64c6a32b7761cc7b85b3fafd70a9082114277e9dc99e3.png)
    
3.  Create topic threads for each workflow area
    
    ![](https://storage.googleapis.com/papyrus_images/11e6413a42a4bfc5c7b82bd612a84f8ae87c0c0d553702b4e30164703fcfbfa9.png)
    
4.  Add your agent/bot/account and grant permissions (post + read)
    
    ![](https://storage.googleapis.com/papyrus_images/5c59e69a2e8ec4d908b5c0be262037554b55bd6070f441298240f338b8fd3948.png)
    
5.  Connect OpenClaw/Clawdbot to Telegram (bot token + target chat id)
    
    ![](https://storage.googleapis.com/papyrus_images/7dfe47c32069f7b922111e060e32de77d43a6e7f05df131b253ea588b6da0396.png)
    
6.  (Optional) Capture topic/thread IDs and map each automation to the right topic
    
    ![](https://storage.googleapis.com/papyrus_images/2cfce4d7eff698de76371fff5e7dc416be747f859c9fd80c2c1420729c122bc1.png)
    
7.  Test end-to-end: Telegram -> Atlas receives; Atlas -> posts back into the correct topic
    

![](https://storage.googleapis.com/papyrus_images/5d05745851ce1816ff96c0fb94bb821f30b205809ad8d8d51a129ce1db846d02.png)

---

*Originally published on [🚀 Exponential TOM 🚀](https://paragraph.com/@exponentialtom/telegram-hq)*