220 Labs
Menu
Get in touch GitHub

← All integrations

GitHub

Optional. Any git remote carries the work between machines; pull requests and CI are GitHub's.

Pull requests, CI before a merge, and the hub between machines. Without it, work lands on one machine, or moves between machines through any git remote: a bare repository over ssh or a forge of your own.

GitHub's site

At a glance

Without it

No account

  • Works: Work lands on one machine, offline
  • Works: Hand-over between machines, over any git remote
  • Not here: Pull requests and CI before a merge
  • Not here: autofinish, landing idle work unattended
  • Not here: Issues from beacon, deadman and helm
  • Not here: Branch rules on private repositories

Free

$0

  • Works: Work lands on one machine, offline
  • Works: Hand-over between machines, over any git remote
  • Works: Pull requests and CI before a merge
  • Works: autofinish, landing idle work unattended
  • Works: Issues from beacon, deadman and helm
  • Not here: Branch rules on private repositories

Paid

Pro, or Team at $4 a user a month for the first 12 months

  • Works: Work lands on one machine, offline
  • Works: Hand-over between machines, over any git remote
  • Works: Pull requests and CI before a merge
  • Works: autofinish, landing idle work unattended
  • Works: Issues from beacon, deadman and helm
  • Works: Branch rules on private repositories

What it brings, by module

wharfEvery session's work is sent to GitHub as it grows, so your other machines can read it, and a pull request opens at the first send. /finish lands the work through that pull request, after the project's check.
wharfA new project starts as a private repository with rebase-only merges and the check set up, and branch protection where the plan has it. The check runs on GitHub Actions, on a Mac of your own, or on CircleCI, switched in one command.
wharf-runsautofinish lands an idle piece of work through the same pull request, unattended.
keelWithout spacesheep, you answer a decision document in GitHub's editor.
helloworldA project's public twin is a GitHub repository, and its downloads a release's files. name-check reads GitHub handles.
lighthousebeacon files each contact message as an issue; deadman opens one when an unattended machine goes quiet. helm does the same for a stalled run.

Free plan

  • Unlimited public and private repositories.
  • 2,000 GitHub Actions minutes a month for private repositories.
  • Branch rules only on public repositories: on a private one, main is guarded by regatta's own git hooks alone.

  • Pro price not listed on the pricing page

    • Protected branches and required reviews on private repositories.
    • 3,000 Actions minutes a month.

  • Team $4 a user a month for the first 12 months

    • Branch rules and required reviewers on private repositories, for an organisation.
    • 3,000 Actions minutes a month.

As listed on github.com/pricing, read 2026-10-24.

Without it

  • No remote: one machine. /finish merges the work into main on the machine itself, offline, after the project's check.
  • Any git remote, a bare repository over ssh or a self-hosted forge: sessions push and fetch their work, dispatch hands it to another machine, and /finish merges locally and pushes main.
  • What stays GitHub's: pull requests, CI and branch rules, autofinish's unattended landing, and the issues beacon, deadman and helm open. beacon's Telegram sink still reaches you; deadman files its alarms as issues, so it needs GitHub.

Sources

Prices and limits as each page listed them on 2026-10-24.