---
title: Configuration
description: Environment options and private git configuration.
sidebar:
  label: Overview
  order: 1
---

Most behaviour is controlled by explicit CLI flags. Runtime configuration uses environment variables for process context, tracked application config files, and private YAML files for git/GitHub repo tracking and optional dashboard source cards.

<CardGroup cols={2}>
  <Card title="Environment Variables" href="/configuration/environment/">All `DOT_*`, `DOTFILES_*`, and `OMARCHY_*` options.</Card>
  <Card title="Private Git Config" href="/configuration/private-git/">The `dot-git.yml` schema for repo activity and notifications.</Card>
  <Card title="Private Dashboard Config" href="/configuration/private-dashboard/">The `dot-dashboard.yml` schema for optional dashboard source cards.</Card>
  <Card title="Yazi" href="/configuration/yazi/">Restore the shared Yazi plugin set across devices.</Card>
  <Card title="Plannotator" href="/configuration/plannotator/">Restore shared Plannotator review settings across devices.</Card>
  <Card title="Lazygit" href="/configuration/lazygit/">Run shared repository maintenance commands from Lazygit.</Card>
  <Card title="Cursor" href="/configuration/cursor/">Restore the last window type or choose Editor and Agents explicitly.</Card>
  <Card title="Packages" href="/configuration/packages/">Use the signed public repository, AUR fallback, and private packages.</Card>
</CardGroup>

:::note[Configuration policy]
For dotfiles and system scripts, prefer explicit CLI flags over environment-variable toggles for runtime behaviour. Environment variables are used for standard process context (`HOME`, `PATH`, `XDG_*`), secrets, paths, and compatibility shims.
:::