Settings

Modern dotfiles installer with animated progress display.

Clone and run the dotfiles installer from https://github.com/jiunbae/settings

Quick install:  curl -LsSf https://settings.jiun.dev | bash -s -- --all
Core only:      curl -LsSf https://settings.jiun.dev | bash -s -- --core
Pick & choose:  curl -LsSf https://settings.jiun.dev | bash -s -- zsh nvim tmux tools

Post-install: exec zsh

╔══════════════════════════════════════════════════════════════╗
║  Settings Installer                                          ║
╠══════════════════════════════════════════════════════════════╣
║ [████████████████████████████████████████░░░░░░░░░░]  80%    ║
║  [6/8] Rust toolchain                                        ║
╚══════════════════════════════════════════════════════════════╝

  ✓ Installing Rust via rustup
  ✓ Installing cargo-binstall
  ⠋ Installing eza...

Quick Start

One-Line Install (Recommended)

# Install everything
curl -LsSf https://settings.jiun.dev | bash -s -- --all

# Install specific components
curl -LsSf https://settings.jiun.dev | bash -s -- zsh nvim tmux

# Interactive selector
curl -LsSf https://settings.jiun.dev | bash -s -- --interactive

Manual Clone

git clone https://github.com/jiunbae/settings.git
cd settings
./install.sh --all

Presets

./install.sh              # Interactive selector (pick components in a menu)
./install.sh --all        # Install everything
./install.sh --core       # Core dev environment (base, zsh, nvim, tmux, tools)
./install.sh --basic      # Minimal (base, zsh, nvim, tmux)

Features

Modular Architecture - Install only what you need
Cross-Platform - Linux, macOS, and WSL support
Progress Display - Animated spinner with progress bar
Dry-Run Mode - Preview changes before applying
Idempotent - Safe to run multiple times

Usage

Usage: install.sh [OPTIONS] [COMPONENTS...]

Options:
  -i, --interactive   Interactive component selector (default when no args)
  -a, --all           Install all components
  --core              Install core dev environment (base, zsh, nvim, tmux, tools)
  -b, --basic         Install basic dev environment (base, zsh, nvim, tmux)
  -f, --force         Force reinstall (overwrite existing)
  -c, --copy          Copy config files instead of symlink
  -l, --link          Create symlinks for config files (default)
  -v, --verbose       Enable verbose output
  -n, --dry-run       Show what would be done
  --no-sudo           Skip commands that require sudo privileges
  -h, --help          Show help message

Components:
  base          Basic packages (curl, wget, git, build-essential)
  zsh           Zsh + zinit + Powerlevel10k
  nvim          NeoVim + LazyVim
  tmux          tmux + TPM (terminal multiplexer)
  zellij        zellij (modern terminal multiplexer)
  rust          Rust toolchain + cargo-binstall
  uv            uv (fast Python package manager)
  tools         CLI tools (eza, fd, bat, ripgrep, fzf)
  tools-extra   Extra CLI tools (delta, dust, procs, bottom)
  ssh           SSH config (copy only, not symlinked)
  hishtory      hishtory (better shell history with sync support)
  hammerspoon   Hammerspoon (macOS-only: window manager + keybindings)
  codex         Codex CLI/App config, hooks, and notify chain
  claude        Claude Code settings, hooks, skill index, memory, MCP
  cship         cship + Starship (fast Claude Code statusline)

Components

Shell Environment

Component	Description
Zsh	Modern shell
zinit	Fast plugin manager
Powerlevel10k	Fast, customizable prompt
zsh-syntax-highlighting	Fish-like syntax highlighting
zsh-autosuggestions	Fish-like autosuggestions

Editor

Component	Description
NeoVim	Hyperextensible Vim-based editor
LazyVim	Fast, modern Neovim setup powered by lazy.nvim

Terminal

Component	Description
tmux	Terminal multiplexer (default)
TPM	Tmux plugin manager
zellij	Terminal multiplexer (alternative)
Windows Terminal	Modern terminal for Windows

AI Coding Agents

Component	Description
Claude Code	`settings.json`, hooks, skill index and memory, symlinked to this repo — see Restoring AI agent state
Codex	`config.toml` managed half, merged over local runtime state
cship	Claude Code statusline (Rust) — replaces ccstatusline: ~33ms vs ~1,250ms per render, ~18MB vs ~99MB peak RSS
Starship	Required by cship for the `$directory` / `$git_branch` / `$git_metrics` / `$custom.worktree` passthrough segments

Development Tools

Component	Description
Rust	Systems programming language
cargo-binstall	Binary package installer
uv	Fast Python package manager (10-100x faster than pip)

