# \*Upgraded Chat (v6.2.0)

### Overview: Unified Experience

On [v6.2.0](https://docs.tabnine.com/main/getting-started/tabnine-chat/pages/risy3bTOlfBfgFRRXK8K#v6.2.0), Tabnine has upgraded Chat for a fuller conversational experience. This upgrade simplifies the architecture and delivers a more consistent user experience.\
Tabnine chat will now be powered by the same strong agentic agent, allowing multiple-shot answers and tool utilization. 

The chat mode will run read-only tools.

In addition, Chat will get its own dedicated Chat Usage page under the Analytics tab in the Tabnine Admin Console.

### What's Changing

#### **Inherited Capabilities**

Chat now runs on an advanced backend. This includes the following key features now being available in Chat:

* Apply All
* Scoping chips
* Custom commands
* Attribution for code blocks

#### **Chat Mode Configuration**

Chat Mode is designed to be a fast Q\&A experience with the following configurations:

* **Limited Turns**: Chat conversations are capped at 5–15 turns, focused on read operations.
* **Read-Only Tools**: In Chat mode, only read tools are provided to the LLM, but not write actions.
* **No MCP access**: Chat mode does not include MCP server access, which these remain exclusive to Agent mode.

{% hint style="info" %}
Tabnine doesn’t charge customers for chat mode token consumption, either in the old version or the new one.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.tabnine.com/main/getting-started/tabnine-chat/upgraded-chat-v6.2.0.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.