remember

Run friction analysis, then consolidate .factory/stash/*.md + friction antigens into one project-local .factory/remember/MEMORY.md and inject it into AGENTS.md. Friction runs automatically (best-effort) — there is no separate /friction command. A detect-only docs check runs at the end. Why each rule exists: docs/product/remember-README.md.

Rules

• Simple and scoped: minimal implementation, only the requested outcome.
• Scripts: call every bundled script (friction.cjs, version-check.cjs, sync-rules.cjs, stub-check.cjs, docs-builder.cjs) by its absolute path — the cwd is the target repo, not this package, so a cwd-relative path fails.
• Precision over recall: a false antigen loaded via @.factory/remember/MEMORY.md steers every future session — unsure → do not promote; leave it to recurrence.
• Mid-tier model: steps 2, 3 and 4a use your tool's balanced mid tier — never the cheapest tier, never a vendor model name.
• Batch stashes: up to 5 stashes per extraction agent, as few agents as possible (3 → 1 agent, 7 → 2); if more than one, run them concurrently.
• Facts are short rules, not prose: one line, target 160 chars, hard stop 180, stating a rule that changes future behaviour. Events and history are not facts.
• Never re-read session logs: work from the quotes in antigen_clusters.json.
• Never hand-compute counts: friction.cjs count does them.
• Relay script output verbatim, never re-worded (a paraphrase loses the filename the user needs). This covers output meant for the user; JSON a step consumes (e.g. friction.cjs count) is input, not something to relay.
• Tiers (defined once): High = 5+ distinct sessions → loaded hot via @MEMORY.md; Medium = 3-4 → recorded under Antigens, not loaded; Low = under 3 → ledger observing at 2 sessions, nothing at 1. Grouping consolidates evidence, never elevates it. Never auto-promote below High.

Steps

1. Run friction first (best-effort — friction analyzes ALL your usage, so point it at the tool's global sessions root, not a per-project directory)

   • Locate friction.cjs — bundled at remember/friction.cjs beside this file (installed or run from the package). If it exists nowhere, skip to step 1 (stash-only) and tell the user it is missing.
   • Check for a newer liteagents (best-effort, one line, never blocking):

     node ~/.factory/commands/remember/version-check.cjs
     

     If that path does not exist, use the directory you resolved for friction.cjs (the two ship side by side). It prints one advice line if the install is behind the registry, else nothing; it exits 0 always, caches 24h, and is bounded to ~2s. If it prints a line, relay it verbatim in the final report; never act on it, never run the install yourself.
   • Script missing from both locations → say so (one line). A failed check (offline, registry down, timeout) stays silent by design; a missing script means an incomplete install.
   • Resolve the global sessions root — probe top-to-bottom, use the first that exists and holds .jsonl files directly or one level down in per-project subdirectories (friction scans exactly those two levels). Never prompt the user.

     # ── Add your own global sessions root at the TOP so it is checked first ──
     ~/.claude/projects/                 # Claude Code
     ~/.factory/projects/                # Droid / Factory
     ~/.config/amp/projects/             # Amp
     ~/.config/opencode/projects/        # opencode
     ~/.codex/sessions/                  # Codex CLI  (use $CODEX_HOME/sessions/ if set)
     ~/.gemini/antigravity-cli/brain/    # Antigravity
     

     Note: friction.cjs parses Claude Code's session schema. The Codex/Antigravity roots will resolve but yield no signals until friction learns their formats — open an issue to request one: https://github.com/hamr0/liteagents/issues

   • Run node <friction.cjs> "<resolved-root>". It writes to .factory/remember/friction/ in the current project. Run it as its own command — nothing chained before or after it — with a 10-minute tool timeout: it scans the whole sessions root and can take a minute or more.
   • On any miss — loud, never silent. If no root resolves, friction errors, or it finds no usable sessions, print this and continue stash-only:

     ⚠️ Friction didn't run — no sessions found. To enable it, open this skill's own file and add your tool's global sessions root to the TOP of the probe list in step 0, then re-run /remember. Consolidating stashes only this time.