workspace

This is the configuration for the tools I use for agent driven development.

I'm trending towards doing as much in the terminal as I can and biasing towards tools with high levels of customizability.

Uses the fantasic mise to bootstrap everything.

What's inside

Path	Tool	Installed by	Symlinked to
herdr/config.toml	herdr	mise/workspace.toml -> herdr	~/.config/herdr/config.toml
nvim/	LazyVim	mise/workspace.toml -> neovim	~/.config/nvim
ghostty/config	Ghostty	post-tools hook (brew --cask)	~/.config/ghostty/config
ghui/config.json	ghui	mise/workspace.toml -> npm:@kitlangton/ghui	~/.config/ghui/config.json
hunk/config.toml	hunk	mise/workspace.toml -> hunk	~/.config/hunk/config.toml
pi/agent/settings.json	pi	mise/workspace.toml -> npm:@earendil-works/pi-coding-agent	~/.pi/agent/settings.json
pi/agent/extensions/	pi extensions	(config only)	~/.pi/agent/extensions
skills/effect-setup/	agent skill	(config only)	~/.agents/skills/effect-setup
skills/mise-setup/	agent skill	(config only)	~/.agents/skills/mise-setup
mise/workspace.toml	(tool list)	—	~/.config/mise/conf.d/workspace.toml

Global tools

The CLI tools (herdr, neovim, hunk, ghui, pi) are declared in mise/workspace.toml, which is symlinked to ~/.config/mise/conf.d/workspace.toml. mise loads conf.d/*.toml into the global config, so the tools are active in every directory, not just this repo, and your personal ~/.config/mise/config.toml stays untouched. mise bootstrap installs them from the merged config.

Only config is tracked. Runtime files (logs, sockets, state.json, caches, session.json) stay out.

For pi, only non-secret config is tracked: settings.json (preferences + package list) and the extensions/ directory. Secrets and runtime state — auth.json, sessions/, npm/, trust.json — are deliberately left out. The pi binary itself is installed by mise bootstrap (via mise/workspace.toml), but you still need to authenticate it yourself — auth.json is never tracked.

Skills live in the shared ~/.agents/skills/ directory (read by pi and other agents). That directory also holds skills installed by a skill manager, so each tracked skill under skills/ is symlinked individually rather than linking the whole directory. Add a skill by dropping its folder in skills/ and adding a matching [dotfiles] entry in mise.toml.

Install

From a fresh clone, run the install script. It installs mise if missing, trusts the repo, and runs mise bootstrap. Re-running is safe:

./install.sh

The bootstrap process...

1. applies [dotfiles], including the conf.d/workspace.toml global-tools link,
2. installs those tools (herdr, neovim, hunk, ghui, pi) into the global config,
3. runs the post-tools hook to install the Ghostty cask.

For dotfiles which are being symlinked, the install script will back up any existing files. Otherwise running the installer would be destructive.