Cross-machine parity via sync
Cross-machine parity via sync
Rule
Every machine (corp laptop, personal laptop, future laptop) can be primary. Sync auto keeps them equal. No machine-specific state that can't be reproduced from cloud + workspace.
Machines in scope
- Corp laptop — Windows 11,
C:\D\oriz. Bedrock chain for Claude. Currently primary. - Personal laptop — TBD build. Same workspace layout. Free-provider fallback for AI.
- Future laptops — bootstrap from
install-and-bootstraprunbook.
What syncs
- Workspace tree —
git clone --recurse-submodules chirag127/workspace. - Memory —
chirag127/claude-memorypull on SessionStart. - Globals —
sync-globals.mjsderives~/.claude/,~/.opencode/, etc. from workspace. - Skills — junction from
repos/own/infra/agent-skillsto user-global dirs.
What does NOT sync
- Auth tokens — per-machine, in
~/.claude/settings.local.json(gitignored). Re-auth on new machine. - Session logs / TUI history — ephemeral.
- Absolute binary paths — machine-specific; scripts detect at runtime.
Bootstrap on new machine
Per install-and-bootstrap runbook. 5-minute target:
gh auth logingit clone --recurse-submodules https://github.com/chirag127/workspace.git C:\D\orizcd C:\D\oriz\repos\own\backup && .\bootstrap.ps1(installs everything)node scripts/sync-globals.mjs --bootstrap(writes globals)- Import age key from Bitwarden
- First session pulls MEMORY.md automatically
Why 5-min target
- Corp laptop failure = personal laptop primary within 5 min = no work-day lost.
- Card-off dependency check — nothing in bootstrap requires paid tier.
Anti-patterns
- ❌ Machine-specific rules or scripts that don't check
hostnameor per-machine profile - ❌ Uncommitted config that "works on my machine"
- ❌ Manual sync steps not in a script — cron / hook everything