Drop the bug.
Mention BugsBunny in Slack or create an issue in the workspace. Keep the conversation and context together.
Report → issueYOUR AI CODING SIDEKICK
Turn bug reports into investigated fixes, verified changes, and draft pull requests. Keep building the good stuff.

A shorter hop from
“it’s broken” to “here’s the fix.”
One connected workflow, from the first report to the pull request you review.
Mention BugsBunny in Slack or create an issue in the workspace. Keep the conversation and context together.
Report → issueCodex investigates the repository, works on a fix, and runs configured checks in a fresh container.
Investigate → verifyGet a draft pull request when a fix is ready, or a clear blocker when Bunny needs your help.
Draft PR → your reviewThe context, checks, and controls a coding teammate needs to be useful.
Slack intake connects reports to the right app. Repository settings give Bunny the branch, folder, and commands to work with.
Fresh-container verification, setup logs, and run progress make the work inspectable. See what passed and what still needs attention.
Draft PRs, commit-specific code reviews, and PR lifecycle updates keep the fix connected to the issue.
Choose automation per app, configure environments and spending limits, and cancel a run when plans change.
A TEAMMATE, WITH BOUNDARIES
Follow the investigation. Inspect the checks. Review the code.
A draft pull request is a starting point for your judgment.
BugsBunny is an AI coding teammate for your apps. It collects issues, investigates code with Codex, works on fixes, runs your configured checks, and can open draft pull requests. It also supports GitHub code reviews and keeps issue and PR activity in one workspace.
The fix workflow publishes draft pull requests for you to review. You decide what to merge. Automation is opt-in per app, and you can inspect progress or cancel active runs.
Connect a GitHub repository and configure the app’s branch, working folder, and install and test commands. Agent runs need a configured model provider and worker environment. Slack is optional for reporting issues and receiving replies.
Runs can surface blockers or ask for more information. You can inspect the run, provide context, and retry. BugsBunny does not treat a blocked run as a completed fix.
This BugsBunny workspace uses administrator-managed access. Sign in with the credentials your workspace administrator provides. There is no public self-service signup.