> 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/getting-started/code-completion/code-acceptance-logs.md).

# Code Acceptance Logs

**Code Acceptance Logging** tracks all explicit acceptances of code recommendations by the use or code recommended by Tabnine. These logs can be leveraged for compliance needs. This applies both to our IDE plugin and the Tabnine CLI.

{% hint style="info" %}
Code Acceptance collection is turned off by default and requires an explicit request from an Admin to enable it. To activate this service and access all Acceptance Logs, please contact <support@tabnine.com>.
{% endhint %}

{% hint style="info" %}
This is only available for self-hosted instances.
{% endhint %}

AI-generated code accepted via the Agent ([v6.3.0](https://docs.tabnine.com/main/getting-started/code-completion/pages/risy3bTOlfBfgFRRXK8K#v6.3.0)) and CLI ([v6.3.0](https://docs.tabnine.com/main/getting-started/code-completion/pages/risy3bTOlfBfgFRRXK8K#v6.3.0)) is logged alongside existing code completion logging. All accepted code is traceable and accessible for organization admins. Accepted code may come from any of these code generation sources (in both our IDE plugin and the Tabnine CLI):

1. [Tabnine Agent](/main/getting-started/tabnine-agent.md)
2. [Tabnine Chat](/main/getting-started/tabnine-chat.md)
3. [Code Completions](/main/getting-started/code-completion.md)
4. [Test Agent](https://github.com/codota/docs/blob/main/main/getting-started/getting-the-most-from-tabnines-code-completion/broken-reference/README.md)

All logs will include standard information such as:

1. Full accepted code snippet
2. Timestamp of the acceptance event
3. Session ID
4. Source of generation (agent, cli, chat, or code completion)
5. Model name
6. User ID
7. Team ID

\
Admins can export logs via the Admin Console using the Download as CSV button or via API. Exports support filtering by date range and source.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tabnine.com/main/getting-started/code-completion/code-acceptance-logs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.