Settings

Configure Tabnine CLI behavior and appearance through settings.

Opening Settings

/settings

Opens an interactive settings editor with validation and descriptions.

Settings Locations

Tabnine CLI uses hierarchical settings:

Global Settings

Location: ~/.tabnine/agent/settings.json

Applies to all projects.

Project Settings

Location: <project>/.tabnine/agent/settings.json

Applies only to the current project. Overrides global settings.

Common Settings

General

Checkpointing

{
  "general": {
    "checkpointing": {
      "enabled": true
    }
  }
}

Enable automatic snapshots before file modifications. See Checkpointing.

This setting is not available in the /settings dialog and must be set directly in the settings JSON file.

Model

{
  "model": {
    "id": "gemini-2.0-flash-exp"
  }
}

Set default AI model. See Model Selection.

UI

Theme

{
  "ui": {
    "theme": "ANSI"
  }
}

Set color theme. See Themes.

Footer

{
  "ui": {
    "footer": {
      "hideModelName": false
    }
  }
}

Show/hide footer elements.

Input

{
  "ui": {
    "input": {
      "multiLine": true,
      "vimMode": false
    }
  }
}

Configure input behavior.

Advanced

Custom Bug Command

{
  "advanced": {
    "bugCommand": "open https://your-issue-tracker.com"
  }
}

Customize /bug command behavior.

Settings Structure

{
  "general": {
    "checkpointing": { "enabled": boolean }
  },
  "model": {
    "id": string
  },
  "ui": {
    "theme": string,
    "footer": {
      "hideModelName": boolean
    },
    "input": {
      "multiLine": boolean,
      "vimMode": boolean
    }
  },
  "advanced": {
    "bugCommand": string
  },
  "context": {
    "fileFiltering": {
      "respectGitIgnore": boolean,
      "respectTabnineIgnore": boolean
    }
  }
}

Editing Settings

Via /settings Command (Recommended)

1

Open the editor

Run /settings.

2

Navigate

Use the arrow keys to move between fields.

3

Edit

Press Enter to edit values.

4

Save

Changes are saved automatically.

Benefits:

• Validation prevents errors

• Descriptions and help text

• Safe editing

Manually Editing JSON

Edit .tabnine/agent/settings.json directly:

# Global
vim ~/.tabnine/agent/settings.json

# Project
vim .tabnine/agent/settings.json

Invalid JSON will cause errors. Use /settings command when possible.

Settings Precedence

Settings are merged hierarchically. Later settings override earlier ones.

1

Global — ~/.tabnine/agent/settings.json

2

Workspace — <workspace>/.tabnine/agent/settings.json

3

Project — <project>/.tabnine/agent/settings.json

Validation

The /settings command validates settings:

• Type checking (boolean, string, number)

• Value constraints

• Required fields

Invalid settings are rejected with error messages.

Settings Schema

Full schema available at: ~/.tabnine/agent/schemas/settings.schema.json

Resetting Settings

Remove Settings File

# Global
rm ~/.tabnine/agent/settings.json

# Project
rm .tabnine/agent/settings.json

Tabnine CLI will use defaults.

Reset Specific Setting

Edit .tabnine/agent/settings.json and remove the key, or set it to the default value.

Troubleshooting

Invalid settings.json

Cause: Malformed JSON

• Check for syntax errors (missing commas, quotes, braces).

• Use /settings command instead of manual editing.

• Validate JSON: cat ~/.tabnine/agent/settings.json | jq

Settings not taking effect

Check the following:

• Settings file location (global vs project)

• Settings precedence (project overrides global)

• Restart Tabnine CLI after changes

Can't find a setting

Use /settings command and search for settings by name.

See Also

• Commands: /settings

• Checkpointing

• Themes