Analyzers

Analyzers (introduced in v6.0.1) are part of the Context Engine and control which context layers are extracted from your code repositories.

This page lets you view which analyzers run on your connected data sources, how they are triggered, and what kind of information they extract. You can manage analyzers on the Data Source page.

From the Admin Console, navigate to Context Engine on the menu, then select Analyzers. You’ll see a list of available analyzers, along with their descriptions, trigger types, and supported data sources.

Built-in Analyzers

The Built-in tab displays analyzers that are available out of the box. These analyzers are maintained by Tabnine and designed to cover common use cases across repositories. Each analyzer is shown as a card with a short description, its trigger type (“Automatic” or “On Demand”), and its data sources.

Currently, there are two built-in: Symbols and Summary & API. Enabling both will usually provide the best results: ‘Symbols’ builds the foundation, while ‘Summary & API’ adds architectural understanding on top.

Symbols

The Symbols analyzer extracts structural elements from your codebase (functions, classes, and variables). This analyzer runs automatically in the background whenever your connected repositories are updated.

The Symbols analyzer will run on your Git repos and your Perforce depots.

Summary & API

The Summary & API analyzer* generates a high-level understanding of your services and interfaces. It will generate a high-level summary of each service (its purpose, dependencies, and key interfaces). Most importantly, it both detects and then extracts any OpenAPI / Swagger specifications from repositories.

*Only available when Agentic Context Engine is enabled

This analyzer runs on demand, allowing you to control when summaries are generated or refreshed. From the Data Sources tab, you can enable it only for specific repos.

The Summary & API analyzer also runs on your Git repos and your Perforce depots.

Next Steps

After enabling analyzers, you can:

• Use Tabnine Chat to ask questions about your codebase structure and services

• Run code reviews with deeper context about functions and dependencies

• Explore extracted APIs and service summaries directly from your repositories

If your organization uses multiple repositories or data sources, make sure analyzers are enabled across all relevant sources to ensure consistent coverage.