Bots

A bot is a group member: it reads the messages of the groups it was added to and nothing else. The server still cannot read your messages.

A VeilMesh bot is a program you run on your own machine or server, veilmesh-bot. It has its own account and its own keys, and it takes part in a group the same way a person does: it decrypts and encrypts on its own machine. Use it for alerts, CI results, monitoring, tickets, or an assistant that answers questions in a group.

How it fits together

  • The daemon, veilmesh-bot, holds the bot's keys in an encrypted vault and is the group member. It runs in Docker (Linux, x86-64 and ARM64).
  • Your code talks to the daemon over a local HTTP API on the same machine, with the bot's token. Client libraries for Python, JavaScript and Rust wrap it; any language that speaks HTTP works.
  • Webhooks post into a group from anything that can send an HTTP request, such as Alertmanager or a CI job.
  • AI agents can read and answer a group through the MCP bridge, limited to the groups you allow.

The rules

  • Bots work in group chats only: no one-to-one chats, calls or channels.
  • A bot sees only the messages sent after it joined a group.
  • Every bot belongs to a person, its owner, who signs its certificate. Members see the bot under its name with “bot · owner <name>”, and the AI providers it sends messages to, if any.
  • Only a group's creator adds a bot. A member who owns a bot can ask with “Suggest My Bot”.
  • The owner must be in the group. If the owner leaves, the bot is removed and its messages are no longer shown.
  • The owner can revoke a bot at any time from My Bots on their primary device.
  • On the public relay each account can have one bot. On a private relay the administrator decides.
  • VeilMesh does not host bots.

Where to go next