podium

Orbi

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.

Rubric
0.3 · 51 criteria
Source checks
2026-11-17
Agent cross-checked
50 criteria
Comparisons
1

Access and agent choice

ACC-01

Client access

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: desktop_os unsupported; mobile_apps unsupported; browser partial; editor_extensions partial; task_actions partial; notifications partial.
9 atomic answers
  • 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.
  • Cli [supported] orbi CLI with add, suggest, draft, status, session, setup, doctor, check, install-units, milestone, notify and ticket subcommands. Sources: orbi:pubc, orbi:ops.
  • 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.

Sources: orbi:readme, orbi:gs, orbi:srch-clients, orbi:c-faq, orbi:c-status, orbi:pubc, orbi:ops, orbi:plugin, orbi:wf, orbi:cfg, orbi:c-notif

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: harnesses partial; custom_adapters partial; mixed_harness_operation unsupported.
5 atomic answers
  • 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.

Sources: orbi:gs, orbi:cfg, orbi:srch-agents, orbi:prov, orbi:opencode, orbi:pi-launch, orbi:ops

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: vendor_credits partial; account_switching partial; provider_restrictions unknown.
7 atomic answers
  • 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.

Sources: orbi:prov, orbi:c-model, orbi:c-billing, orbi:c-limits, orbi:dock, orbi:cfg, orbi:gs, orbi:c-faq

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: no_git unsupported; local_git_without_remote unsupported; byo_vps_onboarding partial.
7 atomic answers
  • 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.
  • Managed cloud setup [supported] Orbi Cloud five-step setup: sign in, install GitHub App, connect repository, prepare environment (10-20 seconds), write first request. Sources: orbi:c-prov, orbi:c-status.
  • 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.

Sources: orbi:gs, orbi:c-prov, orbi:readme, orbi:ops, orbi:sec, orbi:c-status, orbi:dock

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: api unsupported; sdk unsupported; mcp_server unsupported; webhooks unsupported; operations partial.
8 atomic answers
  • 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.

Sources: orbi:pubc, orbi:ops, orbi:srch-api, orbi:plugin, orbi:timer, orbi:wf, orbi:sec

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: mcp_client partial; custom_tools partial; authentication partial; permission_scope unsupported.
7 atomic answers
  • 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.

Sources: orbi:cfg, orbi:srch-api, orbi:ops, orbi:wf, orbi:pi-launch, orbi:sec, orbi:gs

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: desktop_implementation unsupported; mobile_implementation unsupported; hybrids unsupported; implementation_evidence partial.
4 atomic answers
  • 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.

Sources: orbi:gs, orbi:srch-clients, orbi:c-status

Planning and context

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: external_import partial; chat_git_triggers partial; supported_edits partial; external_roundtrips partial.
9 atomic answers
  • 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.
  • Stable ids [supported] GitHub Issue numbers; branch orbi/<owner>-<repo>-issue-<N>. Sources: orbi:pubc.
  • 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.

Sources: orbi:wf, orbi:pubc, orbi:ops, orbi:c-status, orbi:srch-api, orbi:readme, orbi:sec

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: plans partial; editors partial; revisions partial.
7 atomic answers
  • 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.
  • 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.

Sources: orbi:wf, orbi:readme, orbi:ops, orbi:pubc, orbi:cfg

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: hierarchy partial; state_propagation partial; identity_retention partial.
9 atomic answers
  • Epics [supported] Epic = ai-epic Issue never claimed; completion reconciled from native sub-issues each tick. Sources: orbi:wf.
  • Hierarchy [partial] Native sub-issues (GitHub depth limits apply); milestones group releases. Sources: orbi:wf.
  • 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.

Sources: orbi:wf, orbi:claim, orbi:pubc

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: memory unsupported; scope partial; provenance partial; correction partial; deletion partial; freshness partial.
10 atomic answers
  • 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.

Sources: orbi:cfg, orbi:wf, orbi:plugin, orbi:srch-misc, orbi:sec, orbi:ops, orbi:pubc

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: code_search partial; indexing unsupported; external_knowledge unsupported; multimodal_inputs unsupported; freshness partial; access_scope partial; api_retrieval unsupported; citations unsupported; conflict_detection partial; review_enforcement partial.
10 atomic answers
  • 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.

Sources: orbi:wf, orbi:ops, orbi:srch-misc, orbi:cfg, orbi:sec, orbi:c-sec, orbi:srch-api, orbi:c-faq

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: edit partial; prioritize partial; assign partial; search partial; filter partial; archive partial; reopen partial; project_epic_views partial; metadata partial.
17 atomic answers
  • Create [supported] orbi add / draft / suggest and the Cloud Write a request create Issues; GitHub creates too. Sources: orbi:ops, orbi:pubc.
  • Edit [partial] Issue edit is on GitHub; body edits steer an active delivery. Sources: orbi:wf.
  • Discuss [supported] Issue comments are the discussion and are injected into prompts when authors are trusted. Sources: orbi:wf.
  • Prioritize [partial] p0 and bug labels order pickup; otherwise oldest first; no priority numbers. Sources: orbi:wf.
  • Label [supported] Delivery, type (ops/content/release) and p0 labels are used. Sources: orbi:wf.
  • Assign [partial] The Runner claims by label; no human or agent assignee model. Sources: orbi:wf.
  • Filter [partial] GitHub label/milestone filters; orbi status --repo/--issue. Sources: orbi:ops.
  • Archive [partial] Closing the Issue; ai-merged is terminal. Sources: orbi:wf.
  • Reopen [partial] Reopen on GitHub; a blocked Issue is re-dispatched by relabelling. Sources: orbi:ops.
  • Project epic views [partial] GitHub sub-issue/milestone views; Cloud project overview and task history tabs. Sources: orbi:c-status.
  • Idea parking [supported] An Issue without ai-ready is parked; ai-needs-detail parks a thin ticket. Sources: orbi:wf.
  • Explicit dispatch [supported] Adding ai-ready dispatches. Sources: orbi:wf.
  • Task session separation [supported] Issue (task) is separate from run_id attempts, sessions and PRs; a retry creates a new run. Sources: orbi:pubc.
  • Metadata [partial] Labels, milestone, run markers and hidden scene JSON; no custom fields. Sources: orbi:pubc.
  • Durable states [supported] Seven label states persisted on GitHub plus scene block. Sources: orbi:wf.
  • External tracker requirement [supported] GitHub Issues are required and are the tracker. Sources: orbi:readme.

