Settings Reference

Complete reference for all Kodezi CLI configuration options, including file paths, environment variables, flags, and detailed field definitions.

This page provides complete reference for every configuration option in Kodezi CLI. Use this guide when customizing your workflow, enabling new features, configuring LSP, MCP, permissions, or project-wide context settings.

Configuration File Locations

Kodezi CLI loads configuration from multiple layers, depending on your OS and whether you're working globally or inside a project.

Tip: You can view these paths with one command

Run:

kodezi dirs

This prints the exact global config, data directory, and project config file locations.

File Structure Overview

kodezi-cli.json

File Types

1. Global Config

  • Linux/macOS: ~/.config/kodezi-cli/kodezi-cli.json
  • Windows: %LOCALAPPDATA%\kodezi-cli\kodezi-cli.json

2. Global Data Config

  • Linux/macOS: ~/.local/share/kodezi-cli/kodezi-cli.json
  • Windows: %LOCALAPPDATA%\kodezi-cli\kodezi-cli.json

Warning: Do not manually edit the Data Config

This file is modified automatically by the CLI. Manual edits may break internal state.

3. Project Config

Located at project root:

kodezi-cli.json
.kodezi-cli.json

Configuration Structure

Every config file follows this structure:

{
  "$schema": "optional schema URL",
  "auth": {...},
  "lsp": {...},
  "mcp": {...},
  "options": {...},
  "permissions": {...},
  "tools": {...}
}

Each section is explained in detail below.

Configuration Sections

Environment Variables

# Skip authentication (development only)
export KODEZI_CLI_SKIP_AUTH="true"

# Disable metrics
export KODEZI_CLI_DISABLE_METRICS="true"
export DO_NOT_TRACK="true"

# Disable provider auto update
export KODEZI_CLI_DISABLE_PROVIDER_AUTO_UPDATE="true"

Command Line Flags

FlagShortDescription
--cwd /path-cWorking directory
--data-dir /path-DData directory
--debug-dDebug logging
--yolo-yAuto-approve all
--help-hShow help
--version-vShow version

Variable Substitution

Configuration values support variable substitution:

  • $VAR or ${VAR}: Environment variable
  • $(command): Command substitution

Example:

{
  "mcp": {
    "database": {
      "env": {
        "DATABASE_URL": "${DATABASE_URL}",
        "API_KEY": "$(cat ~/.api-key)"
      }
    }
  }
}

Configuration Priority

Settings are applied in this order (later overrides earlier):

  1. Built in defaults
  2. Global config
  3. Global data config
  4. Project config
  5. Environment variables
  6. Command line flags

Example Configurations

Minimal Setup

Perfect for getting started quickly:

{
  "auth": {
    "email": "user@example.com",
    "token": "your-token"
  }
}

This minimal configuration includes only authentication. All other settings use defaults.

Development Setup

Enhanced configuration for development work:

{
  "auth": {
    "email": "dev@example.com",
    "token": "dev-token"
  },
  "options": {
    "debug": true,
    "debug_lsp": true
  },
  "lsp": {
    "typescript": {
      "command": "typescript-language-server",
      "args": ["--stdio"]
    }
  }
}

Includes debugging enabled and LSP for TypeScript.

Team Project Setup

Configuration for team collaboration:

{
  "options": {
    "context_paths": [
      "docs/ARCHITECTURE.md",
      "docs/STANDARDS.md"
    ]
  },
  "lsp": {
    "typescript": {
      "command": "typescript-language-server",
      "args": ["--stdio"]
    }
  },
  "permissions": {
    "allowed_tools": ["view", "grep", "ls", "glob"]
  }
}

Includes project context files and allowed tools for consistent team workflows.

Management Commands

# View config location
kodezi dirs config

# View data location
kodezi dirs data

# Generate JSON schema
kodezi schema > schema.json

# View logs
kodezi logs