Public, non-sensitive dotfiles for a repeatable macOS development environment.
This repository uses chezmoi for dotfiles and
Homebrew Bundle for software.
It has a shared private layer plus separate work and personal machine profiles.
The public Brewfile intentionally contains only common baseline tools.
~/Development/
├── dotfiles/ # public baseline
├── dotfiles-private/ # shared private configuration and apps
├── dotfiles-work/ # work-only configuration and apps
└── dotfiles-personal/ # personal-only configuration and apps
All four repositories use the conventional filename Brewfile. Their paths
make the layers unambiguous.
The public bootstrap is the unauthenticated entry point. It installs Homebrew
when needed, installs Git, gh, and chezmoi, authenticates GitHub, and clones
the shared private repository plus the selected profile. It then hands control
to bootstrap.sh in the public clone, making the repositories the source of
truth for the rest of the setup.
# Work computer
curl -fsSL https://raw.githubusercontent.com/mikejoyceio/dotfiles/main/bootstrap.sh \
| sh -s -- --work
# Personal computer
curl -fsSL https://raw.githubusercontent.com/mikejoyceio/dotfiles/main/bootstrap.sh \
| sh -s -- --personalAdd --macos after the profile to apply the macOS preferences too.
Run the repository copy directly. Before installing anything, it updates all three repositories used by the selected profile with fast-forward-only merges:
~/Development/dotfiles/bootstrap.sh --work
# or
~/Development/dotfiles/bootstrap.sh --personalThe bootstrap stops if a repository has uncommitted changes, is ahead of or has diverged from its upstream branch, or is not currently on a branch. It never discards local work to match the remote.
The work profile installs public + private + work. The personal profile
installs public + private + personal. The selected profile is saved locally
so .zshrc sources only its matching shell configuration.
Review changes before applying them manually with:
chezmoi -S "$HOME/Development/dotfiles" diffwtmux and agents manage persistent tmux sessions for Git worktrees, so
long-running tools keep working after a disconnect and can be reattached
locally or over SSH.
# Enter or create a tmux session for the current worktree
wtmux
# Create the session and start Claude Code
wtmux claude
# Create the session and start Cursor CLI
wtmux agent
# Pass arguments to Claude Code
wtmux claude --resume
# Pass arguments to Cursor CLI
wtmux agent resume
# List and attach to running worktree sessions
agents
# Attach directly to a named session
agents repository--branch-nameThe command runs only when the session is first created. Running wtmux
again for the same worktree, with or without a command, reattaches to the
existing session and never starts a second agent on top of the running one.
To switch agents, exit the running agent and start the other one from the
shell inside the same session (exit, then agent or claude).
Recent Cursor CLI installations expose the command as agent; older
installations may use the backward-compatible alias cursor-agent.
Detaching (Ctrl+b, then d) leaves the session and anything running in it,
such as Claude Code, alive.
consume sends one exact source to the Hermes pkm profile and its existing
consume skill. The wrapper does not write Obsidian files, classify sources,
normalize URLs, or duplicate any other PKM behavior.
consume 'https://x.com/example/status/123?s=20'
consume 'https://www.linkedin.com/posts/example'
consume 'https://example.com/article?ref=home&campaign=reading'
consume 'A book title to read later'
consume "$HOME/Documents/Reading List/book draft.pdf"Quote sources containing spaces or shell-sensitive characters such as &.
The v0.1 interface accepts exactly one argument and does not read stdin.
The command requires Hermes, a profile named pkm, a valid terminal.cwd for
that profile, and the consume skill installed in the profile.
The Raycast Script Command is installed by chezmoi at:
~/.config/raycast/script-commands/consume.sh
In Raycast Preferences, open Extensions, click +, choose Add Script Directory, and select ~/.config/raycast/script-commands. The command accepts
an optional source argument and otherwise uses the clipboard. A global hotkey
can be assigned after Raycast indexes the command.
The reliable browser workflow is:
copy the current URL → run Consume → Return
Chezmoi stores one machine-specific Consume mode:
local Run the canonical Hermes-backed command and install consume-remote.
remote Send the exact source over SSH stdin to the primary Mac.
The initial chezmoi setup prompts for the role. To change an existing machine,
edit the persisted configuration, change [data.consume].mode, and then apply
the complete target state so the role transition can also remove a stale
primary-only bridge:
chezmoi edit-config
chezmoi -S "$HOME/Development/dotfiles" diff
chezmoi -S "$HOME/Development/dotfiles" applyThe public interface remains consume <source> in both modes. Raycast always
delegates to ~/.local/bin/consume and contains no remote behavior.
In remote mode, the client runs the fixed command consume-remote through the
private SSH alias pkm-consume. Source content is written only to SSH stdin; it
is never interpolated into SSH arguments, remote command strings, SSH
configuration, or transport diagnostics generated by the wrappers. The primary
bridge passes the source as one argument to the canonical local command and
does not interpret its output.
The personal SSH layer must define Host pkm-consume with the primary Mac's
Tailscale DNS name, account, and a dedicated public IdentityFile backed by
the 1Password SSH agent. Use Tailscale only for private network reachability;
the primary must run macOS Remote Login/OpenSSH on tailnet TCP 22, and Tailscale
SSH must not intercept this connection because the authorization boundary is
the OpenSSH authorized_keys forced command. The matching public key on the
primary should use:
restrict,command="/Users/<primary-user>/.local/bin/consume-remote" ssh-ed25519 <public-key> pkm-consume
This workflow requires the primary Mac to be powered on, awake or remotely wakeable, connected to Tailscale, and accepting SSH. SSH failures—including status 255—pass through unchanged. There is no local queue, retry, offline buffer, public HTTP endpoint, or fallback Hermes installation.
After configuring the secondary Mac, test both the CLI and Raycast against an existing duplicate source. Invoke Raycast several times and record whether 1Password requests authorization on the first and repeated SSH operations. If every capture requires approval, keep the forced-command/Tailscale boundary and treat credential ergonomics as a separate follow-up decision.
Current-browser automation is intentionally not included. A future full Raycast extension may use Raycast's Browser Extension API if clipboard use proves too costly; browser-specific AppleScript should not be added merely to avoid one copy action.
Herdr setup, SSH troubleshooting, and backup policy are documented in
~/Development/dotfiles-private/HERDR.md. Keep machine-specific details and
configuration in the private layers; the public Brewfile only installs the app.
Do not commit credentials, tokens, employer/client details, private hostnames,
or a revealing software inventory here. Put shared sensitive configuration in
dotfiles-private, employer/client tooling in dotfiles-work, and
personal-only apps in dotfiles-personal. Secrets themselves should come from
a password manager or another dedicated secret store, not Git.
The split reduces future exposure; it does not erase information from an older repository's Git history.