50 of 51 criteria have a sourced finding; 50 were also cross-checked by a second agent. Every comparison that includes Orbi links here for scope, limitations, atomic answers and sources.
Humans approve the rubric, templates and prototype; they do not review every finding. An agent source cross-check is not a hands-on product test. A missing sourced finding is not evidence that a capability is absent.
Self-hosted engine is CLI-only (orbi) on Linux (systemd user session) and macOS (launchd, "not yet verified on real hardware"); work is driven through GitHub Issues and PRs in a browser. Orbi Cloud adds a browser status page that works on a phone. No desktop app, native mobile app or editor extension.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted), GitHub Issues, labels and pull requests as the control surface, Orbi Cloud: hosted GitHub App with browser status page · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Desktop os [unsupported] No desktop client exists; the engine runs as a headless runner on Linux (systemd) and macOS (launchd). Windows is not listed in the prerequisites. Sources: orbi:gs, orbi:srch-clients.
Mobile apps [unsupported] No native iOS or Android app; Orbi Cloud FAQ says everything happens in the browser and GitHub. Sources: orbi:c-faq, orbi:srch-clients.
Browser [partial] Orbi Cloud has a browser status page and GitHub is the primary control surface; the self-hosted engine has no web UI. Sources: orbi:c-status, orbi:readme.
Mobile browser [supported] The Orbi Cloud status page documents "On a phone": the same actions are available on a phone browser. Sources: orbi:c-status.
Editor extensions [partial] No editor extension; a Claude plugin ships /orbi:ship and /orbi:status commands and issue-writing skills for Claude Code. Sources: orbi:plugin, orbi:srch-clients.
Task actions [partial] Start by labelling an Issue ai-ready or orbi add; steer by commenting on the Issue; review and approve the PR on GitHub; resume is automatic by the next tick; orbi status/session observe. Orbi Cloud adds Write a request, Let Orbi do this and status actions. Sources: orbi:wf, orbi:ops, orbi:c-status.
Notifications [partial] Optional Telegram messages for blocked, needs-detail, awaiting-merge, human-review wait and merged; no push notifications beyond that. Sources: orbi:cfg, orbi:c-notif.
Cross device continuity [supported] State lives in GitHub Issues, labels and PRs, so any device with GitHub access sees and can steer the same delivery; Cloud status page works from any browser. Sources: orbi:readme, orbi:c-status.
Orbi embeds one coding harness, Pi (earendil-works/pi), launched as a CLI process per task; the model provider is configurable through Pi. No second harness (Claude Code, Codex CLI, OpenCode) is launched.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted) · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Harnesses [partial] Exactly one harness, Pi; pi_executable may name another executable only if it accepts every Pi flag. Sources: orbi:gs, orbi:cfg, orbi:srch-agents.
Model providers [supported] Any provider in Pi's catalog or a pi_providers JSON file (DeepSeek, xAI, OpenRouter, Gemini, z.ai, Groq, Cloudflare Workers AI, local llama.cpp, GitHub Models, OpenCode Zen, ChatGPT/Codex OAuth). Sources: orbi:prov, orbi:cfg, orbi:opencode.
Custom adapters [partial] Custom model providers via pi_providers and Pi extensions (pi_extensions); no adapter for a different coding-agent CLI. Sources: orbi:cfg, orbi:srch-agents.
Session integration [supported] Orbi launches Pi in print/session mode, reads the session JSONL under .pi-session and supervises it (idle/model-wait recovery); it is a process launch, not an API. Sources: orbi:pi-launch, orbi:ops.
Mixed harness operation [unsupported] Only one harness is supported, so no mixed-harness operation; implementer and reviewer can use different models of the same harness (review_pi_* keys). Sources: orbi:cfg, orbi:srch-agents.
Model access is bring-your-own-key or subscription login through Pi (including ChatGPT Plus/Pro and Codex OAuth), local llama.cpp models, or Orbi Cloud's platform credits with BYOK fallback.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted), Orbi Cloud: hosted GitHub App with browser status page · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Agent subscriptions [supported] Docs describe signing in with a ChatGPT plan and Codex OAuth through Pi for self-hosted runs; quota and billing stay with that provider. Sources: orbi:prov.
Api accounts [supported] API keys for many providers via Pi auth or .orbi/env; Orbi Cloud BYOK for a provider list or any OpenAI-compatible endpoint. Sources: orbi:prov, orbi:c-model.
Vendor credits [partial] Orbi Cloud includes model usage (3 free merged deliveries; Solo 400M and Pro 1.2B tokens/month) on a platform channel; the self-hosted engine has no vendor credits. Sources: orbi:c-billing, orbi:c-limits.
Local models [supported] Local llama.cpp OpenAI-compatible endpoints and a local-qwen template are documented. Sources: orbi:prov, orbi:dock.
Account switching [partial] One provider/model per host config (a separate review provider is allowed); switching is a config edit. No multi-account rotation. Sources: orbi:cfg.
Vendor account requirement [supported] Self-hosting needs no Orbi account; it needs a GitHub login (gh) and a model provider. Orbi Cloud requires GitHub sign-in and the GitHub App. Sources: orbi:gs, orbi:c-faq.
Provider restrictions [unknown] Provider terms on automated use of ChatGPT/Codex subscriptions are not stated by Orbi docs and are owned by those providers.
Self-hosting needs Python 3.14 via uv, Pi on Node 22.19+, git, gh >= 2.94, a scheduler user session, and a GitHub repository with Issues; orbi setup creates labels and units. Orbi Cloud needs only GitHub sign-in, App installation and a repository.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted), Orbi Cloud: hosted GitHub App with browser status page · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
First task setup [supported] One-line installer, orbi.toml with source_repos, orbi setup, orbi doctor/check, then label an Issue ai-ready; Docker image alternative. Sources: orbi:gs, orbi:readme.
No git [unsupported] Work requires a Git repository checkout (worktrees, branches) and a GitHub repository. Sources: orbi:gs, orbi:ops.
Local git without remote [unsupported] Claim, PR, review and merge all run through gh against an origin on GitHub; a repository without a GitHub remote cannot be delivered. Sources: orbi:gs, orbi:ops.
Hosted git [supported] GitHub-backed repositories are the only supported model; git transport ssh or https. Sources: orbi:gs, orbi:sec.
Prerequisite guidance [supported] orbi check is a read-only prerequisite gate that fails fast with reason, fix and docs link. Sources: orbi:ops, orbi:gs.
Byo vps onboarding [partial] Self-host on any machine with a systemd user session; no dedicated VPS installer, though a one-line installer and a community Docker image exist. Sources: orbi:gs, orbi:dock.
Programmable surface is the orbi CLI (add, suggest --json, status, session, milestone, notify) plus GitHub labels, comments and in-ticket /orbi commands. No HTTP API, SDK, MCP server or webhooks.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted), GitHub Issues, labels and pull requests as the control surface · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Cli [supported] Documented orbi subcommands with --config and machine-readable --json on suggest; public contract table. Sources: orbi:pubc, orbi:ops.
Api [unsupported] No HTTP API in the engine; automation uses GitHub's API and labels. Sources: orbi:srch-api.
Sdk [unsupported] No SDK shipped. Sources: orbi:srch-api.
Mcp server [unsupported] No MCP server; the Claude plugin supplies commands and skills only. Sources: orbi:srch-api, orbi:plugin.
Webhooks [unsupported] No webhook receiver; the runner polls on a five-minute tick. Sources: orbi:srch-api, orbi:timer.
Operations [partial] Create (orbi add/draft), inspect (status, session), steer (Issue comment), stop (close Issue) and review (PR) exist through CLI or GitHub; no single programmatic stop/steer command. Sources: orbi:ops, orbi:wf.
Authentication [supported] Uses the gh login or GH_TOKEN; steering trusts only GitHub admin/write logins. Sources: orbi:sec, orbi:wf.
Stability [supported] Public contracts page states what is stable and says anything outside the table is internal and may change; changes are called out in release notes. Sources: orbi:pubc, orbi:ops.
Tool extension is through Pi: Pi skills (skills config), Pi extensions (pinned npm/git/local via pi_extensions), context files and AGENTS.md. Orbi does not provide an MCP client and runs Pi with --no-extensions so global extensions are not loaded.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted) · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Mcp client [partial] No Orbi-owned MCP client; a Pi MCP adapter package can be installed in Pi, and docs warn it can stall unattended sessions. Sources: orbi:srch-api, orbi:ops.
Plugins [supported] pi_extensions entries with pinned npm:/git sources or local paths, enabled per entry with injected env. Sources: orbi:cfg.
Custom tools [partial] Custom tools come from Pi extensions; Orbi ships one internal clarify_verdict tool. Sources: orbi:cfg, orbi:wf.
Instructions import [supported] context_files (host and repository policy) and skills paths are injected into prompts; repository AGENTS.md can be listed. Sources: orbi:cfg, orbi:wf.
Authentication [partial] Extension env is injected per extension; the Runner environment (including gh auth and any cloud keys) passes to Pi unfiltered except the Telegram token. Sources: orbi:cfg, orbi:pi-launch.
Permission scope [unsupported] No permission scoping for tools: ops tickets receive the whole Runner environment and there is no command whitelist. Sources: orbi:wf, orbi:sec.
Integration owner [supported] Connections come from Pi and the host environment, not Orbi; GitHub access is through gh. Sources: orbi:gs, orbi:cfg.
The engine is a Python 3.14 package (CLI) driving Pi and gh; no GUI client. Orbi Cloud's browser client implementation is not documented and its source is private.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted), Orbi Cloud: hosted GitHub App with browser status page · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Desktop implementation [unsupported] No desktop client; the product is a Python CLI/runner (src/orbi, pyproject.toml). Sources: orbi:srch-clients, orbi:gs.
Mobile implementation [unsupported] No mobile client; Cloud is a responsive web page. Sources: orbi:c-status, orbi:srch-clients.
Hybrids [unsupported] No Electron, Tauri or hybrid client in the engine repository. Sources: orbi:srch-clients.
Implementation evidence [partial] Engine implementation is pinned source (Python); the Cloud web client technology is unknown because its repository is private. Sources: orbi:gs.
Intake is GitHub Issues (authoritative tracker): orbi add, orbi draft/suggest conversations, or a human creating an Issue and labelling it ai-ready. Issue IDs are GitHub numbers; Orbi reads and writes Issue labels/comments on GitHub rather than syncing a copy.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted), GitHub Issues, labels and pull requests as the control surface, Orbi Cloud: hosted GitHub App with browser status page · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Local creation [supported] orbi add creates an Issue and labels it ai-ready; orbi draft turns a request into Issues. Sources: orbi:ops, orbi:pubc.
Prompt intake [supported] orbi draft, orbi suggest and Orbi Cloud Write a request turn a prompt into drafted Issues. Sources: orbi:pubc, orbi:c-status.
External import [partial] Only GitHub Issues are in scope; no Linear/Jira import. External pull requests can be triaged via an orbi:external-pr marker. Sources: orbi:wf, orbi:srch-api.
Chat git triggers [partial] Triggers are Issue labels and in-ticket /orbi commands on GitHub; no chat integration. Sources: orbi:wf, orbi:ops.
Authoritative tracker [supported] GitHub Issues are the only state store. Sources: orbi:readme.
Sync [supported] No copy is kept; reads and writes go straight to GitHub. Sources: orbi:readme, orbi:sec.
Supported edits [partial] Orbi edits labels, comments, milestones, appended acceptance criteria and sub-issues; humans edit the body and steering restarts the run. Sources: orbi:wf.
External roundtrips [partial] Everything is on GitHub; creating and prioritizing Issues beyond Orbi's commands happens in GitHub's UI. Sources: orbi:wf.
Orbi writes a plan artifact in the task worktree and the Issue body carries acceptance criteria (optionally appended by the thin-ticket gate). Plans are run artifacts, not editable durable plan objects; steering the Issue restarts the session.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted), GitHub Issues, labels and pull requests as the control surface · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Plans [partial] The dev session follows plan → implement → test → verify and keeps a plan file as a run artifact in the worktree. Sources: orbi:readme, orbi:ops.
Acceptance criteria [supported] Issue body acceptance condition; /orbi amend appends proposed criteria under an orbi:acceptance:v1 section. Sources: orbi:wf, orbi:pubc.
Editors [partial] The GitHub Issue editor is the only plan/criteria editor; the plan artifact is not editable. Sources: orbi:wf.
Revisions [partial] GitHub keeps Issue body edit history; Orbi adds no plan revisions. Sources: orbi:wf.
Implementation links [supported] PR body carries Fixes #N and the run marker; scene block links PR and branch. Sources: orbi:wf, orbi:pubc.
Amendment [supported] Editing the Issue or commenting restarts the active session with the correction, up to steering_max_rounds (3). Sources: orbi:wf, orbi:cfg.
Restart persistence [supported] Issue and PR persist on GitHub; the worktree is rebuilt from the remote branch if missing. Sources: orbi:wf, orbi:ops.
Hierarchy uses GitHub primitives: ai-epic Issues with native sub-issues, native blocked-by relations that prevent claims, milestones and P0/bug ordering. /orbi split turns a thin ticket into an Epic with children. No arbitrary workflow DAG.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted), GitHub Issues, labels and pull requests as the control surface · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Blockers [supported] Native blockedBy relations; an Issue with an open blocker is skipped and logged blocked_by. Sources: orbi:wf, orbi:claim.
Readiness [supported] Ready means ai-ready, no open blocker, milestone scope match; pickup order p0, bug, then oldest. Sources: orbi:wf.
Enforcement [supported] Claim scan enforces blockers; "Depends on #N" prose is deliberately not parsed. Sources: orbi:wf, orbi:claim.
State propagation [partial] Epic completion is derived from children; no other upward propagation. Sources: orbi:wf.
Task to epic [supported] /orbi split (or the clarification gate) turns a ticket into an Epic with created child Issues. Sources: orbi:wf, orbi:pubc.
Identity retention [partial] The split ticket keeps its number and becomes the Epic; its discussion remains, children are new Issues. Sources: orbi:wf.
Workflow constraints [supported] A fixed seven-state label workflow is required; type labels pick dev, ops or content. Sources: orbi:wf.
Context comes from repository files (context_files, AGENTS.md), Pi skills and the trusted Issue/PR comment timeline injected into each prompt. No cross-session memory store; the GitHub record is the continuity.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted), GitHub Issues, labels and pull requests as the control surface · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Instructions [supported] context_files and repository AGENTS.md are injected into the implementer and reviewer prompts; prompt templates are configurable (host-only). Sources: orbi:cfg, orbi:wf.
Skills [supported] skills config lists Pi skill paths; the Claude plugin ships two issue-writing skills. Sources: orbi:cfg, orbi:plugin.
Project docs [supported] Repository docs referenced via context_files with existence and size checks. Sources: orbi:wf.
Memory [unsupported] No managed memory in the engine; bounded search found none. Sources: orbi:srch-misc.
Scope [partial] Context files can be host-wide or per repository policy; comment timeline is per Issue and capped by issue_comments_limit (200). Sources: orbi:cfg, orbi:wf.
Provenance [partial] Only comments from write/admin authors are trusted and shown; no citations of context files in answers. Sources: orbi:wf, orbi:sec.
Correction [partial] Corrections are made by editing files or commenting; there is no memory edit tool. Sources: orbi:wf.
Deletion [partial] Context is deleted by editing repo files or removing comments; local run artifacts are removed by worktree reclamation. Sources: orbi:ops.
Freshness [partial] The repository policy file is read from the default branch tip at each claim, and the Issue body is fresh each review round; no staleness detection. Sources: orbi:wf.
Takeover continuity [supported] The scene block and trusted comments let any tick (or a human re-labelling) resume the same run, branch and PR. Sources: orbi:wf, orbi:pubc.
No Orbi-owned code indexing or knowledge retrieval; the Pi agent reads the repository with its own tools. Review is an independent session against the exact diff and the repository's own tests and coverage requirements.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted) · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Code search [partial] Search is whatever Pi tools provide inside the worktree; orbi suggest reads the repository to propose Issues. Sources: orbi:ops, orbi:srch-misc.
Indexing [unsupported] No indexing or embeddings in the engine. Sources: orbi:srch-misc.
External knowledge [unsupported] No external knowledge connectors; extensions could add some via Pi. Sources: orbi:srch-misc, orbi:cfg.
Multimodal inputs [unsupported] No image or screenshot input feature in the engine; Issue text only. Sources: orbi:srch-misc.
Freshness [partial] The repository is read at the frozen base SHA of each claim, so inputs are fresh per run. Sources: orbi:wf.
Access scope [partial] The agent can read the worktree and anything the Runner user can; the Cloud environment has only the connected repository. Sources: orbi:sec, orbi:c-sec.
Api retrieval [unsupported] No API retrieval service. Sources: orbi:srch-api.
Citations [unsupported] No citation feature. Sources: orbi:srch-misc.
Conflict detection [partial] Base drift is detected and absorbed by merge; no architecture-conflict detection. Sources: orbi:wf.
Review enforcement [partial] An independent review session judges the diff against the Issue and repository contract; its strength depends on the model and repository tests. Sources: orbi:wf, orbi:c-faq.
Issue management is GitHub's: Orbi adds delivery labels, dispatch via ai-ready, priority labels p0/bug, milestones, epics and a clarification gate. Orbi does not provide its own issue editor, search or board; Orbi Cloud shows a task history list.
Scope
Surfaces: GitHub Issues, labels and pull requests as the control surface, Orbi Cloud: hosted GitHub App with browser status page · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
The agent and Runner share the same GitHub Issue numbers and labels humans use: the Runner claims, comments, labels, creates sub-issues and blocked-by edges (via /orbi split), and records results; humans see all of it on GitHub with the runner identity as author. No MCP/API surface for third-party agents.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted), GitHub Issues, labels and pull requests as the control surface · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Children [supported] Native sub-issues are attached by split. Sources: orbi:wf.
Results [supported] Merged receipt, failure and review-round comments with machine markers. Sources: orbi:pubc.
Human visibility [supported] Everything is a normal GitHub label or comment; Cloud links to it. Sources: orbi:wf, orbi:c-status.
Attribution [partial] Actions are attributed to the Runner's GitHub identity (or App) with run_id markers, not to a per-agent identity. Sources: orbi:pubc, orbi:c-sec.
No living product specification: Issues carry per-task acceptance criteria and AGENTS.md/context files are static instructions. No requirement store, drift detection or spec review.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted) · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
9 atomic answers
Persistent requirements [unsupported] Bounded search finds no product-spec store; context_files are plain files. Sources: orbi:srch-misc, orbi:cfg.
Human edits [unsupported] No spec object to edit. Sources: orbi:srch-misc.
Agent edits [unsupported] No spec object; agents edit repository files like any other. Sources: orbi:srch-misc.
Revisions [unsupported] No spec revision feature (git history only). Sources: orbi:srch-misc.
Approvals [unsupported] No spec approval flow. Sources: orbi:srch-misc.
Up to five concurrent deliveries per host (max_concurrency 1-5, default 1) via flock slots; each task has its own worktree, branch and run. Status is visible through labels, orbi status and journal.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted), Orbi Cloud: hosted GitHub App with browser status page · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Partly established: observed_concurrency unknown.
5 atomic answers
Concurrent sessions [supported] Slots are flock files; max_concurrency timers can run simultaneously. Sources: orbi:ops, orbi:cfg.
Concurrent tasks [supported] Each concurrent delivery has its own Issue, worktree and PR. Sources: orbi:ops.
Quotas [supported] max_concurrency 1-5 (MAX_RUNNER_INSTANCES); one repository per host config; Cloud repository limits 1/1/5. Sources: orbi:cfg, orbi:c-limits.
Observed concurrency [unknown] No measured concurrency figures in the catalog; sustainable capacity depends on CPU and memory and is not stated.
Status visibility [supported] Labels show running (ai-in-progress), waiting (ai-pr-opened, ai-awaiting-merge), failed (ai-blocked, ai-fix-needed) and finished (ai-merged); orbi status and Cloud task history show them. Sources: orbi:wf, orbi:cli-status, orbi:c-status.
Dispatch is the ai-ready label; the Runner claims one Issue per slot by exclusive flock and label swap, ordered p0, bug, then oldest. Blockers prevent claims. No human/agent assignee.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted), GitHub Issues, labels and pull requests as the control surface · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Human assignment [unsupported] Humans do not assign Issues to agents; they label ai-ready. Sources: orbi:wf.
Agent assignment [unsupported] No agent-to-agent assignment. Sources: orbi:sec.
Claims [supported] Claim adds ai-in-progress and creates the run; recovery keeps the run id. Sources: orbi:wf.
Queues [supported] ai-ready is the queue, scanned in three ordered scans with oldest-first. Sources: orbi:wf.
Routing [partial] Routing by labels (dev/ops/content/release) and milestone scope; no skill routing. Sources: orbi:wf.
Duplicate prevention [supported] Branch is stable per Issue, slots are exclusive locks, overlapping task pools are diagnosed. Sources: orbi:ops, orbi:wf.
Ownership enforcement [supported] Slot flock and GitHub label state enforce exclusive work; overlapping hosts on one pool are warned about, not blocked. Sources: orbi:ops.
The product orchestrates sequential roles inside a delivery: an implementer Pi session, an independent review session (optionally a different model) and, for splitting, ticket sessions. It states it has no multi-agent parallelism and no coordinator that delegates to child agents.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted) · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Roles [partial] Implementer, independent reviewer, clarification judge and drafting/suggest sessions are fixed roles. Sources: orbi:wf, orbi:cfg.
Model harness effort [partial] Provider, model and thinking level for implementation and a separate set for review; same harness only. Sources: orbi:cfg.
Messages [partial] Roles communicate through Issue/PR comments and a REVIEW_VERDICT, not live messages. Sources: orbi:wf.
Results return [supported] Review round comments carry verdicts and the scene; merge records the receipt. Sources: orbi:pubc.
Work starts unattended: a five-minute systemd/launchd timer polls GitHub for ai-ready Issues; milestones can advance automatically and a configured milestone workflow creates release tasks. No cron-style recurring task scheduler or event webhook.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted), Orbi Cloud: hosted GitHub App with browser status page · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Schedules [partial] Only the five-minute tick; no user-defined schedule. Sources: orbi:timer, orbi:srch-sched.
Events [partial] Labels are polled; Cloud wakes the runner when ai-ready is added with the timer as fallback. Sources: orbi:c-faq, orbi:srch-sched.
Recurring tasks [unsupported] No recurring task definition. Sources: orbi:srch-sched.
Completion conditions [supported] Delivery ends at merge; release state machine has gates; milestone completion closes the milestone. Sources: orbi:wf.
Scheduler location [supported] User systemd timer or launchd agent on the host; in Cloud, the vendor environment. Sources: orbi:timer, orbi:c-prov.
Overlaps [supported] A runner that cannot take a slot logs capacity_full and exits; slots prevent overlap. Sources: orbi:ops.
Retries [supported] One automatic re-queue after a transient GitHub failure; recoverable failures resume next tick; five review rounds; three-failure dead-loop guard. Sources: orbi:wf, orbi:rounds.
Client independence [supported] The timer runs without any client; no UI needs to stay open. Sources: orbi:timer.
Intervention is by GitHub: steer by comment/body edit (3 restarts), stop by closing the Issue, and recover blocked work by relabelling; pending decisions are labels (ai-blocked, ai-needs-detail, ai-awaiting-merge, ai-human-review) with optional Telegram alerts.
Scope
Surfaces: GitHub Issues, labels and pull requests as the control surface, Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted) · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Pause [partial] Pause a deployment by disabling timers; no per-task pause. Sources: orbi:ops.
Stop [partial] Closing the Issue stops the closeout and no PR is opened; the pushed branch keeps the work. No kill-session command. Sources: orbi:ops, orbi:c-faq.
Resume [supported] Automatic on the next tick; relabel ai-fix-needed to continue a blocked delivery. Sources: orbi:ops.
Steer [supported] Trusted comment or body edit restarts the session with the correction. Sources: orbi:wf.
Notifications [partial] Optional Telegram for blocked, needs-detail, awaiting-merge, human-review and merged. Sources: orbi:cfg, orbi:c-notif.
Pending decisions [supported] Labels name the pending decision and the comment names the one action. Sources: orbi:wf.
Escalation [partial] ai-blocked plus Telegram; health Issues for crash loops (health_alert_repo). Sources: orbi:cfg.
Visible errors [supported] Failure comments carry the full scene and reason on Issue and PR. Sources: orbi:wf, orbi:pubc.
Chat terminal parity [unsupported] No interactive chat or terminal question path; Pi runs unattended and questions are not routed. Sources: orbi:sec.
Retained history [supported] Journal, comments and session JSONL are retained. Sources: orbi:ops.
No fleet UI in the engine beyond orbi status and GitHub label views. Orbi Cloud's status page shows projects, an attention list, task history tabs (In progress, Under review, Done) and per-task usage; epics are not visualized there.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted), Orbi Cloud: hosted GitHub App with browser status page · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Fleet fixture [supported] Cloud status page lists several tasks with states; orbi status lists active deliveries per repo. Sources: orbi:c-status, orbi:cli-status.
Parent child [partial] Epic completion is reconciled on GitHub; the Cloud task table is flat per project. Sources: orbi:wf, orbi:c-status.
Dependencies [partial] Queued tasks show what they wait for including unresolved dependencies. Sources: orbi:c-status.
Attention [supported] Cloud shows N items need you with reason and action. Sources: orbi:c-status.
History [supported] Task history with updated time and elapsed/AI-call/token data. Sources: orbi:c-status.
Workload [partial] Per-task tokens and elapsed time in Cloud; engine journal metrics via the optional exporter. Sources: orbi:c-status, orbi:exporter.
Navigation errors [supported] Unreadable state is shown as unreadable, not empty. Sources: orbi:c-status.
Fixture mode [partial] The documented screenshots use vendor sample data in a partner-e2e demo repository. Sources: orbi:c-status.
Workflow is a fixed pipeline (claim, implement, review, merge, optional release) with ticket types dev/ops/content; configuration is per host or repository policy. No natural-language workflow builder or per-agent configuration beyond implementer/reviewer model choice.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted) · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Self-hosted: runs on any machine you control (local, VPS, NAS via Docker) as a timer runner that survives client disconnects; Orbi Cloud runs the same engine in a vendor per-tenant environment. No separate laptop client exists.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted), Orbi Cloud: hosted GitHub App with browser status page · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Partly established: hybrid unsupported; resources unknown; region unknown; expiry partial.
12 atomic answers
Local [supported] Runs on the user's own computer with a systemd/launchd user session. Sources: orbi:gs.
Byo remote [supported] Any VPS or home server with a user systemd session; the engine is the whole system. Sources: orbi:gs, orbi:dock.
Self hosted [supported] The engine is the control plane; Docker image optional. Sources: orbi:readme, orbi:dock.
Managed cloud [supported] Orbi Cloud provisions a dedicated environment per repository. Sources: orbi:c-prov, orbi:c-sec.
Hybrid [unsupported] No documented mix of local and cloud execution for one task. Sources: orbi:readme.
Each task runs in its own git worktree and branch of one checkout as the Runner user, with no container, VM or OS sandbox; the Runner environment (secrets) is passed to Pi. Orbi Cloud gives each tenant a separate OS user environment.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted), Orbi Cloud: hosted GitHub App with browser status page · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Partly established: container unsupported; vm unsupported; os_sandbox unsupported; filesystem partial; process partial; network unsupported; secrets partial; code_separation partial; security_boundary unsupported.
12 atomic answers
Checkout [supported] One delivery checkout (repo_dir) shared by worktrees. Sources: orbi:cfg.
Branch [supported] orbi/<owner>-<repo>-issue-<N> per Issue. Sources: orbi:pubc.
Worktree [supported] a worktree directory named orbi-<owner>-<repo>-issue-<N>-<run_id> under the gitignored worktrees folder, from the frozen base SHA. Sources: orbi:ops.
Container [unsupported] No per-task container; Docker is a community wrapper for the whole runner. Sources: orbi:srch-container, orbi:dock.
Vm [unsupported] No VM isolation in the engine. Sources: orbi:srch-container.
Filesystem [partial] Worktree separation only; the agent can reach anything the user can. Cloud tenants are separate OS users. Sources: orbi:sec, orbi:c-sec.
Process [partial] Separate Pi process per task; same user locally. Sources: orbi:pi-launch.
Network [unsupported] No network restriction documented for the agent. Sources: orbi:srch-container.
Secrets [partial] Telegram token is removed from Pi's environment; everything else, including gh credentials, is passed; ops tickets get the whole environment. Sources: orbi:pi-launch, orbi:wf.
Code separation [partial] Tenant isolation in Cloud by OS user; locally one user. Sources: orbi:c-sec.
Security boundary [unsupported] Docs say the boundary is GitHub branch protection and token scopes, not an agent sandbox. Sources: orbi:sec.
Resume is core: a killed runner leaves ai-in-progress and the next tick resumes the same run; missing worktrees are rebuilt from the remote branch; failures are classified recoverable (ai-fix-needed) or blocked. Session transcripts are JSONL in the worktree.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted) · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Dependency setup is the repository's own and the agent installs inside the worktree; Orbi manages no caches, snapshots, services or ports. Orbi sets up its own labels, units and checkout.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted) · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Dependencies [partial] Agent runs repository setup in the worktree as the prompt directs; no product dependency manager. Sources: orbi:ops, orbi:srch-misc.
Caches [unsupported] No cache management. Sources: orbi:srch-misc.
Snapshots [unsupported] No snapshots. Sources: orbi:srch-misc.
Services [unsupported] No service orchestration. Sources: orbi:srch-container.
Secrets [partial] Host .orbi/env file loaded by the unit; no per-task secret injection. Sources: orbi:sec.
Duplicate installs [unsupported] Each worktree installs separately. Sources: orbi:srch-misc.
Collisions [unsupported] No collision handling. Sources: orbi:srch-container.
Remote setup [supported] orbi setup is idempotent and installs units; orbi check diagnoses. Sources: orbi:gs, orbi:ops.
Automatic repair [partial] Doctor reports drift and orbi install-units repairs units; project environment problems are for the user. Sources: orbi:ops.
Limits are narrow: no task time or token limit; review rounds capped at 5, steering at 3, dead-loop at 3, model idle thresholds (hung request 1800s) and a one-hour idle recovery cap. Cloud has token and repo quotas.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted), Orbi Cloud: hosted GitHub App with browser status page · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Observability is a structured systemd journal with run_id on every line, GitHub progress comments, orbi status/session, an optional Prometheus exporter and Grafana dashboard. Cloud status shows per-task usage. Orbi provides no speed benchmarks.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted), Orbi Cloud: hosted GitHub App with browser status page · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
The engine does not track API cost. Orbi Cloud shows tokens (input, output, cache) per task and monthly platform usage against the allowance; no dollar amounts.
Scope
Surfaces: Orbi Cloud: hosted GitHub App with browser status page, Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted) · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Session cost [unsupported] No session cost. Sources: orbi:srch-cost.
Child cost [unsupported] No child accounting. Sources: orbi:srch-cost.
Epic cost [unsupported] No epic aggregation. Sources: orbi:srch-cost.
Harness aggregation [unsupported] Single harness. Sources: orbi:srch-agents.
Billed vs estimated [partial] Tokens measured; subscription pricing is separate; no estimates of dollars. Sources: orbi:c-limits.
Tokens [supported] Input, output and cache-read tokens in Cloud. Sources: orbi:c-limits.
Subscription allowance [supported] Allowance with used percentage and reset time. Sources: orbi:c-status.
Provider reconciliation [unsupported] BYOK usage is measured separately and not reconciled with provider bills. Sources: orbi:c-limits.
Compute cost [unsupported] Compute is bundled into the plan; not itemized. Sources: orbi:c-billing.
Refresh delay [partial] Status observed about every 15 seconds; usage not reported for some tasks is excluded and noted. Sources: orbi:c-status, orbi:c-limits.
Alerts [partial] The usage bar turns amber at 80 percent and red at 100 percent; no budget alerts. Sources: orbi:c-limits.
Export [unsupported] No export. Sources: orbi:srch-cost.
Drilldown [partial] Monthly usage to per-task rows. Sources: orbi:c-status.
Scheduling is bounded by max_concurrency slots on one host; excess Issues wait in the queue and review work takes priority over new claims. No CPU/RAM-aware scheduling, shared check cache or deduplication.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted) · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Collaboration is GitHub's: shared Issue discussion and steering comments from any trusted (write/admin) user; there is no presence, shared live session or co-prompting UI. Comments steer the same delivery with the person attributed on GitHub.
Scope
Surfaces: GitHub Issues, labels and pull requests as the control surface · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Visibility [supported] Everyone with repository access sees labels, comments and PRs. Sources: orbi:readme, orbi:wf.
Discussion [supported] Issue comments are injected into prompts. Sources: orbi:wf.
Comments [supported] Issue and PR comments incl. inline review feedback reach the reviewer. Sources: orbi:wf.
Presence [unsupported] No presence feature. Sources: orbi:srch-team.
Coprompting [partial] Any trusted commenter can steer by comment; this is asynchronous steering with a 3-restart bound, not simultaneous prompting. Sources: orbi:wf.
Ordering [partial] Corrections are polled every 60 seconds and ordered by comment time. Sources: orbi:wf, orbi:cfg.
Conflicts [partial] A later correction restarts again until the cap; no merge of conflicting instructions. Sources: orbi:wf.
Roles come from GitHub repository permissions and the GitHub App installation (organizations become separate Cloud tenants). No SSO, org roles or provisioning in Orbi itself.
Scope
Surfaces: GitHub Issues, labels and pull requests as the control surface, Orbi Cloud: hosted GitHub App with browser status page · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Task roles [unsupported] No task roles. Sources: orbi:srch-team.
Membership [partial] Managed on GitHub; Cloud organization tenants follow the App installation. Sources: orbi:c-faq.
Sso [unsupported] No SSO in the engine; Cloud signs in with GitHub OAuth (user:email). Sources: orbi:srch-team, orbi:c-sec.
Provisioning [unsupported] No SCIM or provisioning. Sources: orbi:srch-team.
Unauthorized access [supported] Untrusted comment authors and body editors are ignored for steering and resume; recorded in the journal. Sources: orbi:wf, orbi:sec.
Revocation [supported] Uninstall the GitHub App to cut Cloud access immediately. Sources: orbi:c-sec.
Plan scope [partial] Organization installation gets its own tenant, subscription and usage. Sources: orbi:c-faq.
Approvals are GitHub's: branch protection, required reviews, and an optional human acceptance gate (ai-human-review) before review/merge. Agent commands are not approved per command: Pi runs with full access in the worktree and ops tickets receive the whole environment.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted), GitHub Issues, labels and pull requests as the control surface · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Command [unsupported] No per-command approval; no command whitelist exists. Sources: orbi:wf.
Tool [unsupported] No tool approval. Sources: orbi:wf.
Network [unsupported] No network approval or restriction. Sources: orbi:srch-container.
Secret [unsupported] No secret approval; environment is passed through. Sources: orbi:wf, orbi:pi-launch.
Delivery [supported] Human acceptance gate and GitHub required reviews gate delivery; Orbi merges as the same identity so approvals may need configuration. Sources: orbi:wf, orbi:c-sec.
Approver identity [supported] The person applies ai-human-review or approves on GitHub. Sources: orbi:wf.
Lifetime [unsupported] No temporary grants. Sources: orbi:srch-team.
Deny [partial] Close the Issue or remove labels. Sources: orbi:wf.
Revoke [supported] Revoke tokens or the GitHub App. Sources: orbi:c-sec, orbi:sec.
Tunnels [unsupported] No tunnels. Sources: orbi:srch-api.
Defaults [supported] Default is unattended full automation with human gate off; the AI never merges, the Runner does. Sources: orbi:wf, orbi:sec.
Safer modes [partial] human_review_gate and branch protection are available safer modes. Sources: orbi:wf.
Enforcement [supported] Merge-only-after-clean-verdict, head binding and merge gate are enforced in Runner code, not by prompt. Sources: orbi:sec, orbi:merge-exec.
History is the GitHub record (comments, labels, PRs, review rounds) with run markers, plus the local journal and session JSONL. Not a defined audit log: GitHub comments can be edited and journals are local.
Scope
Surfaces: GitHub Issues, labels and pull requests as the control surface, Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted) · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Review is an independent AI review session plus the human PR on GitHub; the optional acceptance checklist lists what a person still has to confirm. No Orbi review UI, keyboard model or batch UI.
Scope
Surfaces: GitHub Issues, labels and pull requests as the control surface, Orbi Cloud: hosted GitHub App with browser status page · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Any authorized person with GitHub access can take over: the work is Issue, branch and PR state, and the runner continues regardless of who is online. Local session transcripts are not shared.
Scope
Surfaces: GitHub Issues, labels and pull requests as the control surface, Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted) · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Retained outputs are the PR diff, commits, round comments, CI results and release notes on GitHub; run artifacts (plan, test log, session JSONL) stay in the local worktree. No screenshot/recording gallery.
Scope
Surfaces: GitHub Issues, labels and pull requests as the control surface, Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted) · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Gates: repository tests and coverage are expected in the dev prompt and independent review; the merge gate requires clean verdict on current head, head containing the base, CI concluded and mergeable; releases require CI green on the release commit. No spec checks.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted) · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Tests [supported] Implementer and reviewer run the repository's declared tests; CI is read at merge. Sources: orbi:wf.
Lint [partial] Whatever the repository CI runs. Sources: orbi:wf.
Types [partial] Whatever the repository CI runs. Sources: orbi:wf.
Ci [supported] Merge gate and release gate read CI conclusions; pending defers. Sources: orbi:wf.
Independent review [supported] Separate review session with verdict. Sources: orbi:wf, orbi:rounds.
Spec checks [unsupported] No spec checks. Sources: orbi:srch-misc.
Required checks [supported] Merge requires clean verdict plus CI concluded; an ordinary PR with no reported checks can still merge, test status not reported as passed. Sources: orbi:c-sec, orbi:wf.
Failure blocking [supported] Failed CI blocks merge or release; red base pauses. Sources: orbi:wf.
Requirement conflicts [unsupported] No requirement registry. Sources: orbi:srch-misc.
Configured policy [partial] Policy keys exist for clarification, steering, human gate. Sources: orbi:cfg.
Enforced policy [supported] Merge gate enforced in Runner code with head matching. Sources: orbi:merge-exec, orbi:sec.
Integrated Git/PR flow: stable branch per Issue from frozen base SHA, Runner pushes (never force), opens one PR with Fixes #N, absorbs base by plain merge, reviews and merges with the repository-allowed method, handles red CI by next review round.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted), GitHub Issues, labels and pull requests as the control surface · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Partly established: rebase unsupported; conflicts partial.
The Runner is the only merge actor (never the AI), merging the reviewed head with --match-head-commit; releases push a version commit, tag and GitHub Release by a gated state machine. No deployment step.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted), GitHub Issues, labels and pull requests as the control surface · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Approve [partial] Runner review verdict; humans approve on GitHub or via ai-human-review. Sources: orbi:wf.
Merge [supported] Runner merges after clean verdict and merge gate. Sources: orbi:sec.
Release [supported] Release task state machine creates tag and GitHub Release. Sources: orbi:wf.
Deploy [unsupported] No deployment feature; ops tickets can run deploys at the ticket's direction. Sources: orbi:wf.
Exact revision [supported] Verdict head must equal PR head; --match-head-commit. Sources: orbi:sec.
Authority enforcement [supported] Branch protection and rulesets remain the final boundary; Cloud notes the self-approval limitation. Sources: orbi:sec, orbi:c-sec.
Delivery evidence links Issue, PR, merge commit and release via Fixes #N, merged receipt comments and release notes with per-item evidence. No task rollback command; reviews bind to the head SHA and a changed head requires re-review.
Scope
Surfaces: GitHub Issues, labels and pull requests as the control surface, Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted) · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Build links [partial] CI checks on the PR/release commit. Sources: orbi:wf.
Deployment links [unsupported] No deployment links. Sources: orbi:srch-misc.
Delivery status [supported] ai-merged and the merged receipt. Sources: orbi:wf.
Retained evidence [supported] Release notes carry scope, gate and test evidence. Sources: orbi:wf.
Rollback [unsupported] No rollback feature. Sources: orbi:srch-misc.
Revert [unsupported] No revert command. Sources: orbi:srch-misc.
Stale approval invalidation [supported] A head change requires review again; a saved clean review is reused only when head and rendered Issue body hash match. Sources: orbi:wf.
No batch review queue beyond the label states and the Cloud task list; each delivery is reviewed and merged automatically one at a time. Milestones group releases.
Scope
Surfaces: GitHub Issues, labels and pull requests as the control surface, Orbi Cloud: hosted GitHub App with browser status page · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Engine: AGPL-3.0 (LICENSE) or alternatively the Sustainable Use License v1.0 (dual licence, choose either). Orbi Cloud server is closed; Cloud docs repo and website repo are public.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted), Orbi Cloud: hosted GitHub App with browser status page · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Client license [supported] The CLI/engine is AGPL-3.0 or SUL v1.0; the Claude plugin manifest says AGPL-3.0-only. Sources: orbi:license-file, orbi:licdoc, orbi:plugin.
Server license [supported] There is no separate server in self-hosting; the engine is the control plane under the same dual licence. Sources: orbi:licdoc.
Hosted extensions [unknown] Orbi Cloud's platform code is not public; its licence is not published.
Source visibility [supported] Engine, Cloud docs and website repositories are public; the orbi-cloud repository is not. Sources: orbi:repoapi.
Source revision [supported] Tag v0.7.45 at commit 892f350. Sources: orbi:releases.
Hosted parity [unknown] Cloud runs the engine plus closed platform code; parity cannot be verified.
Self-hosting is the product: the engine runs on your machine with only GitHub and a model provider as external services; state lives in your GitHub repository. Cloud depends on the vendor and Stripe.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted), Orbi Cloud: hosted GitHub App with browser status page · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Partly established: import partial.
8 atomic answers
Self hosting [supported] Free under either licence; Python package, one-line installer, Docker image. Sources: orbi:readme, orbi:licdoc.
Vendor dependencies [supported] No Orbi service is required; GitHub and a model endpoint are. Sources: orbi:sec.
Export [supported] Data is already in GitHub issues, PRs and git. Sources: orbi:readme.
Import [partial] Existing GitHub Issues can be labelled; no other importer. Sources: orbi:wf.
Formats [supported] Standard git, GitHub objects and TOML config; hidden JSON markers. Sources: orbi:pubc.
Cancellation [supported] Cloud: cancel through Stripe; connections and history are kept and uninstalling the App is separate. Sources: orbi:c-billing.
Account independence [supported] Everything works without an Orbi account when self-hosting. Sources: orbi:readme.
History portability [supported] History stays in the repository. Sources: orbi:readme.
Self-hosted: code and prompts go from your machine to GitHub and your chosen model endpoint; no engine telemetry in code. Cloud: prompts and repository context go to the default DeepSeek model unless BYOK; key AES-256-GCM encrypted; data handled per the Cloud privacy policy.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted), Orbi Cloud: hosted GitHub App with browser status page · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Code data [supported] Self-host: local plus GitHub plus model provider. Cloud: per-tenant environment. Sources: orbi:sec, orbi:c-sec.
Prompts [supported] Sent to the configured model; the Cloud default is DeepSeek. Sources: orbi:site-privacy.
Credentials [supported] Local .orbi/env and gh; Cloud BYOK encrypted and masked. Sources: orbi:sec, orbi:c-sec.
Logs [supported] Local journal; Cloud says keys are never logged. Sources: orbi:ops, orbi:c-sec.
Artifacts [supported] Worktrees local, PRs on GitHub. Sources: orbi:ops.
Retention [partial] Worktree retention windows self-host; Cloud deletion on request via Telegram or privacy email. Sources: orbi:cfg, orbi:site-privacy.
Deletion [partial] Cloud deletion on request, GitHub and Stripe records remain. Sources: orbi:site-privacy.
Training [unknown] Neither Orbi nor the default provider's training terms are stated in the checked docs.
Residency [unknown] No residency statement.
Subprocessors [partial] Privacy policy names Stripe and DeepSeek; a full list was not found. Sources: orbi:site-privacy.
Telemetry disclosure [supported] No telemetry in engine code per bounded search; Cloud privacy policy discloses data uses. Sources: orbi:srch-tele, orbi:site-privacy.
Telemetry defaults [supported] Nothing is sent by default in the engine; Telegram is off until configured. Sources: orbi:srch-tele, orbi:cfg.
Telemetry controls [unsupported] No telemetry controls because none exist in the engine. Sources: orbi:srch-tele.
Consent prompt [unsupported] No consent prompt documented. Sources: orbi:srch-tele.
Provider separation [supported] Model provider policies are separate and under the user's provider account (BYOK). Sources: orbi:prov, orbi:c-model.
Self-hosted engine is free. Orbi Cloud: Free (3 merged deliveries, no card), Solo US$29/month (US$290/year, 400M tokens, 1 repo), Pro US$79/month (US$790/year, 1.2B tokens, 5 repos); no per-token overage; FOUNDING50 gives 50% for life (6 places). Own-key use allowed on any plan.
Scope
Surfaces: Orbi Cloud: hosted GitHub App with browser status page, Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted) · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
No scenario pricing. Self-hosting costs host plus model tokens; Cloud allowances are expressed in tokens with the vendor's measured delivery ranges, not as one, two or five-developer workloads.
Scope
Surfaces: Orbi Cloud: hosted GitHub App with browser status page · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
One person [partial] Solo US$29/month covers one repo and 400M tokens; the number of tasks it buys depends on repository size. Sources: orbi:c-billing, orbi:site-pricing.
Two people [partial] Plans are per tenant/account; two collaborators can share one subscription, not priced per user. Sources: orbi:c-billing.
Five people [partial] Pro covers five repositories, not five developers. Sources: orbi:c-billing.
Task assumptions [unknown] The catalog does not invent task volumes.
Concurrency [unknown] Cloud concurrency is not stated.
Tokens [partial] Allowances 400M and 1.2B tokens/month. Sources: orbi:c-limits.
Compute hours [unknown] Compute hours are not itemized.
Fixed cost [supported] US$29 or US$79 per month on monthly billing. Sources: orbi:site-pricing.
Included cost [supported] Tokens and compute are included. Sources: orbi:c-billing.
Unknown cost [partial] Cost per task is unknown; the site publishes measured delivery counts that the catalog did not verify. Sources: orbi:site-pricing.
Open-source engine with very frequent releases (v0.7.40 to v0.7.45 in eight days); Cloud has a public status page link, Telegram group and support email; Cloud billing questions go to support@orbi.build. No response commitments found.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted), Orbi Cloud: hosted GitHub App with browser status page · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Free ways in: the AGPL/SUL engine is free to self-host (you pay model and host), and Orbi Cloud gives three merged deliveries free without a card plus BYOK on any plan.
Scope
Surfaces: Orbi engine: orbi CLI plus systemd/launchd timer runner (self-hosted), Orbi Cloud: hosted GitHub App with browser status page · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Ongoing free [partial] Self-hosting is free forever; Cloud free tier is limited to three merged deliveries. Sources: orbi:licdoc, orbi:c-billing.
Trial [supported] Three merged deliveries free. Sources: orbi:c-billing.
Credits trial [unsupported] Not a credit trial; deliveries are counted. Sources: orbi:c-limits.
Self host cost [supported] Host plus model and gh access. Sources: orbi:readme.
Paid only [unsupported] Not paid-only. Sources: orbi:c-billing.
Early access [partial] Founding member 50% offer limited to 6 places. Sources: orbi:c-billing.
Free scenarios [partial] Free covers BYO subscription/API and self-hosted remote; mobile and collaboration are GitHub's. Sources: orbi:prov, orbi:c-model.
Card required [supported] No card for the free tier. Sources: orbi:c-billing.
Usage caps [supported] Three merged deliveries; one repository. Sources: orbi:c-limits.
Paid evaluation [unsupported] Meaningful evaluation needs no payment. Sources: orbi:c-billing.
Cloud pricing is transparent on the website data (price, tokens, repository counts, no overage, cancellation through Stripe) but compute and model markup are not itemized; the self-hosted engine has no price.
Scope
Surfaces: Orbi Cloud: hosted GitHub App with browser status page · Version: v0.7.45 (commit 892f350, released 2026-11-16); Orbi Cloud docs commit d33c2ee (2026-11-11) · Plan: Self-hosted engine (AGPL-3.0 or Sustainable Use License) and Orbi Cloud (Free, Solo, Pro) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
GitHub Issue labelled ai-ready to Pi implementation in a worktree, PR, independent review, merge, release; GitHub Issues are the only state store (no database, queue or daemon); systemd/launchd timer ticks every 5 minutes; AGPL-3.0 or Sustainable Use License; Orbi Cloud offered.
Seven delivery states via labels, bounded review/fix loop, steering by comment, epics via native sub-issues, release state machine, blocked-by queueing, repository policy file.
Kind
documented
Locator
The complete chain; Steering; Delivery labels; Epics, Release tasks and P0; blocked by; .github/orbi.toml
No install needed; GitHub App on private repos and organizations; dependent Issues via blocked by; steering up to 3 restarts; merge without approval unless branch protection requires one.
No desktop app, mobile app, editor extension or web UI in the engine repo; matches only a test ratchet tool and the optional metrics exporter HTTP server; Windows only appears in Pi idle handling comments. Orbi Cloud has its own browser status page documented separately.
Sessions start the Pi executable with provider/model/thinking flags and the Runner environment minus ORBI_TELEGRAM_BOT_TOKEN; no container or sandbox wrapper.
Kind
source-inspected
Locator
pi_process.py env filter at line 681 (drops ORBI_TELEGRAM_BOT_TOKEN); the --no-extensions flag is set in src/orbi/pi_command.py line 65
No adapter for another coding agent CLI; only Pi is launched (pi_executable must accept Pi flags). Codex and ChatGPT are reachable as model providers through Pi.
Runner is the only merge actor, merges the reviewed head with --match-head-commit; no sandbox; secrets local; credential-routing keys host-only; no task DAG, multi-agent parallelism or policy engine.
Kind
documented
Locator
Delivery boundaries; The AI never merges; Local state files; Repository-level config trust
No webhook receiver, MCP server, HTTP API or SDK in the engine; the only MCP mention is a note about the pi-mcp-adapter Pi package; automation surface is the orbi CLI, GitHub labels and comments.
No repository indexing or embedding feature, no screenshot/recording capture, no cross-task memory store and no task revert command in the engine; matches are unrelated (CI triage text, KV-cache note, engine install rollback).
Per-tenant separate OS user environment; BYOK key AES-256-GCM at rest; repository access limited to the GitHub App installation; Orbi merges as the same App identity.
Kind
documented
Locator
Isolation between tenants; Where your model key lives; Branch protection
Only the five-minute timer tick; no cron-style task scheduler or event trigger besides labels polled on each tick (Orbi Cloud wakes the runner when ai-ready is added, per its FAQ).
The engine spawns Pi directly on the host as the Runner user in a git worktree; no per-task container, VM or OS sandbox. Docker is only a community wrapper around the whole runner.
No SSO, roles, presence or multi-user session features; authorization relies on GitHub repository permission (admin/write) for trusted comments and steering.
v0.7.45 published 2026-11-16 is the latest release at retrieval; releases are tags with notes and no binary assets; v0.7.40 to v0.7.45 shipped in eight days.
Cloud sends prompts and repository context to the default model (DeepSeek deepseek-flash) unless a customer key is configured; Stripe processes payments; deletion by request.
No telemetry or analytics code or documentation in the engine repo; outbound calls are GitHub (gh), the model endpoint, Telegram when configured, and the engine source update channel.