Build

Repositories

Connect code, index it, then run agents against it.

Ara sessions run against connected GitHub repositories or GitLab projects. A repo is connected when Ara can reach it through the Ara GitHub App or a GitLab.com OAuth connection in your organization.

The path to a ready repo

1

Connect

Install or update the GitHub connection, or connect GitLab.com, so Ara can see the repository or project.

2

Index

Indexing builds the repo wiki and code understanding. It runs in the background.

3

Prepare

Add environment setup and secrets; native Codex memory compounds as sessions run.

4

Run

Create sessions with the repo path. GitHub uses owner/name; GitLab projects may use nested paths such as group/subgroup/project. Include the provider field when a path is ambiguous.

What indexing gives the agent

Indexing gives Ara a map of the repository. It powers wiki pages, setup readiness, and better code context before the agent starts editing.

If a repo is not connected, session creation fails with repo_not_connected. If the same path is connected on more than one provider, pass provider to pick GitHub or GitLab explicitly.

Useful API calls

List repositories

See what Ara can access.

Index a repository

Start or restart indexing.

Indexing status

Check whether the repo is ready.

Setup helper

Find likely repos and readiness gaps.