How Recon works

Recon combines two things that are normally separated: what exists in your artifacts and what happened while you worked on them.

1. Sources provide the boundary

Recon reads only the folders and documents you confirm. Files are evidence, not a second copy of your entire filesystem. Raw events and exact live state should still come from their original systems.

2. Knowledge organizes what is current

Recon reads supported files in bounded batches, extracts source-backed facts, connects related topics, and forms a concise current view. The original receipts remain attached, including older information that was not used in the short summary.

Knowledge is a projection over evidence. It is not the only copy of your memory and can be rebuilt as organization improves.

3. Work preserves the reasoning

The installed Recon guidance asks a supported Claude Code or Codex session to retrieve relevant memory before it guesses. When a durable decision, rejection, correction, lesson, or revisit condition lands, the agent captures that specific result.

Recon does not save every message. It keeps the parts that should survive the session.

4. Recall returns a bounded answer

When you ask a question, Recon retrieves a small set of relevant local receipts. Your selected AI connection uses that context to form an answer. Follow-up questions use a bounded rolling conversation summary instead of resending an unlimited transcript.

A good answer can show:

• what was decided
• why it was decided
• what was tried or rejected
• what changed later
• when the choice should be revisited
• which file or work session supports each claim

5. You can inspect the system

Use Knowledge to inspect a topic and its connections. Use Your Work to inspect meaningful efforts and their sessions. Open receipts to verify the source. Use Settings > AI usage to see which model-backed operations ran and whether token counts are reported or estimated.