-
Notifications
You must be signed in to change notification settings - Fork 0
Channels
Aleksandr Artamokhov edited this page Jun 26, 2026
·
1 revision
One agent core, many mouths. CLI, Telegram, HTTP, and MCP all funnel into the same bounded loop — each channel owns its own auth model.
Full reference: argus/docs/channels.md
| Channel | Auth | Command / endpoint |
|---|---|---|
| CLI | Local user |
argus chat, argus ask
|
| Telegram | Owner-lock (first /start wins) |
argus serve + bot token |
| HTTP | Bearer ARGUS_HTTP_TOKEN on POST /ask
|
argus serve — GET /health open |
| MCP server | Local stdio trust |
argus mcp — tools argus_ask, argus_status
|
argus serve # HTTP + Telegram (per config)
argus mcp # stdio MCP for Cursor / Claude Desktop-
Interactive (CLI, Telegram): sensitive tools prompt
/yesor terminal confirm. - Non-interactive (HTTP, MCP): sensitive tools default-deny unless configured otherwise.
WARDEN vets MCP regardless of channel — the channel decides who may ask, WARDEN decides what may run.
| Route | Auth |
|---|---|
GET /health |
Open — used by Alien Monitor 👽 |
GET /status |
Open |
POST /ask |
Authorization: Bearer $ARGUS_HTTP_TOKEN |
Body: { "task": "…" } → streamed or JSON response per config.
Exposing ARGUS as MCP is how other agents invoke it in the mesh / hub economy — highest ecosystem fit. See Economy.
Discord, Slack, Email, Matrix, WhatsApp, voice, web widget — tracked in repo channels.md.