Update the Orbit Quickstart, overview card, and group status billing link
What does this MR do and why?
This MR updates three parts of the Orbit dashboard after the Orbit docs redesign call on 2026-10-13.
- Quickstart: two options side by side, GitLab Duo and your own agents, in place of three numbered steps. Ask GitLab Duo sends a prompt that asks for one real cross-project example of what Orbit adds, and three questions to ask next. When Orbit is off for GitLab Duo, the option links to Preferences. Without GitLab Duo, only the agents option shows. The agents option links to the Orbit docs and to Connect via MCP.
- Overview card: the In your graph total shows in compact form, such as "801.3M items", on one line, with the exact number in a tooltip. Group and project counts use the locale number format. The line under the globe is removed, with the code that only it used.
- Group status: a group that is on shows a View billing button, with the same shape as Contact sales, that opens the GitLab Credits dashboard. Owners on GitLab.com get the group dashboard. Administrators on self-managed and Dedicated get the instance dashboard. Members get no button.
References
- Orbit docs redesign call on 2026-10-13: transcript (internal).
Screenshots or screen recordings
Local GDK in SaaS mode, this branch. The local stack has no Orbit indexer, so index status shows as not available.
Quickstart
| Before | After |
|---|---|
![]() |
![]() |
Other Quickstart states and Ask GitLab Duo
| Orbit off for GitLab Duo | GitLab Duo not available | 700px wide |
|---|---|---|
![]() |
![]() |
![]() |
Duo Chat opens in agentic mode with the GitLab Duo agent, and createAiDuoWorkflow gets the prompt as its goal. The GDK has no Duo Workflow Service, so the panel shows "Connection lost" after the prompt.
Four prompts ran in GitLab Duo on GitLab.com with Orbit on. The MR uses prompt 4.
| Prompt | Time | Orbit calls | Result |
|---|---|---|---|
| 1. What can you answer with Orbit that you cannot answer without it? One example, three questions. | 81s | 3 | Real example, long intro, one question with placeholders |
| 2. As 1, plus "spans more than one project", "keep it short", "real names" | 101s | 4 | Better example, extra statistics, one unchecked guess |
| 3. As 2, plus "in one sentence" for the intro | 140s | 4 | Grounded, still extra statistics |
| 4. One example that spans more than one project, "and nothing else" | 100s | 3 | Open MRs in 3 projects from one query, no extra content, three short questions with real project names |
Overview card
The Orbit graph_status response is a real GitLab.com response for gitlab-org, replayed for the local group, so both sides show the same numbers at scale.
| Before | After |
|---|---|
![]() |
![]() |
![]() |
![]() |
Group status
| Before | After |
|---|---|
![]() |
![]() |
Contact sales row, self-managed administrator, and link checks
Contact sales uses the same button classes (btn-default btn-sm):
Self-managed administrator, with the link to the instance dashboard:
| User | Link | Result |
|---|---|---|
| GitLab.com Owner | /groups/<group>/-/settings/gitlab_credits_dashboard |
The page passes its access checks. Locally it returns 500 because the local CustomersDot is down and the page needs plan data. |
| GitLab.com Developer | — | No button |
| Self-managed administrator | /admin/gitlab_credits_dashboard |
200 |
How to set up and validate locally
-
Sign in as the Owner of a group that has Orbit on, with GitLab Duo available. Open
/dashboard/orbit/overview. -
The Quickstart shows two options with no step numbers. Select Ask GitLab Duo: Duo Chat opens with the GitLab Duo agent and sends the Orbit prompt.
-
The card shows the total in compact form with "items" on the same line, and the exact number on hover. No line shows under the globe.
-
Open Group status. The row shows View billing, which links to the group GitLab Credits dashboard. As a Developer, the row shows no button.
-
Run the specs:
yarn jest ee/spec/frontend/orbit
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.













