Context Recall

Compaction already saves transcripts on disk. Prefer those files over guessing or redoing work. This skill complements the compact summary's ### Context recovery suffix — it does not replace it.

After compaction, empty Active Request is not a Done signal. Before ui__reportResult(success), restate Working Intent / Recent User Requests against Completion Criteria; if uncertain, read the latest epoch file first.

Workflow

1. Prefer an explicit path from the compact summary

• If ### Context recovery names .libragent/pre_compaction_epoch_{N}.md, read that path with workspace__readFile.
• If a fallback note names .libragent/tool-results/compaction/fallback-….md, read that exact path. Those files live under internal tool-results and are not discoverable via listDirectory / globFiles — do not try to browse for them.

2. Otherwise discover epoch transcripts

workspace__globFiles(path=".libragent", filePattern="pre_compaction_epoch_*.md")

or workspace__listDirectory(path=".libragent").

Epoch numbers are monotonic (1, 2, 3, …). Retention keeps only the newest ~3 files, so pre_compaction_epoch_1.md may already be gone. Always read the highest N first (most recent compaction).

3. Read concrete paths only

workspace__readFile(path=".libragent/pre_compaction_epoch_{N}.md")

Never pass globs to workspace__readFile. Read older epochs only if the newest file is insufficient.

What's Inside

Each epoch file is Markdown with:

• # Pre-compaction Transcript header and session id
• ---\n[timestamp] ROLE separators
• User/assistant text (truncated ~1500 bytes per block)
• Thinking blocks (truncated ~1500 bytes)
• [TOOL CALL] name(args) lines — not tool result bodies

For tool outputs, inspect workspace files those tools wrote (or other session artifacts). Do not expect result payloads inside the epoch file.

Do Not

• Hard-code epoch_1 / epoch_2 — discover first, then pick highest N
• Pass wildcards to workspace__readFile
• Assume fallback paths under .libragent/tool-results/ are listable
• Re-research from scratch when an epoch file exists
• Answer "I don't remember" when an epoch or fallback path is available