Add new machine rollout guide

README.md

@@ -24,6 +24,7 @@ The biggest issue was not a lack of raw stored data. It was that durable, reusab
 ## Repo Layout
 
 - `docs/research.md`
+- `docs/new-machine-setup.md`
 - `templates/global/AGENTS.md`
 - `templates/global/config.toml`
 - `memory/`
@@ -37,6 +38,14 @@ Install this kit into your current Codex home:
 bash scripts/install_codex_kit.sh
 ```
 
+Set up a fresh machine from this repo:
+
+```bash
+git clone https://github.com/slaguru666/codex-ops-kit.git
+cd codex-ops-kit
+bash scripts/install_codex_kit.sh
+```
+
 Create a portable export bundle you can move to another machine:
 
 ```bash
@@ -83,4 +92,8 @@ Run the audit script periodically. If session storage balloons again, archive th
 - `balanced`: everyday profile
 - `deep`: higher-effort work when architecture or debugging really needs it
 
-These profiles are defined in [templates/global/config.toml](/Users/timevans/Documents/New%20project/templates/global/config.toml). The installer preserves machine-specific plugin and trust settings while merging the managed cost and memory block into your live `~/.codex/config.toml`.
+These profiles are defined in `templates/global/config.toml`. The installer preserves machine-specific plugin and trust settings while merging the managed cost and memory block into your live `~/.codex/config.toml`.
+
+## New Machine Rollout
+
+Use the short guide in `docs/new-machine-setup.md` when bringing another Mac or workstation onto the same Codex setup.

docs/new-machine-setup.md

@@ -0,0 +1,84 @@
+# New Machine Setup
+
+This guide is the shortest path for rolling the Codex Ops Kit onto another machine.
+
+## 1. Clone The Repo
+
+```bash
+git clone https://github.com/slaguru666/codex-ops-kit.git
+cd codex-ops-kit
+```
+
+## 2. Install The Kit
+
+```bash
+bash scripts/install_codex_kit.sh
+```
+
+What this does:
+
+- backs up any existing `~/.codex/config.toml`
+- backs up any existing `~/.codex/AGENTS.md`
+- installs the managed profile block
+- installs the global `AGENTS.md`
+- copies the portable memory notes into `~/.codex/memories/portable-kit/`
+
+## 3. Start Using Profiles
+
+- `balanced`: default for most work
+- `economy`: use for smaller tasks and cheaper runs
+- `deep`: use for hard debugging, architecture, and more demanding tasks
+
+## 4. Carry Forward Durable Memory
+
+When you learn something worth reusing, update the markdown files in:
+
+```bash
+~/.codex/memories/portable-kit/
+```
+
+Then commit those changes back to this repo so your other machines can pull them.
+
+## 5. Keep Local Storage Healthy
+
+Audit the Codex home:
+
+```bash
+bash scripts/audit_codex_home.sh
+```
+
+Preview large old transcripts:
+
+```bash
+bash scripts/prune_codex_sessions.sh
+```
+
+Archive them after review:
+
+```bash
+bash scripts/prune_codex_sessions.sh --apply
+```
+
+## 6. Sync To Another Machine
+
+On the machine that already has the latest memory updates:
+
+```bash
+git add memory docs README.md templates scripts
+git commit -m "Update Codex kit memory and setup"
+git push
+```
+
+On the next machine:
+
+```bash
+cd codex-ops-kit
+git pull
+bash scripts/install_codex_kit.sh
+```
+
+## Notes
+
+- Do not sync `~/.codex/auth.json`.
+- Do not sync live SQLite databases or raw `sessions/` history.
+- Keep the portable layer small and curated so Codex does not waste tokens reloading unnecessary context.