ChivesBot
Let’s talk about fixing things.
Most AI tools raise the ceiling. They don’t raise the floor. The people closest to the problem still can’t use them.
PMs, support, design, ops — they see the issues first. But the tools are built for engineers, so they copy links, translate context, and wait for someone else to push the button.
The people closest to the problem aren’t empowered to fix it.
ChivesBot turns Slack into the launchpad. You @mention
it in Slack. It investigates,
writes the fix, runs tests, and returns a PR.
Approval‑gated. Work routes across PM, design, and engineering.
@chivesbot checkout latency jumped after deploy. https://app.datadoghq.com/...
SELECT ... FROM promotions
promotions.user_id
promotions.user_id
One bot. Unlimited workflows.
Workflows are markdown files. Engineers review them in PRs. Anyone can trigger them.
Today you collect bots like trading cards. Each team ships their own, with its own commands, channels, and rituals. Onboarding turns into a scavenger hunt: which bot lives where, and what phrase wakes it up?
ChivesBot replaces the mess with one bot and one way to trigger work. The workflows are the memory. The bot is the doer.
-
Audit trail + clean hand‑offs
Every run is logged. Every approval is recorded. The hand‑off from PM to engineer to reviewer is explicit and traceable. A PM can start an investigation, the bot can find the right repo, and the engineer with access can approve the fix. Same for data tools and MCPs. You always know who approved what, and why.
-
One bot instead of a bot zoo
Today every team builds their own bot, their own trigger, their own rules. Support has one bot, data has another, infra has a third, and none of them talk to each other. ChivesBot is the shared runtime, so workflows can work together instead of in silos.
-
Cross‑tool context → PR
Pull the signal from Sentry or Datadog, do the work in a sandbox, and return a reviewable change. If the signal is in Datadog but the fix lives in code, the workflow connects the dots and ships one PR instead of a long Slack thread.
I’m building this now.
Want early access? Drop your email. I’ll set up your first workflows and onboard your team. If you don’t get value in the first week, you should walk away.