Chapter 03
Connecting repositories
How to connect a repository to Vyazen, understand indexing status, and manage connected repos.
Prerequisites
A source-control integration (GitHub, GitLab, or Bitbucket) must be configured on your instance. If it isn't, see Integrations or ask your admin.
Connect a repository
From the dashboard:
- Choose Connect repository and pick your provider (GitHub, GitLab, or Bitbucket).
- Authorize Vyazen to access the repository through the provider's approval flow.
- Select the repository and the branch you want to work on.
A repository in Vyazen is scoped to a branch — the branch is where the agent makes changes. You can connect the same repo on multiple branches as separate entries.
GitHub (GitHub App)
If your instance uses the GitHub App, you install the app into your GitHub account or organization, then pick which repositories it can access. Once installed, those repos are available to connect.
GitLab
Connect via a GitLab access token with read access to the target repository. Paste the token when configuring the integration, then select the repo and branch.
Bitbucket / Bitbucket Cloud
Connect via Bitbucket credentials configured as an integration, then select the repo and branch.
The indexing pipeline and status
Once connected, Vyazen builds the code graph (the index). The dashboard shows a live status per repository:
| Status | What it means |
|---|---|
| Queued | Waiting for a free worker to start. |
| Running | Vyazen is reading your repo and building the graph. |
| Ready | The graph is built; you can create tasks and browse the wiki. |
| Failed | Something went wrong; see troubleshooting below. |
suggestion
Manage connected repositories
From the repository's row or detail view you can:
- Refresh — re-sync the repository and rebuild affected parts of the graph (used after big changes upstream).
- Resume — restart indexing for a repository that stalled or was paused.
- Delete — remove the repository and its graph from Vyazen (does not touch your source repo).
Troubleshooting
- Connection failed during authorization — re-check the provider credentials/integration, then retry. See Integrations.
- Indexing stuck on "queued" or "running" — large repos can take a while; if it's truly stuck, try Refresh or Resume.
- Indexing failed — see FAQ & troubleshooting.