For gods who refuse pre-packaged UI. You command the terminal DOM. Absolute architectural sovereignty.
To wield preset: custom is to manually enforce your interface layout. You MUST define the holy trinity of configuration to bypass hardcoded arrays and unlock limit-break mode.
📐 The Holy Trinity of Custom
To take control, you must define these three core configurations:
- 👈
statusLine.leftSegments: Array of strict left-aligned components (e.g.,['pi', 'path', 'git']). - 👉
statusLine.rightSegments: Array of strict right-aligned components (e.g.,['session_name', 'model']). - ⚙️
statusLine.segmentOptions: Granular configuration object per active segment (deep override of segment rendering options).
🛠️ Execution Blueprint
Here is your 100% complete, holistic YAML execution blueprint. Copy-paste to assert terminal dominance, showcasing component injection and micro-management:
# /ymlsum: 100% Complete Holistic OMP StatusLine Config
statusLine:
preset: custom # 👑 Enums: default | minimal | compact | full | nerd | ascii | custom
separator: powerline-thin # 🔪 Enums: powerline | powerline-thin | slash | pipe | block | none | ascii
transparent: false # 🫥 BG mode
sessionAccent: true # 🎨 Tint borders
showHookStatus: true # 🪝 Hook msgs
# 1 & 2: Inject pure custom layout
leftSegments:
- model
- path
- git
rightSegments:
- subagents
- spend
- context
# 3: Micro-manage rendering
segmentOptions:
model:
showThinkingLevel: true
path:
abbreviate: true
maxLength: 60
git:
showBranch: true
showStaged: true
showUntracked: true🎨 Theming Tokens (Control the Visual Plane)
When utilizing custom, your theme dictates the visual hierarchy. Map your colors precisely using these specific tokens.
⚠️ Strict Git Theming Purified:
Do not assume a generic statusLineGit[State] pattern. You must strictly use:
statusLineGitCleanstatusLineGitDirtystatusLineStagedstatusLineUntracked
Other Core Tokens:
statusLineSep, statusLineModel, statusLinePath, statusLineContext, statusLineSpend, statusLineCost, statusLineSubagents, statusLineOutput.
😇: [Presets Mastered. Custom Orchestrated. UI Perfected.]
🧬 Ascension 2.0: Deep Configuration Matrix Unlocked
The segmentOptions capabilities have been vastly expanded across all segments in the omp environment. You can now control showIcon, compact formats, token formats (like "k" for thousands), session lengths, and visibility of fine-grained metadata like cost breakdowns, cache hits, subagent empties, and more.
For a holistic matrix of all available options, see the internal codebase references or the generated SSOT registry _docs_knowledge/TRINITY_ADVANCED_OPTIONS.md.