Orbi

Codex · GitHub Issues · tagged release

Run Codex on your GitHub Issues, all the way to a release

The endpoint is a tagged release. Sign in once with your ChatGPT/Codex subscription, put ai-ready on one concrete Issue, and Orbi writes the code, opens the PR, sits through an independent review, merges the approved head, then tags and publishes the GitHub Release. Nobody watches the queue.

Self-host Orbi ↗Run it with Cloud →

THE LOGIN

Codex OAuth, no API key

Orbi's runner (Pi) talks to OpenAI through its native openai-codex provider over OAuth. It does not use OPENAI_API_KEY and needs no second provider file — what it spends is your ChatGPT/Codex subscription allowance. The steps below are the provider guide's Codex OAuth section, in order:

  1. 01 · SESSION
    Start an interactive Pi session with pi
  2. 02 · LOGIN
    At the Pi prompt, run /login codex

    Complete the Codex OAuth authorization in the browser.

  3. 03 · VERIFY
    Back in Pi, check the login

    pi auth check --provider openai-codex --model gpt-5.6-luna --json should report "status":"ready" and "authType":"oauth". The command refreshes expired OAuth credentials by default, so keep --credentials out of shared terminals.

  4. 04 · CONFIGURE
    Only after the check succeeds, configure Orbi

    Delete pi_providers if it exists and leave it unset; do not create an openai-codex entry. Pi supplies the catalog, and Orbi's per-run agent directory reuses Pi's native auth.

Minimal Orbi configuration — copied from the provider guide
source_repos = ["OWNER/YOUR-REPO"]
repo_dir = "/path/to/your-repo"
deploy_home = "/path/to/orbi"
workspace_root = "/path/to"
base_branch = "main"
max_concurrency = 1

# No pi_providers = ... line.
pi_provider = "openai-codex"
pi_model = "gpt-5.6-luna"

THE DELIVERY LINE

One label, then unattended to the release

After login, the workflow is the one described in the Orbi workflow — the full walkthrough lives on Issue to release.

  1. 01 · LABEL
    Mark the Issue ai-ready

    The label puts one concrete Issue into the delivery queue.

  2. 02 · IMPLEMENT
    Codex implements it in an isolated worktree

    The change is written away from the shared checkout and becomes a normal GitHub PR with its evidence.

  3. 03 · REVIEW
    A second model session reviews the frozen diff

    Up to five rounds; the reviewer can repair the branch and push directly.

  4. 04 · MERGE
    Only the approved head merges

    CI green, the head unchanged, the base current — otherwise the review runs again.

  5. 05 · RELEASE
    Tag and publish the GitHub Release

    The completed milestone turns into a tagged GitHub Release. That is the finish line, not a merged PR.

WHAT OPENAI SHIPS

OpenAI's own integration covers reviews and PR tasks

OpenAI documents a Codex integration for GitHub: ask for a code review with @codex review, turn on automatic reviews, and start cloud tasks from other @codex comments — a task can push fixes to a branch. Review and PR-scoped tasks are what those docs cover; a tagged release is not part of them. Orbi takes the same subscription and runs the remaining line: merge gates, tag, GitHub Release.

Your subscription already paid for the whole line — the release included.

WHAT IT COSTS

A subscription, or pennies per PR

Self-hosted with Codex OAuth.
Orbi is free under AGPL-3.0; the model spend is your existing ChatGPT/Codex subscription allowance.

Self-hosted without a subscription.
Any OpenAI-compatible API works. Orbi's own repository is delivered on DeepSeek: 20 merged PRs measured, median $0.125 per PR off-peak — numbers and method on the cost page.

Prefer managed.
Orbi Cloud signs in with GitHub; the first 3 merged deliveries are free and no card is required. When an allowance runs out, deliveries pause — no overage bills. Start at Orbi Cloud.

PUBLIC EVIDENCE

Orbi delivers its own repository

The orbi-build/orbi repository is built this way: 546 merged pull requests and 66 releases delivered by Orbi through the same line — label in, tagged release out, under AGPL-3.0.

FAQ

Questions before you hand Codex the queue

Do I need an OpenAI API key?
No. The openai-codex provider logs in over OAuth and spends the subscription allowance; see the provider guide.

Does Orbi Cloud run on my Codex subscription?
The Codex OAuth login is documented for self-hosted Orbi. Cloud is a separate path: sign in with GitHub, first 3 merged deliveries free.

How far does one label go?
To a tagged GitHub Release — PR, independent review of up to five rounds, merge of the approved head, tag, release. The long form is on Issue to release.

How does it compare with other autonomous agents?
Category, not copy — see Orbi vs Devin for a feature-by-feature comparison.

Is it open source?
Yes, under AGPL-3.0.

ISSUE IN, RELEASE OUT

Put the subscription to work

One label starts it. A tagged release ends it.

Self-host Orbi ↗Let Cloud run it →