DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run persistent memory on an OpenClaw gateway with chat feeds with Claude Mem

Install the Claude Mem plugin on an OpenClaw gateway and optionally send observation feeds to chat apps.

Remote script. The installer is a script piped from the network into bash, so download and read it first if your gateway policy requires review.

Who it is forAn operator of an OpenClaw gateway who wants agent memory that persists and wants live observations sent to team chat.

The problemOpenClaw gateway agents lose context between sessions, and the team has no view of what the agent observed.

The outcomeThe gateway runs Claude Mem as a persistent memory plugin, and optional real-time observation feeds go to chat tools the installer supports.

What you need first

  • Node.js 20.0.0 or higher
  • Claude Code with plugin support, or a supported agent host such as OpenCode or T3 Code
  • A claude-mem sign-in or your own memory provider key, if you do not use the installer's local option
  • Bun and uv, which the README says are auto-installed if missing

Steps

  1. Confirm Node.js 20.0.0 or higher is installed on the gateway host
  2. Run curl -fsSL https://install.cmem.ai/openclaw.sh | bash
  3. Follow the installer prompts for AI provider configuration and optional feeds to Telegram, Discord, Slack, or others
  4. Check that the worker started and that a test session produces an observation

Prompt for your agent

On the OpenClaw gateway at <gateway host>, run the claude-mem OpenClaw installer from https://install.cmem.ai/openclaw.sh, then confirm the worker is running. Report the provider chosen and any chat feed configured. Verify that a test session creates an observation in memory.

Caveat. The README names Telegram, Discord, and Slack as feed targets and says more are supported, but it does not list the others, so check the OpenClaw integration guide before you rely on a specific one.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page