Repository Integration

Connect your Git repositories to DevSpec so the AI can understand your codebase in context. DevSpec works with GitHub, Bitbucket Cloud, GitLab (gitlab.com or self-managed), and the Gitea family (Gitea, Forgejo, Codeberg) — connecting with read-only permissions and never modifying your repos. Once connected, your code is indexed and available to reference during sessions.

Connecting a Repository

From your project page, click "Add Repository." Choose your git provider, authorize the connection if you haven't already, then select the repository you want to connect. DevSpec will index the repository automatically. Already-tracked repositories are shown in the list so you can avoid adding duplicates.

Steps

• Open your project page.
• Click "Add Repository" in the Repos tab.
• Choose your provider (GitHub, Bitbucket, GitLab, or Gitea / Forgejo) and authorize the connection if you haven't already. For a self-managed GitLab or Gitea instance, enter its URL and connect with OAuth or a personal access token.
• Select the repository you want to connect.
• DevSpec begins indexing automatically — a progress bar shows the status.

Your git connection is yours, not the project's: you authorize a provider once (under You → Connections), and it works across every project you administer. A project doesn't store a credential — it just references your connection for the repositories you track into it. You can only add a repository with your own connection, but once you do, every member of the project can read and interact with that repository through it. A single project can hold repositories from more than one provider (for example a GitHub repo and a Bitbucket repo), each tracked with whoever's connection added it. See Git Provider Connections for the full model, permissions, and recovery if a connection breaks.

Indexing Progress

After connecting, you'll see a progress bar showing parsing and categorization stages. An estimated time remaining is displayed alongside the percentage. A banner warns during sessions if a repo is still being processed, so you know the AI might have incomplete context until indexing finishes.

Change Detection & Freshness

DevSpec uses each provider's webhooks to detect when you push to the default branch and incrementally re-indexes only the changed files, so no full re-clone is needed. The repo card shows when it was last indexed, how many commits behind it is, and a "Check for updates" button you can use to trigger a manual refresh. This freshness tracking ensures the AI always works with up-to-date code.

Using Code Context in Sessions

Once indexed, start a session and the AI will have full awareness of your code structure, file contents, and dependencies. You can ask questions about specific files, patterns, or architectural decisions — regardless of which provider hosts the repository.