> ## Documentation Index
> Fetch the complete documentation index at: https://docs.truecourse.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Repositories

> The Code list, connecting a repository, and the six tabs of a repository's console.

**Code** lists the repositories of the workspace and opens each one's console.

## The list

| Column           | What it says                                                                                             |
| ---------------- | -------------------------------------------------------------------------------------------------------- |
| **Repository**   | The provider's mark and the repository's name. It says **onboarding** while its first work is in flight. |
| **Requirements** | The repository's sections as a bar and a count per status.                                               |
| **Proven**       | The share of its sections that succeeded.                                                                |
| **Last check**   | The verdict of its last run, and when. It opens the run.                                                 |
| **Baseline**     | The default branch, and when its corpus was built.                                                       |

Search matches the repository's name. The tally at the bottom counts repositories by their last check: Failing, Passing or Neutral.

## Connect a repository

**Connect repository** opens a dialog with four steps:

<Steps>
  <Step title="Provider">
    The accounts already connected, one row each. In local mode, **Local folder** is a row of its own. See [Local folders](/local-folders). Connecting a new account is Settings' job, and the last row links there.
  </Step>

  <Step title="Repositories">
    What that account can see. A repository already connected is shown as connected and cannot be picked twice.
  </Step>

  <Step title="Context">
    Which of the workspace's [sources](/guard/web-sources) the repository reads. A source that is a picked repository's own documentation is checked to begin with.
  </Step>

  <Step title="Confirm">
    **Connect and start onboarding** writes the repository and starts its [Flow setup](/guard/setup) in the background.
  </Step>
</Steps>

With no model provider saved, the repository is still connected, and the app says that nothing will run until a provider is set in [Settings](/configuration/llm-transport).

## The repository console

A repository has six tabs, in two groups. The tab rides the address, so a tab is a place you can link to.

| Tab              | What it holds                                                                                                                                                                                                                     |
| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Runs**         | Every stored run, newest first, led by the run in flight. A row opens that run with its evidence. See [Flow run](/guard/run).                                                                                                     |
| **Pipeline**     | The three pieces of work this repository runs: Flow setup, Flow generation and Flow run. Each row carries its last outcome, one fact, when it happened, and a **Run** or **Re-run** button. A row opens that work's conversation. |
| **Context**      | Every source of the workspace with a switch: the ones switched on are what this repository reads.                                                                                                                                 |
| **Interfaces**   | The catalog Flow setup mapped: screens, operations, commands and entry points.                                                                                                                                                    |
| **Dependencies** | What the program needs you to provide. See [External services](/guard/external-services).                                                                                                                                         |
| **Settings**     | The repository's name, provider and default branch, and **Unlink repository**.                                                                                                                                                    |

The header carries the repository's name, its default branch, and the verdict and time of its last check. When the workspace has no model provider, a banner says so above the tabs.

Flows are not a tab here. A flow belongs to the workspace and is listed across every repository on [Flows](/flows). Documents are not a tab either: they belong to the workspace, under [Context](/guard/web-sources). This console's Context tab only says which sources this repository reads.

## Unlinking a repository

**Unlink repository** on the Settings tab disconnects it. Whatever it has in flight is cancelled. Its sources stay, because a source belongs to the workspace and losing one reader is not losing the source.

## Next steps

<CardGroup cols={2}>
  <Card title="Flow setup" icon="screwdriver-wrench" href="/guard/setup">
    What starts as soon as a repository is connected.
  </Card>

  <Card title="Repositories and providers" icon="gear" href="/settings/repositories">
    Where accounts are connected, and which providers exist.
  </Card>
</CardGroup>