Skip to main content
Lift uses a layered TOML configuration system. Each layer overrides the previous:
  1. Built-in defaults β€” embedded in the binary from lift.default.toml
  2. User config β€” ~/.taho/lift/lift.toml
  3. System config β€” /etc/taho/lift/lift.toml
  4. CLI flags β€” highest priority
Run lift --config to see the resolved configuration with file status.

Configuration files

Create ~/.taho/lift/lift.toml to customize Lift behavior. All fields are optional β€” only specify what you want to override.

Available settings

Tool-specific settings

Examples

Custom pipeline (run only lint and vibes by default):
Python project:
Go project:
CLI flags always override file config. For example, lift -m overrides the pipeline setting to run only Inky for that invocation.

Commit tracking

Lift tracks which commits each tool has processed in ~/.taho/lift/:
Tracking is VCS-agnostic and stores commit hashes regardless of backend.