Sources: orbi:wf, orbi:c-status, orbi:ops, orbi:pubc, orbi:readme

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: assign unsupported; attribution partial; conflicts partial.
14 atomic answers
  • Shared ids [supported] GitHub issue numbers are the shared IDs. Sources: orbi:pubc.
  • Read [supported] The Runner reads body, trusted comments, labels and blockers. Sources: orbi:wf.
  • Create [supported] The Runner creates child Issues (split), repair Issues (fix-base), draft Issues and release/milestone confirmation Issues. Sources: orbi:wf, orbi:pubc.
  • Update [supported] It appends acceptance criteria, edits labels and posts comments. Sources: orbi:wf.
  • Claim [supported] Claim = swapping ai-ready for ai-in-progress with a worktree and run marker. Sources: orbi:wf.
  • Assign [unsupported] No assignee assignment; claim is by label. Sources: orbi:wf.
  • State changes [supported] Runner drives all delivery label transitions; humans apply ai-human-review. Sources: orbi:wf.
  • Dependencies [supported] Split creates native blockedBy dependencies between children. Sources: orbi:wf.
  • 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.
  • Permissions [supported] GitHub token scopes; trusted-author rule uses repository permission admin/write. Sources: orbi:sec.
  • Conflicts [partial] Dead-loop guard, idempotent comments and fail-closed epic reconciliation; no general conflict resolution UI. Sources: orbi:wf.

Sources: orbi:wf, orbi:pubc, orbi:c-status, orbi:c-sec, orbi:sec

Agent cross-checked unsupported

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.
  • Later retrieval [unsupported] Context files are re-injected but no spec retrieval exists. Sources: orbi:srch-misc.
  • Drift detection [unsupported] No drift detection. Sources: orbi:srch-misc.
  • Review integration [unsupported] Review reads the Issue and repository contract, not a spec registry. Sources: orbi:srch-misc, orbi:wf.

Sources: orbi:srch-misc, orbi:cfg, orbi:wf

Coordination and automation

COORD-01

Parallel work

Agent cross-checked partial

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.

Sources: orbi:ops, orbi:cfg, orbi:c-limits, orbi:wf, orbi:cli-status, orbi:c-status

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: human_assignment unsupported; agent_assignment unsupported; routing partial.
7 atomic answers
  • 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.

Sources: orbi:wf, orbi:ops, orbi:sec

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: roles partial; model_harness_effort partial; messages partial; cross_harness unsupported; live_progress partial.
12 atomic answers
  • 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.
  • Cross harness [unsupported] Only Pi. Sources: orbi:srch-agents.
  • Orchestration owner [supported] The Runner (product code) owns the pipeline; not a model-led coordinator. Sources: orbi:sec.
  • Activation [supported] Always active for a delivery; reviewer overrides are config keys. Sources: orbi:cfg.
  • Authentication [supported] Same Runner credentials. Sources: orbi:sec.
  • Live progress [partial] Progress comments and orbi session/status --follow; Cloud shows the latest reported activity. Sources: orbi:ops, orbi:c-status.
  • Retained results [supported] Session JSONL stays in the worktree; round comments stay on GitHub; failed worktrees are retained. Sources: orbi:ops.
  • Followup [supported] Next tick resumes the same run; humans can relabel ai-fix-needed. Sources: orbi:wf, orbi:ops.
  • Invocation [supported] No invocation needed. Sources: orbi:wf.

Sources: orbi:wf, orbi:sec, orbi:cfg, orbi:pubc, orbi:srch-agents, orbi:ops, orbi:c-status

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: schedules partial; events partial; recurring_tasks unsupported.
8 atomic answers
  • 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.

Sources: orbi:timer, orbi:wf, orbi:srch-sched, orbi:c-faq, orbi:c-prov, orbi:ops, orbi:rounds

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: pause partial; stop partial; notifications partial; escalation partial; chat_terminal_parity unsupported.
10 atomic answers
  • 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.

Sources: orbi:wf, orbi:cfg, orbi:ops, orbi:c-faq, orbi:c-notif, orbi:pubc, orbi:sec

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: parent_child partial; dependencies partial; workload partial; fixture_mode partial.
8 atomic answers
  • 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.

Sources: orbi:c-status, orbi:cli-status, orbi:wf, orbi:exporter

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: presets partial; natural_language partial; agent_configuration partial; in_run_changes partial; live_roles partial; auth_friction partial.
10 atomic answers
  • Quick task [supported] A single labelled Issue is enough. Sources: orbi:wf.
  • Growing epic [supported] A thin ticket can become an Epic via /orbi split. Sources: orbi:wf.
  • Presets [partial] Ticket-type labels and repository policy keys; no named presets. Sources: orbi:wf.
  • Natural language [partial] orbi draft is conversational for Issues; workflow itself is not configured by language. Sources: orbi:pubc.
  • Agent configuration [partial] Provider, model and thinking per implementer and reviewer. Sources: orbi:cfg.
  • In run changes [partial] Steering restarts the session; config changes apply from the next tick. Sources: orbi:wf, orbi:cfg.
  • Live roles [partial] orbi status shows role and phase; Cloud shows the three steps. Sources: orbi:cli-status, orbi:c-status.
  • Retained relationships [supported] Run id ties branch, worktree, PR and comments. Sources: orbi:pubc.
  • Discoverability [supported] Docs site, orbi doctor and orbi check explain the pipeline. Sources: orbi:ops.
  • Auth friction [partial] Needs gh, Pi login and model credentials once. Sources: orbi:gs.

Sources: orbi:wf, orbi:cfg, orbi:pubc, orbi:cli-status, orbi:c-status, orbi:ops, orbi:gs

Execution and reliability

