agentpush

agentpush — the agentpush ⇄ agentproto transmitter

Bidirectional bridge between an imported agentpush MCP server (Telegram, etc.) and live agentproto sessions: transmit_message sends outbound and can bind the recipient to the sending session, and inbound replies from that contact then route straight into the SAME session as a real user turn — instead of spawning a brand-new agent for every reply.

Source: packages/runtime/src/transmitter-bindings.ts, inbound-adapters.ts, outbound-adapters.ts, inbound-router.ts, inbound-watcher.ts, the inbound_*/transmit_message/telegram_bot_* tools in orchestration-tools.ts/telegram-bot-creds.ts, and the POST /inbound(/:slug) routes in http-server.ts. Full reference: packages/runtime/docs/TRANSMITTER.md.

The model

One TransmitterBindingStore maps

(alias, source, contactRef) -> { sessionId, mode, provider?, lastSeenTs }

• alias — the imported MCP alias (agentpush) or bot-token alias (telegram).
• source — the channel/phone/chat id the message is scoped to.
• contactRef — the sender's id within that source.
• sessionId — the agentproto session future inbound replies from this contact should route into.
• mode — "route" or "route-or-spawn" (the mode this binding was created under).
• provider — the outbound provider the binding was created through ("agentpush", "telegram", …). Defaults to "agentpush".

Bindings live in memory, persist (debounced write) to ~/.agentproto/transmitter-bindings.json, load on construct, and start empty on a missing/corrupt file rather than throwing. One store instance is shared across the poll watcher, transmit_message, and the inbound HTTP routes.

MCP tools that actually exist

All verified against orchestration-tools.ts / telegram-bot-creds.ts — don't assume a verb exists beyond this list.

tool	purpose
transmit_message	Send outbound through a provider; binds the recipient to a session by default. Registered only when both an MCP proxy and a binding store are wired.
inbound_watcher_start	Start a background poller against poll_inbound on an imported agentpush alias; spawns (or routes, per mode) per contact_ref. Returns a watcherId.
inbound_watcher_stop	Stop a watcher by id. Cursor position is preserved for a later restart.
inbound_watcher_list	List all watchers (running + stopped) with cursor, poll/fire times, spawn count.
inbound_endpoint_create	Create/update a provider-agnostic POST /inbound/<slug> webhook endpoint (dialect, alias, mode, optional signing secret).
inbound_endpoint_list	List endpoints. Secrets are never emitted.
inbound_endpoint_delete	Delete an endpoint by slug.
telegram_bot_token_set	Store/rotate a Telegram bot token (0600 file under ~/.agentproto/telegram-bot-creds/), never echoed back.
telegram_bot_token_status	Check whether a token is configured (fingerprint/last4 only).
telegram_bot_set_webhook	Call Telegram's setWebhook for a bot alias using the stored token.
mcp_import	Prerequisite: import the agentpush MCP server under an alias before any tool above can use it.