Skip to content
Docs0.9GitHubInstall

GuidesAnswer from Telegram or Discord

Answer agents from Telegram or Discord

Give each conversation a Telegram topic or a Discord channel, and answer agents from a bot only you can talk to.

This guide connects a bot of your own, so each agent conversation gets a Telegram topicTopic. A conversation's thread in Telegram; on Discord it is a channel. or a Discord channel and questions arrive as buttons. Only the owner you configure can send input.

Each is a plugin the worker runs; there is nothing else to start. Connect either or both.

Create a bot with @BotFather and enable Topics for it there. Then add your numeric user ID and the token’s source to the config:

~/.config/vendetta/config.toml
[plugins.telegram]
owner_id = 123456789
token = { env = "VENDETTA_TELEGRAM_TOKEN" }
# or a command that prints only the token:
# token = { command = ["op", "read", "op://Vault/Item/password"] }

A token command runs as a literal argv, with no shell, and must finish within 8 seconds, so have your password manager open first. The token is kept only in memory. Stop any other program that polls the same bot.

In the Developer Portal, create a bot with Message Content Intent.

In your server, create a private category: deny View Channel to @everyone and allow it for you and the bot. Add a #control channel inside it with synced permissions.

Grant the bot Manage Channels, View Channel, Read Message History, Send Messages, Attach Files, Embed Links, and Pin Messages.

[plugins.discord]
owner_id = "123456789012345678"   # IDs are quoted
guild_id = "234567890123456789"
category_id = "456789012345678901"
channel_id = "345678901234567890" # #control
token = { env = "VENDETTA_DISCORD_TOKEN" }

The worker reads credentials when it starts:

vendetta notify stop && vendetta notify start
vendetta notify status   # plugins: messaging=running

If a service manager runs your worker, restart it there instead.

On Telegram, message a topic that has no agent yet. A picker opens:

  • choose a project, or type a project name or path;
  • choose a provider, and for omp or Claude a profile, then press Start;
  • once the agent is found, choose whether your first message becomes its prompt.

/session starts another conversation from an existing chat, and /cancel leaves the picker.

Agents you already run get a topic or channel of their own. On Discord each project gets a private category copied from yours, with a channel per conversation and a pinned status card.

  • Text in an agent’s topic is a normal prompt, also while the agent works. It never interrupts. Telegram reacts with a thumbs-up when the agent accepts a message and a thumbs-down when it rejects one.
  • Text in the root chat, or in Discord’s #control, goes to the Master, and starts it when none is running.
  • Questions from omp, Claude Code, and OpenCode appear as buttons, with multi-select, your own answer, and cancel. For your own answer, use Reply on the bot’s prompt.
  • Photos become image prompts: JPEG, PNG, or WebP, up to 8 MiB each. An album holds at most 10 images and 16 MiB. Discord takes one image per message and no other files.
  • Voice notes become prompts when transcription is configured, and the transcript is posted back. A note longer than 15 minutes, the default limit, is cut there and its first part sent.
  • Replying to an earlier message sends it along as quoted context.

While an agent works, one message is edited as it goes. Replies from Claude Code, Codex, and omp arrive formatted from their transcripts; OpenCode, Gemini, and Aider send labelled terminal snapshots.

Command Telegram Discord
/status Whether the agent takes a prompt now, and why not Same
/stop Stops the agent; the conversation and topic stay Interrupts the turn
/delete Deletes the agent and its topic after Yes, delete Deletes at once
/mute, /unmute Silence or restore the topic’s agent Same
/keep, /unkeep Keep the conversation from auto-delete, or stop Same

On Discord, type slash commands as ordinary message text.

An exited conversation’s topic stays. Your next message there restores that exact conversation and delivers the message.

Input is refused while the agent has an open question or approval, is in an unknown state, or was replaced by a new process. A refused message is never replayed later; send it again.

When Vendetta can’t tell whether a prompt, launch, stop, or deletion happened, it never repeats it. The conversation pauses, and on Telegram the operation is retired after 15 minutes with a notice asking you to check the agent’s terminal.

Everything else is in Telegram and Discord.