Skip to content

Commit 505631f

Browse files
authored
Explain Slack broker (#143)
1 parent b541f9a commit 505631f

1 file changed

Lines changed: 23 additions & 0 deletions

File tree

README.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -74,6 +74,12 @@ Upgrade later:
7474
sudo baudbot update
7575
```
7676

77+
Connect/talk to the control agent:
78+
79+
```
80+
sudo baudbot attach
81+
```
82+
7783
Install with a specific pi version (optional):
7884

7985
```bash
@@ -95,6 +101,23 @@ sudo baudbot env set ANTHROPIC_API_KEY
95101

96102
See [CONFIGURATION.md](CONFIGURATION.md) for required environment variables and secret setup.
97103

104+
## The Slack broker (optional)
105+
106+
The primary way to talk to Baudbot remotely is through Slack.
107+
108+
You have two choices:
109+
110+
1. **Create/manage your own Slack app** (hard)
111+
2. **Use our hosted Slack broker + control plane** at https://baudbot.ai (easy) [ALPHA]
112+
113+
What the Slack broker does:
114+
- One-click install to connect your Slack workspace to your Baudbot instance
115+
- Broker forwards messages to your Baudbot instance (encrypted)
116+
- Broker strips PII and sensitive values
117+
- Broker tool-restricts access to individual Slack users, channels, etc (COMING SOON)
118+
119+
The broker does not have access to your Baudbot instance. Baudbot is pull-only; it doesn't expose additional ports or host a control plane.
120+
98121
## Core agents
99122

100123
| Role | Purpose |

0 commit comments

Comments
 (0)