Agent cross-checked partial

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.
  • Provisioning [supported] Self-host: orbi setup; Cloud: automatic in 10-20 seconds. Sources: orbi:gs, orbi:c-prov.
  • Payer [supported] Self-host: you pay host and model; Cloud: Orbi plan, tokens included, BYOK optional. Sources: orbi:c-billing.
  • Resources [unknown] Cloud environment CPU, RAM and disk sizes are not published.
  • Region [unknown] Cloud hosting region is not stated.
  • Expiry [partial] No documented task lifetime; self-host worktrees retained 72 hours after the Issue closes (worktree_retain_hours). Sources: orbi:cfg, orbi:c-prov.
  • Client disconnect [supported] No client is required; the timer runs the work. Sources: orbi:timer.
  • Other device continuation [supported] Observe and steer from any device through GitHub or the Cloud page. Sources: orbi:c-status.

Sources: orbi:readme, orbi:c-prov, orbi:gs, orbi:dock, orbi:c-sec, orbi:c-billing, orbi:cfg, orbi:timer, orbi:c-status

Agent cross-checked partial

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.
  • Os sandbox [unsupported] No OS sandbox; Pi runs as the Runner user. Sources: orbi:srch-container, orbi:pi-launch.
  • 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.

Sources: orbi:ops, orbi:sec, orbi:cfg, orbi:pubc, orbi:srch-container, orbi:dock, orbi:pi-launch, orbi:c-sec, orbi:wf

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: expiry partial; process_reconnect unsupported; context_loss partial; manual_repair partial.
12 atomic answers
  • Client disconnect [supported] No client dependency. Sources: orbi:timer.
  • Worker crash [supported] Leftover ai-in-progress is resumed by the next tick with the same run id. Sources: orbi:ops.
  • Service restart [supported] The timer restarts ticks; state is on GitHub. Sources: orbi:ops, orbi:wf.
  • Expiry [partial] No sandbox expiry; closed-Issue worktrees are reclaimed after retention. Sources: orbi:ops, orbi:cfg.
  • Transcript reload [supported] orbi session prints the live JSONL path. Sources: orbi:ops.
  • Process reconnect [unsupported] A dead Pi process is not reattached; the run restarts a session. Sources: orbi:ops.
  • Task resume [supported] Same run, branch, worktree and PR resume. Sources: orbi:wf.
  • State reconstruction [supported] Scene block and branch rebuild a worktree. Sources: orbi:wf, orbi:pubc.
  • Context loss [partial] A restarted Pi session may lose in-session context; the Issue timeline and PR carry decisions. Sources: orbi:wf.
  • Duplicate actions [supported] Stable branch, idempotent comments, failure fingerprint dedup and dead-loop guard limit duplicates. Sources: orbi:wf.
  • Manual repair [partial] ai-blocked requires a person to relabel or fix. Sources: orbi:ops.
  • Multi day continuity [supported] No task timeout and state on GitHub. Sources: orbi:sec.

Sources: orbi:wf, orbi:ops, orbi:timer, orbi:cfg, orbi:pubc, orbi:sec

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: dependencies partial; caches unsupported; snapshots unsupported; services unsupported; ports unsupported; secrets partial; duplicate_installs unsupported; collisions unsupported; automatic_repair partial.
10 atomic answers
  • 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.
  • Ports [unsupported] No port allocation. 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.

Sources: orbi:ops, orbi:srch-misc, orbi:srch-container, orbi:sec, orbi:gs

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: time_limits unsupported; turn_limits partial; token_limits partial; spend_limits unsupported; timeouts partial; enforcement partial.
8 atomic answers
  • Time limits [unsupported] The security page says there is no business task timeout. Sources: orbi:sec.
  • Turn limits [partial] Review rounds (5) and steering restarts (3) are bounded; model turns are not. Sources: orbi:rounds, orbi:cfg.
  • Token limits [partial] Cloud monthly token allowance; none on the engine. Sources: orbi:c-limits.
  • Spend limits [unsupported] No spend limit in the engine. Sources: orbi:srch-cost.
  • Timeouts [partial] model_wait_dead_seconds (1800) and swallowed-request probe; release CI waits 1800s. Sources: orbi:cfg.
  • Retries [supported] One automatic transient re-queue; failure comments dedupe. Sources: orbi:wf.
  • Provider failures [supported] Idle recovery windows, pi_recovery and failure classification; blocked after cap. Sources: orbi:gs, orbi:ops.
  • Enforcement [partial] Round/steering bounds are enforced; Cloud quotas pause new claims only. Sources: orbi:rounds, orbi:c-limits.

Sources: orbi:wf, orbi:cfg, orbi:sec, orbi:rounds, orbi:c-limits, orbi:srch-cost, orbi:gs, orbi:ops

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: traces partial; usage_export unsupported; task_stats partial; agent_stats unsupported; project_stats partial; time_stats partial; performance_method unknown; responsiveness unknown.
13 atomic answers
  • Logs [supported] Journal lines start with [run_id] with stable event names. Sources: orbi:ops, orbi:pubc.
  • Traces [partial] Session JSONL and run_id correlation; no trace format. Sources: orbi:ops.
  • Failure reasons [supported] Structured failure comments and journal reasons. Sources: orbi:wf, orbi:pubc.
  • Usage export [unsupported] No usage export in the engine. Sources: orbi:srch-cost.
  • Task stats [partial] Cloud task rows show elapsed, calls and tokens; engine has journal run duration. Sources: orbi:c-status.
  • Agent stats [unsupported] No per-agent stats. Sources: orbi:srch-cost.
  • Project stats [partial] Cloud monthly usage and the Grafana dashboard by repo. Sources: orbi:c-status, orbi:exporter.
  • Time stats [partial] Grafana panels for run duration; Cloud monthly usage. Sources: orbi:exporter.
  • Failure status [supported] ai-blocked/ai-fix-needed with reasons. Sources: orbi:wf.
  • Approval status [supported] ai-awaiting-merge and ai-human-review labels. Sources: orbi:wf.
  • Reconnect consistency [supported] State is derived from GitHub on each tick. Sources: orbi:wf.
  • Performance method [unknown] Orbi site reports its own measurements; the catalog measures none and those figures are not verified here.
  • Responsiveness [unknown] No catalog measurement; the Cloud status page observes about every 15 seconds. Sources: orbi:c-status.