Modern CLI Tools

Basic tools (tools):

Tool	Replaces	Description
eza	`ls`	Modern ls with icons and git integration
fd	`find`	Simple, fast alternative to find
bat	`cat`	Cat with syntax highlighting
ripgrep	`grep`	Fast regex search tool
fzf	-	Fuzzy finder

Extra tools (tools-extra):

Tool	Replaces	Description
delta	`git diff`	Better git diff viewer
dust	`du`	Intuitive disk usage
procs	`ps`	Modern process viewer
bottom	`htop`	System monitor

Shell History

Component	Description
hishtory	Better shell history with context, search, and sync

AI Coding Tools

Component	Description
codex	Managed Codex config template. Applies stable model/plugin/MCP/hook settings, disables legacy `~/.codex/hooks.json`, and preserves machine-local runtime sections such as project/hook trust, `notify`, TUI state, and desktop settings.

hishtory features:

Context-aware history (directory, exit code, duration)
Fuzzy search with Ctrl+R
E2E encrypted sync across machines
Self-hosted server support

Configuration (~/.envs/hishtory.env):

# Self-hosted server (optional, local-only mode without this)
export HISHTORY_SERVER="https://hishtory.example.com"

# Secret key for cross-device sync (get from `hishtory status`)
export HISHTORY_SECRET="your-secret-key-uuid"

Without HISHTORY_SERVER, hishtory runs in local-only mode. To sync across devices, use the same HISHTORY_SECRET on all machines.

macOS Automation

Component	Description
Hammerspoon	Lua-scriptable macOS automation (window/screen/keyboard)

Installs via Homebrew Cask and symlinks ~/.hammerspoon/init.lua to this repo. Skipped automatically on Linux/WSL. Accessibility permission must be granted manually: System Settings → Privacy & Security → Accessibility → enable Hammerspoon.

Restoring AI agent state on a new machine

Claude Code and Codex keep their configuration in different shapes, so this repo manages them differently. Follow the order below — step 2 must happen before step 3, because configs/claude/settings.json references hook scripts that live in the agent-skills repo.

# 1. this repo
git clone git@github.com:jiunbae/settings.git ~/personal/settings

# 2. hook scripts referenced by Claude settings.json
git clone git@github.com:jiunbae/agent-skills.git ~/personal/agent-skills

# 3. shared skill/static-doc repo, then lay down ~/.agents/
git clone git@github.com:rtzr/agents.git ~/workspace/agents
~/workspace/agents/scripts/install-static.sh
~/workspace/agents/scripts/install-shims.sh

# 4. external runtimes used by the managed hooks (examples)
#    Install and log in to Claude Code and Codex through their official installers.
brew install open330/tap/muxa             # or follow muxa's platform instructions
npm install -g oh-my-prompt               # provides omp

# 5. agents + statusline
cd ~/personal/settings
./install.sh claude cship codex

# Restore Oh My Prompt's Codex notify entry after its own setup. Later Codex
# config applies preserve this machine-local absolute command.
omp install codex

# 6. private state — never in git
#    - ~/.envs/*.env
#    - ~/.config/muxa/config.toml
#    - the gitignored personal files created from agents/*/*.sample.{md,yaml}
#      (restore from a secure backup or replace every {{PLACEHOLDER}})
#    - re-login instead of copying Claude/Codex credential files

# 7. Codex directory trust is exact-path based and per-machine. The codex
#    component installs this helper from scripts/codex/workspace-trust-sync.sh.
~/.local/bin/codex-workspace-trust-sync

The three Git clones restore versioned configuration and scripts. They cannot restore credentials, dashboard tokens, or the personalized agents/static and agents/callabo/static files because those are deliberately gitignored. A matching file count under ~/.agents is therefore only a topology check; verify the contents and resolve the install-static placeholder warning before use.

Warning

These are personal settings for trusted workspaces. The managed Codex config uses approval_policy = "never" with sandbox_mode = "danger-full-access", and Claude settings skip the dangerous-mode confirmation. Do not install them unchanged on an untrusted repository or shared machine. The configured muxa, Oh My Prompt, and prompt-logger hooks also receive agent lifecycle events or prompt content; review those local tools and their storage policies first.

What each agent stores, and how it is managed

