Overview

Loop’s behavior is controlled by ~/.loop/agent/settings.json. Project-level overrides live in .loop/settings.json (requires project trust). View current settings in the TUI:

Complete Schema

Field Reference

Model & Provider

Appearance

Compaction

Sandbox

Permissions

Extensibility

MCP

Each MCP server entry:
Use command/args for stdio servers or url/headers for remote HTTP servers.

Response headers

Tracing

Global only. A project cannot override this block. The telemetry feature must be compiled in for /tracing to export spans. See Tracing. Secrets (Langfuse secret key, OTLP authorization header) stay in the credential store.

Custom providers

Global only. Filled by /login custom.

Project-Level Settings

Create .loop/settings.json in your project root to override global settings per-project:
Project settings require the project to be trusted. See Project Trust.

Configuration Precedence

Settings are resolved in this order (later wins):
  1. Built-in defaults
  2. ~/.loop/agent/settings.json (global)
  3. .loop/settings.json (project, if trusted)
  4. Command-line flags
  5. Environment variables