Sources: orbi:ops, orbi:exporter, orbi:pubc, orbi:wf, orbi:srch-cost, orbi:c-status

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: task_cost partial; session_cost unsupported; child_cost unsupported; epic_cost unsupported; harness_aggregation unsupported; billed_vs_estimated partial; provider_reconciliation unsupported; compute_cost unsupported; refresh_delay partial; alerts partial; export unsupported; drilldown partial.
14 atomic answers
  • Task cost [partial] Cloud shows per-task tokens, not currency. Sources: orbi:c-status.
  • 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.

Sources: orbi:c-status, orbi:c-limits, orbi:srch-cost, orbi:srch-agents, orbi:c-billing

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: cpu_ram unsupported; host_awareness unsupported; check_reuse partial; check_deduplication unsupported; bounded_tests partial; cancellation partial; fairness partial.
12 atomic answers
  • Concurrency [supported] max_concurrency 1-5 slots. Sources: orbi:ops, orbi:cfg.
  • Queues [supported] ai-ready queue, oldest first with p0/bug precedence. Sources: orbi:wf.
  • Cpu ram [unsupported] No CPU or RAM limits; docs say measure before raising concurrency. Sources: orbi:cfg, orbi:srch-container.
  • Backpressure [supported] capacity_full means exit without claiming; CI-pending deliveries are skipped. Sources: orbi:ops, orbi:wf.
  • Host awareness [unsupported] No host resource awareness. Sources: orbi:srch-container.
  • Check reuse [partial] A clean review is reused after a deferred merge when head and Issue body hash match. Sources: orbi:wf.
  • Check deduplication [unsupported] No cross-task check deduplication. Sources: orbi:srch-misc.
  • Bounded tests [partial] Tests are the repository's; the Runner waits on CI with bounded gates and does not run local release tests. Sources: orbi:wf.
  • Cancellation [partial] Close the Issue; no kill command. Sources: orbi:ops.
  • Fairness [partial] Oldest-first within priority class; waiting merges yield to other work. Sources: orbi:wf.
  • Recovery [supported] Locks are released by the kernel on exit; resume scans pick up work. Sources: orbi:ops.
  • Shared limits [supported] Slots are shared across repositories served by the same runner. Sources: orbi:ops, orbi:wf.

Sources: orbi:ops, orbi:wf, orbi:cfg, orbi:srch-container, orbi:srch-misc

Human collaboration and control

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: presence unsupported; coprompting partial; ordering partial; conflicts partial.
11 atomic answers
  • 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.
  • Attribution [supported] GitHub authorship. Sources: orbi:wf.
  • Permissions [supported] Only logins with admin/write (or the runner account) can steer. Sources: orbi:wf, orbi:sec.
  • Plan restrictions [supported] No plan gating on steering in self-host; Cloud plans limit repositories and tokens only. Sources: orbi:c-limits.
  • Owner online [supported] The runner works without anyone online. Sources: orbi:timer.

Sources: orbi:wf, orbi:readme, orbi:srch-team, orbi:cfg, orbi:sec, orbi:c-limits, orbi:timer

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: organization_roles unsupported; project_roles partial; task_roles unsupported; membership partial; sso unsupported; provisioning unsupported; plan_scope partial.
9 atomic answers
  • Organization roles [unsupported] No Orbi-defined organization roles. Sources: orbi:srch-team.
  • Project roles [partial] GitHub repository permission levels determine trusted comment authors. Sources: orbi:sec.
  • 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.

Sources: orbi:sec, orbi:c-faq, orbi:srch-team, orbi:c-sec, orbi:wf

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: command unsupported; tool unsupported; network unsupported; secret unsupported; lifetime unsupported; allow partial; deny partial; tunnels unsupported; safer_modes partial.
14 atomic answers
  • 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.
  • Allow [partial] Allow = apply label or merge approval. Sources: orbi:wf.
  • 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.

Sources: orbi:wf, orbi:sec, orbi:srch-container, orbi:pi-launch, orbi:c-sec, orbi:srch-team, orbi:srch-api, orbi:merge-exec

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: edits partial; export partial; mutability partial; retention partial; integrity unsupported.
11 atomic answers
  • Actions [supported] Orbi actions are comments and label changes under the runner identity. Sources: orbi:pubc.
  • Approvals [supported] Human-review label and PR approvals on GitHub. Sources: orbi:wf.
  • Edits [partial] GitHub edit history for Issue/PR text. Sources: orbi:wf.
  • Discussion [supported] Issue and PR threads. Sources: orbi:wf.
  • Decisions [supported] Review verdicts and merged receipts, milestone decisions. Sources: orbi:pubc.
  • Cross user persistence [supported] GitHub keeps them for all users. Sources: orbi:readme.
  • Cross session persistence [supported] Scene and comments span sessions. Sources: orbi:pubc.
  • Export [partial] GitHub export tools; local journal readable; no Orbi export command. Sources: orbi:ops.
  • Mutability [partial] Comments can be edited or deleted by GitHub authorized users; journal files are local. Sources: orbi:ops.
  • Retention [partial] GitHub retention; local worktrees reclaimed after 72 hours post-close by default. Sources: orbi:cfg.
  • Integrity [unsupported] No integrity guarantee, so it is not called an audit log. Sources: orbi:sec.

Sources: orbi:pubc, orbi:ops, orbi:wf, orbi:readme, orbi:cfg, orbi:sec

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: change_understanding partial; evidence_navigation partial; effort partial; missed_evidence partial; keyboard unknown; narrow_screen partial; context_switching partial.
13 atomic answers
  • Pending reviews [supported] ai-pr-opened, ai-awaiting-merge and ai-human-review labels; Cloud lists Under review. Sources: orbi:wf, orbi:c-status.
  • Change understanding [partial] PR body links Issue and run; review round comments summarize findings; the checklist lists evidence. Sources: orbi:wf.
  • Evidence navigation [partial] Round comments cite files and lines; CI check status in checklist. Sources: orbi:wf.
  • Comments [supported] Human feedback on the PR is fed to the reviewer. Sources: orbi:wf.
  • Request changes [supported] A formal review or inline comment on the PR goes into the next review round. Sources: orbi:wf.
  • Shipping guidance [supported] Comments name the one maintainer action for ai-awaiting-merge. Sources: orbi:wf.
  • Effort [partial] Column 2 lists the machine-unverifiable minimum, aiming for none. Sources: orbi:wf.
  • Missed evidence [partial] Missing-evidence items appear when head checks have not passed. Sources: orbi:wf.
  • Keyboard [unknown] GitHub provides review keyboard support; Orbi adds none and documents none.
  • Narrow screen [partial] Cloud page is phone-usable; GitHub mobile for PR. Sources: orbi:c-status.
  • Context switching [partial] Cloud links to the Issue and PR. Sources: orbi:c-status.
  • Roles [supported] Implementer and reviewer sessions are separate. Sources: orbi:wf.
  • Retained context [supported] Round comments and the scene persist. Sources: orbi:pubc.

