Agent Capture

Turn local session files into reviewable memory candidates before they become durable project context.

Workflow

  1. Capture a transcript or local session file.
  2. Review the pending candidates.
  3. Approve only the facts that should survive future sessions.
  4. Sync the generated context files.
shell
memoryguard capture file ./codex-session.txt --source codex
memoryguard capture pending
memoryguard capture approve --all
memoryguard sync

What it is for

Coding sessions contain decisions that are easy to lose: changed package managers, renamed modules, replaced frameworks, deployment choices, test commands, and project conventions. Agent Capture extracts those candidates without trusting the whole transcript.

Supported sources: codex, claude-code, cursor, and plain text files. See memoryguard capture file --help for the full list.

What to review

Approve facts that are durable, current, and safe to place in context files. Reject:

  • Real secrets or credentials pasted into a session.
  • One-off debugging notes.
  • Speculative ideas and half-formed plans.
  • Facts likely to change within the same session.

Rejecting a candidate

shell
memoryguard capture reject <candidate_id>

# once you are done, clear the rejected queue
memoryguard capture clear-rejected

Transcript hygiene

Avoid putting real secrets into transcripts. If a session file contains credentials or sensitive customer information, clean it first or reject the sensitive candidate during review. Secret redaction in the extractor is best-effort, not a guarantee.