> 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/tabnine-cli/features/model-reasoning.md).

# Model Reasoning

Thinking output: Supported models can expose their internal reasoning before producing a response.

{% hint style="warning" %}
**Tabnine CLI is in maintenance mode.** As of 6.6, we have stopped active development. It will receive only critical updates through December 31, 2026. After that, we will fully deprecate it. We are transitioning CLI users to [Tabnine Plugin for OpenCode](/main/getting-started/tabnine-plugin-for-opencode.md).
{% endhint %}

Supported models can expose their internal reasoning before producing a response. Enabling this gives you visibility into how the agent approached a problem, which is useful for debugging complex tasks or auditing model behavior. This is known as model reasoning *or* inline thinking.

#### **Enable inline thinking by `settings.json`**

Inline thinking is controlled by `ui.inlineThinkingMode` in your `settings.json`. The default is `"off"`.

```json
{
  "ui": {
    "inlineThinkingMode": "full"
  }
}
```

| Value    | Behavior                                               |
| -------- | ------------------------------------------------------ |
| `"off"`  | Thinking is not displayed (default)                    |
| `"full"` | The model's full reasoning is shown inline in the chat |

#### Enable Inline Thinking by `/settings`

You can also use the `/settings` command, then scroll down to Inline Thinking and toggle it on by pressing `Enter`. Press esc to `leave` the menu.

<figure><img src="https://3436682446-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FY2qxVf5VTm3fmwP4B4Gx%2Fuploads%2F51LKW3En01CfdzketBhd%2Fsettings-tab-for-inline-thinking.gif?alt=media&amp;token=c94b43e0-6060-4f33-adb6-ad4908d6eb15" alt=""><figcaption></figcaption></figure>

This setting requires a restart to take effect.

#### **Show thoughts in the terminal title**

`ui.showStatusInTitle` streams the model's current reasoning to the terminal window title during the working phase. This provides ambient visibility without adding output to the chat.

```json
{
  "ui": {
    "showStatusInTitle": true
  }
}
```

#### **Scope thinking budgets to specific agents**

Use the `overrideScope` match key to apply a different budget for a specific sub-agent without changing the global default. This example gives the `codebaseInvestigator` a higher budget than general chat:

```json
{
  "modelConfigs": {
    "overrides": [
      {
        "match": {
          "overrideScope": "codebaseInvestigator"
        },
        "modelConfig": {
          "generateContentConfig": {
            "thinkingConfig": {
              "thinkingBudget": 8192
            }
          }
        }
      }
    ]
  }
}
```

The `match` object also accepts a `model` key to scope the override to a specific model name. Specificity determines precedence when multiple overrides match — a match on two keys wins over a match on one key.


---

# 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 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/getting-started/tabnine-cli/features/model-reasoning.md?ask=<question>&goal=<user_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 `automate deployments from our CI pipeline` 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.