Sources: orbi:wf, orbi:c-status, orbi:pubc

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: session_history partial; runtime_context partial; ownership partial; context_loss partial; harness_transfer unsupported.
12 atomic answers
  • Ongoing takeover [supported] A person can push to the task branch or steer; an external-takeover scan handles outside PRs. Sources: orbi:wf.
  • Same task [supported] Same Issue and PR. Sources: orbi:wf.
  • Session history [partial] Round comments and Issue timeline; Pi JSONL stays on the host. Sources: orbi:ops.
  • Decisions [supported] Recorded in comments. Sources: orbi:wf.
  • Artifacts [supported] Branch and PR. Sources: orbi:wf.
  • Permissions [supported] GitHub permissions. Sources: orbi:sec.
  • Runtime context [partial] Worktree is local; it is rebuilt from the remote branch. Sources: orbi:ops.
  • Owner disconnect [supported] No owner session exists. Sources: orbi:timer.
  • Ownership [partial] Ownership is the runner claim; humans change labels. Sources: orbi:wf.
  • Attribution [supported] GitHub authorship. Sources: orbi:wf.
  • Context loss [partial] Pi session context is lost on a new session. Sources: orbi:wf.
  • Harness transfer [unsupported] Single harness; a different model is a config change. Sources: orbi:srch-agents.

Sources: orbi:wf, orbi:ops, orbi:sec, orbi:timer, orbi:srch-agents

Verification and delivery

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: documents partial; screenshots unsupported; recordings unsupported; previews unsupported; gallery unsupported; prompt_leakage partial.
13 atomic answers
  • Diffs [supported] PR diff. Sources: orbi:wf.
  • Documents [partial] Plan file in worktree; ops evidence comments. Sources: orbi:ops, orbi:wf.
  • Screenshots [unsupported] No screenshot feature. Sources: orbi:srch-misc.
  • Recordings [unsupported] No recordings. Sources: orbi:srch-misc.
  • Previews [unsupported] No previews. Sources: orbi:srch-misc.
  • Test outputs [supported] Test log in the worktree; CI checks on the PR. Sources: orbi:ops.
  • Reviewer outputs [supported] Review round comments. Sources: orbi:pubc.
  • Persistence [supported] GitHub and retained worktrees. Sources: orbi:cfg.
  • Child findings [supported] Round comments persist. Sources: orbi:pubc.
  • Prompt leakage [partial] Prompts instruct against posting secrets; Cloud docs warn not to paste keys; failure comments carry scenes and commands redacted. Sources: orbi:c-sec, orbi:pi-launch.

Sources: orbi:ops, orbi:wf, orbi:srch-misc, orbi:pubc, orbi:sec, orbi:cfg, orbi:c-sec, orbi:pi-launch

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: lint partial; types partial; spec_checks unsupported; requirement_conflicts unsupported; configured_policy partial.
11 atomic answers
  • 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.

Sources: orbi:wf, orbi:sec, orbi:rounds, orbi:srch-misc, orbi:c-sec, orbi:cfg, orbi:merge-exec

Agent cross-checked partial

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.
9 atomic answers
  • Branches [supported] orbi/<owner>-<repo>-issue-<N>. Sources: orbi:pubc.
  • Worktrees [supported] Per-run worktrees. Sources: orbi:ops.
  • Commits [supported] The agent commits; the Runner pushes. Sources: orbi:sec.
  • Pull requests [supported] Runner creates the PR. Sources: orbi:ops.
  • Comments [supported] Run-marked comments and human PR feedback processed. Sources: orbi:wf.
  • Ci response [supported] A failing head returns to the review loop; base-red pauses with fix-base issue creation. Sources: orbi:wf.
  • Rebase [unsupported] Orbi uses plain git merge of the base; no rebase. Sources: orbi:wf.
  • Conflicts [partial] Conflicts are not auto-resolved by the Runner; the review session resolves in-session. Sources: orbi:wf.
  • Product state [supported] Labels and scene reflect the PR state. Sources: orbi:wf.

Sources: orbi:wf, orbi:ops, orbi:merge-exec, orbi:pubc, orbi:sec

Agent cross-checked 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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: approve partial; deploy unsupported.
6 atomic answers
  • 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.

Sources: orbi:sec, orbi:wf, orbi:merge-exec, orbi:c-sec

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: build_links partial; deployment_links unsupported; rollback unsupported; revert unsupported.
9 atomic answers
  • 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.

Sources: orbi:wf, orbi:pubc, orbi:srch-misc

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: review_queue partial; summaries partial; grouping partial; risk_size_filters unsupported; artifacts unsupported; check_deduplication partial.
12 atomic answers
  • Review queue [partial] Opened PRs are scanned oldest first (100 candidates); Cloud Under review tab. Sources: orbi:wf, orbi:c-status.
  • Summaries [partial] Round comments and checklist per PR. Sources: orbi:wf.
  • Grouping [partial] Milestones and epics. Sources: orbi:wf.
  • Risk size filters [unsupported] No risk/size filters. Sources: orbi:srch-misc.
  • Findings [supported] Retained per round. Sources: orbi:pubc.
  • Artifacts [unsupported] No artifact navigation. Sources: orbi:srch-misc.
  • Request changes [supported] PR feedback feeds the next round. Sources: orbi:wf.
  • Exact revision approval [supported] Head-bound verdict. Sources: orbi:sec.
  • Dependency queues [supported] Blocked-by gating before work; release gate waits for open deliveries. Sources: orbi:wf.
  • Next actions [supported] Comments name the action. Sources: orbi:wf.
  • Stale approval invalidation [supported] Re-review on head change. Sources: orbi:wf.
  • Check deduplication [partial] Clean review reuse only. Sources: orbi:wf.

