Rusuban vs Claude Code GitHub Actions
Both put Claude Code to work on your GitHub repos, and both are MIT-licensed. Claude Code GitHub Actions runs it in a workflow on a GitHub Actions runner, when someone mentions @claude or an event you chose fires. Rusuban runs it on your own machine, reads every issue and pull request, judges each one against the rules in your repo, and merges what those rules allow behind its locks. Claude Code GitHub Actions is the better choice when you want Claude on demand in your threads, with no machine of yours to keep on.
This page is published by the Rusuban project. The details on Claude Code GitHub Actions come from Anthropic's documentation and the anthropics/claude-code-action repository, checked in November 2026. The sources are listed at the end.
At a glance
| Rusuban | Claude Code GitHub Actions | |
|---|---|---|
| Where Claude Code runs | On your machine, Windows, macOS or Linux | In a GitHub Actions workflow, on the repo's runner |
| How work starts | Rusuban reads every issue and PR, every 90 seconds by default, and judges what needs it | A mention of @claude in a comment, a review or a new issue, or any workflow event or schedule given a prompt |
| What decides the work | Plain-text rules in .rusuban/rules/, the same for every item | The request in the comment, or the prompt in the workflow |
| Merging | Rusuban's server merges what your rules allow, behind eight gates, on the exact head it checked | Claude cannot approve pull requests, and is instructed not to merge branches |
| Your decisions | Cards in one inbox for all your projects, on your desktop or your phone | Comments and pull requests on GitHub |
| What you pay | Nothing for Rusuban. The agents run on your Claude plan | GitHub Actions minutes, plus Claude API tokens or a Claude subscription token |
| Where prompts go | Where your Claude Code login sends them. Rusuban has no server of its own | To the Claude API or the cloud provider you set up |
| License | MIT | MIT |
| Setup | npm install -g rusuban, then rusuban init | /install-github-app in Claude Code, or a GitHub App, a secret and a workflow by hand |
What both do
- Claude Code on your issues and pull requests. Both answer, write code and push commits to a branch.
- Your Claude plan. Both can run on a Claude subscription rather than on API tokens.
- Work on a schedule. A workflow can run on a cron with a prompt. Rusuban runs tasks written as text, at their times.
- Open source. Both are MIT-licensed.
Where Rusuban differs
It reads everything, not only mentions
Nobody has to call it. Rusuban reads every issue, PR, review and CI run of your repos, and a judge gives each item a kind, an owner, a next step and a date to look again. A new issue, a stale PR or a failing check gets handled because your rules say how. See issue and PR triage.
Your rules, in the repo
One set of rules decides every item: what the agents do alone, what comes to you, how long a third party is waited for. They are read from the default branch only, so a pull request cannot change the rules it is judged by. See Writing rules.
It merges, behind locks
Agents never merge, in Rusuban either. Its server does, when your rules let a PR merge without a person and eight gates pass on the exact head it checked: CI green, no open thread, your path and size locks among them. See auto-merge behind locks.
One inbox for what is yours
What your rules keep for you comes as a card, with options that each say what happens next. Every project's cards land in one inbox, which you answer in the dashboard or on your phone through your tailnet.
On your machine
Workers build and test in worktrees of Rusuban's own clone, with the tools of your machine, and can reserve test machines over SSH. No Actions minutes are spent. What agents may run there is your host profile, and no repo can change it.
When Claude Code GitHub Actions is the better choice
- You want Claude on demand in a thread. Your team asks
@claudefor a review, an answer or a fix, right where the discussion is. - You keep no machine on. It runs on GitHub's runners, or on your self-hosted ones.
Using both
They do not get in each other's way. A pull request that comes from Claude Code GitHub Actions is, for Rusuban, a pull request like any other: judged against your rules, and merged only behind the locks.
Getting started
- Install Rusuban:
npm install -g rusuban, thenrusuban init. - Write your first rules, or start from an example.
- Keep merges paused while you read the first judgments.
Comparing other tools as well? See the GitHub Copilot cloud agent alternative and Rusuban vs Mergify.
Sources
Claude Code GitHub Actions facts, checked November 2026:
- Triggers, billing, providers and setup: code.claude.com/docs/en/github-actions
- Runs on your runner, MIT license: github.com/anthropics/claude-code-action
- Issue assignment and label triggers: docs/usage.md
- No approvals, instructed not to merge: docs/capabilities-and-limitations.md
Rusuban facts link to its documentation above.
Claude and Claude Code are trademarks of Anthropic, and GitHub of GitHub, Inc. Rusuban is an independent project, not affiliated with or endorsed by either.