0bridge and Slack bots for coding agents
A common way to steer coding agents from a phone is a Slack bot that starts them and posts their output in a thread. 0bridge does the job from Claude, ChatGPT or a dashboard instead, with approvals relayed to you. As of 2026-10-01.
Last updated
The short version#
Use a Slack bot if your team already lives in Slack and wants agent work visible in a channel, with threads as the record. Use 0bridge if the work is yours, on your machine, and you'd rather steer it from the AI app you already have open, with a phone-sized approval page.
Side by side#
| 0bridge | A Slack bot you run | |
|---|---|---|
| Interface | Claude, ChatGPT, any MCP client, a dashboard | Slack threads |
| Where it runs | A small program on your machine, relayed by 0bridge | Wherever you host the bot |
| Reaching your machine | An outbound connection from your machine, no open port | Depends on how you set it up |
| Permission prompts | Relayed to you; unanswered ones are denied after 30 minutes | As you build it |
| Notifications | ntfy or email, linking to the task page | Slack's |
| Visible to a team | Not yet: it is one person's account | Yes, in a channel |
| Safety defaults | Off until enabled twice, allowlisted repos, worktree per task, deny rules | Whatever you build |
| Upkeep | None on your side | You maintain the bot |
When not to use 0bridge#
- Your team needs to watch and join agent work together in a channel. 0bridge's control is personal today.
- You need Slack's own features: threads, search, retention rules and compliance export.
- You want one-tap approvals from a notification. 0bridge's notifications link to a page where you approve.