Passive Capture

Review Queue

All passive capture sources produce drafts. Review and confirm them in one place.

Why Drafts?

Passive capture is designed to be fast and silent. When the scanner, git hooks, file watcher, or MCP auto-capture detect something that looks like a decision, pattern, or context update, they do not immediately write it to memory. Instead, they create a draft.

This gives you full control. You review drafts when it suits you — at the end of a session, before pushing, or whenever contxt status shows pending items. Nothing enters your memory store without your explicit confirmation.

CLI Interface

$ contxt review                  # Interactive review of all drafts
$ contxt review --source scan     # Only from code scanning
$ contxt review --source hooks    # Only from git hooks
$ contxt review --source mcp      # Only from MCP auto-capture
$ contxt review --confirm-all     # Confirm everything without prompting
$ contxt review --discard-all     # Discard everything without prompting
$ contxt review --count           # Just show the pending count

Interactive Mode

Running contxt review without flags opens an interactive session. Each draft is shown in full with its source and detected type:

contxt review — 3 drafts pending

[1/3] DECISION  (source: hooks:post-commit)
  "Migrate from Express to Fastify"
  detected from: feat(server): switch to Fastify for better perf

  [c] Confirm   [e] Edit then confirm   [d] Discard   [s] Skip
> c
  ✓ saved to memory.

[2/3] PATTERN   (source: scan)
  "API routes: Zod schema → validate → handler → typed response"
  detected in: src/api/users.ts:12

  [c] Confirm   [e] Edit then confirm   [d] Discard   [s] Skip
> e
  opening editor...

[3/3] CONTEXT   (source: mcp:auto)
  "Refactoring auth middleware to support multi-tenancy"

  [c] Confirm   [e] Edit then confirm   [d] Discard   [s] Skip
> d
  discarded.

review complete — 2 confirmed, 1 discarded

Draft Sources

Every draft carries a source tag so you know exactly where it came from during review.

Source tagOrigin
scanCode comment extraction via contxt scan
hooks:post-commitDetected from git commit messages by the post-commit hook
import:readmeExtracted from README, Cursor rules, Claude config, or ADR files via contxt capture
mcp:autoAI auto-capture during an MCP conversation session with Claude Code or Cursor

Status Reminder

The pending draft count surfaces in contxt status so your normal workflow check always includes a reminder:

$ contxt status

  project   my-app
  branch    main
  session   active — 42 min
  drafts    3 pending  ← run "contxt review" to process