Pipe Script Output to Messaging Platforms

mibyan send is a small, scriptable CLI that pushes a message to any messaging platform Mibyan is already configured for. Think of it as a cross-platform curl for notifications — you don’t need a running gateway, you don’t need an LLM, and you don’t need to re-paste bot tokens into each of your scripts. Use it for:

System monitoring (memory, disk, GPU temp, long-running job finished)
CI/CD notifications (deploy done, test failure)
Cron scripts that need to ping you with results
Quick one-shot messages from a terminal
Piping any tool’s output anywhere (make | mibyan send --to slack:#builds)

The command reuses the same credentials and platform adapters that mibyan gateway already uses, so there’s no second configuration surface to maintain.

Quick Start

# Plain text to the home channel for a platform
mibyan send --to telegram "deploy finished"

# Pipe in stdout from anything
echo "RAM 92%" | mibyan send --to telegram:-1001234567890

# Send a file
mibyan send --to discord:#ops --file ~/.mibyan/cache/scratch/report.md

# Attach a subject/header line
mibyan send --to slack:#eng --subject "[CI] build.log" --file build.log

# Thread target (Telegram topic, Discord thread)
mibyan send --to telegram:-1001234567890:17585 "threaded reply"

# List every configured target
mibyan send --list

# Filter by platform
mibyan send --list telegram

Argument Reference

Flag	Description
`-t, --to TARGET`	Destination. See target formats.
`message` (positional)	Message text. Omit to read from `--file` or stdin.
`-f, --file PATH`	Read the body from a file. `--file -` forces stdin.
`-s, --subject LINE`	Prepend a header/subject line before the body.
`-l, --list`	List available targets. Optional positional platform filter.
`-q, --quiet`	No stdout on success (exit code only — ideal for scripts).
`--json`	Emit the raw JSON result of the send.
`-h, --help`	Show the built-in help text.

Target Formats

Format	Example	Meaning
`platform`	`telegram`	Send to the platform’s configured home channel
`platform:chat_id`	`telegram:-1001234567890`	Specific numeric chat / group / user
`platform:chat_id:thread_id`	`telegram:-1001234567890:17585`	Specific thread or Telegram forum topic
`platform:#channel`	`discord:#ops`	Human-friendly channel name (resolved against the channel directory)
`platform:+E164`	`signal:+15551234567`	Phone-addressed platforms: Signal, SMS, WhatsApp

Any platform Mibyan ships adapters for works as a target: telegram, discord, slack, signal, sms, whatsapp, matrix, mattermost, feishu, dingtalk, wecom, weixin, email, and others.

Exit Codes

Code	Meaning
`0`	Send (or list) succeeded
`1`	Delivery failed at the platform level (auth, permissions, network)
`2`	Usage / argument / config error

Exit codes follow the standard Unix convention so your scripts can branch on them the same way they would on curl or grep.

Message Body Resolution

mibyan send resolves the message body in this order:

Positional argument — mibyan send --to telegram "hi"
--file PATH — mibyan send --to telegram --file msg.txt
Piped stdin — echo hi | mibyan send --to telegram

When stdin is a TTY (no pipe), Mibyan does not wait for input — you’ll get a clear usage error instead. This keeps scripts from hanging if they accidentally omit the body.

Real-World Examples

Monitoring: Memory / Disk Alerts

Replace ad-hoc curl https://api.telegram.org/... calls in your watchdogs with a single portable line:

#!/usr/bin/env bash
ram_pct=$(free | awk '/^Mem:/ {printf "%d", $3 * 100 / $2}')
if [ "$ram_pct" -ge 85 ]; then
  mibyan send --to telegram --subject "⚠ MEMORY WARNING" \
    "RAM ${ram_pct}% on $(hostname)"
fi

Because mibyan send reuses your Mibyan config, the same script works on any host where Mibyan is installed — no need to export bot tokens into each machine’s environment manually.

Don’t alert the gateway about itselfFor watchdogs that might fire when the gateway itself is struggling (OOM alerts, disk-full alerts), keep using a minimal curl call instead of mibyan send. If the Python interpreter can’t load because the box is thrashing, you still want that alert to go out.

CI / CD: Build and Test Results

# In .github/workflows/deploy.yml or any CI script
if ./scripts/deploy.sh; then
  mibyan send --to slack:#deploys "✅ ${CI_COMMIT_SHA:0:7} deployed"
else
  tail -n 100 deploy.log | mibyan send \
    --to slack:#deploys --subject "❌ deploy failed"
  exit 1
fi

Cron: Daily Report

# Crontab entry
0 9 * * * /usr/local/bin/generate-metrics.sh \
  | /home/me/.mibyan/bin/mibyan send \
      --to telegram --subject "Daily metrics $(date +%Y-%m-%d)"

Long-Running Tasks: Ping When Done

./train.py --epochs 200 && \
  mibyan send --to telegram "training done" || \
  mibyan send --to telegram "training failed (exit $?)"

Scripting with `--json` and `--quiet`

# Hard-fail a script if delivery fails; don't clutter logs on success
mibyan send --to telegram --quiet "keepalive" || {
  echo "Telegram delivery failed" >&2
  exit 1
}

# Capture the message ID for later editing / threading
msg_id=$(mibyan send --to discord:#ops --json "build started" \
  | jq -r .message_id)

Does `mibyan send` Need the Gateway Running?

Usually no. For any bot-token platform — Telegram, Discord, Slack, Signal, SMS, WhatsApp Cloud API, and most others — mibyan send calls the platform’s REST endpoint directly using credentials from ~/.mibyan/.env and ~/.mibyan/config.yaml (or the equivalent files under your resolved Mibyan home — %LOCALAPPDATA%\mibyan on Windows, or the profile directory when mibyan_HOME / -p is set). It’s a standalone subprocess that exits as soon as the message is delivered. If a platform reports not configured, the error lists the exact files it read and what each one held, e.g.

Looked in: C:\Users\me\AppData\Local\mibyan\.env (no DISCORD_BOT_TOKEN), C:\Users\me\AppData\Local\mibyan\config.yaml (no platforms.discord block), environment (DISCORD_BOT_TOKEN unset), external secret sources (none configured)

. When a gateway started from the same home has that platform connected, the token only exists in the gateway’s process environment — add it to that home’s .env so mibyan send can use it. When your shell is scoped to a profile home (mibyan_HOME=<root>/profiles/<name>) but the connected gateway runs from the default root, the error says so — the gateway never read the profile’s .env, and mibyan send --list points at the root’s channel_directory.json. A live gateway is only required for plugin platforms that rely on a persistent adapter connection (for example, a custom plugin that keeps a long-lived WebSocket open). In that case you’ll get a clear error pointing at the gateway; start it with mibyan gateway start and retry.

Listing and Discovering Targets

Before sending to a specific channel, you can inspect what’s available:

# Every target across every configured platform
mibyan send --list

# Just Telegram targets
mibyan send --list telegram

# Machine-readable
mibyan send --list --json

The listing is built from ~/.mibyan/channel_directory.json, which the gateway refreshes every few minutes while it’s running. If you see “no channels discovered yet”, start the gateway once (mibyan gateway start) so it can populate the cache. Human-friendly names (discord:#ops, slack:#engineering) are resolved against this cache at send time, so you don’t need to memorize numeric IDs.

Comparison with Other Approaches

Approach	Multi-platform	Reuses Mibyan creds	Needs gateway	Best for
`mibyan send`	✅	✅	No (bot-token)	Everything below
Raw `curl` to each platform	Each scripted separately	Manual	No	Critical watchdogs
`cron` job with `--deliver`	✅	✅	No	Scheduled agent tasks

mibyan send is intentionally the simplest possible surface. If you need an agent to decide what to say, schedule a cron job — the agent’s final response is auto-delivered to the configured deliver: target (the agent no longer fires messages itself). If you need a scheduled run with LLM-generated content, use cronjob(action='create', prompt=...) with deliver='telegram:...'. If you just need to pipe a raw string, reach for mibyan send.

Automate Anything with Cron — scheduled jobs whose output auto-delivers to any platform.
Gateway Internals — the delivery router that mibyan send shares with cron delivery.
Messaging Platform Setup — one-time configuration for each platform.

تطبيق ديسكتوب

البداية

استخدام مبيان

الميزات

منصات المراسلة

التكاملات

الأدلة والدروس

دليل المطوّر

المرجع

Pipe Script Output to Messaging Platforms

Quick Start

Argument Reference

Target Formats

Exit Codes

Message Body Resolution

Real-World Examples

Monitoring: Memory / Disk Alerts

CI / CD: Build and Test Results

Cron: Daily Report

Long-Running Tasks: Ping When Done

Scripting with `--json` and `--quiet`

Does `mibyan send` Need the Gateway Running?

Listing and Discovering Targets

Comparison with Other Approaches

​Quick Start

​Argument Reference

​Target Formats

​Exit Codes

​Message Body Resolution

​Real-World Examples

​Monitoring: Memory / Disk Alerts

​CI / CD: Build and Test Results

​Cron: Daily Report

​Long-Running Tasks: Ping When Done

​Scripting with --json and --quiet

​Does mibyan send Need the Gateway Running?

​Listing and Discovering Targets

​Comparison with Other Approaches

​Related

Quick Start

Argument Reference

Target Formats

Exit Codes

Message Body Resolution

Real-World Examples

Monitoring: Memory / Disk Alerts

CI / CD: Build and Test Results

Cron: Daily Report

Long-Running Tasks: Ping When Done

Scripting with `--json` and `--quiet`

Does `mibyan send` Need the Gateway Running?

Listing and Discovering Targets

Comparison with Other Approaches

Related