Introduction
Runbear puts AI agents inside the tools your team already works in.
On this page
Runbear is a platform for building AI agents and putting them where work already happens: Slack, Microsoft Teams, Discord, HubSpot, Zendesk, your own product, and your inbox.
An agent is defined by four things, each configured on its own tab in the dashboard:
| Part | What it does |
|---|---|
| Instructions | The behavior you write, split into named context blocks |
| Knowledge | Documents synced from Notion, Confluence, Google Drive, Slack, SharePoint, websites, or direct upload |
| Tools | Live actions and lookups through MCP servers |
| Channels | Where the agent listens and replies |
Once an agent is configured you can also run it without a person asking: an event trigger fires it on a schedule, a webhook, or an event in a connected app.
Team agents and the Inbox Agent#
A team agent acts on its own. It reads a message, runs tools, searches knowledge, and posts a reply. You create as many as you need and deploy each one to one or more channels.
The Inbox Agent is personal and never acts on its own. It watches your Slack mentions, Gmail, and Google Calendar and prepares drafts and briefs that only you see. Every organization member has one.
Where to start#
Getting started walks through creating an agent and putting it in Slack. It takes about ten minutes and assumes no prior setup.
If you are integrating Runbear into your own software instead, start with the Web SDK to embed a chat widget, or the REST API to call agents directly.