> For the complete documentation index, see [llms.txt](https://docs.tabnine.com/main/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tabnine.com/main/welcome/readme.md). # Overview

## What is Tabnine? Tabnine is a fully private, organization-aware AI coding agent designed to run entirely within your environment. It connects to your repositories and development systems to deliver real-time, secure code assistance and automated workflows across the software lifecycle. Tabnine boosts engineering velocity, code quality, and developer happiness by automating the coding workflow through AI tools customized to your team. #### How to use Tabnine * Use Tabnine Agent, via either [**CLI**](/main/getting-started/tabnine-cli.md) or [**IDE**](/main/getting-started/tabnine-agent.md) environments, to perform your coding tasks. * Use [**Tabnine Chat**](/main/getting-started/tabnine-chat.md) to ask questions about your codebase. * Learn about the [**administrator's capabilities**](/main/administering-tabnine/managing-your-team.md) to understand, control, and govern your organization's usage of Tabnine. #### Other topics


General information	Security AI Models System requirements Tabnine plans
Using Tabnine	Install Quickstart Tabnine Agent Tabnine Chat
Admin Capabilities	Analytics Team Management User Management Context Engine Settings APIs

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.tabnine.com/main/welcome/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.