RAGit
CommandsMemory

memory recall

Rebuild the smallest useful packet for resuming work

What It Does

memory recall reconstructs the packet you need to continue active work. It starts from current working memory and then supplements it with the same retrieval planner/executor used by query and context pack, plus recall-only artifact overlays that are relevant to the goal.

When To Use / When Not To Use

When to use it

  • You are resuming an interrupted task.
  • You want open loops, constraints, related decisions, and next actions in one packet.

When not to use it

  • You only want a general repository search. Use query.
  • You only want a prompt-sized retrieval pack with no working state. Use context pack.

Syntax

pnpm ragit memory recall <goal> \
  [--view minimal|default|full] [--format text|json|both] \
  [--cwd <path>]

Arguments And Options

  • <goal>: The task you want to resume.
  • --view minimal|default|full: Control how much retrieved detail is projected into the packet.
  • --format text|json|both: Choose text, JSON, or both.
  • --cwd <path>: Run against another repository.

Input And Output Contract

  • Input is positional only.
  • JSON output includes goal, constraints, openLoops, relatedDecisions, retrievedHits, and nextActions.
  • retrievedHits can contain both snapshot hits and artifact-origin hits, but the packet still remains selective rather than replaying raw history.
  • --view minimal is the best default for agent resumes.
  • --view default balances readability and detail.
  • --view full is only for cases where the restored packet must carry richer text from retrieval hits.

Examples

Human terminal flow:

pnpm ragit memory recall "resume auth flow"

Agent-oriented flow:

pnpm ragit memory recall "resume auth flow" --view minimal --format json

Failures And Cautions

  • memory recall depends on working-memory state quality. If wraps are poor, recall quality drops too.
  • This command does not replay the entire session history. It intentionally produces a selective packet.
  • When snapshot retrieval is unavailable, recall can still return an artifact-backed packet with warnings instead of failing immediately.