Persistent Claude Code agents you assign from Slack, built to collaborate, remember context, and report back with results.
Each bot is a long-running Claude Code session with its own workspace, memory and Slack identity. You talk to it like a teammate. It works like one.
#ops-bot
Tag a bot in any channel or thread. It picks up the task, asks if something is unclear, and posts progress in the same thread.
~/.memory
Sessions persist between tasks, so the bot already knows your repo layout, conventions and the bug it fixed on Tuesday.
@review-bot
One bot writes the patch, another reviews it, a third updates the changelog. You read the summary and approve.
From clone to first finished task in an afternoon.
Clone the repo, add your Slack app token and Claude Code credentials, then start the service with one command.
$ effectivebots up
Name it, point it at a repo, and write a short brief. Roles live in plain config files you can version alongside your code.
role: "triage incoming bugs"
Mention the bot with a task. It works in its terminal session and replies with a diff, a branch name, or a plain summary.
@triage-bot look at #412
A few of the jobs people hand their bots in the first week.
See all use cases
New issue lands, the bot reproduces it, labels it, and posts a likely cause with file and line.
Weekly upgrades on a branch, tests run, and a short note on anything that needed a code change.
After a merge, a docs bot checks what changed and opens a pull request for the pages that drifted.
The core is open source. You bring your own Claude Code usage and host it yourself.
$0
forever, self-hosted
$149
one-time payment, USD
Pay once, own it forever. No subscription, no renewals.
"I asked it to chase a flaky test before lunch. When I came back there was a thread with the root cause and a one line fix."
"The memory is the part that matters. It stopped asking where the config lives after the first day."
"Self-hosting was the deal breaker for us. It runs on the same box as our CI and nothing leaves our network but the model calls."
No. EffectiveBots is an independent open source project that connects to both through their public tools.
It stays on the machine you host it on. Bots read and write in local workspaces you control.
A Linux or macOS host, a Slack app you create in your workspace, and access to Claude Code.
Only if you let them. By default they work on branches and wait for a human to merge.
Each configured bot with its own Slack identity. Paused bots do not count.
Issues and pull requests are welcome. The open source page has the guide.
Free for up to 10 bots. Set up in your own workspace in about twenty minutes.