chorus/chorus-memory.plugin.src/commands/chorus-reflect.md at 2ddf19985024bd540ee483392f4e8e307073a0e0

Files

T

jason d366ca4032 Phase 1: mechanical echo→chorus rename with back-compat shims

Identity rename, no behavior change (CHORUS-PLAN.md Phase 1):
- Plugin echo-memory → chorus-memory: manifest (v2.0.0-alpha.1), skill dir,
  16 scripts (chorus.py, chorus_config.py, …), EchoError → ChorusError,
  /chorus-* commands, hook paths, docs, scaffold seeds, eval harness,
  build.py. Docs endpoint → chorusapi.mpm.to.
- Env ECHO_* → CHORUS_*; config → ~/.claude/chorus-memory/config.json;
  state dir → ~/.chorus-memory/; marker → _agent/chorus-vault.md.

Back-compat shims (one major version):
- chorus_config aliases legacy ECHO_* env at import; reads a legacy
  echo-memory config.json when no CHORUS config exists (writes never
  land there); doctor/config report the legacy source.
- State dir honors an existing ~/.echo-memory when the new dir is absent
  (offline queue not stranded).
- Marker dual-probe in load/doctor/bootstrap/lint/sweep/migrate: a
  pre-fork _agent/echo-vault.md counts as bootstrapped; bootstrap repair
  won't write a second marker; routing gains agent-marker-legacy (GET).

Verified: 25/25 unit tests, scaffold + routing-sync checks, 4 mock e2e
suites, run_eval metrics unchanged, +6 shim smoke tests green.
Rebuilt chorus-memory.plugin (79 entries).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-21 13:35:51 -05:00

2.0 KiB

Raw Blame History

description, argument-hint

description	argument-hint
Reflect on this session — extract durable memories and propose them for one-tap capture	[optional focus, e.g. 'just decisions']

Use the chorus-memory skill to run session reflection (H5). Scan this conversation for things worth remembering across sessions, then propose them — don't write blindly.

Extract durable items from the conversation: new facts, preferences, decisions, commitments, people/companies/projects introduced, and anything the operator said to remember. Skip the ephemeral. Anchor relative dates on the conversation's currentDate.
Emit a JSON array of proposals (one per item), each: {"title","kind","body","aliases","tags","sources","confidence"} — kind ∈ person, company, concept, reference, meeting, project, area, semantic, episodic, working, skill, decision; set "inbox": true when the home is genuinely unknown; confidence 0–1 (items below 0.6 are dropped — send those to the inbox instead). Write the array to a file with the Write tool (cross-platform; no heredoc).
Preview, then apply. Dry-run first (writes nothing) and show the operator the plan; only apply after they confirm.

CHORUS="${CLAUDE_PLUGIN_ROOT}/skills/chorus-memory/scripts/chorus.py"   # python3 (Windows: python / py -3)
[ -f "$CHORUS" ] || CHORUS=$(ls /sessions/*/mnt/.remote-plugins/*/skills/chorus-memory/scripts/chorus.py 2>/dev/null | head -1)   # CoWork sandbox fallback
python3 "$CHORUS" reflect proposals.json            # dry-run: validate + classify + preview
python3 "$CHORUS" reflect proposals.json --apply    # write — routes each via capture (indexed, linked, logged)

reflect dedups every proposal against the entity index (so it shows create-vs-update), skips below-confidence items, and routes inbox proposals to the capture inbox. Each applied item goes through the normal capture path — canonical frontmatter, auto-linking, and the recall index — and the writes are lock-guarded. $ARGUMENTS

2.0 KiB Raw Blame History Unescape Escape

2.0 KiB

Raw Blame History