messaging-daemon

Runs a multi-tenant WebSocket and HTTP server for real-time chat apps.

75|5|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/vbuterin/messaging-daemon --skill messaging-daemon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: messaging-daemon
Source: https://github.com/vbuterin/messaging-daemon/tree/main
Command: npx skills add https://github.com/vbuterin/messaging-daemon --skill messaging-daemon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill unifies local messaging by aggregating Signal, email, and Telegram messages into a single, queryable store and HTTP API, enabling safe access for AI agents and local software to read messages and request sends with explicit user confirmation.

Core Features & Use Cases

  • Unified HTTP API on port 6000 to read messages across backends, filter by backend/account, and perform cross-backend queries.
  • Confirmation UI on port 7000 to review and approve outbound messages, ensuring user control over sending messages to others.
  • Central SQLite database storage of all messages with per-backend accounting, enabling persistent access and easy auditing.
  • Setup-driven account management for Signal, Email, and Telegram backends, with per-backend polling and lifecycle management.

Quick Start

Install and configure accounts for Signal, Email, and Telegram, then run the daemon to start polling and serving the API.

Frequently Asked Questions about messaging-daemon

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I unify Signal, Telegram, and email messages into a single local API?

You can unify Signal, Telegram, and email messages by running a local daemon that polls each backend, stores messages in a central SQLite database, and exposes a unified HTTP API on port 6000 for cross-backend querying.

How do I add a human confirmation step for AI agents sending messages?

To add a human confirmation step for outbound messages, use the local confirmation UI exposed on port 7000, which allows users to review and approve message sends requested via the HTTP API.

Can I filter and query messages across multiple messaging backends locally?

Yes, you can filter and query messages across multiple backends by sending requests to the local HTTP API, which retrieves unified message data stored in the SQLite database.

Does this messaging daemon require separate account setup for Signal and Telegram?

Yes, the messaging daemon requires a setup-driven account management process for each backend, including Signal, Telegram, and email, to enable per-backend polling and message retrieval.

What's the best way to persist local messaging history for AI agent access?

The best way to persist local messaging history is using the daemon's central SQLite database, which aggregates all messages from configured backends for persistent access and easy auditing.

Why are there separate ports for reading and confirming messages in the unified API?

There are separate ports to isolate functionality: port 6000 serves the read-only HTTP API for querying messages, while port 7000 provides the human confirmation UI to safely guard outbound message sends.