Connection: Global codebase awareness
What is Connection?
Connection (Global RAG) personalizes Tabnine to your organization’s code by extending the available context for Tabnine Chat to include remote code repositories, even if they’re not part of the local IDE workspace.
This enhances AI code suggestions, making them more accurate and relevant to the organization.
Why is this important?
In many cases, the relevant context for Tabnine is located in remote repositories that are not included in the current project.
For example, users may need specific code that resides outside the IDE or suggestions that rely on patterns from the remote codebase.
Who has access to the Connection feature?
The Connection feature is available to enterprise customers in all deployments.
To enable this feature for your team, please contact your account manager.
How to enable this feature:
The Enterprise team admin manages the connected repositories. The admin can establish connections to Git providers using:
SSH: By configuring Tabnine’s SSH key
HTTPS: By using access tokens from the Git providers
How does the end user work with connected repositories?
Context Scoping
Specify which repositories are relevant for Tabnine to use as context. Learn more about Context Scoping.
Get answers based on references from remote repositories
Tabnine Chat may generate answers using context from remote repositories. The exact references used will appear in the "References" section.
Navigate to Resource
Quickly access relevant remote code references by clicking the corresponding link. The browser will open the original source code directly within the connected Git provider.
Which Git providers are supported?
Supported providers:
GitHub
GitLab
Bitbucket
Note:
Both cloud and self-hosted installations are supported, provided Tabnine servers can connect to the Git providers.
For other providers:
Indexing and retrieving chat answers from remote repositories generally works for most standard Git providers.
Navigating to remote repositories' references may not work consistently due to variations in URL patterns.
Which users have access to context from the remote repository?
Connections are managed at the team level.
Each user only has access to the repositories that are connected to their specific team.
Which files are being indexed?
Indexing process and RAG index
Your connected repositories are cloned to Tabnine servers for indexing and are deleted immediately after indexing is complete.
The RAG index is securely retained on Tabnine servers and remains private.
A periodic background process checks for updates in the connected repositories and refreshes the corresponding index when needed.
This update process can take up to one hour.
Read more on the Index Lifecycle.
Last updated
Was this helpful?
