​Most agents live inside a single interface — your app, a chatbot widget, a CLI. But users don't. They're in Slack, Discord, Telegram. And the tasks they need done happen across websites, forms, dashboards, and web apps they can't give your agent API access to.

​Mastra's Channels and Browser primitives solve both problems.

​Channels let your agent show up where your users already are — handling message routing, threading, and platform-specific formatting with minimal config.

​The new browser primitive gives your agent the ability to perform any task a human can do in a browser — navigate, click, fill forms, extract data, interact with authenticated web apps.

​Together, they turn your agent from something users have to visit into something that lives alongside them and acts on the open web.

You'll learn:

​How Channels work under the hood — routing, threading, and multi-platform message formatting

​Configuring agents for Slack, Discord, and Telegram with a few lines

​The architecture of Mastra's new browser primitive and how it executes tasks

​Giving your agent access to authenticated sessions, form submission, and data extraction

​How Channels and Browser compose — an agent that receives a request in Slack and completes it in a browser