Skip to content

Cade's Dotfiles

My macOS and Linux development environment: shells, languages, editors, and agents. Package lists select the tools; configuration templates set them up.

Bootstrap runs both paths. After setup, you can apply configuration changes separately.

From an interactive terminal:

Install from a checkout
git clone https://github.com/cadebrown/dotfiles ~/dotfiles
~/dotfiles/bootstrap.sh

Expect name/email prompts, installer progress, then a tool check. Linux runs without sudo; initial macOS Homebrew setup may request administrator authentication.

Edit the zsh source, inspect the diff, then apply:

Edit → inspect → apply
"${EDITOR:-vi}" ~/dotfiles/home/dot_zshrc.tmpl
chezmoi diff ~/.zshrc
chezmoi apply ~/.zshrc
exec zsh -l

The new shell loads the result. Edit sources under home/ to retain changes across applies. Find other files in the configuration map or follow a configuration recipe.

With Codex installed and signed in:

Start a review session
cd ~/dotfiles
codex -p review
Example prompt
Trace how DF_USE_PLAT changes the Node executable path.
Show the source files and line references, then give me a command
to inspect the result in my current shell. Do not change files.

The review profile is read-only. Expect source locations and an inspection command to run on the target machine.

Choose an agent · Codex profiles · Instructions · Workflow examples

I need to…Start here
Find a tool or connectionPackages · Skills · MCP servers
Understand how it fits togetherArchitecture · Paths
Configure my workspaceShell & editors · Environment variables
Use local models or resume workLocal AI · Durable tasks
Add a featureWrite the guide · Show it working
CommandEffect
~/dotfiles/bootstrap.sh updatePull repository changes and install missing tools
~/dotfiles/bootstrap.sh upgradeUpdate the repository and request package upgrades
bash ~/dotfiles/install/verify-path.shCheck executable locations and PATH ordering
bash ~/dotfiles/install/codex.sh checkCheck the managed Codex setup

Search an error message or open Troubleshooting. See Daily maintenance for package and configuration updates.