chorus/chorus-memory.plugin.src/commands/chorus-recall.md

---
description: Recall a topic from CHORUS memory — matching notes plus their linked neighbourhood
argument-hint: "[topic, person, or project]"
---

Use the **chorus-memory** skill to recall context for:

> $ARGUMENTS

Run the one-call recall — it resolves the term against the entity index, searches, and expands one hop along `## Related` links and `source_notes`, so you get the connected web (linked decisions, people, prior sessions), not an isolated note:

```bash
CHORUS="${CLAUDE_PLUGIN_ROOT}/skills/chorus-memory/scripts/chorus.py"
[ -f "$CHORUS" ] || CHORUS=$(ls /sessions/*/mnt/.remote-plugins/*/skills/chorus-memory/scripts/chorus.py 2>/dev/null | head -1)   # CoWork sandbox fallback
python3 "$CHORUS" recall "$ARGUMENTS"   # add --author <member> to filter to one member's notes
# Windows: use `python` or `py -3` if `python3` is not on PATH.
```

The corpus spans the entity graph **plus session logs and journal notes**, ranked by relevance × freshness × status — each hit shows its `updated:`/`status:`, so prefer fresh/active hits and treat stale ones as history. Add `--json` for structured hits (`path/score/type/updated/status/excerpt`) when you need to act on the results programmatically.

Then answer from the assembled context. If you only need the canonical path for one entity, use `chorus.py resolve "<title>"` instead. Don't narrate the retrieval.