Sources: orbi:wf, orbi:c-status, orbi:srch-misc, orbi:pubc, orbi:sec

Ownership, privacy and economics

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: hosted_extensions unknown; hosted_parity unknown.
6 atomic answers
  • 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.

Sources: orbi:license-file, orbi:licdoc, orbi:repoapi, orbi:plugin, orbi:releases

Agent cross-checked partial

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.

Sources: orbi:readme, orbi:sec, orbi:licdoc, orbi:wf, orbi:pubc, orbi:c-billing

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: retention partial; deletion partial; training unknown; residency unknown; subprocessors partial; telemetry_controls unsupported; consent_prompt unsupported.
15 atomic answers
  • 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.
  • Provider separation [supported] Model provider policies are separate and under the user's provider account (BYOK). Sources: orbi:prov, orbi:c-model.

Sources: orbi:srch-tele, orbi:site-privacy, orbi:c-sec, orbi:sec, orbi:ops, orbi:cfg, orbi:prov, orbi:c-model

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: seats partial; seat_minimum unsupported; workspace_fees partial; credits unsupported; overages unsupported; taxes unknown.
12 atomic answers
  • Currency [supported] US dollars on the pricing data. Sources: orbi:site-pricing.
  • Interval [supported] Monthly or yearly, plus one-time Alipay/WeChat payments. Sources: orbi:c-billing.
  • Seats [partial] Plans are per account/tenant; seats are not priced. Sources: orbi:c-billing.
  • Seat minimum [unsupported] No seat minimum is stated. Sources: orbi:c-billing.
  • Workspace fees [partial] Repository limits per plan; no separate fee. Sources: orbi:c-billing.
  • Included usage [supported] 3 free deliveries; 400M and 1.2B tokens per month. Sources: orbi:c-limits.
  • Credits [unsupported] No credit packs; allowance only. Sources: orbi:c-billing.
  • Trial [supported] First three merged deliveries free. Sources: orbi:c-billing.
  • Overages [unsupported] No per-token overage; new deliveries pause (or BYOK). Sources: orbi:c-billing.
  • Taxes [unknown] Tax treatment is not stated in the checked pages.
  • Model cost [supported] Included on the platform channel; BYOK pays the provider. Sources: orbi:c-model.
  • Compute cost [supported] Included in the plan; self-host compute is yours. Sources: orbi:c-billing.

Sources: orbi:c-billing, orbi:site-pricing, orbi:c-limits, orbi:c-model

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: one_person partial; two_people partial; five_people partial; task_assumptions unknown; concurrency unknown; tokens partial; compute_hours unknown; variable_cost partial; unknown_cost partial.
11 atomic answers
  • 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.
  • Variable cost [partial] BYOK provider cost only. Sources: orbi:c-model.
  • 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.

Sources: orbi:c-billing, orbi:site-pricing, orbi:c-limits, orbi:c-model

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: access_restrictions partial; response_commitments unsupported; status_history partial; deprecation unknown.
8 atomic answers
  • Release stage [supported] Pre-1.0 (0.7.x) engine, Cloud generally available with free tier. Sources: orbi:releases.
  • Access restrictions [partial] Cloud sign-in via GitHub; founding offers limited to 6 places. Sources: orbi:c-billing.
  • Support [supported] Telegram group, support@orbi.build, GitHub Issues and Discussions. Sources: orbi:c-faq, orbi:readme.
  • Response commitments [unsupported] No response commitments in the checked pages. Sources: orbi:c-faq.
  • Release activity [supported] Releases every few days, last push 2026-11-16. Sources: orbi:releases, orbi:repoapi.
  • Status history [partial] A status link exists in the footer; history was not inspected. Sources: orbi:c-status.
  • Deprecation [unknown] No deprecation policy stated for Cloud.
  • Export options [supported] Data is in GitHub. Sources: orbi:readme.

Sources: orbi:releases, orbi:c-faq, orbi:c-billing, orbi:readme, orbi:repoapi, orbi:c-status

No sourced public finding not-published

No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: ongoing_free partial; credits_trial unsupported; paid_only unsupported; early_access partial; free_scenarios partial; paid_evaluation unsupported.
10 atomic answers
  • 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.

Sources: orbi:c-billing, orbi:licdoc, orbi:c-limits, orbi:readme, orbi:prov, orbi:c-model

Agent cross-checked partial

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
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
  • Partly established: compute_markup unknown; model_markup unknown.
9 atomic answers
  • Units [supported] Per plan per month/year, tokens and repositories. Sources: orbi:c-billing.
  • Included limits [supported] 400M and 1.2B tokens, 1 and 5 repositories. Sources: orbi:c-limits.
  • Overages [supported] No overage billing; pause or BYOK. Sources: orbi:c-billing.
  • Compute markup [unknown] Compute is bundled and not itemized.
  • Model markup [unknown] Model cost inside the plan is not itemized.
  • Minimum commitment [supported] None stated; cancel any time via Stripe. Sources: orbi:c-billing.
  • Cancellation [supported] Stripe customer portal. Sources: orbi:c-billing.
  • Sales only unknowns [supported] No sales-only tier; Solo to Pro upgrade for active subscribers is by contacting the vendor. Sources: orbi:c-limits.
  • Transparency classification [supported] Transparent for listed plans; compute and model markup unspecified. Sources: orbi:site-pricing.

Sources: orbi:c-billing, orbi:site-pricing, orbi:c-limits

Sources

orbi:readme

Orbi README

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.

Kind
documented
Locator
Intro; Quick start; What it does; License
Source date
Not stated
Retrieved
2026-11-17
orbi:wf

Workflow

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
Source date
Not stated
Retrieved
2026-11-17
orbi:cfg

Configuration reference

