Persist agent memory and isolate prompt evaluation - #1
Merged
Merged
Conversation
MemoryWorld
marked this pull request as ready for review
September 22, 2026 14:11
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fresh agents skipped their first memory write because empty memory objects were falsey. Persist complete memory snapshots, summary counters and access counts, restore them across runs, and reject stale concurrent writes. Reflexion now restores temporary state on failures and persists its attempt history.
Add separate OPRO tuning tasks, explicit evaluation-protocol metadata, isolated benchmark sessions, and deterministic demo dependencies without global model patches. Include offline regression tests and Windows/Linux CI.
Validation: 53 offline tests passed on Windows/Python 3.12; critical Ruff checks and git diff checks passed; the standalone offline demo completed with provider/network guards covered by tests.
Evaluation limits are documented: the QA scorer remains a substring smoke test, synthetic demo scores do not measure model quality, and model token cost/latency were not benchmarked. Memory and trajectory writes are separate transactions; background job status remains process-local.