CLI: query and briefings

These commands are the read path agents should use before making project-specific claims. They turn curated memories, activity, commits, and source evidence into answers and briefings.

codifix query

Ask concrete project questions and inspect the cited memories.

codifix query --project memory --question "How does the MCP server resolve projects?"
codifix query --project memory --question "What changed in the docs site?" --json

Useful options vary by version, so check codifix query --help; common knobs include result limits, confidence thresholds, output modes, graph-aware retrieval, and LLM-backed answer synthesis. Current common filters include --type, --tag, --limit, --min-confidence, --include-stale, --history, and --json.

Good questions name the project object, subsystem, file, workflow, or decision you care about. Avoid vague prompts like “what do you know?” when you need actionable context.

codifix resume

Resume is for returning after interruptions.

codifix resume --project memory
codifix resume --project memory --limit 20

It combines recent activity, changed memories, warnings, next actions, and checkpoint context when available.

codifix up-to-speed

Use this for a new agent or a wider handoff.

codifix up-to-speed --project memory
codifix up-to-speed --project memory --llm

It is broader than resume and should be run at task start when the agent lacks project continuity.

codifix activities

Activities are persisted audit events.

codifix activities --project memory --limit 30
codifix activities --project memory --kind checkpoint

Use activity output to verify whether captures, curation, proposals, embedding jobs, watcher events, or checkpoints actually happened.

codifix history

History shows how canonical memories evolved.

codifix history <memory-id>
codifix history <memory-id> --json

Use it when a remembered fact seems stale, replaced, or tombstoned.

codifix verify-provenance

Verify provenance before relying on a memory that cites files or directories.

codifix verify-provenance --project memory
codifix verify-provenance --project memory --json
codifix verify-provenance --project memory --dry-run --json

This does not prove a memory is semantically correct, but it catches missing, moved, or changed source evidence.