max_concurrency 1-5, pi_provider/pi_model/pi_thinking, review_pi_* overrides, human_review_gate, steering keys, Telegram notifications; telegram token excluded from Pi environment.

Kind
documented
Locator
Scheduling; Model provider; Delivery behaviour; Steering; Notifications
Source date
Not stated
Retrieved
2026-11-17
orbi:ops

Operations

orbi CLI subcommands, journal events, slots as flock files, worktree retention, failure recovery and resume rules.

Kind
documented
Locator
Timers; CLI; Public surface; Worktrees; Failure recovery; Concurrency; Logs
Source date
Not stated
Retrieved
2026-11-17
orbi:pubc

Public contracts

Inventory of CLI, config, labels, journal, session files, markers; says anything outside the table is internal; hidden orbi:scene:v1 and orbi:run markers.

Kind
documented
Locator
Public interface inventory; comment kinds; clarification; draft command contract
Source date
Not stated
Retrieved
2026-11-17
orbi:gs

Getting started

Prerequisites Python 3.14, uv, Pi CLI on Node 22.19+, git, gh >= 2.94, systemd user session (Linux) or launchd (macOS, not verified on real hardware).

Kind
documented
Locator
Prerequisites; One-line installation; PyPI installation
Source date
Not stated
Retrieved
2026-11-17
orbi:plugin

Claude plugin manifest

Plugin with /orbi:ship and /orbi:status commands and skills that write ai-ready Issues; it does not expose Orbi operations over MCP.

Kind
source-inspected
Locator
plugin.json; commands/ship.md; skills/
Source date
Not stated
Retrieved
2026-11-17
Commit
892f350cf287eb7321aaa2a82d4cc9471d7a5de0
Path
integrations/claude-plugin/plugin.json
orbi:c-status

Orbi Cloud status page

Browser status page with task history tabs, per-task elapsed time and token usage, project overview, usage, phone layout, 15-second observation.

Kind
documented
Locator
Task history; Usage and settings; On a phone; Refreshing
Source date
Not stated
Retrieved
2026-11-17
orbi:c-notif

Orbi Cloud notifications

Telegram messages for blocked, needs-detail, awaiting-merge and merged; not a live stream; replying does not steer.

Kind
documented
Locator
When Orbi sends a message
Source date
Not stated
Retrieved
2026-11-17
orbi:c-faq

Orbi Cloud FAQ

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.

Kind
documented
Locator
Running deliveries; Getting started
Source date
Not stated
Retrieved
2026-11-17
orbi:srch-clients

Bounded search: desktop/mobile/web clients

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.

Kind
source-inspected
Locator
rg -i "electron|tauri|react.native|webview|flask|fastapi|uvicorn" src tools systemd launchd; windows|win32
Source date
Not stated
Retrieved
2026-11-17
Commit
892f350cf287eb7321aaa2a82d4cc9471d7a5de0
Path
src/orbi
orbi:prov

Model providers

Providers via Pi: DeepSeek, xAI, OpenRouter, Gemini, z.ai, Cloudflare Workers AI, local llama.cpp, GitHub Models, ChatGPT/Codex OAuth, Groq, OpenCode; quota and billing stay with the provider.

Kind
documented
Locator
Catalog; Sign in with ChatGPT; Codex OAuth; free tiers
Source date
Not stated
Retrieved
2026-11-17
orbi:opencode

OpenCode provider

OpenCode Zen is used as a Pi model provider with an API key, not as a harness.

Kind
documented
Locator
What is authenticated; Catalog and Orbi configuration
Source date
Not stated
Retrieved
2026-11-17
orbi:pi-launch

Pi process launch

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
Source date
Not stated
Retrieved
2026-11-17
Commit
892f350cf287eb7321aaa2a82d4cc9471d7a5de0
Path
src/orbi/pi_process.py
orbi:srch-agents

Bounded search: other coding agent harnesses

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.

Kind
source-inspected
Locator
rg -i "claude code|codex cli|opencode|gemini cli|cursor agent|aider" src prompts
Source date
Not stated
Retrieved
2026-11-17
Commit
892f350cf287eb7321aaa2a82d4cc9471d7a5de0
Path
src/orbi
orbi:dock

Docker (community-maintained)

Community Linux container that runs the unmodified official deployment with systemd as PID 1; env vars ORBI_PI_*; Linux only; no compose.

Kind
documented
Locator
When to use it; Quick start; Boundaries
Source date
Not stated
Retrieved
2026-11-17
orbi:c-billing

Orbi Cloud billing

Free (3 merged deliveries), Solo (400M tokens/month, 1 repo), Pro (1.2B tokens/month, 5 repos); Stripe billing; no per-token overage; self-hosting stays free.

Kind
documented
Locator
The plans; Cancelling
Source date
Not stated
Retrieved
2026-11-17
orbi:c-limits

Orbi Cloud limits and quotas

Token usage counts input, output and cache reads; quota pauses new claims only; BYOK resumes; running deliveries are never interrupted.

Kind
documented
Locator
At a glance; The monthly token allowance; What is never interrupted
Source date
Not stated
Retrieved
2026-11-17
orbi:c-model

Orbi Cloud model configuration

Platform model channel by default, BYOK providers incl. OpenAI, DeepSeek, Anthropic compatibility, Gemini, OpenRouter, any OpenAI-compatible endpoint.

Kind
documented
Locator
Supported providers; How your key is stored
Source date
Not stated
Retrieved
2026-11-17
orbi:sec

Security

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
Source date
Not stated
Retrieved
2026-11-17
orbi:c-prov

Orbi Cloud provisioning

Per-repository dedicated environment is created, cloned and set up in 10-20 seconds.

Kind
documented
Locator
What happens during provisioning
Source date
Not stated
Retrieved
2026-11-17
orbi:timer

systemd timer template

Runner tick every five minutes, one timer instance per concurrency slot.

Kind
source-inspected
Locator
OnCalendar=*-*-* *:00/5
Source date
Not stated
Retrieved
2026-11-17
Commit
892f350cf287eb7321aaa2a82d4cc9471d7a5de0
Path
systemd/orbi@.timer
orbi:srch-api

Bounded search: API, MCP server, webhooks, SDK

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.

