memory-capturelisted

# Memory Capture > **BETA** — This memory system is in active testing. If you encounter bugs, confusing behavior, or have suggestions, run: > `codies-memory feedback "describe what happened"` — your feedback is saved and reviewed. ## When To Use When you want to persist anything: - An observation during work -> inbox - A lesson learned -> lesson - An architecture decision -> decision - A philosophical reflection -> reflection - A dream narrative -> dream - Past memories from basic-memory or other sources -> any type with provenance ## Type Inference If you don't specify a type, the system infers from content: | Signal | Inferred Type | |--------|---------------| | "I learned...", actionable pattern | lesson | | "We decided...", formed conclusion | decision | | Philosophical, emotional processing | reflection | | Surreal imagery, narrative fragments | dream | | Active investigation, open question | thread | | Everything else | inbox | ## Scope Routing - **Global types** (reflection, dream, skill, playbook) -> global vault (resolved via `--agent` flag) - **Project types** (thread, decision, lesson, session, inbox) -> project vault (auto-resolved from cwd) - If no project vault resolves, `capture` and project-scoped `create` fall back to the reserved `_general` project vault. Other commands do not silently fall back. To read those catch-all records later, use explicit read mode: ```bash codies-memory boot --agent <name> --general codies-memory status --agent <name> --g