🐝New: AI bots that do your tasksLearn more →
GitHub + BusyBee.Day bots

A bot that triages your GitHub issues and pull requests

Connect GitHub with a token limited to the repositories you choose, and let a bot read code, sort issues and prepare changes for review.

Short answer

BusyBee.Day connects to GitHub through GitHub's official MCP server with a personal access token. A bot can read repositories and files, search code, list and comment on issues and pull requests, and, if your token allows, create branches and pull requests. Anything that is not read-only asks for your OK first.

Examples

You write

Summarise the open pull requests in the client repo and say which are ready to merge.

The bot

Reads the pull requests and their checks and writes the summary in the task.

You write

Turn issue 214 into a BusyBee.Day task with the steps to reproduce.

The bot

Reads the issue and creates the task.

You write

Fix the typo on the pricing page and open a pull request.

The bot

Asks for your OK, creates the branch and the pull request and links it.

Keep the token narrow

  • Use a fine-grained personal access token limited to the repositories this project needs.
  • Give it only the permissions you want the bot to have, for example read-only for triage.
  • Limit the connection to the client's project.
  • Combine it with the bot computer (Pro and above) to clone the repository and run tests.

Questions and answers

Why a token and not Sign in with GitHub?

GitHub's MCP server does not let other apps register for sign-in, so it uses a personal access token. You control its repositories, permissions and expiry.

Give your first task to a bot

The Free plan includes one bot and 30 credits a month. No credit card needed.

Start free