---
title: GitHub
description: Bring a repository's documentation and issue history into memory — useful for agencies that build as well as design.
---

<span class="vy-eyebrow">Sources</span>

# GitHub

For teams whose work includes building things, GitHub holds decisions that
never make it into a document: why an approach was chosen, what a client asked
for mid-sprint, how a component is meant to be used.

## Connect it

**Sources → GitHub → Connect**, and authorise with your GitHub account. Vythos
lists the repositories you can see; choose the ones to sync.

## What gets synced

- **Documentation** — the repository's README and the Markdown in its `docs/`
  folder.
- **Issues** — titles and descriptions, most recently updated first, open and
  closed.

The text goes into your memory, where Ask can search it. Nothing from GitHub
becomes a rule.

## When it's worth connecting

- You maintain a product alongside client work and want its decisions
  searchable.
- Your delivery process lives in a repository rather than in Notion.
- Client feedback arrives as issues.

If your repositories are only code, the value is small: Vythos reads prose, not
source files.

## Syncing again

On demand, from the Sources page. Re-syncing replaces what changed rather than
duplicating it.

## Access and privacy

Vythos sees what the account you connected can see. Private repositories stay
private: their text goes into **your** memory, which nobody else in the
workspace can search.

Disconnecting removes Vythos's access to GitHub.