Agent	State	Managed as
Claude Code	`~/.claude/settings.json`	symlink → `configs/claude/settings.json`
Claude Code	`~/.claude/hooks/*.sh`	symlink → `agent-skills/hooks/`
Claude Code	`~/.claude/skills/skill-index`	symlink → `configs/claude/skill-index`
Claude Code	`~/.claude/skills/<category>/<name>`	46 symlinks rebuilt from `configs/claude/skills.manifest`
Claude Code	`~/.claude/projects/<slug>/memory`	symlink → `configs/claude/memory`
Claude Code	MCP servers	`claude mcp add` (idempotent, run by the module)
Codex	`~/.codex/config.toml`	merge — managed plugins/MCP/hooks + local trust, notify and UI state
Codex	`~/.local/bin/codex-workspace-trust-sync`	symlink/copy from this repo; regenerates exact-path project trust
Both	statusline	`cship` module (binaries + `~/.config/{cship,starship}.toml` symlinks)

Why Claude Code is symlinked but Codex is not. Claude Code never rewrites settings.json — a full session and the /config UI both left the symlink and its target untouched, so the repo copy can be the real file. Codex writes into its config continuously: 137 project-trust entries and 18 hook trust hashes on this machine. Symlinking it would drag that churn into git, so scripts/codex/apply-config.sh layers the managed half over whatever the local machine already has instead.

configs/claude/settings.json uses $HOME/... rather than absolute paths. Hook commands and statusLine.command are run through a shell, so the expansion happens at run time and the file works under any username. Codex does not expand $HOME in TOML values, which is why its per-machine paths are excluded from the template rather than rewritten.

Symlink or copy

Symlink is the default and the reason drift cannot happen: ~/.claude/settings.json is configs/claude/settings.json, so editing one edits the other. The cost is that the live config depends on the repo staying checked out at a branch that contains it.

--copy installs real files and directories instead, including all 46 nested skills, for machines where that dependency is unwanted:

./install.sh -c claude cship        # copy instead of symlink

Copy mode is idempotent — a second run compares contents and reports "already up to date" rather than re-copying. The trade-off is that local edits no longer flow back, so after changing a copied config you have to bring it into the repo by hand.

The self-extracting release bundle always forces copy mode because its temporary extraction directory is removed as soon as installation finishes.

No template engine sits in between: after excluding per-machine runtime state, zero managed values need substitution. configs/claude/settings.json and both cship configs contain no absolute paths at all, and Codex's template contains none either now that project trust, hook hashes and the version-pinned [[skills.config]] path are captured out.

Keeping the repo in sync

# after changing Codex settings by hand or through its UI
./scripts/codex/capture-config.sh && git diff configs/codex

# after adding or removing a nested Claude skill
python3 ~/.claude/skills/skill-index/build.py
./scripts/claude/capture-skills.sh && git diff configs/claude

Claude Code needs nothing — ~/.claude/settings.json is the repo file.

Deliberately not managed

	Why
`~/.envs/*.env`	Secrets. Restore by hand; `~/.agents/*.md` documents which key each integration needs.
`agents/{static,callabo/static}` personal files	Profile, endpoints and service-specific context. They are gitignored; restore from a secure backup or fill the generated samples.
`~/.claude.json`	MCP registrations sit next to per-project state Claude Code rewrites constantly. The `claude` module re-adds servers instead.
`~/.claude/.credentials.json`, `~/.codex/auth.json`	OAuth tokens. Re-login on the new machine.
`~/.config/muxa/config.toml`	Carries a dashboard auth token; restore it privately after installing muxa.
Codex `notify`	Absolute, machine-local Oh My Prompt hook path. Create it with `omp install codex`; later applies preserve it.
Codex project trust	Exact-path and per-machine; regenerate with the repo-installed `codex-workspace-trust-sync`.

Directory Structure

settings/
├── install.sh              # Main entry point
├── bootstrap.sh            # Remote installation bootstrap
├── lib/                    # Core libraries
│   ├── core.sh            #   Logging, spinner, utilities
│   ├── platform.sh        #   Platform detection, package manager
│   └── cli.sh             #   CLI argument parsing
├── modules/                # Installation modules
│   ├── base.sh            #   Basic packages
│   ├── shell.sh           #   Zsh + zinit + P10k
│   ├── editor.sh          #   NeoVim + LazyVim
│   ├── tmux.sh            #   tmux + TPM
│   ├── zellij.sh          #   zellij
│   ├── rust.sh            #   Rust + cargo-binstall
│   ├── python.sh          #   uv
│   ├── tools.sh           #   CLI tools
│   ├── ssh.sh             #   SSH config
│   ├── hishtory.sh        #   hishtory + self-hosted sync
│   ├── hammerspoon.sh     #   Hammerspoon (macOS-only)
│   ├── codex.sh           #   Codex CLI/App config
│   ├── claude.sh          #   Claude Code settings, skills and memory
│   └── cship.sh           #   cship + Starship statusline
├── worker/                 # Cloudflare Worker (settings.jiun.dev)
│   ├── index.js           #   Proxy raw GitHub content
│   └── wrangler.toml      #   Wrangler configuration
├── scripts/                # Build scripts
│   ├── bundle.sh          #   Create bundled installer
│   ├── claude/            #   Skill-farm capture helper
│   ├── codex/             #   Config capture/apply + trust sync
│   └── wsl2-network.ps1   #   WSL2 network setup script
├── configs/                # Configuration files
│   ├── .zshrc
│   ├── .p10k.zsh
│   ├── .tmux.conf         #   tmux configuration
│   ├── zellij/            #   zellij config + layouts
│   ├── nvim/              #   NeoVim + LazyVim config
│   ├── hishtory/          #   hishtory config template
│   ├── codex/             #   Codex managed config template
│   ├── claude/            #   Claude settings, manifest, index and memory
│   ├── cship/             #   cship + Starship configs
│   └── windows-terminal/  #   Windows Terminal configuration
└── .github/workflows/      # CI/CD
    └── release.yml         #   Auto-release on tag

