# Model Reasoning

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="/files/M5NeXyYZEw9U2INzOMtc" 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: 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-cli/features/model-reasoning.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.