# message-cache

> OpenClaw Telegram delivery insurance system. Solves "did my message get delivered?" by caching all agent outputs to external files with metadata, enabling manual resend capability.

- Author: Waking Love
- Repository: wakinglove/Thinking
- Version: 20260206131055
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-06
- Source: https://github.com/wakinglove/Thinking
- Web: https://mule.run/skillshub/@@wakinglove/Thinking~message-cache:20260206131055

---

# Message Cache System

**Status:** Ready for Production
**Version:** 1.0.0
**Author:** Waking Love (Neo Young)
**Created:** 2026-02-06

## Description

OpenClaw Telegram delivery insurance system. Solves "did my message get delivered?" by caching all agent outputs to external files with metadata, enabling manual resend capability.

## Features

- Automatic message caching with metadata (timestamp, token count)
- Resend any cached message on demand
- Auto-cleanup after 7 days
- GitHub backup ready (Daily-Chats repo)
- Works with ANY OpenClaw agent

## Installation

```bash
mkdir -p ~/.openclaw/message-cache
cp scripts/message-cache-enhanced.sh ~/.openclaw/message-cache.sh
chmod +x ~/.openclaw/message-cache.sh
```

## Usage

```bash
./message-cache.sh --save "Your message here" 150
./message-cache.sh --last 1
./message-cache.sh --list
./message-cache.sh --cleanup
```

## The Key Insight

Previous OpenClaw personalities thought: "I can't access my outputs"

Reality: Use the `read` tool on external files!

```bash
read ~/.openclaw/message-cache/YYYY-MM-dd.txt
```

The limitation was understanding, not capability. External files persist forever!