Help us learn about your current experience with the documentation. Take the survey.

Troubleshooting GitLab Orbit Remote

  • Tier: Premium, Ultimate
  • Offering: GitLab.com
  • Status: Beta

The availability of this feature is controlled by a feature flag. For more information, see the history. This feature is available for testing, but not ready for production use.

When working with GitLab Orbit Remote, you might encounter the following issues.

Error: glab orbit exits with code 2

Remote glab orbit commands might exit with code 2.

This issue occurs when the knowledge_graph feature flag is not enabled for your namespace or instance.

To resolve this issue, contact your GitLab administrator to enable the knowledge_graph feature flag for your namespace.

Error: glab orbit exits with code 3

Remote glab orbit commands might exit with code 3.

This issue occurs when you are not authenticated with the GitLab CLI.

To resolve this issue, sign in:

glab auth login

Error: insufficient_scope on the MCP endpoint

A connection to the GitLab Orbit MCP endpoint might fail with insufficient_scope.

This issue occurs when the personal access token or OAuth token does not include the mcp_orbit scope. The read_api scope alone is not sufficient for the MCP transport.

To resolve this issue, create a token with the mcp_orbit scope, or authenticate again to grant the additional scope.