← ClaudeAtlas

memory-worktreelisted

Verify, customize, or opt out of moflo's AUTOMATIC durable-learning sharing across git worktrees / Conductor workspaces on one machine. As of the worktree-auto-sharing change this is on by default — learnings converge across a repo's worktrees with no setup. Use when the user asks "is memory shared across my worktrees?", "where are my worktree learnings stored?", "turn off worktree memory sharing", "share learnings across my separate clones", or "point my worktrees at a custom store". For a team or cross-machine (git-tracked) sharing, use /memory-team instead.
eric-cielo/moflo · ★ 18 · AI & Automation · score 81
Install: claude install-skill eric-cielo/moflo
# /memory-worktree — Durable Sharing Across Worktrees (Automatic) Working across git worktrees is a core moflo competency, so durable-learning sharing across the worktrees of a repo is now **automatic and on by default**. When a checkout is part of a repo with worktrees in play, moflo derives a shared durable store at **`<git-common-dir>/moflo/durable.db`** and converges the `learnings` + `knowledge` namespaces across every worktree at session start — no config. A plain single checkout writes nothing and behaves exactly as before. This skill is for the three things you might still want: **verify** it's working, **customize** where it stores (or extend it to non-worktree clones), or **opt out**. > Only the durable slice travels. Structural + ephemeral data stays local per checkout and rebuilds > itself — the same safety model the auto path is built on (a dedicated `durable.db`, never a full > `moflo.db`). See [[memory-team]] for the git-tracked, cross-machine variant. **Arguments:** `$ARGUMENTS` — `--off` to opt out, `--path <store>` to set a custom shared store. ## When to use - "Is memory / are learnings shared across my worktrees?" → **verify** (Step 1). - "Where are my worktree learnings stored?" → it's `<git-common-dir>/moflo/durable.db`; verify to confirm. - "Turn off / disable worktree memory sharing" → **opt out** (Step 2). - "Share learnings across my separate clones / a custom location" → **customize** (Step 3). For a team, or your own laptop+desktop over git,