docs: refactor follow-up - remove extra disclaimers and fix CLI references

> For more information, see the history.

> This feature is available for testing, but not ready for production use.

<!-- -->

> [!disclaimer]

Orbit indexes your GitLab instance and exposes your entire SDLC as a queryable knowledge graph.

Enable it on a group and Orbit maps everything: projects, users, merge requests, pipelines,

work items, security findings, and the source code itself, then builds a property graph of how they

## Orbit Local

Orbit Local runs entirely on your machine. The `orbit` CLI parses a local repository,

Orbit Local runs entirely on your machine. The Orbit CLI (`orbit`) parses a local repository,

extracts definitions and cross-file references, and writes the graph to a local DuckDB file.

No GitLab instance or network connection required.

```mermaid

flowchart LR

    accTitle: Orbit Local architecture

    accDescr: The orbit CLI parses a local repository, builds a code graph, and writes it to a local DuckDB file. You query the graph via the CLI.

    accDescr: The Orbit CLI parses a local repository, builds a code graph, and writes it to a local DuckDB file. You query the graph via the CLI.

    Repo[Local repository] --> CLI["orbit CLI"]

    CLI --> DB[("DuckDB\n~/.orbit/graph.duckdb")]

{{< /history >}}

> [!disclaimer]

Orbit Local runs entirely on your machine. Build a code graph for any local

repository and query it using the same query language as Orbit Remote. No

GitLab account, no network connection required.

| Method | Description |

|---|---|

| [orbit CLI](access/cli.md) | Run the `orbit` binary directly to index and query |

| [glab CLI](access/glab.md) | Drive Orbit Local through `glab orbit local` (planned) |

| [The Orbit CLI (`orbit`)](access/cli.md) | Run the `orbit` binary directly to index and query |

| [The GitLab CLI (`glab`)](access/glab.md) | Drive Orbit Local through `glab orbit local` (planned) |

| [MCP](access/mcp.md) | Expose the local graph to Claude Code, Codex, and other agents |

## Billing

stage: Analytics

group: Knowledge Graph

info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments

description: Build and query a local code graph with the orbit CLI binary. No GitLab account or network connection required.

title: Use Orbit Local with the orbit CLI

description: Build and query a local code graph with the Orbit CLI (orbit) binary. No GitLab account or network connection required.

title: Use Orbit Local with the Orbit CLI (`orbit`)

---

{{< details >}}

{{< /history >}}

> [!disclaimer]

The `orbit` CLI builds a code graph for any local repository and queries it

The Orbit CLI (`orbit`) builds a code graph for any local repository and queries it

against a local DuckDB file. No GitLab connection required.

> [!note]

group: Knowledge Graph

info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments

description: The glab orbit local subcommands and glab orbit setup are planned for a future glab release. Until they ship, build from source and use the orbit binary directly.

title: Use Orbit Local with the glab CLI

title: Use Orbit Local with the GitLab CLI (`glab`)

---

{{< details >}}

> [!disclaimer]

The [`glab` CLI](https://docs.gitlab.com/cli/) is the canonical way to install,

The [GitLab CLI (`glab`)](https://docs.gitlab.com/cli/) is the canonical way to install,

run, and integrate Orbit Local with your AI agent. `glab orbit local` mirrors

`glab orbit remote`, so the same patterns work whether you query the GitLab

instance or your local machine.

> [!note]

> Both `glab orbit local` and `glab orbit setup` are planned for a future glab

> release. Every command on this page is the future shape, not the current one.

> Until they ship, build from source - see [Use the orbit CLI directly](cli.md).

> Until they ship, build from source - see [use `orbit` directly](cli.md).

Two top-level commands (both planned, not yet shipped):

{{< /history >}}

> [!disclaimer]

Orbit Local can run as an MCP server, exposing the same two tools as Orbit

Remote (`query_graph`, `get_graph_schema`) but pointed at the local DuckDB

graph instead of a GitLab instance.

## Prerequisites

- The `orbit` CLI is installed. See [Use the orbit CLI directly](cli.md).

- The Orbit CLI (`orbit`) is installed. See [Use the Orbit CLI directly](cli.md).

- A local repository has been indexed (`orbit index <path>` or

  `glab orbit local index <path>`).