Skip to content

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

83 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

environment — dotfiles and tools for ghost, silence, and the box

One repo that defines three machines: ghost (Mac Studio, the always-on compute machine), silence (MacBook Pro, the portable client), and the box (a Linux agent machine). Config is shared through Stow. Programs are installed directly — no Homebrew. Each machine keeps its own secrets and app state.

The machines

  • ghost — always on. Owns all projects, the OpenCode service, Postgres, the SSH host, and the Zed/Cursor remote servers. Work happens here.
  • silence — portable client. UIs run here; files, tools, and agents act on ghost over Tailscale + SSH. silence is set up; its ongoing job is to stay in sync with ghost.
  • the box — Linux (Debian, x86_64) agent machine with Claude Code + pstack, plus the OpenCode CLI. Same Stow tree and pinned tools as the Macs, Linux builds. Runs no OpenCode service, no Postgres, and no local tailscale or tailscaled (a client on the box is wiped when the box is replaced). Tailnet access comes from Grok Bot's Tailscale connector, authenticated in the Grok Bot app. Address tailnet hosts by their full MagicDNS name (ghost.tail483f5.ts.net, silence.tail483f5.ts.net) over HTTPS. SSH from the box is not supported (its shell egress is an HTTP proxy). The box works on ghost through ghost-env, an MCP server on ghost (envd, LaunchAgent dev.scozu.envd) served tailnet-only at https://ghost.tail483f5.ts.net/mcp and added in Grok Bot as an MCP server: doctor, versions, repo status, fast-forward pull, stow dry run. The proposed tailnet policy limits the box's device (tag:grokbot) to ghost:443 — see docs/tailnet-policy.md (not applied yet). Linux-only behavior sits behind uname -s checks in the scripts or in the gitignored .local files.

What this repo contains

  • home/ — the Stow package (dotfiles), target $HOME
  • scripts/doctor.sh — read-only health check for the current machine
  • scripts/envd-setup.sh — ghost only: install/start envd and its 443 serve
  • launchd/ — LaunchAgent templates rendered by setup scripts (not stowed)
  • docs/tailnet-policy.md — proposed Tailscale policy for the box
  • docs/tools.md — how programs are installed and updated (read this before touching any tool)
  • docs/workflows.md — the daily operating manual

How programs are installed (no Homebrew)

Every CLI tool lives at ~/.local/opt/<tool>/ with symlinks to its executables in ~/.local/bin, which .zshenv puts first on PATH. The same file also exports RUSTUP_HOME and CARGO_HOME under ~/.local/opt/rustup. Runtime state (Postgres data, logs) lives in ~/.local/var/. Two exceptions: OpenCode installs itself to ~/.opencode/bin, and desktop apps are .app bundles in /Applications (see the GUI apps section of docs/tools.md).

To install or update any program — "install bun", "update nvim", anything — follow the playbook in docs/tools.md. It is the same procedure for every tool. This README and that file together are the source of truth: when you change a tool, update its entry in the inventory in the same commit.

The three loops

1. Stow loop — edit shared config

cd ~/Developer/environment
stow --no-folding -n -t "$HOME" home   # dry run — read it
stow --no-folding -t "$HOME" home      # apply

--no-folding links files but leaves parent directories real (~/.cursor and the Cursor User directory must stay real; the apps write state into them).

  • Edit files under home/ in this repo. A GUI may rewrite a linked file (Zed settings, Cursor settings, OpenCode config): commit real setting changes, git restore the noise.
  • Stowed files: .zshenv (PATH), .zshrc, .ssh/config, Neovim config, Ghostty config, Zed settings, OpenCode opencode.jsonc, AGENTS.md, and agents/lead.md, Claude Code ~/.claude/settings.json and ~/.claude/rules/pstack-models.md, Rex ~/.config/rex/init.lua, Cursor rules (~/.cursor/rules/*.mdc), and the rex and envd scripts in ~/.local/bin (envd's server is ~/.local/share/envd/envd.ts). Cursor User/settings.json is deliberately not stowed — the app rewrites it as state (see docs/workflows.md).
  • Machine-specific values go in the gitignored .local files, which the stowed configs source automatically: ~/.zshrc.local (aliases), ~/.zshenv.local (env vars), ~/.ssh/config.local (SSH overrides).
  • On the other machine: git pull — existing symlinks update in place, no re-stow needed. On a machine without the links yet, run Stow after pulling.
  • If the dry run reports a conflict, move that file out of $HOME and retry.

2. Tool loop — install or update a program

Pin a version, put the program in ~/.local/opt/<tool>, symlink its entry points into ~/.local/bin, record the version in the tools inventory, verify with doctor.sh, repeat on the other machines. Full procedure: docs/tools.md.

The direct release tools (nvim, pnpm, bun, node, gh, cloudflared, claude, ffmpeg, rustup, cmake, poppler) are scripted: scripts/sync-tools.sh installs or updates them to the pinned versions on whichever machine it runs, macOS or Linux (--check is read-only; doctor uses it). rustup, cmake, and poppler are macOS pins (the box skips them, like claude): cmake is a Kitware official binary, used only to source-build poppler (pdftotext; no official macOS binary). stow and postgres (source builds) and opencode (self-updating) stay manual by design.

3. Doctor — verify the machine

cd ~/Developer/environment && scripts/doctor.sh

A clean run means the Stow tree is settled and this machine's checks passed. Run it after every change, on every machine. It detects its role: ghost by hostname, the box by uname -s = Linux, otherwise silence.

Never commit these

.gitignore blocks the copies that would land inside home/:

  • SSH private keys, known_hosts, authorized_keys
  • the .local override files
  • OpenCode service.json, auth.json, and ~/.local/share/opencode data
  • Cursor argv.json (per-machine crash-reporter id), cli-config.json, plugins, extensions, project caches, and other app state the apps rewrite

Rules that keep this working

  1. No Homebrew. Every tool follows the direct-install pattern, or documents its exception in docs/tools.md.
  2. Docs are part of the system. Any tool change updates the inventory in docs/tools.md in the same commit.
  3. Secrets and app state never enter the repo. Machine-specific config goes in the .local files.
  4. ghost and silence run the same tool versions, and the box matches them except Claude Code. The box is still on 2.1.302 while the Macs are on 2.1.325, so the box needs upgrading (claude install 2.1.325). That upgrade has not been done. Doctor does not compare the box's Claude version. Doctor runs clean on all three.

Read the longer docs

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages