Settings

Context Engine Settings page in the Tabnine Console

To enable and control Context Engine preprocessing, open the Context Engine Settings page. At the top, locate the Context Engine Enablement panel.

To enable advanced preprocessing, use the control in this panel and read the description to confirm what will change. Make sure your organization is ready for Context Engine to analyze the repositories you configured on the Codebase tab.

To choose the model that powers Context Engine, open the “Context Engine Model” dropdown. Select a supported model such as “Claude 4.5 Haiku” according to your performance and cost requirements.

To control which repositories Context Engine can access, set the “Context Engine User” field. Choose a user account that has exactly the repository permissions you want Context Engine to have.

To define when preprocessing can run, use the “Pre‑Processing Schedule” section. Select “Any time” to allow Context Engine to run jobs whenever needed, or choose “Controlled” if you plan to restrict heavy processing to dedicated windows.

When you need to stop Context Engine temporarily, click the “Disable Context Engine” button. To adjust model, user, or scheduling settings, click “Edit” and save your changes when done.

To manage how users access Context Engine‑powered tools, scroll to the Context Engine Tools Configuration panel. Read the description to understand how this affects tools such as Tabnine CLI and Tabnine Agent.

To expose Context Engine capabilities to end users, turn on the “Enable Context Engine tools to end users” switch. To keep Context Engine running only as an internal service, turn this switch off so client tools cannot call it.

Use this panel to stage rollouts. First, enable Context Engine and validate runs and assets, then enable end‑user tools when you are satisfied with the results.

---