Platform Support

Platform	Package Manager	Architecture
Ubuntu/Debian	apt	x86_64, arm64
macOS	Homebrew	Intel, Apple Silicon
WSL	apt	x86_64

Examples

# Preview installation (dry-run)
./install.sh --dry-run --all

# Install shell environment only
./install.sh zsh

# Install with verbose output
./install.sh -v zsh nvim tmux

# Force reinstall everything
./install.sh --force --all

# Install Rust and CLI tools
./install.sh rust tools tools-extra

Post-Installation

# Restart your shell
source ~/.zshrc
# or
exec zsh

# Verify installations
eza --version
fd --version
bat --version
rg --version

Shell Aliases

After installation, these aliases are configured in .zshrc:

# Modern replacements
alias ls='eza --icons'
alias ll='eza -la --icons --git'
alias cat='bat'
alias find='fd'
alias grep='rg'
alias du='dust'
alias ps='procs'
alias top='btm'

# Zellij (terminal multiplexer)
alias zs='zellij -s'        # new session
alias za='zellij attach'    # attach
alias zl='zellij list-sessions'  # list


# Editor
alias vim='nvim'
alias vi='nvim'

Windows Terminal Configuration

Configuration for Windows Terminal is available in configs/windows-terminal/settings.json.

How to apply

Open Windows Terminal
Press Ctrl + , to open Settings
Click Open JSON file at the bottom of the left sidebar
Copy the contents of configs/windows-terminal/settings.json and paste them into your settings.json

Tip

This configuration uses JetBrainsMonoNL Nerd Font. Make sure it's installed on your Windows system for the best experience.

Troubleshooting

View installation log:

cat ~/.install.log

Force reinstall a component:

./install.sh --force zsh

Run in verbose mode:

./install.sh --verbose --all

License

MIT

Name		Name	Last commit message	Last commit date
Latest commit History 330 Commits
.github/workflows		.github/workflows
.hammerspoon		.hammerspoon
.ssh		.ssh
assets		assets
configs		configs
docs		docs
lib		lib
modules		modules
scripts		scripts
vault-scripts		vault-scripts
worker		worker
.gitignore		.gitignore
.homumu.toml		.homumu.toml
README.md		README.md
bootstrap.sh		bootstrap.sh
install.sh		install.sh
iterm-default.json		iterm-default.json

Navigation Menu

Repository files navigation

Settings

Quick Start

One-Line Install (Recommended)

Manual Clone

Presets

Features

Usage

Components

Shell Environment

Editor

Terminal

AI Coding Agents

Development Tools

Modern CLI Tools

Shell History

AI Coding Tools

macOS Automation

Restoring AI agent state on a new machine

What each agent stores, and how it is managed

Symlink or copy

Keeping the repo in sync

Deliberately not managed

Directory Structure

Platform Support

Examples

Post-Installation

Shell Aliases

Windows Terminal Configuration

How to apply

Troubleshooting

License

About

Releases

Packages

Used by

Contributors

Languages

Folders and files

Latest commit

History

Repository files navigation

Settings

Quick Start

One-Line Install (Recommended)

Manual Clone

Presets

Features

Usage

Components

Shell Environment

Editor

Terminal

AI Coding Agents

Development Tools

Modern CLI Tools

Shell History

AI Coding Tools

macOS Automation

Restoring AI agent state on a new machine

What each agent stores, and how it is managed

Symlink or copy

Keeping the repo in sync

Deliberately not managed

Directory Structure

Platform Support

Examples

Post-Installation

Shell Aliases

Windows Terminal Configuration

How to apply

Troubleshooting

License

About

Resources

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages