Next
The main card changes with the work. During setup it shows your current step. During a delivery it names the Issue and shows its three steps, Writing code → Checking → Merging, the latest reported activity and a folded Latest progress. The report describes what the session most recently said it was doing; the Issue labels and pull request determine the delivery result. When something needs you, the main card shows the selected task’s reason and action. With several waiting items, use N more need you to move to another without leaving the page. The multi-project overview can also show the total number of items needing attention. Follow the action for the selected Issue: approve its PR, add detail or confirm Orbi’s proposal, correct a missing base branch, have Orbi file fix tickets for a failing base branch, or read Orbi’s blocked comment. See troubleshooting.Headlines
Suggestions can appear in the main card while a project is idle, or in a separate Orbi also suggested these card while work is running. Review draft opens a new task for you to check; Let Orbi do this dispatches an existing Issue immediately, or opens checkout once your free deliveries are used up. Why this expands the reason for a suggestion.
With several projects, use All or a project selector. All starts with one suggestion per ready project; expand the remaining suggestions to see more. Choose a project before requesting a new batch. See your first Issue.
Setup progress
There are five steps: Sign in → Install GitHub App → Connect repository → Prepare work environment → Write your first request. The last step is complete once you hand over the first task; it does not wait for a merge. Release creation and subscription are separate actions, not extra setup steps. The installation, connection and first-request steps have short how-to videos. The environment step updates automatically while Orbi prepares it.Project overview
The Project / Projects area summarizes each connected project’s current work, including the Issue number and title when work is running. Manage projects opens repository management and shows the used allowance and plan limit. An official example copy is listed separately and does not use a real-project slot. With one project, its current state and task history appear directly. With several, open a project row for its base branch, current version, progress, task history and Versions. The multi-project overview does not merge every project’s task table into one. For a public project, expand README badge to preview its delivery badge and copy Markdown into your README. After the first merge, View badge highlights that entry. The count updates automatically, with a cache of about an hour; clicking the badge opens the project’s delivery records. The status page offers this entry for public real projects, not private repositories or example copies. To change the base branch, open Manage projects → Change base branch, choose an existing branch and save. See connecting a repository.Task history
For a single project, Task history is a list showing the Issue, status and update time. It starts with the three most recently updated tasks; Show all (N) expands the rest and Hide folds them again. Times use your browser’s local time zone. In the selected-project details of a multi-project account, history still uses three tabs:
A queued task says what it is waiting for, including unresolved Issue dependencies. View progress selects that task’s progress. When usage has been reported, the task also shows elapsed time, AI calls and tokens split into input, output and cache; an interrupted run can show its resume count. Usage that has not been reported is not counted as zero.
The delivery lifecycle explains each status. Open the Issue for Orbi’s explanation and the PR for the change. If the history cannot be read, that area says so; this does not mean there have been no tasks.