These tools share a workspace without forming a mandatory chain. Foot provides the terminal window, a shell interprets commands, Starship renders the prompt, and tmux manages detachable sessions. Neovim, Git, Lazygit, mise and Docker handle editing, version control, a Git interface, development tool versions and containers.
Example: editing and running a project.
Enter the project in Foot. Starship shows directory and repository context; optionally use tmux for a persistent session.
Edit files in Neovim. Language tools may be managed by mise or installed through another route.
Inspect and commit changes with Git. Lazygit operates on the same repository through another interface.
If the project uses containers, Docker can run services or the application. Container runtimes do not automatically match the host version selected by mise.
A broken prompt, missing editor completion, wrong runtime version and unreachable container service each suggest a different component. Replacing the terminal does not address them all.
Each catalogued component is explained below: purpose, architecture, configuration, troubleshooting, limitations and further reading. Use the component links to jump to its explanation.
Default terminal in this source snapshot. A terminal hosts the shell; it is not the shell itself.
Package
foot
Membership
Core manifest
Omarchy configuration or entry point
~/.config/foot/foot.ini
Purpose and everyday use
A Wayland terminal emulator and this snapshot’s default terminal. It displays shell output and sends keyboard input; commands themselves run in the shell or child programs.
How it works and connects
Terminal rendering, shell behavior and prompt formatting are separate layers. Foot renders the interface; Starship can format the prompt and tmux can organize sessions.
Configuration and customization
Omarchy documents ~/.config/foot/foot.ini. Fonts, colors and terminal key bindings belong here; shell aliases belong in shell configuration.
Troubleshooting approach
For missing glyphs, inspect fonts; for broken prompts, inspect shell initialization. Compare a plain shell with your customized environment before changing terminal settings.
Limits and change considerations
Changing terminals does not automatically migrate shell settings. Closing a terminal may terminate attached work unless managed by a persistent session tool.
Local inspection and version checks
Read local package metadata to confirm installation and version. These inspection commands do not install, restart or change configuration; run them in your own Omarchy environment.
pacman -Qi foot
foot --version
Queries can fail when a package is absent, a service is stopped, or the command needs a graphical session or project directory. Interpret the result in context. Review machine-specific details before sharing output.
Omarchy integration follows the 2026-10-12 quattro snapshot. Match upstream configuration guidance to your installed version. These are documentation-based explanations and diagnostic suggestions, not hardware-tested results.
Customizable command prompt showing context such as the current Git repository.
Package
starship
Membership
Core manifest
Purpose and everyday use
Builds a command prompt showing context such as directory, Git state and language versions. Useful for orientation while moving between projects.
How it works and connects
The shell invokes Starship to render prompt segments. Repository checks and enabled modules influence what appears and how long rendering takes.
Configuration and customization
Upstream uses ~/.config/starship.toml unless overridden. Adjust modules and formatting separately from terminal fonts and shell aliases.
Troubleshooting approach
If the prompt is missing, inspect shell initialization. If only one project is slow, compare enabled modules and repository-related checks.
Limits and change considerations
Prompt information is a convenience, not an authoritative security indicator. Custom modules may run commands whenever a prompt is drawn.
Local inspection and version checks
Read local package metadata to confirm installation and version. These inspection commands do not install, restart or change configuration; run them in your own Omarchy environment.
pacman -Qi starship
starship --version
Queries can fail when a package is absent, a service is stopped, or the command needs a graphical session or project directory. Interpret the result in context. Review machine-specific details before sharing output.
Omarchy integration follows the 2026-10-12 quattro snapshot. Match upstream configuration guidance to your installed version. These are documentation-based explanations and diagnostic suggestions, not hardware-tested results.
Terminal multiplexer for sessions, windows and panes.
Package
tmux
Membership
Core manifest
Purpose and everyday use
Organizes terminal sessions, windows and panes. Detaching lets terminal work remain available for later reattachment while the tmux server continues running.
How it works and connects
A server owns sessions while clients attach to them. This differs from Hyprland workspaces, which organize graphical windows rather than terminal processes.
Configuration and customization
Configure key bindings, status lines and behavior through tmux configuration. Keep terminal shortcuts and tmux prefix bindings distinct to avoid conflicts.
Troubleshooting approach
List sessions before assuming work is lost. For color or key issues, compare running the program inside and outside tmux.
Limits and change considerations
Detachment is not a backup and does not survive every reboot or server termination. Ending a session can stop its processes.
Local inspection and version checks
Read local package metadata to confirm installation and version. These inspection commands do not install, restart or change configuration; run them in your own Omarchy environment.
pacman -Qi tmux
tmux list-sessions
Queries can fail when a package is absent, a service is stopped, or the command needs a graphical session or project directory. Interpret the result in context. Review machine-specific details before sharing output.
Omarchy integration follows the 2026-10-12 quattro snapshot. Match upstream configuration guidance to your installed version. These are documentation-based explanations and diagnostic suggestions, not hardware-tested results.
Terminal text editor; Omarchy adds its own configuration package.
Package
nvim
Membership
Core manifest
Purpose and everyday use
A modal text editor for files and code. Normal mode navigates and operates on text; insert mode enters text. Learn save and quit operations before editing system configuration.
How it works and connects
Core editing can be extended through Lua configuration and plugins. Language servers provide additional analysis; their failures need not indicate a failure of the editor itself.
Configuration and customization
Omarchy supplies an editor configuration package. Read that integration before replacing user configuration; prefer targeted changes to replacing the entire setup.
Troubleshooting approach
Distinguish file permissions, plugin errors and language-tool failures. Inspect the message before reinstalling the editor or deleting configuration.
Limits and change considerations
Plugins execute code and can change files. A buffer with unsaved changes is not stored merely because the editor window is still open.
Local inspection and version checks
Read local package metadata to confirm installation and version. These inspection commands do not install, restart or change configuration; run them in your own Omarchy environment.
pacman -Qi nvim
nvim --version
Queries can fail when a package is absent, a service is stopped, or the command needs a graphical session or project directory. Interpret the result in context. Review machine-specific details before sharing output.
Omarchy integration follows the 2026-10-12 quattro snapshot. Match upstream configuration guidance to your installed version. These are documentation-based explanations and diagnostic suggestions, not hardware-tested results.
Version control for source code and your own configuration history.
Package
git
Membership
Core manifest
Purpose and everyday use
Records version history for projects or selected personal configuration. Commits capture deliberate snapshots that can be compared, branched and shared.
How it works and connects
Working files, the staging area, local history and remotes are separate states. Lazygit provides an interface to these same concepts rather than a different storage system.
Configuration and customization
Keep global identity settings separate from repository-specific behavior. Use ignore rules for generated files and secrets before staging a configuration repository.
Troubleshooting approach
Start with git status and a diff. A rejected push may involve remote history or authentication; it does not imply local commits disappeared.
Limits and change considerations
Git history is not a backup of untracked files. Rewriting shared history and destructive cleanup have different consequences from making a new commit.
Local inspection and version checks
Read local package metadata to confirm installation and version. These inspection commands do not install, restart or change configuration; run them in your own Omarchy environment.
pacman -Qi git
git status --short
Queries can fail when a package is absent, a service is stopped, or the command needs a graphical session or project directory. Interpret the result in context. Review machine-specific details before sharing output.
Omarchy integration follows the 2026-10-12 quattro snapshot. Match upstream configuration guidance to your installed version. These are documentation-based explanations and diagnostic suggestions, not hardware-tested results.
A terminal interface for inspecting changes, staging, committing and navigating Git history. Useful for seeing repository state without memorizing every command.
How it works and connects
Operates on the same Git repository and index as the Git CLI. Actions in the interface change real repository state, not a separate preview.
Configuration and customization
Customize display and key bindings using its own configuration. Learn panel focus and action descriptions before assigning shortcuts from another tool.
Troubleshooting approach
When an action fails, read the underlying Git message and verify repository state with Git itself. Check whether you opened the intended worktree.
Limits and change considerations
Discard, reset and rebase remain consequential even behind a friendly UI. Review the selected files and scope before confirming them.
Local inspection and version checks
Read local package metadata to confirm installation and version. These inspection commands do not install, restart or change configuration; run them in your own Omarchy environment.
pacman -Qi lazygit
lazygit --version
Queries can fail when a package is absent, a service is stopped, or the command needs a graphical session or project directory. Interpret the result in context. Review machine-specific details before sharing output.
Omarchy integration follows the 2026-10-12 quattro snapshot. Match upstream configuration guidance to your installed version. These are documentation-based explanations and diagnostic suggestions, not hardware-tested results.
Manages development tools and language runtime versions.
Package
mise-bin
Membership
Core manifest
Purpose and everyday use
Manages development tool versions, environment settings and tasks. Useful when projects require different language runtimes without replacing system packages.
How it works and connects
Selects tools according to configuration and activation. A shell’s effective PATH determines which executable is used, so installed and active versions can differ.
Configuration and customization
Separate project settings from global defaults. Pin versions deliberately and review project configuration before trusting its environment or tasks.
Troubleshooting approach
Compare active tool versions with the project requirement and shell activation. A command found in one terminal but not another often points to environment differences.
Limits and change considerations
Tool downloads, plugins and tasks can execute code. mise complements the system package manager; it does not replace management of desktop libraries or drivers.
Local inspection and version checks
Read local package metadata to confirm installation and version. These inspection commands do not install, restart or change configuration; run them in your own Omarchy environment.
pacman -Qi mise-bin
mise --version
Queries can fail when a package is absent, a service is stopped, or the command needs a graphical session or project directory. Interpret the result in context. Review machine-specific details before sharing output.
Omarchy integration follows the 2026-10-12 quattro snapshot. Match upstream configuration guidance to your installed version. These are documentation-based explanations and diagnostic suggestions, not hardware-tested results.
Runs containers; related packages add Compose and Buildx.
Package
docker
Membership
Core manifest
Purpose and everyday use
Runs applications in containers built from images. Useful for development services and reproducible environments; Compose describes groups of services.
How it works and connects
A client talks to the container daemon. Containers share the host kernel while using isolation features; volumes and published ports connect them to host resources.
Configuration and customization
Define persistent storage, ports and environment explicitly. The pinned Omarchy setup enables docker.socket; inspect actual service state before changing startup behavior.
Troubleshooting approach
Separate daemon-access errors from an application failing inside a container. Inspect the affected service and its logs before removing images or volumes.
Limits and change considerations
Daemon access is powerful; mounts and port publishing affect host security. Removing containers does not always remove data, while deleting volumes can destroy it.
Local inspection and version checks
Read local package metadata to confirm installation and version. These inspection commands do not install, restart or change configuration; run them in your own Omarchy environment.
pacman -Qi docker
docker --version
Queries can fail when a package is absent, a service is stopped, or the command needs a graphical session or project directory. Interpret the result in context. Review machine-specific details before sharing output.
Omarchy integration follows the 2026-10-12 quattro snapshot. Match upstream configuration guidance to your installed version. These are documentation-based explanations and diagnostic suggestions, not hardware-tested results.