Channels

Always available. You ask, you watch, you approve, in the same place. A published agent gets its own page, signed in, running the same runtime as the builder.

Built and tested against a mock transport: a private link that binds one Telegram identity to one agent, duplicate-message rejection, questions and approvals as buttons, a durable outbox for progress and results, and revocation that cancels outstanding runs.

Not live yet. Unverified against the real Telegram. It needs a bot token, a publicly reachable HTTPS installation and a deliberate webhook registration, none of which exist here. A delivery receipt would also never be proof that a person read the message.

Texting works, and has been run end to end on a real phone. A number proves itself first by texting a code in; nothing is ever sent to a number that has not done that. After that the agent takes instructions, asks its questions and sends its answers over iMessage.

When a run stops for you — a question, a sign-in code, an approval — it appears at the top of whatever page you are on, and it reaches your phone as well if you have given it a number. On the screen always; on your phone once you have set it up.

Not live yet. Not in this installation. Texting needs a messaging provider, and this one has no credentials for it, so an agent's Channels tab shows iMessage as not live here rather than claiming a delivery it cannot make.

Not live yet. Sending email out is not built. The send path, the card and the setup blocker are written and it needs a provider key and a verified sending domain. It appears on an agent's Channels tab marked not live rather than being hidden, because the definition really does carry it.

Nobody has set a price for messages in this product, so the Usage page counts them and reports them as unpriced. It does not report them as free.