Using ntfy for OpenClaw agent notifications
A Reddit user describes using ntfy (specifically the self-hosted version of ntfy.sh) as a push notification system for OpenClaw agents instead of Discord or Telegram bots.
Setup details
The user runs their OpenClaw gateway headless on a Lightnode VPS and needed reliable notifications when long scripts finish or if the agent crashes. They set up ntfy serve on the same VPS and pointed their domain to it using Caddy.
How it works
ntfy uses a basic HTTP pub-sub model. Instead of setting up bot channels, background agents make HTTP POST requests to ntfy, which then pushes notifications to devices. The user reports using it successfully with spare phones and smart devices.
Benefits mentioned
- Easier to set up on devices without Discord/Telegram
- Completely free and self-hosted
- Cleaner than cluttering a Discord server with automated logs
- Agents can potentially set it up themselves with one sentence (given permissions)
The user specifically mentions they're using "ntfy serve" (the self-hosted version) and found it performed well enough to share their positive experience.
📖 Read the full source: r/openclaw
👀 See Also
A Two-Step AI Workflow for Legacy Code Modernization
A Reddit post outlines a two-step 'reverse engineering' approach for using AI with legacy code: first extract business logic into a technology-agnostic Business Requirement Document, then use a 'Master Architect' prompt to rebuild from scratch with modern best practices.
llama.cpp Massive Prompt Reprocessing with Coding Agents: Debugging KV Cache and Context Swapping
A user reports llama.cpp reprocessing 40k+ tokens on similar prompts when using opencode + pi.dev, despite high LCP similarity. Config details and suspected causes are shared.
Practical Claude Code Workflow Tips for Complex Development Projects
A Claude Pro user shares specific workflow strategies for developing complex audio plugins, including using planning mode for major features, creating context files, managing token usage, and implementing validation steps.
Preventing output drift in long Claude threads by anchoring high-quality responses
A user describes how Claude responses degrade after 30-40 messages, and how they anchor the best mid-thread output to start fresh conversations.