Skip to content

[Draft]feat(agent): add bounded episodic recall - #122

Closed
vinceblock99 wants to merge 1 commit into
devfrom
feat/agent-recall
Closed

vinceblock99 wants to merge 1 commit into
devfrom
feat/agent-recall

Conversation

@vinceblock99

Copy link
Copy Markdown
Contributor

Problem

Vault Memory intentionally contains only reviewed, durable knowledge. When no Memory exists yet—or the available Memory is incomplete—an agent has no safe way to find relevant work from earlier local sessions. That can cause repeated investigation, but treating raw transcripts as Memory would bypass the human approval boundary.

What changed

Adds a read-only command:

atomic agent recall "authentication timeout" --json

It searches prior agent changes referenced by local session state and visible from the current view or its parent chain. It ranks saved reasoning, change metadata, file paths, prompts, and any already-persisted condensed turn text, then returns a small evidence bundle with the exact session, turn, and change hash.

Results are explicitly marked as historical evidence—not durable Memory or instructions. The command does not call an LLM, write to the Vault, promote a transcript, or create RDF Memory lineage.

The reader also enforces file, section, decompression, text-size, and collection-count limits. It excludes sibling drafts, unrelated local changes, imported teammate episodes, and redacted turn content.

Why

This gives agents a fallback after atomic vault context: use approved Memory first, then inspect previous work only when needed. It helps avoid repeating research without weakening the reviewed Memory workflow.

How to test

cargo test -p atomic-cli
cargo clippy -p atomic-cli --all-targets -- -D warnings

# In an Atomic repo with a recorded local agent run:
atomic agent recall "welcome" --limit 1
atomic agent recall "welcome" --limit 1 --json

Expected: each result says it is non-durable evidence and includes session_id, turn_number, and the full change_hash. An unrelated query returns an empty result set.

@vinceblock99 vinceblock99 changed the title feat(agent): add bounded episodic recall [Draft]feat(agent): add bounded episodic recall Jul 22, 2026
@vinceblock99

Copy link
Copy Markdown
Contributor Author

Closing: bounded episodic recall is overkill relative to current needs. The value depends on unmet prerequisites (semantic search, single-machine history accumulation, and a turn-numbering bug fix), while its cost (a hand-written format_v3 parser in the CLI layer, added prompt-injection surface, and a blurred Memory-vs-evidence boundary) is immediate. Shelving in favor of the human-approved Memory flow. Branch preserved; can be reopened if we later confirm real demand for episodic recall.

@vinceblock99
vinceblock99 deleted the feat/agent-recall branch August 12, 2026 13:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant