ChivesBot

Describe a bug. Get a PR.

Your support lead sees the bug. Your PM knows the fix. But it sits in the backlog for weeks because engineering has higher priorities.

ChivesBot lets anyone on your team trigger AI coding agents from Slack. Engineers review. Nothing merges without approval.

Support thread • #support-escalations
Run #8421
CS
Support Lead 2:14 PM
Customer escalation

@chivesbot customer is seeing a 500 on checkout — https://sentry.io/acme/issues/4821...

🌿
ChivesBot 2:14 PM
Investigation
Sentry error NullReferenceError in promo_code_lookup
Root cause Null promo code passed to lookup without validation
Repo acme/checkout-service
Needs approval from someone with write access to acme/checkout-service
Approve Deny
E
Engineer 2:15 PM
Approved. Run it under my access.
🌿
ChivesBot 2:18 PM
Fix ready
Added null check in promo_code_lookup
Added regression test for null promo code path
Tests: 84 passed, 0 failed
PR github.com/acme/checkout-service/pull/312
View PR View Session Reject
Investigate

Support asks "what's wrong?" Agent traces the issue through code and logs. Answer in the thread.

Automate

PM schedules a weekly report. Agent queries the database and posts results every Monday.

Fix

Anyone describes a change. Agent writes the code, runs tests, opens a PR. Engineer reviews.

Why not just Claude in Slack?

Claude in Slack can answer questions. It can't clone your repo, run your tests, or open a PR. ChivesBot connects to your codebase, runs agents in isolated sandboxes, and routes work through approvals. Every action is gated and logged.

Want early access? Drop your email.