Docs navigation
Agent

Surfaces

Surfaces are the channels where people can reach an agent. Configure surfaces to decide whether the agent is available in chat, Slack, phone, or meetings, and what each channel should expose.

How to use surfaces
  1. 01Open the agent's Surfaces area.
  2. 02Enable the channels the agent should support.
  3. 03Save the surface configuration.

What surfaces are available

  • Chat: Let users start direct conversations with the agent in the Brainbase web app.
  • Slack: Let the agent respond in channels, mentions, or direct messages.
  • Linear: Let people delegate issues to an agent or mention it in Linear; each issue runs as a Brainbase task. See Linear.
  • GitHub: Let the agent review pull requests, answer @mentions, and work with repository code. See GitHub.
  • Phone: Let the agent receive inbound calls from approved callers.
  • Meetings: Let the agent join meetings, take notes, and follow up.
Meeting behavior
When the Meetings surface is enabled, the agent can automatically join scheduled meetings. If you want the agent to prepare before a meeting or perform follow-up afterward, include those expectations in its Instructions.

Set up Slack

Connect an agent to a Slack workspace: create a Slack app from the manifest Brainbase generates, install it into your workspace, then save the credentials back on the agent. Follow the interactive walkthrough below.

Set up Slack
UI
  1. 01Create a Slack app at api.slack.com/apps using the agent's manifest.
  2. 02Install the app to your workspace, or request admin approval.
  3. 03Copy the signing secret, bot token, and app ID back into the agent.

Set up Linear

Connect an agent to a Linear workspace: create a private Linear app from the manifest Brainbase prefills, paste its credentials, and authorize it into the workspace. Once connected, delegate an issue to the agent or mention it in a comment. The full walkthrough, the tools the agent gets in Linear, and its settings are on the Linear page.

Best practices

  • Enable only the channels where the agent should actually be reachable.
  • Use template prompts to guide first-time users toward good starting tasks.
  • Limit available models when a surface needs predictable cost or behavior.
  • Keep high-risk channels off until instructions, tools, and permissions are reviewed.
  • Revisit surfaces whenever an agent's audience changes.