Memory Telegram Group with Topic (single user)
I have the following setup. A telegram group with topics where the only two member are me and openclaw. I will not give access to other member to the group. So Im treating this group as a DM betwenn be and the bot. This structure is pretty useul because I constantly swithching context when talking to clawbot (single agent). For example I have a topci #config that I use to discuss and adjust the config and settings for openclaw, a topic research where I we conduct research, a project topic when we work on various coding project.
So it's not unsual that I start a coding project but then I need to adjust the capability of openclaw (e.g. new settings, giving new skills) and the topic structure of telegram prevent the topic conversation to be off topic. Im not really a fan of the /new command.
---
However this setup is not really working correcly with the memory setup that claude provide. I think that im fighting a bit against it.
Ideally like something like a memory/<topic>/MEMORY.md and memory/<topic>/YYYY-MM-DD.md. So it's project has it own MEMORY.md and keep track of the progression through the days in the YYYY-MM-DD.md .
On top of that I like to retain the MEMORY.md (global) and memory/YYYY-MM-DD.md that is used when dm the bot. The memory/YYYY-MM-DD.md woud be the summary/grouping of memory/<topic>/YYYY-MM-DD.md while the globsl MEMORY.md is a distilled version of the sum of the various memory/<topic>/MEMORY.md.
Each topic session is allow to edit only the memory/<topic>/.md
Each topic session can read MEMORY.md , memory/YYYY-MM-DD.md and memory/<topic>/.md
The main agent session can edit the the MEMORY.md and memory/YYYY-MM-DD.md
Then main agent session can read from the MEMORY.md, memory/*.md
The questions is now how we can update the MEMORY.md and memory/YYYY-MM-DD.md when only using topics. Maybe we can use HEARTBEAT.md
---
what do you think? Is this doable? easy to implement?
So it's not unsual that I start a coding project but then I need to adjust the capability of openclaw (e.g. new settings, giving new skills) and the topic structure of telegram prevent the topic conversation to be off topic. Im not really a fan of the /new command.
---
However this setup is not really working correcly with the memory setup that claude provide. I think that im fighting a bit against it.
Ideally like something like a memory/<topic>/MEMORY.md and memory/<topic>/YYYY-MM-DD.md. So it's project has it own MEMORY.md and keep track of the progression through the days in the YYYY-MM-DD.md .
On top of that I like to retain the MEMORY.md (global) and memory/YYYY-MM-DD.md that is used when dm the bot. The memory/YYYY-MM-DD.md woud be the summary/grouping of memory/<topic>/YYYY-MM-DD.md while the globsl MEMORY.md is a distilled version of the sum of the various memory/<topic>/MEMORY.md.
Each topic session is allow to edit only the memory/<topic>/.md
Each topic session can read MEMORY.md , memory/YYYY-MM-DD.md and memory/<topic>/.md
The main agent session can edit the the MEMORY.md and memory/YYYY-MM-DD.md
Then main agent session can read from the MEMORY.md, memory/*.md
The questions is now how we can update the MEMORY.md and memory/YYYY-MM-DD.md when only using topics. Maybe we can use HEARTBEAT.md
---
what do you think? Is this doable? easy to implement?
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
130,529Members
Resources
Similar Threads
Was this page helpful?
