capture

You can capture conversation decisions and technical notes by appending timestamped bullet entries to a staging file, preserving important facts for later reflection before the session ends.

Append-only logging for conversation facts works by resolving a staging path and adding new timestamped entries with a manual source marker, ensuring prior records remain unchanged for downstream knowledge-graph processing.

Yes, you can extract only technical details or only decisions from a coding session by passing a targeted keyword to the capture command, which filters and stages the specific subset of facts you need.

The best way to auto-summarize important facts is to invoke the capture command with no arguments, which automatically extracts the 3–8 most important facts from the current conversation and stages them.

Yes, manual fact capture works with session-end reflection hooks by using manual source markers to deduplicate entries, allowing automated end-of-session processing to run alongside on-demand staging without conflicts.

Staged conversation facts are stored in an append-only markdown file located at the project scripts directory or a fallback home directory path, ensuring consistent access for downstream knowledge-graph updates.