Cross-platform dotfiles managed with chezmoi.
| Category | macOS | Windows | Both |
|---|---|---|---|
| Shell | Fish, Zsh | PowerShell | — |
| Prompt | — | — | Starship |
| Terminal | Ghostty, iTerm2 | Windows Terminal (pwsh default) | — |
| Version mgmt | — | — | mise (harness CLIs, RTK, Python, Node) |
| Editor | — | — | VSCode, EditorConfig |
| Git | 1Password SSH signing | Credential Manager | Common config |
| SSH | 1Password agent (socket) | 1Password agent (named pipe) | — |
brew install chezmoi
chezmoi init --apply --ssh kelchmOr as a one-liner on a fresh machine:
sh -c "$(curl -fsLS get.chezmoi.io)" -- init --apply --ssh kelchmwinget install twpayne.chezmoi
chezmoi init --apply --ssh kelchmOr as a one-liner:
irm get.chezmoi.io/ps1 | powershell -c - -- init --apply --ssh kelchmchezmoi edit ~/.config/starship.toml # edit a managed file
chezmoi diff # preview pending changes
chezmoi apply # apply changes to home directory
chezmoi cd # cd into source directory
chezmoi add ~/.some/new/file # start managing a new fileChezmoi bootstraps the configured tools; mise upgrades them. Harnesses track latest, so machines share configuration and an update method, but may have different versions until each is upgraded.
- Harness CLIs: Claude Code, Codex, Grok Build, OpenCode
- Filter (not an agent): RTK
- mise selects the installation backends using its registry defaults
- Background self-updates are disabled through mise's environment settings
minimum_release_age = "24h" delays selection of timestamped releases. Grok's HTTP feed has no timestamps, so it is not covered. Already-installed versions are not downgraded.
chezmoi apply # bootstrap tools when config changes
mise install # restore missing configured tools
mise outdated claude codex grok opencode rtk # check these five tools
mise run harness:update # upgrade these five, leaving runtimes aloneLaunch through mise shims or an activated shell so the updater settings are loaded. For scripts, use mise exec -- <command>. GUI launchers should use the shim path, rather than a versioned executable path.
OpenCode's opencode.jsonc merge rule keeps opencode-go available: it adds Go to an existing provider allowlist and removes it from any denylist. Other settings, including local providers and default models, stay machine-specific. If there is no allowlist, OpenCode already allows all connected providers. Connect Go once per machine with /connect; credentials are not stored in these dotfiles. When the rule changes a config, it normalizes JSONC to JSON and removes comments; an already-compliant config is left byte-for-byte unchanged.
On a machine that already had Homebrew, npm, or WinGet copies: apply, then remove those duplicate installations after checking that commands resolve through mise.
RTK integration is initialized during bootstrap and when its setup scripts change (for example, when adding a harness). Routine RTK upgrades need no extra step. If RTK documents an integration migration, rerun the relevant command:
mise exec -- rtk init -g --auto-patch # Claude
mise exec -- rtk init -g --codex
mise exec -- rtk init -g --opencode --auto-patchThese dotfiles manage Codex's default ~/.codex directory. Bootstrap targets that directory even when CODEX_HOME selects a separate profile; custom profiles are managed separately. For a manual Codex migration with a custom profile active, use CODEX_HOME="$HOME/.codex" mise exec -- rtk init -g --codex in Bash/Zsh. In PowerShell, temporarily set $env:CODEX_HOME = Join-Path $HOME ".codex" for the command, then restore its previous value.
- Files are stored in chezmoi's source format (
dot_prefix replaces leading.) - Files ending in
.tmplare Go templates with OS-conditional logic modify_templates merge a small invariant into a tool-owned config file without replacing the rest of the file.chezmoiignorecontrols which files deploy on which OSfish_variablesis intentionally not managed — Fish manages it automatically; important variables are set inconfig.fish