Kind
source-inspected
Locator
rg -i "webhook|mcp server|FastMCP|openapi|sdk" src docs integrations
Source date
Not stated
Retrieved
2026-11-17
Commit
892f350cf287eb7321aaa2a82d4cc9471d7a5de0
Path
src/orbi
orbi:claim

Claim scan

The claim scan skips an Issue while any native blockedBy blocker is open.

Kind
source-inspected
Locator
open_blocker_numbers use near line 428
Source date
Not stated
Retrieved
2026-11-17
Commit
892f350cf287eb7321aaa2a82d4cc9471d7a5de0
Path
src/orbi/claim.py
orbi:srch-misc

Bounded search: indexing, multimodal, memory, rollback

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).

Kind
source-inspected
Locator
rg -i "embedding|vector|semantic search|screenshot|multimodal|recording|memory|revert|rollback" src prompts docs/*.mdx
Source date
Not stated
Retrieved
2026-11-17
Commit
892f350cf287eb7321aaa2a82d4cc9471d7a5de0
Path
src/orbi
orbi:c-sec

Orbi Cloud security

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
Source date
Not stated
Retrieved
2026-11-17
orbi:cli-status

orbi status

orbi status reports slots, active deliveries and the next ready Issue; --follow streams.

Kind
source-inspected
Locator
slot output near line 106
Source date
Not stated
Retrieved
2026-11-17
Commit
892f350cf287eb7321aaa2a82d4cc9471d7a5de0
Path
src/orbi/cli_status.py
orbi:rounds

Review rounds

Review/fix loop capped at five rounds before ai-blocked.

Kind
source-inspected
Locator
MAX_REVIEW_ROUNDS = 5 (line 61)
Source date
Not stated
Retrieved
2026-11-17
Commit
892f350cf287eb7321aaa2a82d4cc9471d7a5de0
Path
src/orbi/review_rounds.py
orbi:srch-sched

Bounded search: schedules and event triggers

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).

Kind
source-inspected
Locator
rg -i "cron|OnCalendar|schedule|webhook" src systemd launchd
Source date
Not stated
Retrieved
2026-11-17
Commit
892f350cf287eb7321aaa2a82d4cc9471d7a5de0
Path
src/orbi
orbi:exporter

Prometheus exporter

Optional read-only exporter derives metrics from the systemd journal; labels exclude run ids and prompts.

Kind
source-inspected
Locator
module docstring; /metrics on 127.0.0.1:9106
Source date
Not stated
Retrieved
2026-11-17
Commit
892f350cf287eb7321aaa2a82d4cc9471d7a5de0
Path
3rd/monitoring/prometheus/orbi-exporter.py
orbi:srch-container

Bounded search: container or sandbox for agent

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.

Kind
source-inspected
Locator
rg -i "docker|podman|bwrap|nspawn|firejail|sandbox" src systemd launchd
Source date
Not stated
Retrieved
2026-11-17
Commit
892f350cf287eb7321aaa2a82d4cc9471d7a5de0
Path
src/orbi
orbi:srch-cost

Bounded search: cost tracking

No per-task cost, spend limit or budget code; matches are unrelated text. Orbi Cloud reports tokens per task in its status page (documented).

Kind
source-inspected
Locator
rg -i "cost_usd|usd|spend|budget|price" src
Source date
Not stated
Retrieved
2026-11-17
Commit
892f350cf287eb7321aaa2a82d4cc9471d7a5de0
Path
src/orbi
orbi:srch-team

Bounded search: roles, SSO, presence

No SSO, roles, presence or multi-user session features; authorization relies on GitHub repository permission (admin/write) for trusted comments and steering.

Kind
source-inspected
Locator
rg -i "saml|sso|oidc|presence|rbac|role" src docs
Source date
Not stated
Retrieved
2026-11-17
Commit
892f350cf287eb7321aaa2a82d4cc9471d7a5de0
Path
src/orbi
orbi:merge-exec

Merge execution

Runner merges with gh pr merge using the repository-allowed method and --match-head-commit.

Kind
source-inspected
Locator
merge method selection lines 94-121; gh pr merge
Source date
Not stated
Retrieved
2026-11-17
Commit
892f350cf287eb7321aaa2a82d4cc9471d7a5de0
Path
src/orbi/merge_exec.py
orbi:licdoc

Sustainable Use License

Orbi is dual-licensed: AGPL-3.0 or the Sustainable Use License v1.0; self-hosting on own repositories free under either.

Kind
documented
Locator
Dual-licence statement
Source date
Not stated
Retrieved
2026-11-17
orbi:repoapi

GitHub repository API for orbi-build/orbi

Repository has 255 stars, GitHub-detected licence AGPL-3.0, default branch main, last push 2026-11-16.

Kind
documented
Locator
stargazers_count; license; pushed_at
Source date
Not stated
Retrieved
2026-11-17
orbi:releases

Orbi releases

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.

Kind
documented
Locator
Latest releases v0.7.40-v0.7.45
Source date
Not stated
Retrieved
2026-11-17
orbi:site-privacy

Orbi Cloud privacy policy

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.

Kind
documented
Locator
Data we use; Service providers
Source date
Not stated
Retrieved
2026-11-17
orbi:srch-tele

Bounded search: telemetry

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.

Kind
source-inspected
Locator
rg -i "telemetry|posthog|sentry|analytics|mixpanel|segment" src docs 3rd systemd templates prompts integrations
Source date
Not stated
Retrieved
2026-11-17
Commit
892f350cf287eb7321aaa2a82d4cc9471d7a5de0
Path
src/orbi
orbi:site-pricing

Orbi website pricing data

Website repository pricing data: Solo US$29/month (US$290/year), Pro US$79/month (US$790/year), 3 free merged deliveries, 400M and 1.2B token allowances.

Kind
source-inspected
Locator
soloMonthlyUsd 29; cloudMonthlyUsd 79; annual 290/790; foundingPromoCode FOUNDING50
Source date
Not stated
Retrieved
2026-11-17
Commit
ac60f66f0dc954cdc758f4f5a5f79658b4bbf268
Path
src/pricing.json

Comparisons with Orbi

Compare Orbi with any other product on adecomparison.com.